There's a request for "Change runbook" that documents/records changes from Day 1
so that in the event of bad changes (malicious or inadvertent ones) being introduced
over along the line of changes, we can rebuild a server/system back selectively,
dropping the "bad" change so that we can bring up the system to a "clean" slate.
Was told it's not "Change Control" nor CRs that we are looking at here.
I've suggested that a 'bare metal' backup be done with incremental backups (think
EMC has one such product) but this is not what the team requires.
Any document, tools or method are much appreciated.
Above URL looks like what my colleague referred to.
I think taking a full bare metal backup with a combination
of differential plus incremental backups will enable us to
skip certain change/state that is bad/corrupt in the rebuild