# SHIFT

--- Sjoerd Hooft's InFormation Technology ---

### Site Tools

backupoverview
##### Differences

This shows you the differences between two versions of the page.

 — backupoverview [2013/05/04 13:24] (current)sjoerd created 2013/05/04 13:24 sjoerd created 2013/05/04 13:24 sjoerd created Line 1: Line 1: + = Template Backup Data Paths = + 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 [[checksprocedure|(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 clarify that it hasn't been forgotten. + + == Overview == + So what does everything mean? Most of the things speak for them selves except maybe for these: + * Schema + ** backup frequency, the schema used here is [[wp>​Sarbanes–Oxley_Act]],​ which actually means: + *** 1 day a week a full backup + *** 6 days a week an incremental backup + *** 1 day a month a month backup + *** 1 day a year a year backup + *** Week full backup is kept for 7 weeks (reused the 8th week) + *** Month full backup is kept for 11 months (reused the 12th month) + *** Year backup is never reused and kept for always + * Disk: Backup is made first to disk + * Tape: Backup is also made to tape + * Tape Combi: It does not matter if data is mixed with other data on the same tape + + |^ 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: + * Customer data is not mixed with company data + * Really important data paths are also determined in for example a ticketing system (#0000156) + * Oracle live database is left out (/​var/​data/​oracle),​ instead the dump directory (/​var/​backup) is in the backup + * There is no license for the groupwise agent, so the restore of the mail can't be guaranteed + + {{tag>​itmanagement backup}}