This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Duplicating the production server database for upgrades with overlays

The following topics provide instructions for copying the backup of the current production server database schema and data to the new staging server and duplicating it on the staging server:

To duplicate the production database backup on the accelerated staging server

  1. Work with your database administrator responsible for the production environment to create a full backup of the current production BMC Remedy AR System database.

    Note

    Record the date and time of the backup. You will need this information in the delta data migration step to determine which data needs to be migrated to the staging server at the end of the upgrade process.

  2. Work with the database administrator responsible for the production environment to restore the database onto the staging server database.
  3. If you are running SQL Server, run the following command in your database:
    sp_changedbowner "ARAdmin"

    Substitute ARAdmin with the appropriate BMC Remedy AR Database Administrator Account.

To duplicate the production database backup on the duplicated staging server

  1. On the staging server, shut down AR System server.
  2. Work with the database administrator responsible for the production environment to restore the database onto the staging server database.
  3. If you are running SQL Server, run the following command in your database:
    sp_changedbowner "ARAdmin"

    Substitute ARAdmin with the appropriate BMC Remedy AR Database Administrator Account

  4. Change the AR System server name to match the new host. For more information, see Changing a server name when using a duplicated or migrated environment.
  5. Restart the BMC Remedy AR System server and verify that the system is functional.
  6. Work with the database administrator responsible for the production environment to back up the staging server database.
  7. Run the AR System database consistency checker. For more information, see Running the database consistency checker.
  8. Run the health check in the BMC Atrium Core maintenance tool to verify that your system is running correctly before the upgrade. For more information, see Getting started with BMC Atrium Core Maintenance Tool.

    Note

    The CMDB health check was introduced in version 7.5. If your staging server runs an earlier version, you can skip this step. 

     

    1. Launch the BMC Atrium Core Maintenance Tool:
      • On Microsoft Windows, go to the <AtriumCoreInstallDir>\atriumcore folder, and double-click theAtriumCoreMaintenanceTool.cmd file.
      • On UNIX, go to the <AtriumCoreInstallDir>/atriumcore/ directory, and launch the AtriumCoreMaintenanceTool.sh file.
    1. Click the Health Check tab, and follow the instructions there.

If you are sharing the database

If you are using one large database server that is shared by production and staging, import the database (staging) with a new name so that it does not conflict with the production. During upgrade you must specify the new database name (staging). 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments