Migrating services to a new host
New hardware or new hardware requirements can require that you migrate services from the current host to a new host. As part of the planning process be sure that you consult with your database administrator to coordinate the migration of your database.
Do not migrate to a different version of the product!
You must move between identical versions of TrueSight Middleware and Transaction Monitor (for instance, 8.1.00 > 8.1.00). Moving between different versions of TrueSight Middleware and Transaction Monitor can result in data loss or corruption.
To migrate to a different version you must first upgrade the current version to the newer version, test the upgrade to ensure it works, and then migrate.
Running the TrueSight Middleware and Transaction Monitor Services on separate server machines is not recommended. When migrating services, you must migrate all of them. Contact BMC Support if you require such a configuration.
Before you begin
For a successful migration, you need:
- Test and production environments running the same version of TrueSight Middleware and Transaction Monitor.
- Storage space for a large zip file.
Migrating to a new system
Because no two environments are the same, BMC recommends that you consult with BMC Customer Support to develop a migration plan. Migrating requires an outage during which time the product media, users, and passwords are moved to another server of the same or different platform. BMC no longer recommends that you use mqsexport to take a snapshot of an entire TrueSight Middleware and Transaction Monitor environment.
Comments
Log in or register to comment.