Preparing for event data migration

To migrate event polices and Cell data from TrueSight Operations Management to BMC Helix Operations Management, you must first obtain the Cell Knowledge Base (KB) and BMC Helix Operations Management details. You must run the event migration utility for each TrueSight Operations Management Cell KB from where you want to migrate the data. For example, if you you have 3 Cells running the same KB, you can migrate data with the details of only one Cell.

To prepare for the migration, you can also run a simulation for the classes that you want to migrate.

Perform the following steps to prepare for event data migration:

1. Obtain the Cell KB details.
2. Obtain the BMC Helix Operations Management tenant details.
3. Download the event migration utility.
4. Specify the precedence order of the policies and rules that you are migrating.
5. Simulate a migration to check if the migration is without errors.

To obtain the Cell KB details

1. Identify the Remote Cell or TrueSight Infrastructure Management Cell that needs to be migrated.
2. On the Cell host, open the command prompt, and navigate to the Cell KB directory: pw\server\etc\<cellname>

3. Run the following commands:

   mquery -q -d -n <cell_name>-a POLICY -f BAROC -w "enabled: == 1" > policies.baroc (With this command, only enabled policies are exported.)
   
   mquery -q -d -n <cell_name> -a SELECTOR -f BAROC > selectors.baroc
   
   mquery -q -d -n <cell_name> -a TIME_FRAME -f BAROC > timeframes.baroc
   
   mquery -q -d -n <cell_name> -a <table_name> -f BAROC > <table_name>.baroc
4. Copy the pw\server\etc\<cellname> directory to where you will run the utility from.
   This directory is used as the input for the migration utility. For instructions on running the utility, see Installing-and-running-the-event-migration-utility.

To obtain the BMC Helix Operations Management tenant details

For event migration, the following BMC Helix Operations Management details are required:

• Tenant URL, which is the URL that you use to open BMC Helix Operations Management.
• Tenant ID
• Access key and secret access key

Perform the following steps to obtain the tenant ID, access key, and secret access key.

1.  Log in to BMC Helix Portal.
2. Navigate to the User access > Users and keys page.
3. On the Access keys tab, click Add key.

4. Enter a name for the key.

   Important

   The key name provided in this step is only a logical representation that is used for easy identification purposes on the UI. This key name cannot be used to authenticate into the system.

    

5. From the Key type list, select Access key. 
6. Select the number of days for which you want this key to be valid.
   You can also set a custom date or set it to never expire. Although you can set the key to never expire, for enhanced security purposes, we recommend that you set a definite key expiry date. After the key expires, you can extend the date by editing the access key.
7. Click Confirm.

8. From the Key details pane, copy and save the access key and the secret key.
   
   
   

   Can I copy the secret key later?

   No.

   The secret key is available for copying only when it is generated for the first time. After that, it is stored in an encrypted format and you cannot copy it. If you do not copy the secret key when it is generated or if you lose it, you must generate a new one.

9. From the Configuration area, copy and save the tenant ID.
   You will need the tenant ID while running the migration utility.
10. In the Groups area, click Select.
11. Select the Administrators group and click Confirm.
12. (Optional) If you have roles with appropriate permissions, assign roles.
    You can also assign groups and roles later from the Access keys tab by clicking Actions > Key details.

13. Close the Key details pane.
    In the Access keys tab, you can see the access key that you created. For information about the actions that you can take on the access key, see Setting up access keys for programmatic access.

To download the event migration utility

1. On the server where you want to run the migration utility, create the eventmigration directory.
   

   All Cell Knowledge Bases (KBs) that need to be migrated must be present on the server where you run the migration utility.

2. In the eventmigration directory, perform the following steps:

   1. Download migration utility from the BMC Electronic Product Distribution (EPD) website.

   2. Unzip the event migration utility files, which creates the following folder structure is created:

      

3. Update the conf/migration.properties file with tenant details that you obtained from .

   Can I configure the maximum event slots to be migrated?

   Yes. However, note that BMC Helix Operations Management supports a maximum 200 event slots per class. 

   For example, the EVENT class has 45 slots in BMC Helix Operations Management. In this case, only 155 slots (200-45) can be configured for this class.

   To configure the maximum number of event slots to be migrated, in the conf/migration.properties file, change the value of the monitor_event.max_slots_no parameter. The default number is 50.

To specify the precedence order of policies and rules

1. Open the <migration_utility_home_folder>/conf/migration.properties file.
2. Specify the cell start and end indexes as shown below:
   <cell_name>_start_index = <value between 0 and 9999>
   <cell_name>_end_index = <value between 0 and 9999>If multiple cells are present, define the execution order of each Cell separately. The values must be between 0 and 9999 because these values are used in BMC Helix Operations Management to determine the policy precedence.

1. Specify spacing between cells as shown below:
   <cell_name>_spacing = <can be between 2 and 5>

For more information about migrating the precedence order, see the Migrating precedence with event policies or rules section in Key-considerations-for-migrating-event-data-to-BMC-Helix-Operations-Management.

To simulate a migration

You can use the Simulation option in the Event Migration Utility console to perform a trial run for all the event rules, classes, and policies without obtaining the tenant details. Simulating a migration smoothens the path for an error-free event data migration.

We recommend that you run the migration simulation in the following order:

1. Event rules 
2. Event classes
3. Event policies.

If you run a simulation for migrating event rules before event classes, you can understand the classes that are required for the event rules to successfully migrate. 

To simulate event rule migration

1. In the Event Migration Utility console, go to the Rules tab.
2. Click the dotted menu icon and click Simulation.
3. In the Event Rule Simulation dialog box, click Next. 
4. Select the rules that you want to run the simulation for.
   To select all rules on the page or all rules in the system, click the Name column.
5. Click Simulate.
   If the simulation is successful, a success message is displayed.
   If you get an error message, that means that the classes required for the rules are not migrated.
   Migrate these classes before migrating the selected rules when you run the event migration utility.

To simulate event class migration

1. In the Event Migration Utility console, go to the Classes tab.
2. Click the dotted menu icon and click Simulation.
3. In the Event Class Simulation dialog box, click Next. 
4. Select the classes that you want to run the simulation for.
   To select all classes on the page or all classes in the system, click the Name column.
5. Click Simulate.
   If the simulation is successful, a success message is displayed.
   If you get an error message, that means that the classes cannot be migrated to BMC Helix Operations Management.
   Do not select these classes during the migration or change their type before running the migration.

To simulate event policy migration

1. In the Event Migration Utility console, go to the Policies tab.
2. Click the dotted menu icon and click Simulation.
3. In the Event Class Policy dialog box, click Next. 
4. Select the policies that you want to run the simulation for.
   To select all policies on the page or all policies in the system, click the Name column.
5. Click Simulate.
   If the simulation is successful, a success message is displayed.
   If you get an error message, that means that the classes or rules in the policy are not migrated. Fix these errors before running the migration.