Migrating compliance rules and discovery signatures

If you are upgrading from a pre-8.0 version of BMC Server Automation, after you complete the basic migration of database data using the BMC BladeLogic Data Migration Manager, you must run the postmigration file. This file migrates the pre-8.x compliance rules and discovery signatures stored in the core BMC Server Automation database and converts them to the new rule format introduced in BMC Server Automation version 8.0.

Ideally, the upgrade, migration, and postmigration activities should be performed in the following order, so that all the Application Server steps are completed first, and the need for a specific BMC Server Automation Console (RCP client) restart doesn't interfere with the postmigration script:

  1. Upgrade the Application Server on Windows.
  2. Perform the database migration.
  3. Perform the postmigration activities: Migrate the compliance rules and discovery signatures.
  4. Stop the RSCD Agent, then upgrade the BMC Server Automation Console

 Note: It is not advisable to have the BMC Server Automation Console and File Server on the same machine.

To migrate compliance rules and discovery signatures

  1. Navigate to the postmigrationfile found within the BMC Server Automation installation directory:

    (Windows)

    <installDirectory>\NSH\bin\postmigration.exe

    (Linux or UNIX)

    <installDirectory>/NSH/bin/postmigration.sh

  2. Run the postmigration.sh or postmigration.exe file.
    Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration.sh or postmigration.sh file.

Was this page helpful? Yes No Submitting... Thank you

Comments