- #Carbon copy cloner safety net archive
- #Carbon copy cloner safety net full
- #Carbon copy cloner safety net free
#Carbon copy cloner safety net archive
CCC also avoids pruning items that were very recently archived - after all, it wouldn't make sense to archive an item on the destination, them immediately delete it. The purpose of CCC's SafetyNet pruning is to make space for additional backups.
#Carbon copy cloner safety net full
"CCC is pruning my SafetyNet, but the disk is still pretty full at the end of the backup task" You may delete the contents of the SafetyNet folder without harm to the rest of your backup set.
#Carbon copy cloner safety net free
Archived files may eventually consume all of the free space on the destination, so you should periodically delete older archive folders to maintain enough free space for future backups. Never prune archives in the SafetyNetĬCC will not automatically prune the contents of the "_CCC SafetyNet" folder at the root of the destination. If the newest archive is larger than the limit that you have specified, that archive will be pruned in entirety. When the cumulative total exceeds the limit that you have imposed, CCC will prune the remaining, older archives. Starting with the most recent archive, CCC will determine the amount of disk space that each archive consumes. Prune archives in the SafetyNet when they are larger than GB Prune archives in the SafetyNet when they are older than daysĬCC will prune archives that were created more than "xx" days ago. If CCC wanted to copy a 40GB file, however, CCC would not fruitlessly copy 25GB of that file, rather it would immediately increase the pruning limit by 40GB, revisit pruning, and then restart the task. For example, if CCC copied 25GB of data, then the pruning limit would be increased by 25GB. CCC will then increase the pruning limit by the larger of either the amount of data copied in the current task, or by the amount of data that was required by the last file CCC attempted to copy. If that task proceeds to copy more than 25GB of data, however, the destination will become full. For example, if your pruning limit is set to the default of 25GB, and you have 25GB of free space at the beginning of the backup task, no pruning will be done at the beginning of the task. When the Auto Adjust option is enabled (and it's enabled by default), CCC will automatically increase the free space pruning limit if your destination runs out of free space during the backup task. Auto Adjustment of the SafetyNet Free Space pruning limit Note that if the archives cumulatively consume less space than the limit requested and the destination volume is full, CCC will prune all of the archives. CCC will continue to prune the oldest archive until the requested amount of free space has been achieved. If your destination volume has less free space than the limit that you have specified, CCC will prune the oldest archive. Automatically prune archived content before copying files Prune archives in the SafetyNet when free space is less than GB If any portion of an archive pushes past the limit that you have imposed, the entire archive (e.g. Lastly, archive pruning works at a macro level. CCC's pruner won't delete the current versions of files on your destination, nor anything outside of the scope of the CCC backup task. Additionally, pruning is always limited to the contents of the _CCC SafetyNet folder that is at the root of the destination. SafetyNet pruning occurs at the beginning of a backup task, so CCC will never delete an item that was archived in the current backup task. You can customize these settings by clicking on the Advanced Settings button in CCC's main window. This limit is automatically adjusted if a 25GB limit is too low for a particular source and destination. To prevent that from happening, CCC prunes the contents of the SafetyNet folder at the beginning of each task if free space is less than 25GB. If left unmanaged, this SafetyNet folder would eventually consume all free space on your destination volume. Carbon Copy Cloner will move previous versions of modified files, as well as files deleted since previous backup tasks to a SafetyNet folder at the root of the destination.
0 kommentar(er)
