Not deleting oldest to make room
Tonight's backup hung again because disk was full. When this happens, unless you have another path for it to create the backup, you can only cancel, the backup. Then you can delete old to make room and then you have to restart. You can't just remove an old to make room while it waits as you are locked out of doing anything but provide a new path.
However, it should have made room on it's own. I checked the settings and it is set to delete oldest when the disk is full. The disk had 5 "MyBackup"s and 2 "SystemBackup"s. I removed the oldest of each to make room and restarted. after wards I checked the settings and confirmed it is set under backup options - Error handling when not enough space in ASZ. I assume ASZ is the drive path I told it to save the backups. Or do I have to make it secure zone before it will remove the oldest as told?
I used a WD 640Gb drive partitioned with a primary 303Gb for NSB to use and the remaining 292Gb is a primary for weekly backups.
same here, 3.5 years later. Can't get support either need to register to get serial number which requires registration.... ?
Product seems to be best out there, but it also takes a good support system to make customers happy. Sad. 2 days to trial end, 750 GB drive filled up with incrementals despite trying every "consolidation" option available.
Wonder if they ever do focus groups. :(
Dwaine, Carl & Timothy, There is a solution but it involves creating a custom task and not accepting any default settings . Setting the backup task with the options that work to your benefit. The version 2013 is much better than version 2012 or 2011 in maintaining the correct number of backups.
You do not need to perform manual deletes. You can have the program perform the deletes based on the designated number of backup files you wish to retain. Yes, the user will have to know or guess as to the backup size but if you have some history of backups, that should be easy to do. The program will delete the oldest backups automatically as new replacements are created--based on your custom settings.
Look at link #2 below and look at illustrations 11-full; or 11-Inc or 11-Diff--based on whether you are using full only (11-full); or full plus x inc (11-Inc); or full plus x diff (11-diff). Adjust the 6 and 4 backup numbers to fit your own needs or space limitations.
"Store no more than x recent version chains" is the key to how many full chains to keep. This will depend upon your storage disk size. You will need to caluculate how many full backups (full +Inc or diff, if used) plus one extra full. TrueImage will not delete the oldest until its replacement has been created so you must allow some extra room.
Do not use the option based on elapsed days or any disk space limitations. The above has worked for me and I believe it will for you too. The key is the cusotm settings and not use any default settings. Below is a sample of what you can expect and the program does all the deletion without any full disk errors.
