Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
backupset [2011/07/04 01:42] henri [Important Notes] |
backupset [2011/07/04 01:46] henri [Access to the Backup Set] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| \\ \\ | \\ \\ | ||
| In summary many snapshots don't make a file more secure. If the file hasn't changed and is the same in all snapshots, then it is only stored once on the disk. If that copy becomes corrupted for any reason, then it will be corrupted in all snapshots. If a file is deleted from one snapshot, it will still exist in the other snapshots. If you require additional security of your files then the recommendation is to generate additional backup sets. The process of distributing backup sets may be carried out with post-actions scripts, with multiple backup configurations or with a manual/automated duplication process. | In summary many snapshots don't make a file more secure. If the file hasn't changed and is the same in all snapshots, then it is only stored once on the disk. If that copy becomes corrupted for any reason, then it will be corrupted in all snapshots. If a file is deleted from one snapshot, it will still exist in the other snapshots. If you require additional security of your files then the recommendation is to generate additional backup sets. The process of distributing backup sets may be carried out with post-actions scripts, with multiple backup configurations or with a manual/automated duplication process. | ||
| + | \\ \\ | ||
| + | ===== Access to the Backup Set ===== | ||
| + | If you managing the backup for a number of users, then you may wish to configure a read-only copy of the snapshot root to allow easy restore of files from the backup set. | ||
| \\ | \\ | ||
| \\ | \\ | ||