Best practices for avoiding CMDB sync performance issues

This topic provides information on best practices for avoiding CMDB sync performance issues.

Filter before syncing

Most CMDB users, especially at the high-end of the scale spectrum, are extremely conservative about the data that is put into CMDB. Best practice for CMDB is to carefully analyze the needs of the planned data consumers, and import only the bare minimum data to address those needs. BMC Helix Discovery synchronization filters ensure that only the data that you want is synchronized to CMDB.

You should not start to use CMDB sync by synchronizing all data from BMC Helix Discovery into CMDB, and then reduce the synchronized data by subsequently applying filters, as this imposes an unnecessarily heavy load on the CMDB when the data that has already been synced is then deleted.

Resynchronizing is an intensive operation

Occasionally the model stored in the CMDB dataset may become out of step with the BMC Helix Discovery shadow copy and require resynchronization. Resynchronization is an intensive operation that must assess the contents of the CMDB dataset against the authoritative version stored in the BMC Helix Discovery datastore and then update the CMDB dataset to match the contents of the BMC Helix Discovery shadow copy.

Empty a dataset before reusing it

When specifying a new CMDB sync connection, always ensure that you use a new or empty CMDB dataset. When you use an existing dataset that contains data, BMC Helix Discovery must perform a resynchronization rather than a less intensive new sync. To clean the dataset, use the corresponding option in the cmdbdiag.exe utility, or create a Reconciliation job to delete or clean the dataset.

Best practices for avoiding CMDB sync performance issues

Filter before syncing

Resynchronizing is an intensive operation

Empty a dataset before reusing it

On this page