Backups: Difference between revisions

From DISI
Jump to navigation Jump to search
No edit summary
m (→‎Restore: asdf)
 
(13 intermediate revisions by 2 users not shown)
Line 3: Line 3:
{{TOCright}}
{{TOCright}}
There are at least three ways to make backups:   
There are at least three ways to make backups:   
* a) We give you a 4TB portable drive, you keep it and write to it. Ask for one.
* a) We give you a 5TB portable drive, you keep it and write to it. Please ask for one!
* b) Use CrashPlan/rsync and/or DropBox/Sync/Box.com to create backups in the cloud.
* b) Use CrashPlan/rsync and/or DropBox/Sync/Box.com to create backups in the cloud.
* c) We backup major cluster disks to tape, as follows:
* c) We backup /nfs/home and some other disks, as follows:


== Weekly backups, starting Friday night ==  
== Monthly backups ==  
* Cluster2: /nfs/home/
* Cluster 2: nfs-home:/nfs/home/ ('''/nfs/home''')
== Quarterly backups, starting first day of quarter ==
* Cluster 2: nfs-soft:/nfs/soft ('''/nfs/soft''')
* Cluster 2: /nfs/db
* Cluster 2: wiki
* Cluster 2: /nfs/store
* Cluster 2: selected sysadmin files (alpha, beta, config files)
== Never backed up ==
* Cluster 2: /nfs/work
* Laptops
* Desktops
* No other user files are backed up, ever, unless by special request and agreed by email exchange.


== Tape rotation and length of historical data ==
== Most disks are never backed up ==  
* We have four savepacks (sets of tapes, in a suitcase) that we rotate for /nfs/home.
* We set aside one of these savepacks quarterly, on the first backup of the quarter, as an offsite backup.
* Thus at any time there is a weekly backup made starting Friday night for the last four weeks, and a quarterly backup for the last four quarters.
* We also pull savepacks out of rotation from time to time to provide additional long-term backups.


= Note =
== Implicit backups ==
At time of writing, this policy is only implemented on [[Cluster 2]]. Select backups of [[Cluster 0]] will follow soon.
* we backup ZINC20 and ZINC-22 to AWS and Wynton.
* all software is in github/gitlab and is thus backed up continuously


= Restore =  
= Restore =  
To have files restored from backup, please write to the [[sysadmin]]s, stating file/directory name, the approximate time of when it was created in the form you want restored and when that copy was deleted or damaged.
To have files restored from backup, please write to the [[sysadmin]]s, stating file/directory name, the approximate time of when it was created in the form you want restored and when that copy was deleted or damaged.  Better: use your own USB drive.


= See Also =  
= See Also =  
Line 34: Line 26:


Return to [[:Category:Sysadmin | system administrator's guide]].
Return to [[:Category:Sysadmin | system administrator's guide]].
[[Category:Sysadmin]]
[[Category:Sysadmin]]
[[Category:Internal]]
[[Category:Internal]]
[[Category:Policy]]
[[Category:Policy]]

Latest revision as of 23:07, 24 May 2024

Policy

There are at least three ways to make backups:

  • a) We give you a 5TB portable drive, you keep it and write to it. Please ask for one!
  • b) Use CrashPlan/rsync and/or DropBox/Sync/Box.com to create backups in the cloud.
  • c) We backup /nfs/home and some other disks, as follows:

Monthly backups

  • Cluster 2: nfs-home:/nfs/home/ (/nfs/home)
  • Cluster 2: nfs-soft:/nfs/soft (/nfs/soft)
  • Cluster 2: wiki
  • Cluster 2: selected sysadmin files (alpha, beta, config files)

Most disks are never backed up

Implicit backups

  • we backup ZINC20 and ZINC-22 to AWS and Wynton.
  • all software is in github/gitlab and is thus backed up continuously

Restore

To have files restored from backup, please write to the sysadmins, stating file/directory name, the approximate time of when it was created in the form you want restored and when that copy was deleted or damaged. Better: use your own USB drive.

See Also

Return to system administrator's guide.

Retrieved from "http://wiki.docking.org/index.php?title=Backups&oldid=16068"