• State Not Answered
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 2262 views
  • Users 0 members are here
Options
Related

RMAD Migration

anavarro
over 1 year ago

I need to migrate the RMAD from one server to another one, from windows 2016 to windows 2022 and installing the new RMAD version, can someone has any documentation or any link to share

thanks.

Parents
  • 0 over 1 year ago in reply to tony massa

    Hi thanks for the answer, I cannot see the link, it says permissions required, exist a way to see it? we have the version 10.0 and i need to see the info to know the steps to migrate to a new server, we will have the new license the next week. even i created an account with my work mail thinking that i can see the info, but no luck.

    thanks in advance.

  • 0 over 1 year ago in reply to anavarro

    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\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
    Please note: If you have an Recovery Manager for AD version prior to 9.0, any folder/registry paths referenced may contain the non-Quest branded path instead of ‘Quest'

    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
Reply
  • 0 over 1 year ago in reply to anavarro

    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\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
    Please note: If you have an Recovery Manager for AD version prior to 9.0, any folder/registry paths referenced may contain the non-Quest branded path instead of ‘Quest'

    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
Children
No Data