Skip to content

Latest commit

 

History

History
105 lines (72 loc) · 3.42 KB

BackupsOutline.md

File metadata and controls

105 lines (72 loc) · 3.42 KB

Backups 101 Outline

57 Minutes w/ 3 minutes flex


Why Should You Backup

Use the examples if they don't get talking, or to elaborate on these points.

Horror Stories (8 minutes)

Stories we have heard here at the libraries:

  • Data backed up in one place, on tapes. Tapes did not work. All data lost.
  • Beth's colleague who lost three months of data without trying to recover (and not having it backed up)

Success Stories (8 minutes)

Stories we have heard where backups saved us:

  • Beware of pinch points in data process: Beth's example of specimens that could get blown away
  • Erasing a file and getting its backup from the external hard drdive

Who Should Backup

Group Exercise (6 minutes)

The instructor will lead the students in an exercise that will ask the students to identify people that should use backups. First, ask the room to name roles who should back up data. Then, give them each example one at a time. Should the person back up?

Examples

  • Undergraduate students entering data for a graduate student's project
  • Faculty writing a textbook
  • Graduate student in the field with paper datasheets
  • Lab manager who maintains lab computer
  • Undergrad student working on their own research project

The point is, the responsible person should back up things they don't want to lose! Don't assume someone else is in charge, though. Ask. Make a backup if you're not sure.


What Should You Backup

But what, specifically, should you keep?

What Files Should You Backup (4 minutes)

How Do You Make That Determination (4 minutes)

Pointers on how to identify what should be backed up

  • Money cost of data to recreate
  • Inconvenience of backup method
  • Time cost of data to recreate
  • How sad will you be?

Some potential tradeoffs to help determine what files need to be backed up or the scale of the backup.

  • Trade off between how fast you can get your files back between inconvenience (backing up whole hard drive)
  • Specific files - you might forget a file
  • A common compromise is all data files, but not your operating system
  • Physical files and some ways you can deal with (scanning, photographing, dividing up samples)
  • Some backups for physical items may be very time consuming or impossible (scientific specimens)

Where Should You Backup

3-2-1 Rule (3 minutes)

  • Three Copies of Your Data
  • Two Copies Local (but on different devices)
  • One Copy at a Remote Location

Medium Considerations (3 minutes)

  • Frequency of use (i.e. harddisks that need to run constantly need to be rated for that)
  • Cost of Operation vs. Security
  • Limitation of the Medium
    • Cloud access loss of control
    • Hard drive is an object to keep track of
  • Advantages of the Medium
    • Cloud access is far away
    • You have control of local hard drive

When Should You Backup

How to Decide on a Frequency (4 minutes)

  • How often does the content change
  • How much work would be lost in the time
  • How much would it cost you to replace that work? (particularly important for physical samples?)
  • How much work is required to maintain that frequency

Backup Culture (4 minutes)

  • Make a group effort
  • Backup Day

How Should You Backup

Useful Tools and Systems (6 minutes)

Point the participants toward some tools (or resources that explain tools) to move toward better backups

  • Some general purpose for all operating systems
  • Some for each of the big three