Re: Run 'onunload' on an HDR secondary?


<mpruet@xxxxxxxxxxx> wrote in message
news:1152878622.836318.55940@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The secondary is in recovery mode and the recovery threads will
continue to apply logs from the primary.



I tried running onunload on the secondary, and it ran to completion just
fine. However, I conclude from above that the resulting onunload file may
not be consistent.

I will do the suggested disabling of replication, then do the onunload, then
re-enable replication.

Follow up questions.... Just out of curiosity... Is it actually necessary to
'onmode -c block', etc. on the primary? Would I actually risk inconsistency
by not forcing a checkpoint? Also, could I avoid touching the primary and
just 'onmode' the secondary back to standard? (I'm thinking it would then
just be like when you initially start HDR, before you get the secondary
operational, and I could easily 'onmode' it back to secondary. [I got
plenty of log space on the primary.])

Thank you all for comments.

Regards,

DG



.

Relevant Pages

  • Re: HDR questions
    ... command when the onunload is done, you would set the primary back to ... # <optionally wait to make sure that the checkpoint is applied to the ... onmode -d standard # On primary ... It seems like once you break replication after the checkpoint has been ...
    (comp.databases.informix)
  • Re: Run onunload on an HDR secondary?
    ... onunload and then reestablish it after the onunload. ... that no new transactions are being applied to the database. ... onmode -c block # Force checkpoint for consistency. ... Of course you can't use your secondary while you are doing the backup. ...
    (comp.databases.informix)
  • Re: Run onunload on an HDR secondary?
    ... I think you would want to do the onmode -c block and then breack ... But onmode -d standard may make sure the secondary is in a consistent ... I tried running onunload on the secondary, and it ran to completion just ... I will do the suggested disabling of replication, then do the onunload, then ...
    (comp.databases.informix)