Run 'onunload' on an HDR secondary?

IDS 10.00.FC1
Solaris 10

Suppose I am running HDR.

Now suppose I run 'onunload -t <filename> <database name>' on the secondary.
'onunload' uses a shared lock on the database, I believe. So, what happens
to the incoming transaction logs (from the primary) that need to be applied
to the secondary? Do they just accumulate on the secondary until the
onunload lock goes away? Then when onunload is finished, are they applied,
and HDR just continues merrily on, as before?

If onunload runs to completion successfully on the secondary, does that mean
I got a consistent, point-in-time backup of the database in the onunload
file?

Thank you.

DG


.

Relevant Pages

  • 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?
    ... Suppose I am running HDR. ... 'onunload' uses a shared lock on the database, ... point-in-time backup of the database in the onunload ...
    (comp.databases.informix)
  • RE: onunload limit
    ... There is 2 GB file size limit for onunload in IDS 7.31. ... system is large enabled file system. ... Cd into a temp filesystem where you will be unloading the database ( ... Create the dummy raw device: mknod dbname p ...
    (comp.databases.informix)
  • Methods for Reducing Extents
    ... file to increase initial/next extents) ... dbexport the entire database ... onload the database or table ... The onunload method seems to work. ...
    (comp.databases.informix)
  • Re: Methods for Reducing Extents
    ... file to increase initial/next extents) ... dbexport the entire database ... onload the database or table ... The onunload method seems to work. ...
    (comp.databases.informix)