Alternative method for performing initial synchronization - assure_mimix - 6.0

Assure MIMIX for AIX Guide
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software for AIX
Version
6.0
ft:locale
en-US
Product name
Assure MIMIX for AIX
ft:title
Assure MIMIX for AIX Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2025-03-12
ft:lastPublication
2025-03-12T05:07:12.494000

To optimize the time to transfer the PVS data onto a remote recovery server at a remote site:

Note: You can also use the -L option with the scconfig command for specific logical volumes to mark the state map zero percent dirty.

  1. On the production server:

    • Stop any application(s)

    • Stop Assure MIMIX for AIX and unload the drivers:

    rtstop -FC < Context ID >

  2. On the recovery server

    • Stop any application(s) that are using a snapshot

    • Unmount the file systems on a snapshot

    rtumnt -C < Context ID >

    • Release any snapshots

    scrt_ra -WC < Context ID >

    • Stop Assure MIMIX for AIX and unload the drivers.

    rtstop -FC < Context ID >

  3. Save the protected data on the production server to tape or disk. You must save at the LV level in block sequence.

    • Save to tape:

    dd if=/dev/db2 of=/dev/rmt0 bs=1024

    • Save to disk:

    dd if=/dev/db2 of=/dev/db2bu bs=16m

  4. Clean the state map on the production server.

           scconfig -WC <Context ID>

  5. Start Assure MIMIX for AIX on the production server.

           rtstart -C <Context ID>

  6. Restore the data from tape or disk to the Replica on the recovery server.

    Note:    The restore must be done to the pt LVs.

    • Restore data from tape:

    dd of=/dev/ptdb2 if=/dev/rmt0 bs=1024

    • Restore data from disk:

    dd of=/dev/ptdb2 if=/dev/db2bu bs=16m

  7. Start Assure MIMIX for AIX on the recovery server. The changes made after the save to tape or disk synchronize to the recovery server.

       rtstart -C <Context ID>