• State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 29 subscribers
  • Views 9367 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

How would I set up a new replication only site with existing data (Recovery points)?

chris.rodgers
over 6 years ago

We have 2 Rapid Recovery servers. They both act as a target and a core. Cross replication.

1 is local and 1 is in an off-site data center. We are trying to move out of the off-site data center, to another off site location. We can't just shut everything down and move it. We want to create a third core server (target only) in the new location which will only be used for replication only. Then, in time we will consolidate both current locations to a single location locally.

We want to set up the new Replication (Target) server, create a replication seed drive from the 2 existing servers (on an external drive) then ship to to the location where the third site will exist, then load all the recovery points to it.

If something happens, in transit to that external drive, we want to make sure the data is unuseable.

What would be the best way to do this?

Parents
  • 0 over 6 years ago
    Greetings. What you are explaining is possible. You can replicate the source to more than 1 location, and/or daisy chain them from one to another depending upon your need. The part that I am not sure of however is this line:

    If something happens, in transit to that external drive, we want to make sure the data is unuseable.

    The seed drive is just a copy, so the source original is still on your source cores (or your target) so as long as you don't seed and then promptly delete data from the core you created the seed from, the data will still be on that core. Therefore if the seed drive itself is lost and/or corrupted you still have the original, just don't do an RP removal until you import the data and validate that it is secure. Does that makes sense? Is that what you're looking for?

    If I missed the point and/or a variable by all means let me know.
Reply
  • 0 over 6 years ago
    Greetings. What you are explaining is possible. You can replicate the source to more than 1 location, and/or daisy chain them from one to another depending upon your need. The part that I am not sure of however is this line:

    If something happens, in transit to that external drive, we want to make sure the data is unuseable.

    The seed drive is just a copy, so the source original is still on your source cores (or your target) so as long as you don't seed and then promptly delete data from the core you created the seed from, the data will still be on that core. Therefore if the seed drive itself is lost and/or corrupted you still have the original, just don't do an RP removal until you import the data and validate that it is secure. Does that makes sense? Is that what you're looking for?

    If I missed the point and/or a variable by all means let me know.
Children
No Data