blob: 613783ff9cb210f0d6f2617f27ab44935353df7b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
<page xmlns="http://projectmallard.org/1.0/"
type="topic" id="backup-check">
<info>
<link type="guide" xref="files#backup"/>
<desc></desc>
<revision pkgversion="3.0" version="0.1" date="2010-02-26" status="review"/>
<credit type="author">
<name>GNOME Documentation Project</name>
<email>gnome-doc-list@gnome.org</email>
</credit>
</info>
<title>Check your backup</title>
<p>
After you have backed up your files, you should have a look to see if the backup was successful.
</p>
<p>
A file integrity check is not done on a copy/move operation. This means if you are copying files to other drives/media, it is not easy to verify data integrity or to single out files that have failed.
</p>
<p>
You can do a check by looking through the copied files and directories in the destination media. By opening and checking the copied files, you can see whether the files you check copied successfully.
</p>
<comment>
<cite date="2010-06-29" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite>
<p>Explain why backups should be tested.</p>
<p>Give methods for checking backups, like MD5sum.</p>
</comment>
</page>
|
