dbdataplus
Member
- Joined
- Nov 14, 2013
- Messages
- 43
- Reaction score
- 5
Before I restore a full backup to another system I want to be able to "scrub" the target system. In other words, like most backup utilities, TAR is an additive process - if directory "x" already exists it adds/replaces files on tape(flashdrive/folder) to folder "x" but it leaves what is already there, so if the target system had previously been configured there can be flotsam and jetsam in the result.
The first most obvious would be any sound files /var/lib/asterisk/sounds/custom
and then I thought about voicemails /var/spool/asterisk/voicemail
But then I remembered the OSS endpoint manager: A template modified is stored in some sort of data base but and original file is retained as a text file. Which led me to extensions themselves and then possibly a lot of other considerations
So what I was wondering is if anyone had developed a comprehensive list of files and/or directories on the target system that should be removed so that a restore of a full backup creates a duplicate of the original?
The first most obvious would be any sound files /var/lib/asterisk/sounds/custom
and then I thought about voicemails /var/spool/asterisk/voicemail
But then I remembered the OSS endpoint manager: A template modified is stored in some sort of data base but and original file is retained as a text file. Which led me to extensions themselves and then possibly a lot of other considerations
So what I was wondering is if anyone had developed a comprehensive list of files and/or directories on the target system that should be removed so that a restore of a full backup creates a duplicate of the original?