I believe communication to board and users is the way to deal with forgotten agreements, deals etc. Communication about backup is a very important part of the backup procedures, and since you should document what you backup, and keep that up to date (see here) why not document it on your intranet or wiki and let people check that once in a while. The template below is what I used to communicate what is in the backup and what is not. Meaning, if there is a server which is not in the backup, it still should be in the list to clearify that it hasn't been forgotten.
| Team / Service | Contact person | Nodes | Datapaths | Filters | Schema | Disk | Tape | Tape combi | Remarks |
|---|---|---|---|---|---|---|---|---|---|
| Development | Dilbert | javabox | /etc /home /data | Sarbanes Oxley | Yes | Yes | Yes | Sourcecode | |
| subversion | /srv/svn/backup | Sarbanes Oxley | Yes | Yes | No | Sourcecode | |||
| oraclebox | /etc /home /var/backup /var/data /var/log | /var/data/oracle | Sarbanes Oxley | Yes | Yes | No | Data paths as determined in ticket #0000156 | ||
| Team / Service | Contact person | Nodes | Datapaths | Filters | Schema | Disk | Tape | Tape combi | Remarks |
| Customer Service | Stef | customerbox | C:\Documents and Settings D:\Data | Sarbanes Oxley | Yes | Yes | No | ||
| customerbox02 | D:\Data | Sarbanes Oxley | Yes | Yes | No | ||||
| Team / Service | Contact person | Nodes | Datapaths | Filters | Schema | Disk | Tape | Tape combi | Remarks |
| IT | Pointy Haired Boss | sequelbox | C:\Documents and Settings Databases: CxFm01 BES-appreg BES-management BES-mdss BES-mdss-appreg master model VMMonitor | Sarbanes Oxley | Ja | Ja | Ja | Databases are backupped through SQL Agent | |
| mailserver | gw1 | Sarbanes Oxley | Ja | Ja | Ja | Groupwise - should be backed through agent - restore is unsure | |||
| ftpbox | No backup required |
Note:
Discussion