This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

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

Duplicating the production server database for the upgrade

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:

Before you restore the production server database to the staging server, disable the following settings:

  • Distributed Server Option (DSO) on all application servers.

  • Escalations on all application servers.

  • Database triggers within the BMC Remedy AR System schema. Work with your database administrator to disable the triggers.

  • BMC Atrium CMDB, the Reconciliation Engine, and Service Level Management collectors in the armonitor.cfg file on the destination server.

    Disable the following daemons by placing a leading # (hash) on each line: 

    After BMC Remedy AR System server is upgradedAfter BMC Atrium Core is upgraded
    • arsvcdsp
    • emaild
    • apsvcae
    • arcmdbd
    • arrecond
    • normeng
    • slmbrsvc
    • slmcollsvc

To duplicate the production database backup on the accelerated staging server

  1. Work with the database administrator responsible for your 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 (DDM) step to determine which data needs to migrate to the staging server at the end of the upgrade process.

  2. Work with the database administrator responsible for your production environment to restore the database onto the staging server database.
  3. Clean up the servgrp_board table. 
  4. If you are running the SQL server, run the following command on your database:
    sp_changedbowner "ARAdmin"

    Replace ARAdmin with the appropriate BMC Remedy AR System database administrator account.

To duplicate the production database backup on the duplicated staging server

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

    Replace ARAdmin with the appropriate BMC Remedy AR System 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  in BMC Remedy AR System documentation.
  5. Restart the AR System server and verify that the system is functional.
  6. Work with the database administrator responsible for your production environment to back up the staging server database.
  7. Run the BMC Remedy AR System database consistency checker.
    For more information, see  Running the database consistency checker  in BMC Remedy AR System documentation.
  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 Collecting logs, diagnostics and performing system health check using the 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.
    2. 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 environments, import the database (in the staging environment) with a new name so that it does not conflict with the production environement. During the upgrade, you must specify the new database name (the staging environment). 

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