How to use Snapshot Jobs for Change Tracking
This topic was created by a BMC Contributor and has not been approved. More information.
A Snapshot Job creates a Snapshot. The Snapshot is buried down within the results of a Snapshot Job, so you'll have to expand the Job Run to see the actual Snapshot. For every target of a Snapshot Job, you should see a corresponding Snapshot within the Job Run.
This page assumes that you have the following:
- A Component Template built with the objects that you wish to track
- Components created for the servers that you wish to track
When your Snapshot Job Completes, view the results and browse the Snapshot(s) that were created. In the example below, the Checksum column is populated because we chose to capture this information in the Snapshot/Audit settings within the Component Template.
If you click on the Change Tracking window, there is no information because this is the first time we have run the Snapshot Job. Subsequent runs of the Job will show us if there are any differences between previous Snapshots.
Subsequent Snapshots - Change Tracking
In the example below, I have gone into the JPetStore directory on my BL-OPMAN server and manually made some changes after the first Snapshot was taken — possibly similar to some changes that might have brought down the application. Using BMC Server Automation, we can see exactly what happened.
- After making some changes to the objects included in your Snapshot, re-execute your Snapshot Job.
- When the Job completes, expand the results and review the Change Tracking Tab information. There you will see a total number of changes, added objects, modified objects, and deleted objects.
- If you expand the Change Tracking results further, you can see exactly what changes took place. At this point you can choose to either remediate these changes, or continue to refine your Component Template.