Disk Space Management

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 3

I've been battling with managing the amount of space my backups require. In my latest attempt to get disk space under control, I've used a "custom backup scheme". (screenshot one) Although, I do not believe this is working as I intended.

Using the above scheme, I should get an entirely new backup on every third week (with 2 chains of the original created each week). After the highest compression of the backup, I make this assumption: 1GB disk space used should be well under 1GB back up size.

Now let's look at the file system. When I look at the location where my backups are being saved, there are 8 files taking up 786 GB! (screenshot two). The original disk it is backing up is only ~200 GB. This means to back up 1 bit, it takes 4 bits?!

I am using the "Automatic Cleanup" feature. Why are are many versions/chains being persisted?

Thanks in advance for any help! I'm using version 11.

Allegato Dimensione
one.png 97.83 KB
two.png 119.18 KB
Ven, 06/28/2013 - 16:36
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Legend
Messaggi: 172
Commenti: 11125

Based on your settings, here is what you can expect.

Recent version chain = 4 files (1 full plus 3 inc)

store no more than 2 version chains indicates you will be keeping 8 fies (2 chains of 4 each)

Acronis will create the next full before any deletion of old occurs, so
the program will create the next full (backup run #9) before it deletes the oldest single chain of 4 files.

In summary,
Add up the space consumed by the 2 chains (8 files)
Also include the temporary space for the next full (run #9) and that is the space requirements.
Currently, your storage disk shows 213GB of free space available for storing a new backup. The next backup needs at least >404GB of temporary space to create the replacement full before the chain can be deleted.

Normally, space permiting using your backup scheme settings, the program will attempt to create the first 9 backup runs. It will either succeed or error out on not enough space. If the "MyBackup" is your full backup, you would need at least 400-500GB (temporary space) of more free space before another full could be completed and oldest chain deleted.

If you are running out of space, you may have to change the "store no more than 2 recent version chain" to a lessor number--such as "1". Such a change would enable you to increase the number of incrementals (slightly) to compensate for the fewer chains being retained.

It appears you may be storing several tasks inside the single storage folder (if drive B is a single disk). This can be confusing both to the user and the program. My recommendation is to use a diferent sub-folder for storing the backup of each task.

Editing or changing the task parameters can also confuse the program which can cause unexpected results.
You may need to create all new tasks and start over in order get an orderly work flow.

The verison of backup you appear to be using is 2011 rather than the much older version 11.

If you are storing several tasks on the same disk, you will need to coordinate your total needs in order to keep from having a space issue error.

The numbering of your backup files would seem to imply(not sure) that one of your backups has been restored which would cause the program to add more number to the file name and to start its retention number over again. After a restoration of a backup, my recommendation is to immediat ely start over with all new tasks.

The size of your "My Backup" is 404GB if that is your full backup. You indicate source is only 200 used space, then something is not matching. Your drive C seems to show 200GB of free space on a 2TB disk. Your backup type is a partition type. My suggestion is that you click the disk mode option and have the program include all partitions on the disk. Many of us prefer the disk mode backup as compared to the partition mode backup.

Edited several times.

Ven, 06/28/2013 - 23:32
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 2
Commenti: 3

GroverH - amazing response! Your explanation of how the backup schemes work is clear and succinct.

I have taken your advice and done the following:

(1) Deleted all existing backups.
Might as well start from scratch as you suggested, because something is clearly wrong with my current backup(s)

(2) Created all new custom backup tasks.
Decreased the chain size to 1. I have no need for multiple chains. Best I can tell from your explanation: a chain is like a separate 'fork' (in the world of software development)

(3) Re-ran all tasks.
Everything seems in order so far...

(4) Wait
I'll keep running the new custom tasks and hopefully my backup drive will not be filled up in under a month

Thanks again,
Ben

Gio, 07/04/2013 - 18:00