Backing up server-specific data

Some forms contain data that cannot be transformed or purged (for example, forms that contain information relating to the network infrastructure, passwords, or licensing). In this case, back up the data from the target system and then restore it after the database has been restored from the system being synchronized.

BMC Helix Data Manager considerations

BMC Helix Data Manager is not permitted to connect directly to the Production or QA database. Therefore, to create a backup of the necessary data from the Production or QA database, move a copy of the Production and QA database into the Onboarding database server.

Ideally, for an onboarding project, this is completed prior to the loading of data into these environments. The database sizes are small, and the Production and QA databases can be restored alongside the Onboarding database, and the relevant data extracted.

To facilitate the copy of the Production and QA database to the Onboarding system, engage BMC SaaS Operations according to the standard process.

Forms to back up and restore

The following forms contain server-specific information to back up:

AR System Configuration Component
AR System Configuration Component-Setting Mapping
AR System Email Mailbox Configuration
AR System Licenses
AR System Server Group Operation Ranking
AR System Service Failover Ranking
AR System Service Failover Whiteboard
SB:LocalApprovalConfiguration *
SB:RemoteApprovalConfiguration *
SmartReportingServer_Info
UDM:RAppPassword

* This form is not in the default data dictionary and may need to be added separately at the customer site.

Important

For BMC Helix ITSM migrations, system accounts are created in the CTM:People form to support integrations. A node has been added for CTM:People and its related User record to back up only these records. In systems outside of BMC Helix ITSM no data is exported.

Backing up the data

To facilitate the backup and restoration of core data, you can use a migration pack. The migration pack contains the forms mentioned above.

Since the synchronization pack is intended to take data and re-import it to the same location, the source and target dictionaries are the same.

The migration of the data follows the standard migration process.

To back up the data

Select Data Migration > Migrate Data.
Select the target system as both the "From" and "To" systems, and select the Synchronization Backup pack.
Click Next.
Because all data will be taken for these forms, there are no parameters to consider.
Click Next again and review the migration summary.
Ensure that the name of the job is updated. Since the forms contain very little data, you do not need to increase the number of threads.
Click Confirm Migration.
The Export Job appears so that you can verify all the settings.
Click Start Export to export the data.
The exported data is stored in the BMC Helix Data Manager file system.