• State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 29 subscribers
  • Views 9366 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
    With a simple change to the XML file in the seed drive you can convert it to an archive so it can be imported on any core. The only way to ensure the data in that seed drive is secure and not able to be used is to encrypt the recovery points related to your agents. To do that you have to enable encryption on each agent. When you do that you'll get a new base image for each machine. If you already have encryption enabled, then you don't have anything to worry about. The data is encrypted and the person importing the seed would have to have your encryption key pass phrase in order to access the data.

    If you don't have encryption enabled and you want that level of security, you could look at using a full disk encryption software to manage the seed drive and encrypt all data being written to it. However, we have not tested this in any way and can't speak to what the performance of that process would be nor whether there may be any hiccups with the import if the performance of the decryption process is slow.

    Your best bet by far is to have your recovery points encrypted in the repository so they are secure.
Reply
  • 0 over 6 years ago
    With a simple change to the XML file in the seed drive you can convert it to an archive so it can be imported on any core. The only way to ensure the data in that seed drive is secure and not able to be used is to encrypt the recovery points related to your agents. To do that you have to enable encryption on each agent. When you do that you'll get a new base image for each machine. If you already have encryption enabled, then you don't have anything to worry about. The data is encrypted and the person importing the seed would have to have your encryption key pass phrase in order to access the data.

    If you don't have encryption enabled and you want that level of security, you could look at using a full disk encryption software to manage the seed drive and encrypt all data being written to it. However, we have not tested this in any way and can't speak to what the performance of that process would be nor whether there may be any hiccups with the import if the performance of the decryption process is slow.

    Your best bet by far is to have your recovery points encrypted in the repository so they are secure.
Children
No Data