Difference between revisions of "FND-Backups"
m |
m |
||
Line 19: | Line 19: | ||
− | {{ | + | {{LIVE}} |
{{Vspace}} | {{Vspace}} | ||
Line 27: | Line 27: | ||
<div id="ABC-unit-framework"> | <div id="ABC-unit-framework"> | ||
== Abstract == | == Abstract == | ||
+ | <section begin=abstract /> | ||
<!-- included from "../components/FND-Backups.components.wtxt", section: "abstract" --> | <!-- included from "../components/FND-Backups.components.wtxt", section: "abstract" --> | ||
... | ... | ||
+ | <section end=abstract /> | ||
{{Vspace}} | {{Vspace}} | ||
Line 44: | Line 46: | ||
=== Objectives === | === Objectives === | ||
<!-- included from "../components/FND-Backups.components.wtxt", section: "objectives" --> | <!-- included from "../components/FND-Backups.components.wtxt", section: "objectives" --> | ||
− | ... | + | This unit will ... |
+ | * ... provide a brief introduction to backup problems and methods to solve them. | ||
+ | |||
{{Vspace}} | {{Vspace}} | ||
Line 51: | Line 55: | ||
=== Outcomes === | === Outcomes === | ||
<!-- included from "../components/FND-Backups.components.wtxt", section: "outcomes" --> | <!-- included from "../components/FND-Backups.components.wtxt", section: "outcomes" --> | ||
− | ... | + | After working through this unit you ... |
+ | * ... have a sensible and effective strategy for backing up your computer; | ||
+ | * ... have demonstrated that you can recover data. | ||
{{Vspace}} | {{Vspace}} | ||
Line 61: | Line 67: | ||
*<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit. | *<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit. | ||
<!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | ||
− | *<b>Journal</b>: Document your progress in your [[FND-Journal| | + | *<b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these. |
<!-- included from "ABC-unit_components.wtxt", section: "deliverables-insights" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-insights" --> | ||
− | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|insights! page]]. | + | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]]. |
{{Vspace}} | {{Vspace}} | ||
Line 85: | Line 91: | ||
Backup your hard-drive now. | Backup your hard-drive now. | ||
− | Risk is probability times damage | + | Risk is probability times damage. The annualized probability of hard drive failure is on the order of 3%. This means about three of your classmates in this course will lose all their data this year. It is a bit better for solid state drives (SSD), perhaps only 0.3 failures per year. But what is the damage? All your essays, coursework, all the pictures on your computer, that email from your first love... There is no question you need to have plans in place to protect your data. After all, storage failure is not a question of ''if'', but ''when''. |
+ | |||
+ | Enterprise-scale data in bioinformatics labs need dedicated solution and that is actually an increasing problem. For your small scale, personal backup needs you have a variety of options; | ||
+ | * Cloud backup may be bandwidth limited; | ||
+ | * Mac OS X has things well covered with thier Time machine / Time capsule, I don't know what the best equivalent is for other systems; | ||
+ | * off-machine storage in removable disk is a questionable startegy because everything that is not fully automatic is liable to fall victim to complecancy; | ||
+ | |||
+ | Whenever possible, make differential backups. And remember: NO backup is a backup unless recovery of data has been tested and shown to work. | ||
+ | |||
+ | {{task|1= | ||
+ | |||
+ | * Use this [https://www.google.ca/search?q=backup+options&num=20&tbs=qdr:y '''Google Search'''] for links to recent articles about backup options. | ||
+ | * Read a few articles that are relevant for your computer. | ||
+ | |||
+ | * Decide on a backup strategy for your computer. | ||
+ | * Implement your strategy. | ||
+ | |||
+ | * Create a test file. | ||
+ | * Backup your computer. | ||
+ | * Delete your test file. | ||
+ | * Recreate the file from your last backup. | ||
+ | |||
+ | }} | ||
+ | |||
+ | |||
{{Vspace}} | {{Vspace}} | ||
Line 93: | Line 123: | ||
<!-- {{#pmid: 19957275}} --> | <!-- {{#pmid: 19957275}} --> | ||
<!-- {{WWW|WWW_GMOD}} --> | <!-- {{WWW|WWW_GMOD}} --> | ||
− | + | <div class="reference-box">Use this [https://www.google.ca/search?q=backup+options&num=20&tbs=qdr:y '''Google Search'''] for links to recent articles about backup options.</div> | |
{{Vspace}} | {{Vspace}} | ||
Line 154: | Line 184: | ||
:2017-08-05 | :2017-08-05 | ||
<b>Modified:</b><br /> | <b>Modified:</b><br /> | ||
− | :2017- | + | :2017-09-11 |
<b>Version:</b><br /> | <b>Version:</b><br /> | ||
− | :0 | + | :1.0 |
<b>Version history:</b><br /> | <b>Version history:</b><br /> | ||
+ | *1.0 Completed to first live version | ||
*0.2 Begin development from legacy material; points only | *0.2 Begin development from legacy material; points only | ||
− | *0.1 | + | *0.1 Material collected from previous tutorial |
</div> | </div> | ||
[[Category:ABC-units]] | [[Category:ABC-units]] |
Revision as of 20:31, 12 September 2017
Data Backup Best Practice
Keywords: Data backup technologies and best practice
Contents
Abstract
...
This unit ...
Prerequisites
This unit has no prerequisites.
Objectives
This unit will ...
- ... provide a brief introduction to backup problems and methods to solve them.
Outcomes
After working through this unit you ...
- ... have a sensible and effective strategy for backing up your computer;
- ... have demonstrated that you can recover data.
Deliverables
- Time management: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
- Journal: Document your progress in your Course Journal. Some tasks may ask you to include specific items in your journal. Don't overlook these.
- Insights: If you find something particularly noteworthy about this unit, make a note in your insights! page.
Evaluation
Evaluation: NA
- This unit is not evaluated for course marks.
Contents
When was the last time you made a full backup of your computer's hard-drive? Too long ago? I thought so.
Backup your hard-drive now.
Risk is probability times damage. The annualized probability of hard drive failure is on the order of 3%. This means about three of your classmates in this course will lose all their data this year. It is a bit better for solid state drives (SSD), perhaps only 0.3 failures per year. But what is the damage? All your essays, coursework, all the pictures on your computer, that email from your first love... There is no question you need to have plans in place to protect your data. After all, storage failure is not a question of if, but when.
Enterprise-scale data in bioinformatics labs need dedicated solution and that is actually an increasing problem. For your small scale, personal backup needs you have a variety of options;
- Cloud backup may be bandwidth limited;
- Mac OS X has things well covered with thier Time machine / Time capsule, I don't know what the best equivalent is for other systems;
- off-machine storage in removable disk is a questionable startegy because everything that is not fully automatic is liable to fall victim to complecancy;
Whenever possible, make differential backups. And remember: NO backup is a backup unless recovery of data has been tested and shown to work.
Task:
- Use this Google Search for links to recent articles about backup options.
- Read a few articles that are relevant for your computer.
- Decide on a backup strategy for your computer.
- Implement your strategy.
- Create a test file.
- Backup your computer.
- Delete your test file.
- Recreate the file from your last backup.
Further reading, links and resources
Notes
Self-evaluation
If in doubt, ask! If anything about this learning unit is not clear to you, do not proceed blindly but ask for clarification. Post your question on the course mailing list: others are likely to have similar problems. Or send an email to your instructor.
About ...
Author:
- Boris Steipe <boris.steipe@utoronto.ca>
Created:
- 2017-08-05
Modified:
- 2017-09-11
Version:
- 1.0
Version history:
- 1.0 Completed to first live version
- 0.2 Begin development from legacy material; points only
- 0.1 Material collected from previous tutorial
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.