Migration of the Core to the new server is a multi-step process, which requires several preparation steps:
- where's the current repository is located? Is it locally attached (DAS), network-attached (SAN or NAS)?
- is repository having multiple extensions?
- is the new Core machine having enough space for the repository, if repository is going to be copied over (for DAS)?
- if repository is networked, can the new Core communicate with it
- are encryption keys used for backups?
- is current Core having replication links?
- are there Virtual Standbys or any other schedules jobs like scheduled archival?
- any custom protection schedules for the agents?
The process of migration consist of these steps:
1. Save all configuration data, list of protected agents, export encryption keys. Delete replication links.
2. Shut down the original Core service
3. Set up and license a new Core server. Save LIC file from rapidrecovery.licenseportal.com and apply it to the new Core.
4a. For DAS repository, copy all repository extension folders to the new Core
4b. For network-attached storage, make sure that new Core can access NAS Share or map the iSCSI target
5. Import encryption keys
6. From the new Core, click on More, Repositories, Open existing DVM repository and point to the copied/networked repository. Fix paths if needed.
7. After the repository went through the maintaining process, re-protect all agents, setting the protection schedules accordingly
8. Re-create replication links, virtual standby, scheduled archives (if applicable)