• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 4681 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Resuming replication with large data set

ajns
over 7 years ago

Good morning,

We have a site backing up two servers to a local core which then replicates offsite to another core. There was a power issue and both servers shut down dirty and new full backups were run. These are very large data sets that take several days to complete a base image so replication was paused.

Now of course when we resume replication it is going to want to replicate tb's of data. Initially we used a seed drive to start replication and when this happens we usually break the replication, clean the data up on the target core then start replication all over again with a seed drive.

Is there a way to avoid breaking the replication and starting over? Can we resume replication and use a seed drive or does it even matter? Either way we have to transport and create/consume a seed drive so I'm not sure doing it another way saves any time. What is the recommended way of doing this?

Thanks in advance

James

Parents
  • 0 over 7 years ago
    Hi James,

    If you have the bandwidth to handle a few Gigabytes of replication data post seed/archive import, you can opt for the following workaround and this should save some time.

    1) Pause rollup for those protected machines on the Source and Target Cores
    2) Pause replication for those machines
    3) Create an archive of the protected machine's RPs with a date range that includes the new base images
    4) Import the archive on the target core until it completes
    5) Resume replication until the RPs are in sync
    6) Resume rollups for those protected machines
Reply
  • 0 over 7 years ago
    Hi James,

    If you have the bandwidth to handle a few Gigabytes of replication data post seed/archive import, you can opt for the following workaround and this should save some time.

    1) Pause rollup for those protected machines on the Source and Target Cores
    2) Pause replication for those machines
    3) Create an archive of the protected machine's RPs with a date range that includes the new base images
    4) Import the archive on the target core until it completes
    5) Resume replication until the RPs are in sync
    6) Resume rollups for those protected machines
Children
No Data