How to move RMAD (RMADFE) 8.5.1 or later to another server (4290790)

This solution outlines how to move Recovery Manager for AD (Forest Edition) from one server to another.

*NOTE* If you have a Recovery Manager for AD version prior to 9.0, any folder/registry paths referenced may contain a non-Quest branded path.

*NOTE* As of 10.2 version for Recovery Manager for AD, the ERDiskAD.mdb is replaced by Rmad.db3 in the "C:\ProgramData\Quest\Recovery Manager for Active Directory\"

1. Make a backup of the below two files:
   C:\ProgramData\Quest\Recovery Manager for Active Directory\Backups.mdb
   C:\ProgramData\Quest\Recovery Manager for Active Directory\ERDiskAD.mdb
2. If you have the RMAD Portal installed, make note of the local group membership for the Portal groups
3. If you have the RMAD Portal instlaled, stop the Quest Recovery Manager Portal service and Application Pool in IIS
4. If you have the RMAD Portal installed, backup the three Portal SQL databases (if they are being moved): RecoveryManagerPortal, DelegationStore and AuditingStore
5. Take note of your current backup schedule (right click on your computer collection within Recovery Manager for Active Directory and go to properties, then go to the schedule tab)
6. Create "C:\ProgramData\Quest\Recovery Manager for Active Directory" on the new server
7. Copy Backups.mdb and ERDiskAD.mdb on the old server to the above location on the new server (Create a separate copy of these files elsewhere as a backup just in case)
8. Copy the backups from your old server to the new server (must be same exact path on new server, unless they are stored on a UNC network path then they can be left alone)
9. Install RMAD on the new server (this will find the existing mdb configuration files and upgrade them)
10. Recreate the schedules (if they exist in the collection settings, rekey the credentials)
11. Expand the Backups node at the bottom, and click on Active Directory and ensure that the backups are pointing to the right location
12. If preinstalled backup agents are being used, make sure to upgrade them as well through the backup agent management node or upgrading them manually on the DC's
13. If you had the RMAD portal Installed on the old server, install the RMAD Portal on the new server
14. Stop Quest Recovery Manager Portal service and Application Pool for our IIS Application
15. Restore the three Portal SQL databases (if databases were moved) from step 5
16. If the Portal databases were moved, ensure they are attached and online in SQL Server Management Studio
17. Transfer group membership to the new local Portal groups on the new server
18. Start Quest Recovery Manager Portal service and Application Pool in IIS
19. If the Portal databases were moved, run the attached powershell script. The script will prompt for the hostname of the SQL server (enter the new server) and the Authentication type (default is Windows)

Please note the following if you are using Forest Edition:

• Copy the Forest Recovery Project files (.frproj) to the new server
• If you are using version 8.8 or 8.8.1 and moving to 9.X on the new server then the certificates will be incompatible between the non-Quest branded and the new Quest branded releases, for this reason the agents must be pushed again from the new 9.x server. If this scenario applies to you, please follow the below steps in addition to the above:
  • Prior to the move, launch Forest Recovery Console on the old server 
  • Uninstall all forest recovery agents from the Domain Controllers
  • After the server move is complete open the Forest Recovery Console on the new server and push the Forest Recovery Agents to the new DC's