Skip to main content

One Full or One Single Disk Full with Time Out TI2013

Thread needs solution

I have twenty workstations. A few of the computers are unable to do a regular Single Version backup.
I end up with 'timeout by user' and 'disk full' messages.

For one computer and this illustrates most of the backups I have setup 'Single Version Chain' with the expectations that on Thursday night the folders and files I have selected to backup will be replaced with a new full backup and the former full backup deleted.

Thus every Friday morning I would have one full backup.

I will discuss Curtis's computer as the example.

I expected a complete full backup and as usual the errors listed are timeout and disk full. The backup is 20GB in size. The USB device is 30 GB.

After those errors I elected to format the device and run another backup. That worked however when the backup ran again as Single Version Chain I got disk full, time out.

I formatted the device and changed from Single Version Chain to Custom. And I got a complete backup until the next backup ran I got the timeout, disk full.

So I formatted the disk and setup the backup as one full backup with differential. The second backup I got another timeout, disk full.

So I replaced the 30GB device with a 60GB device. This time I configured the backup as keep one full backup and then run differentials. Though the full size of the folder and files is around 20GB even on the 60GB device I got time out and disk full.

In order to get a healthy backup on a few machines that keep generating disk full and time out (those machine I replaced 30GB devices with 60GB devices offering vast amounts of digital space for a backup)

So I have a larger device on those machines (60GB) and most of those folders and files are no greater than 25GB. And I get time outs and disk full messages be it Singe Version be it Custom.

Sorry this long note. Let me know if there is a solution. Thanks!

0 Users found this helpful

Be aware that Acrnis will NOT delete the scheduled deletion until AFTER the replacement backup has been completed.

Thus, if your full backup size is 30GB and your only tib which you keep is the 30 GB, you need a minimum of 60GB (30x2) of available storage space to avoid the disk full error; or,
if you also keep 20GB worth of Differentials, then you mimimum available storage space is increased by the 20 or a total of 80GB.

Another example is your weekly backups total 100GB and you want to keep 2 weeks of weekly backups, you still must plan to allow the storage space for 2 weeks of backups plus short term storage space the 3rd full backup.

Here are some links which can help.

http://forum.acronis.com/forum/75086

GH64. 71342: 2015 How to save a non-scheduled task.

AGH-1. 64640: Do's & Don'ts--Hints to help prevent issues with your TIB.

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. 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.

GH11. Create Custom Full Backup Scheme....Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..

GH12. Create Custom Incremental Backup Scheme. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

GH13. Create Custom Differential Backup Scheme. ...Keep Full plus 2 Diff per chain. Store/Keep 2 chains. Use whatever number best fits your needs.

Setting disk size limits (don't exceed 300GB, etc) do not work well;
and setting "elapsed day limit" is most often misunderstood". I believe the best option is the "cleanup option " (when properly understood), where the user sets how many "store x recent version chains" to keep. The number of files inside the chain is the single full plus all diff or inc type files created before the next full. So if you created a full each Monday and then 6 diff or inc files for the remaining 6 days, the chain length is 7 files.
Keeping 4 weeks backups (keeping 4 chains) would indicatge you need storage space for 4 chains (4 weeks of backups) PLUS the short term need for the current planned replacement FULL backup.