How to migrate Recovery Manager for Active Directory to another server (4309010)

How to migrate Recovery Manager for Active Directory to another server

With the changes made to Windows Server 2016 it is required to install Recovery Manager for Active Directory on the same OS level as the highest domain controller OS version.

1. Go to the properties of each collection and note the backup schedule
2. Check the properties of each collection to verify where the backups are being stored. Create the same backups path on the new server and copy all backups so that they have the exact same path structure on the new server. 
3. For version 9.0 and later, create the folder structure "C:\ProgramData\Quest\Recovery Manager for Active Directory" on the new server. Copy the files backups.mdb and ERdiskAD.mdb from the old server in this path to the new server in the same location. *Note* If the old server had an older version of Recovery Manager for AD, check the Release Notes for the new version to ensure that the upgrade is compatible. Even though the upgrade is not being performed on the same server, the configuration in the .mdb files is still being upgraded and needs to be from a supported upgrade path.
4. For version 10.2 and later, create the folder structure "C:\ProgramData\Quest\Recovery Manager for Active Directory" on the new server. Copy the files backups.mdb and Rmad.db3 from the old server in this path to the new server in the same location. *Note* If the old server had an older version of Recovery Manager for AD, check the Release Notes for the new version to ensure that the upgrade is compatible. Even though the upgrade is not being performed on the same server, the configuration in the .mdb files is still being upgraded and needs to be from a supported upgrade path.
5. Install the latest version of Recovery Manager for Active Directory on the new server. The installation will find the existing .mdb files and upgrade them. A new SQL database can be installed for the Reporting feature as the SQL database is only used for temp storage during the Online Restore Wizard
6. Recreate the backup schedule on the properties of each collection. Please note that if the old server is still up and running, the schedules for both servers should not be run at the same time. Ideally, the schedules should be disabled on the old server until the old server has been decommissioned. 
7. If Forest Edition was installed on the old server copy the Forest Recovery files to the new server. These files can be saved anywhere and have the file extension .frproj

IMPORTANT NOTE:
In 10.3.1 onwards
- All credentials will need to be re-entered into all the collections.
- if we had any scripts configured on the original server, you would need to upgrade to 10.3.1 HF3 or later. Due to an updated encryption algorithm, the scripts cannot be read and accessing them will give an exception. In HF3 there will be a GUI fix where you would be able to re-enter scripts without meeting exception.

523958: RMAD Console "The server threw an exception" when accessing computer collection settings Advanced Run Scripts after moving database to a new host

Please note that when migrating RMAD to another server, the "backups.mdb" only has the backup files registration data, and the "Rmad.db3" has the computer collection and console configurations data except for credentials for security reasons. Therefore, In case you had previously configured credentials in the 'scheduled backup' and 'Agent' tabs in your Computer Collections, as this is not automatically migrated into the new server, it is an expected behavior, you will need to re-enter these credentials in each of your Computer Collections manually. In addition, credentials configuration is tied to the Windows Task Scheduler in the server where RMAD is installed. Also ensure the tasks currently in the Windows Task Scheduler in the old server are disabled or removed. Otherwise, you will experience issues with backup jobs triggering from 2 servers simultaneously causing a conflict.