|
1 | | -$DragonFly: src/bin/cpdup/BACKUPS,v 1.4 2007/05/17 08:19:00 swildner Exp $ |
2 | | - |
3 | 1 | INCREMENTAL BACKUP HOWTO |
4 | 2 |
|
5 | 3 | This document describes one of several ways to set up a LAN backup and |
@@ -35,7 +33,7 @@ $DragonFly: src/bin/cpdup/BACKUPS,v 1.4 2007/05/17 08:19:00 swildner Exp $ |
35 | 33 | Before you actually do the NFS mount, create a dummy file for each |
36 | 34 | mount point that can be used by scripts to detect when an NFS mount |
37 | 35 | has not been done. Scripts can thus avoid a common failure scenario |
38 | | - and not accidently cpdup an empty mount point to the backup partition |
| 36 | + and not accidentally cpdup an empty mount point to the backup partition |
39 | 37 | (destroying that day's backup in the process). |
40 | 38 |
|
41 | 39 | touch /nfs/box1/home/NOT_MOUNTED |
@@ -137,7 +135,7 @@ $DragonFly: src/bin/cpdup/BACKUPS,v 1.4 2007/05/17 08:19:00 swildner Exp $ |
137 | 135 | will have a distinct copy of all the file data and you will quickly |
138 | 136 | run out of space in your /backup partition. |
139 | 137 |
|
140 | | - MAINTAINANCE OF THE "/backup" DIRECTORY |
| 138 | + MAINTENANCE OF THE "/backup" DIRECTORY |
141 | 139 |
|
142 | 140 | Now, clearly you are going to run out of space in /backup if you keep |
143 | 141 | doing this, but you may be surprised at just how many daily incrementals |
@@ -338,6 +336,6 @@ $DragonFly: src/bin/cpdup/BACKUPS,v 1.4 2007/05/17 08:19:00 swildner Exp $ |
338 | 336 |
|
339 | 337 | If your OpenSSH version has been patched to support unencrypted transfers |
340 | 338 | *AND* you trust the physical network between the machines involved, you |
341 | | - might want to disable encryption alltogether: |
| 339 | + might want to disable encryption altogether: |
342 | 340 |
|
343 | 341 | cpdup -F -cnone ... |
0 commit comments