How to migrate RMAD SQL Databases to another server? (4225698)

How to migrate RMAD SQL Databases to another server?

How to migrate the RMAD SQL Databases to another server?

WORKAROUND #1 to move the Comparison Reports database (RecoveryManager-Reporting-RMADServerName) and ForestRecovery-Persistence database (if using RMADFE and have the feature enabled), RecoveryMgrHybridRestore database (if enabled) :

1. Run Add/Remove programs on the RMAD Server (Programs and Features in Windows 2008 and later)
2. Select Recovery Manager for AD
3. Click Change
4. Click Next
5. Click Change
6. Highlight the Reports component, click the down arrow and select Entire feature will be unavailable
7. Highlight the Forest Recovery Persistence component, click the down arrow and select Entire feature will be unavailable
8. Highlight the Recovery Manager Hybrid Restore component, click the down arrow and select Entire feature will be unavailable
9. Click Next and allow the wizard to complete
10. Select Recovery Manager for AD in Add/Remove Programs (Programs and Features in Windows 2008 and later)
11. Click Change
12. Click Next
13. Click Change
14. Highlight the Reports component, click the down arrow and select Entire feature will be installed on local hard drive
15. Highlight the Forest Recovery Persistence component, click the down arrow and select Entire feature will be installed on local hard drive
16. Highlight the Recovery Manager Hybrid Restore component, click the down arrow and select Entire feature will be installed on local hard drive
17. Click Next and allow the wizard to complete. It should prompt for all SQL settings again and new settings can be specified.

NOTE: If you receive the error below when adding components in steps 14-16 to a remote SQL Server, follow the additional steps below:



Rather than running the setup via Windows Explorer, run the following command line install from an administrative command prompt ensuring UAC is temporarily turned off:

Msiexec /i "C:\RMADUpgrade\RMADFE_x64.MSI" /l*!+v C:\RMADUpgrade\Manual.Install.log

The command above should execute the installer with super-verbose logging enabled. Please also remember to amend the path to the MSI file accordingly for your own environment.

Prior to re-running the setup, also ensure that the target SQL Server does not already contain the databases required which may have been left behind from a failed installation. The database names are "ForestRecovery-Persistence", RecoveryManager-Reporting-COMPUTERNAME", "RecoveryMgrHybridRestore".

WORKAROUND #2 (can be used if the account does not have rights to create a new database):

1. Close the RMAD console
2. Copy the RMAD DB to the new server
3. Modify the following registry keys to the new values:
   For versions 8.5.2 and earlier:
   
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Recovery Manager for Active Directory\DBReporting\ConnectionString
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Recovery Manager for Active Directory\DBReporting\DB
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Recovery Manager for Active Directory\DBReporting\Server
   - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest Software\Quest Recovery Manager for Active Directory\DBReporting\ConnectionString
    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest Software\Quest Recovery Manager for Active Directory\DBReporting\DB
    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest Software\Quest Recovery Manager for Active
   Directory\DBReporting\Server
   
   For versions 8.6 and later:
    
    
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest\Recovery Manager for Active Directory\DBReporting\ConnectionString
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest\Recovery Manager for Active Directory\DBReporting\DB
    - HKEY_LOCAL_MACHINE\SOFTWARE\Quest\Recovery Manager for Active Directory\DBReporting\Server
   - HKEY_LOCAL_MACHINE\SOFTWARE\Quest\Recovery Hybrid Restore\Setup
    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest\Recovery Manager for Active Directory\DBReporting\ConnectionString
    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest\Recovery Manager for Active Directory\DBReporting\DB
    - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Quest\Recovery Manager for Active Directory\DBReporting\Server

Try to generate a report during online restore. If you receive "login failed" error then please check to make sure your user has db_owner access to the database.

Please note, the ForestRecovery-Persistence database cannot be moved using Workaround 2. The Persistence database has to be recreated as per Workaround 1.

If you have the RMAD Portal installed, use the following steps to move the Portal databases:

1. Stop the Quest Recovery Manager Portal service on the server where the Portal is installed
2. Stop the RecoveryManagerPortal Application Pool in IIS
3. Create a backup of the following databases:
   - AuditingStore (may not exist)
   - DelegateStore
   - RecoveryMgrPortal
4. Restore the databases to the new SQL server
5. Ensure the new databases are attached and online
6. On the server where the Portal is installed, run the powershell script attached to this KB. The script will prompt for the hostname of the SQL server (enter the new server) and the Authentication type (default is Windows)
7. Start the Application Pool
8. Start the Portal service

RMADPortalSQLScript

The SQL database used by Recovery Manager is used as temporary storage for comparison reports. It is not critical to the operation of the product and does not contain configuration of the product, and therefore can be uninstalled and reinstalled to a different SQL server without issue. This process is the same when moving from a stand alone SQL Server install (or SQL Express) to a SQL Cluster.