This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Common scenarios

This topic describes the most common scenarios for using Drift Management.

  • Comparison of the current state of BMC Atrium CMDB with a snapshot
    You want to determine whether drift has occurred over a period of time. You make a snapshot of BMC Atrium CMDB at a given point in time (this becomes your baseline) and later (a day, a week, or a month, for example) compare the current state (your target) with the baseline.
    For more information about using Drift Management for this scenario, see Getting Started. The Getting Started helps you to become familiar with the Drift Management workflow when creating a comparison job.
  • Comparison with a standard (for compliance)
    You compare the state of BMC Atrium CMDB with a baseline to ensure that the physical state is not drifting from the declared standard.
    This scenario is commonly called the golden server or golden CI. Within BMC Atrium CMDB, you have the CIs for a crucial business service (for example, security) configured exactly as needed. The golden CIs are the baseline with which the other security servers (targets) are compared to verify that they are configured to match the declared standard (the baseline).
    A golden CI is configured exactly as needed and is used as a basis of comparison with your target CIs.
  • Comparison between a test dataset and BMC Atrium CMDB
    You want to define a test or sandbox dataset on top of another dataset to determine the impact of potential modifications in the test dataset on BMC Atrium CMDB. In this scenario, BMC Atrium CMDB is the baseline and the test dataset is the target. The comparison uses the BMC Atrium CMDB API to view the equivalent of a merge between the two datasets.
Was this page helpful? Yes No Submitting... Thank you