Fills up drive
I'm using T.I. 2014 on a Windows 8.1 computer, backing up to a dedicated 2TB external drive. I set the option to make the backup no more than 1700 GB (see the attached screenshot). But it filled up the drive (except for a tiny amount). Shouldn't this delete old backup files to keep the total from going over 1700GB?
I'll try that. But sometimes the daily incremental is as small as 700MB and sometimes as large as nearly 16GB.
It seems like the option I was using would be the one that would make the best use of the external drive - get as many backups as you can.
Do be aware that TI makes a replacement backup before deleting the old one so there is a hidden need for enough extra space of temp store one extra full backups.
I moved several backups to another drive for the time being and quick formatted the backup drive. I deleted the old backup job and created a new one. I selected "backup chain" (which I've never used before). It is making its initial backup right now. Do you think backup chain is a good choice?
Post a screen capture of your backup scheme so we have a better understanding of your settings.
Here are a couple examples.
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains.
Attached is the new one. I made a full backup manually and it made another full backup overnight (as it was supposed to).
Jud,
Your screen capture is the same as what is was not working. My recommendation is to use a different backup scheme with the options set as per either of these two examples. You can adjust how many diff to keep before each replacment full, and/or adjust how many chains to keep.
If you continue to use the same as your captures shows, you may have the same full disk or not enough room, etc.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains.
GH14. Custom Differential Backup Scheme . 6 Diff, Keep 4 chains. & folder
OK, I deleted that one and started with the one attached. I started a manual backup, which is running now.
The problem is that the user has to guess at how many version chains to keep. Too few and you aren't making good use of the disk to keep old data. Too many and you can run in to the full disk problem, right?
The program should be able to keep the oldest full backup, then start adding chains. When it sees that there isn't enough room for another chain, delete the oldest chain, keeping the initial full backup.
There is the option to keep the oldest full if you start out with it checked. Yes, determining how many chains to keep can be difficult. I notice this time you switched from differential to incremental. I am assuming that was intentional. The incremental allows only for the most recent inc to be deleted from within the system as each inc is a building block on the prior backup. The differential oldest can be deleted if done from within the system as each dif includes all changes since the full and only needs 2 files to be restorable. If restoring an incremental, the restore needs all files backwards to the full.
I was going by your GH 12 example. Differential will probably work better for me. That gives the difference between the last full backup and the current state, right? So only the most recent full BU and the most recent differential are needed to restore it to a recent state, as I understand it.
My point about determining the number of chains is guesswork for the person, but the program could figure it out.
You've been an enormous help - thanks.
----
Also, "do not delete the first version" is disabled on that screen, so it won't allow me to check that. Do I have to do that before the first full backup? (Also, I wish things like that were stated positively, like "keep the first version" instead of "do not delete".)
Yes, you are correct. Each dif is all changes since the last full. So choose the single dif to be restored. The result will be the full plus the selected dif will be restored or two tib files restored.
Yes, the "do not delete first version" must be checked as part of the backup task creation. Once the task is used, that option ceases to be available.
If you are using the custom/diff backup scheme with "store no more X recent version chains, I have been able to use the program (Acronis Backup Explorer) and delete any dif that I wanted and the program would continue working and the correct numbering would continue without any ill effects. If you try deleting selected dif files, do so on a spare working task just to make sure it works the same for you.
GH5. How to delete backup files within the program using Acronis Backup 'Explorer'
As the forum postings are not technically monitored by Acronis, any comments or suggestion you want them to have must be part of the wish list postings or feedback postings. My comments are just comments from an elderly senior citizen who is attempting to help others to better understand how to use the program so they too know how to protect or recover their data.
As for preferences, I would rather calculate my own space needs rather than have the program invoke their choices. I go to great lengths to totally avoid consolidation--either manual or via program. I do not want the program working a jigsaw puzzle on my data--especially when all the pieces look alike and any mistake by the program can render my backup worthless.
Edit/added. If you have some time, my signature link #2-A below could be helpful as it has numerous example links of common options. Most are the result of these questions being asked over and over again. My signature link #1 index may be something you would want to be aware of its existance.