This documentation applies to the 8.1 version of Remedy IT Service Management Suite, 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.

Setting up the sandbox environment

To minimize business production interruptions, the sandbox server must be overlaid with the production server image and the production database must be restored on the sandbox. Note the time when the production database backup is taken.

This topic addresses the following tasks:

To set up the sandbox environment

  1. Identify the versions of the products currently installed in production, using the following table to record version and patch numbers.


    Version and product information can be found in the SHARE:Application_Properties form.



    Patch level

    BMC Remedy AR System and associated components

    BMC Atrium (CMDB)

    BMC Remedy ITSM

    BMC Service Request Management

    BMC Service Level Management (SLM)

  2. Ensure you have copies of all versions listed in step 1.
  3. Install the required applications in the sandbox environment.


    This may require multiple downloads per product (for example, patches). Refer to the application installation guides for information on application integrations and apply the integrations as required.

    1. Install all BMC Remedy AR System platform-related components (for example, the BMC Remedy Assignment Engine is required) that match the versions identified in step 1. If you are using different locales, select your target locales to install applicable language packs.


      Use the same BMC Remedy AR System instance name, AR database Administrator name (often ARAdmin) and password, and tablespace names (including temporary space).

    2. Install all BMC Atrium CMDB components that are required.
    3. Set the environment variables BMC_AR_LOADAPP_SKIP and BMC_LOADAPP_SKIP to TRUE. This will enable the application installers to perform only the OS level installation without loading the application into the database.


      Conducting English only installations is sufficient for BMC Remedy ITSM, BMC Service Request Management, and BMC SLM.

    4. Install all applicable BMC Remedy ITSM components and the required version patch.
    5. Install BMC Service Request Management if applicable. For BMC Service Request Management 2.2. versions, you do not have to install the subsequent patches. Installing the base version is sufficient.
    6. Install BMC SLM, if applicable, and the required version patch.
    7. Remove the BMC_AR_LOADAPP_SKIP=TRUE and BMC_LOADAPP_SKIP=TRUE environment variables.
    8. Backup the sandbox installation.

To back up the production database

Working with the DBA team, obtain a full backup of the production BMC Remedy AR System database.

To restore the production database backup on the sandbox server

  1. Shutdown BMC Remedy AR System server on the sandbox server.
  2. Restore the database onto the sandbox server.


    If you are running SQL Server, run the following command in your database:
    Execute sp_changedbowner "ARAdmin"
    Substitute ARAdmin with the appropriate BMC Remedy database Administrator account.

  3. Relicense the BMC Remedy AR System server to match the new host.
  4. Restart the BMC Remedy AR System server on the sandbox, and verify that the system is functional.


    Maintain a copy of the production database backup.

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.