Backup drive near capacity
I will not be able to backup because of lack of space.
My cleanup says keep 2 chains and new full after 3 differential. From my reading I cannot delete files anymore from 2015,
Can I delete last set or B4 in Windows Explorer? In screen cap attached
Unfortunately this will not help. I am at capacity. If you looked at the attached the last Full was 1.3TB and the last series is close to 4TB so If I do any work I will have an error with my next backup unless that will trigger a cleanup? Hence my question. The documentation is very poor and no simple way to find answers.
Terry,
This is one example of setting up custom differential schemes which perform automatic deletion.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains. The 2-2 is an example only with user choice for whatever number of chains to be retained best fits the individual needs.
In my usage of 2015, I have found that the user CAN DELETE the oldest differential while keeping the newest diff files and the program will recover and continue to create new diff backups--if that is what you want done. After the deletion, I always simulate the first steps of a recovery so the program will correct its data base (respond ignore to any error prompts) and then click cancel to the simulatede restore. The deletion is done inisde Windows Explorer. Right click on each diff file to be deleted and then choose the delete option. Following the deletion, I do recommend that you validate any remaining pieces of the chain. Validatgion after deleting will update the history file and give you a chance to respond to the program prompts about the manaully deleted items.
In your attachment, you should be able to delete all diff in B4 keeping the B4 Full, or delete all of B4 keeping Full B5.
This is not documented nor recommended but I have found that TrueImage will continue and any Full and matching Diff file will be restorable--or at least it has worked for me. 2015 seems to be the best yet in recovering the deletion of diff backups.
But, don't forget, if the backups are incremental, then NO INCREMENTAL pieces can be deleted.
Thanks much Grover.
I replied in wrong thread. I have made changes to the Auto Cleanup and will see it they take? I choose DIFF so I did not have to keep every INC set and with the amount of data I create (imagery) I want to be protected. I also create copies of drive to store off site on a regular basis.
Now I have backup twice a week, Full after 3 and save 2 chains with delete chains older than 15 days so I will have latest Full and Diff files.
Cheers
Example Rules for "Older than X days":
When is oldest completed chain older than X(15) days?
Chain length is sum of Full plus any incremental or differential files created before the next Full, or your chain length=4 files per chain
If understanding correctly, your chain length is 4 files (Full +3 differential) , in which a twice weekly backup translates into a single completed chain every four backups or every 2 weeks.
So keeping 2 chains, indicates 4 weeks needed to create first 2 chains.
The 15 elapsed day clock does not begin ticking until Backup #8 (last diff of chain 2) is older than 1 day.
So, deletion of chain 2 will first occur after 15 additional days have elapsed FOLLOWING the completion of your chain #2 (or backup #8)
Or, as stated a different way, your first/oldest chain will not be scheduled for deletion (older than 15 days) until you have completed the 4th full backup which is after the 4th full at the start of the 7th week of backups.
This may not be the result you expected. Frankly, I do not like or use this option as it is very deceiving. As my example GH13 indicated, I prefer to use the option "Store no more than X chains" which is more easily predictable. Your use of 15 days here has the same effect as if the setting was "Store no more than 3 chains.
G
I am experiencing TI-Home b6525 failures due to "missing filename" errors, but it's not reporting the specific missing filename. One of the troubleshooting paths I'm investigating is TI attempting to make another Full .tib, since I had the backup task config'd to do that after a number of Incremental .tib. IF this is taking place in my case AND there is no longer sufficient destination storage location space THEN I would hope that I would receive an alert message from the product the task will fail because of this, either before the attempt (ie, check for sufficient space in advance) or upon running out of space during the backup task, stating the cause. Is this the norm with this version?
Also, when the backup location reaches the state where the number of Full and Incremental files reaches the configured task settings, does TI first delete the old files before attempting to save the new Full .tib in order to insure adequate destination storage space? (if yes, that seems a bit on the dangerous side if the new backup fails without having a previous backup available for any subsequent needed Restore, but that may still be preferable in some situations thus making it a task setting would be in order)
Stephen,
You have several postings with several different problems, which would indicate you are in the midst of a learning curve.
To help those wishing to help you, you need to create a new posting of your own and explain your current problem advising which version of TrueImage you are using and which version of Windows and your specific problem.
There are many guides and resources to help you. Here are two such links.
http://forum.acronis.com/forum/75086
http://forum.acronis.com/forum/64640
Also review some of those in my signature and the user guide located along the left margin under the 2014 Web Help.
My suggestion at this point in time would be to start a fresh backup task and use one of the examples (GH11, GH12 or GH13) as to how to set up the backup scheme. We need specifics of what backup scheme you are using before we can help fix your issues. Show us examples of your specific settings and specific examples of where these have gone wrong. Set the new task pointing to a new storage folder or sub-folder. Editing or making changes to a configuration is often the cause for user problems. Avoid editing or changing a backup task.
There are numerous postings which provide answers to problems similar to yours. I wish TI was "user friendly" or intuitive but it is not. Time spent learning the program is an essential part of using it. Any time spent reviewing the postings of users with similar issues will be helpful to you.
does TI first delete the old files before attempting to save the new Full .tib in order to insure adequate destination storage space?
NO, the replacement FULL is first created and if successful and the retention quota exceeded, then the deletion occurs. If too many backups are stored before the user designated limit occurs, then disk full message will prompt for user to find additional storage space.
there is no longer sufficient destination storage location space THEN I would hope that I would receive an alert message from the product the task will fail because of this, either before the attempt (ie, check for sufficient space in advance) or upon running out of space during the backup task, stating the cause. Is this the norm with this version?
Yes, backup will continue to be attempted (as per schedule) and user will be prompted to provide more space. Note user error message controls inside the Task/backup options/error handling. The SysTray in lower right often location for prompting messages.
http://www.acronis.com/en-us/support/documentation/ATI2015/index.html#2…
If you are long time user of TrueImage, the prompt contacting of support within the first 30 days has been in effect for years.
Start over fresh and see give your new settings a test. With specifics, we should be able to help you find your problem but it will take some research time on your part. Good luck.