Question regarding backup size.
Hi,
I am making a full backup (nots ector by sector) and the size on disk is 66gb.
However when I perform the backup it comes out to 22gb with normal compression!
Why is it so small in size as I have used ccleaner first?
The other thing is it marks the backup versions as well, as in 1 2 3 etc, surely this should only be a single version for each day?
Using TI 2014
Thanks for any advice.
Martin

- Se connecter pour poster des commentaires

Hi thomasjk,
Thanks for the info.8-))
I am just making a full disc backup, I have just noticedthat the estimated size is showing 40gb so I will run it again andd see what happens this time.
I appreciate that it does not back up empty space but I can't work out why it seems to keep a version chain...
I will also see if switching to disk mode solves the issue.
Martin
- Se connecter pour poster des commentaires

Hi,
No luck, even in single backup, disk mode it still only takes up 22gb when I would expect about 48gb.8-((
I'm not sure what to try next as I cannot rely on these backups.8-((
Martin
- Se connecter pour poster des commentaires

I appreciate that it does not back up empty space but I can't work out why it seems to keep a version chain...
Please post the details of your backup scheme. Is it a custom scheme. On the Main Screen click the Backp and recovery tab and in the field where you backup jobs appear click on Settings-->Backup Options--->Backup Scheme.
Why do you think you cannot rely on the backups? Have you validated the backup to verify its integrity? The best choice is to use disk mode backup and a custom scheme. I urge to peruse Grover's Guides http://forum.acronis.com/forum/3426. They are very detailed and cover almost very situation.
- Se connecter pour poster des commentaires

Hi thomasjk,
** Edited after posting **
I just found the setting for single backup scheme so the rest below will hopefully be irrelevant, I'll try iy tonight and hopefully that will solve the problem....
Thanks very much for the help.
Martin
The backup scheme is custom, full, disk mode.
Store no more than 1 version and do not delete the first version.
As I move the backups to a folder I don't think that the store more than 1 matters.
Yes, I'll re-read the tutorial and see if I can see what I am doing wrong.
As to not being able to rely on the backups, I have them set to verify which they do.
But this issue with versions seems strange to me, there shouldn't be a version list with a full non incremental backup surely?
As the estimated size as shown on the backup is 45gb why is it that it only takes up about 23gb?
I have an earlier version of TI on my laptop which reports the estimated size and that is what I get.
I feel I cannot rely on the backups as the size difference is so great.
Thanks,
Martin
- Se connecter pour poster des commentaires

Martin,
Do followup on the link provided by Thomas in link #1 above as the link has much detail.
The "disk mode" backup is one that include all partitions on the disk. Check the "exclusions" list to see what is being excluded from the backup,
such as temp files, etc. The size you can expect of a disk mode backup will be about 70% of your used disk space--less any exclusions.
The single version scheme is supposed to overwrite each full backup but the overwrite does not occur until AFTER a new full backup has been completed. I prefer to use the custom with automatic cleanup such as my GH11, GH12 & GH13 examples below.
If using a custom scheme with the "do not delete first verson of backup" checked; plus the "store no more than 1" checked,
what happens is Full 'B1 is created as the do not delete backup and kept & not deleted.
Next comes new full backups such as Full B2, Full B3, Full B4, etc. The store no more than ( & do not delete the first verson) means that
First, Full B1 and Full B2 will be kept;
Next full backup, Full B1 and Full B3 will be kept. Full B2 deleted
Next full backup, Full B1 and Full B4 will be kept. Full B3 deleted
Ongoing Full B1 always kept and oldest other full is deleted.
If you were to start out with the "store no more than (n) number to be greater than 1, then the program would keep the n number plus the "do not delete first version" each full backup run.
Custom Backup Scheme Discussion--extract
http://forum.acronis.com/forum/100416
Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.
Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
GH25. Understanding differences between Incremental and Differential backups for data recovery.
GH64. 71342: 2015 How to save a non-scheduled task.
GH63. 64640: Hints to help prevent issues with your TIB backup files creation.
GH63. 75086: A discussion on how to configure backup schemes.
- Se connecter pour poster des commentaires

HI GroverH,
Thanks very much for the reply, very comprehensive.8-))
I realised that I had missunderstoood the custom scheme that I had set up, assuming single version scheme was a full backup when it appears to have been a chain?
I should have used the single version scheme, hopefully I have that right now.
Martin
- Se connecter pour poster des commentaires