I am using version 6.1.1.8 and have been using 360 backup for several years now - meaning several versions. I upgraded to v6 to help solve a problem and well it did not. I have a fairly simple backup set that backs up my documents folder and the entire contents of another data drive. The destination drive for this entire set of data is roughly 3 times the space of the entire set being backed up. The destination drive is dedicated to this backup set, nothing else uses it. Yet the drive is now full and I can find no reasonable way to manage the backup sets on the destination drive. I realize this isn't an enterprise class backup solution, but there isn't a version limit, any that looks like a rentention policy, so how do I control the size of the data on the destination drive. At this rate a scheduled task with xcopy would be better.
I am running this on a Windows 7 Ultimate 64-bit system.
Thanks for any help or direction on how to better manage this.
I am using version 6.1.1.8 and have been using 360 backup for several years now - meaning several versions. I upgraded to v6 to help solve a problem and well it did not. I have a fairly simple backup set that backs up my documents folder and the entire contents of another data drive. The destination drive for this entire set of data is roughly 3 times the space of the entire set being backed up. The destination drive is dedicated to this backup set, nothing else uses it. Yet the drive is now full and I can find no reasonable way to manage the backup sets on the destination drive. I realize this isn't an enterprise class backup solution, but there isn't a version limit, any that looks like a rentention policy, so how do I control the size of the data on the destination drive. At this rate a scheduled task with xcopy would be better.
I am running this on a Windows 7 Ultimate 64-bit system.
Thanks for any help or direction on how to better manage this.
Since I have only one backup set, the Default, this was of little help. All this does is remove some or all of the files backed up.
It does not explain why there is such apparent bloating of the data size on the destination drive. The size of the data being backed up is 278 GB and the destination has 781 GB, roughly 2.8 time the source data. The change rate on the source data is low thus I would expect even incremental backups to be rather quick and small.
If all that is happening is a FULL backup of the source, then how do I manage how many copies of the FULL backups are kept?
If it is a FULL and then infinite INCREMENTALbackups, then how do I manage the number of copies or versions of changed files are kept?
Somehow there must be a way to control the size of the data in the backup collection.