#BACKUP CARBON COPY CLONER TO MY AMAZON DRIVE FULL#
To avoid the nuisance of the full backup process interfering with my daily work, I move the 'xfer.*' drive to a 2nd machine which has all these other backup drives online (temporarily for the backup). So xfer.* is itself a backup drive (with four volumes on it).Īfter the 'xfer' volumes are brought up to date, all volumes (partitions) on it are themselves perfect clone backups. My process is made less onerous by first making clone backups to one transfer drive, the four 'xfer' volumes xfer.Boot, xfer.Master, xfer.Archive1, xfer.ArchiveP, which are clone backups of my master (original) volumes: Boot, Master, Archive1, ArchiveP. Shown below are volume icons on the desktop as part of a periodic (monthly) backup effort. Accordingly, I maintain multiple sets of backups (each with multiple drives). My data is essential to my living, so I cannot afford to risk losing it. See Cloning as a Backup Strategy for a simplified use case. The simplest form is one original to one backup. Note: my system is a multi-redundant effort as shown here (multiple backups done at once). Verification of data integrity for all files on the backup drives after the backup or at any later time ( Integrit圜hecker).Verification of file system integrity on the backup drives.Process: not wiping out all backups while backing up (hence at least three backups so one can cycle through them on a rotating basis).
Physical redundancy: at least three separate backups stored safely away from the computer, preferably more backups as the value of the data rises, and preferably not all backups stored in the same place.DiglloydTools (data integrity/validation)Ī robust professional backup process includes these attributes:
0 kommentar(er)
