• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 28 subscribers
  • Views 13067 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

Moving everything to a new server.

eramos
over 7 years ago

We have a core with some machines that are being replicated.

The machines and the repository will go to a new server.

I've been looking around and found a few guides on moving the repository.

What I have in mind is installing a 2012 server that has more hardware resources that the one I currently have, but using the same repository.

I know I'll have downtime, I'm ok with whatever time it takes to move everything.

Just looking for suggestions on the recommended steps.

Thank you very much for your time.

Parents
  • 0 over 7 years ago
    Are you migrating the 'source' core (the core that is sending the replications)? Or are you migrating the target core (the one that is accepting the incoming replications)?

    As far as the migration, it sounds as though you are keeping the repo, and keeping it on the same hardware. Which can be added to a new core by simply exposing the Repo to the new core in the same manner as the previous (aka E:\repo or f:\repo) as before and then from the core go into Repositories and 'Open Existing':

    support.quest.com/.../11

    If the path is different you will have to update that path with the 'fix' option that is presented when you go to run through the Open Existing options. This will present you with the repo and the recovery points, and then when you add the agents/replication back in the existing recovery points will then populate underneath the protected machines as before as they will be tied to the same agent ID.

    The Replication pieces might be different depending on what you are trying to do, so I'll wait for that reply, however that is the best way to move a repo from 1 core to another. Just be sure on the new core to reset your retention and nightly jobs/settings before they run.
Reply
  • 0 over 7 years ago
    Are you migrating the 'source' core (the core that is sending the replications)? Or are you migrating the target core (the one that is accepting the incoming replications)?

    As far as the migration, it sounds as though you are keeping the repo, and keeping it on the same hardware. Which can be added to a new core by simply exposing the Repo to the new core in the same manner as the previous (aka E:\repo or f:\repo) as before and then from the core go into Repositories and 'Open Existing':

    support.quest.com/.../11

    If the path is different you will have to update that path with the 'fix' option that is presented when you go to run through the Open Existing options. This will present you with the repo and the recovery points, and then when you add the agents/replication back in the existing recovery points will then populate underneath the protected machines as before as they will be tied to the same agent ID.

    The Replication pieces might be different depending on what you are trying to do, so I'll wait for that reply, however that is the best way to move a repo from 1 core to another. Just be sure on the new core to reset your retention and nightly jobs/settings before they run.
Children
No Data