g-h: linked orphaned backup pages. added content

to backup-check (renamed from backup-testing).

1 files changed, 32 insertions, 0 deletions

diff --git a/gnome-help/C/backup-check.page b/gnome-help/C/backup-check.page
new file mode 100644
index 0000000..613783f
--- /dev/null
+++ b/gnome-help/C/backup-check.page
@@ -0,0 +1,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>