Skip to main content

Target drive is running out of space - Ignores previous full backup

Thread needs solution

Hello,

 

I'm a new user of Acronis 2016.  I have about 1,3 Tb of data on a 4 Tb drive that I want to backup on a 2 Tb drive on my PC.  I want to backup files and folders.  This seems simple enough.  Backup is a custom scheme which is incremental with cleanup after 3 incremetal versions.  PC is working under Windows 7 (familly edition). 

The problem is that once the first backup ends (which seems successful), I can't produce an incremental backup.

The incremental backup produce a second version of the first main backup creating a "running out of space" problem.

First bacukp name is :  DisqueD1_full_b1_s1_v1.tib

There are three other files with the same name but with inc_b1_S2, S3 and S4 in them.  And then, there is the new full backup file.

I don't know what to do...  Can anybody help me ?

 

Roger

 

Attachment Size
acronissystemreport_2016-07-21.zip 10.23 MB
0 Users found this helpful

I also programmed Acronis to send me an Email about it's operations.  When I terminated the backup, it sent me this:

 

1    True Image    2016-07-21 17:38:02    Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2    True Image    2016-07-21 17:38:02    Operation DisqueD1 started by schedule.

3        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

4        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

5        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

6        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

7        2016-07-21 17:38:02    Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...

8        2016-07-21 17:38:02    Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0

9        2016-07-21 17:38:02    Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0

10        2016-07-21 17:38:02    Fdisk2: Use Disk 3 host= 0 bus = 0 target = 0

11        2016-07-21 17:38:02    Fdisk2: Use Disk 4 host= 0 bus = 0 target = 0

12        2016-07-21 17:38:02    Fdisk2: Use Disk 5 host= 0 bus = 0 target = 0

13        2016-07-21 17:38:02    Fdisk2: Use Disk 6 host= 0 bus = 0 target = 0

14        2016-07-21 17:38:02    Refreshing Drivers...

15        2016-07-21 17:38:02    Enter to process disks in Mbr Driver (id = 17)

16        2016-07-21 17:38:02    Exit from process disks in Mbr Driver (id = 17)

17        2016-07-21 17:38:02    Enter to process disks in Gpt Driver (id = 18)

18        2016-07-21 17:38:02    Try to load Alternate Header from 7814037167

19        2016-07-21 17:38:02    Gpt Disk 8360BC31-ADD2-427D-86F6-1B0DC747551D LBA=7814037167 ALBA=1

20        2016-07-21 17:38:02    try to loading Header from 1

21        2016-07-21 17:38:02    Gpt Disk 8360BC31-ADD2-427D-86F6-1B0DC747551D LBA=1 ALBA=7814037167

22        2016-07-21 17:38:02    Exit from process disks in Gpt Driver (id = 18)

23        2016-07-21 17:38:02    LDM: New ProcessDisks(rawLayer, headLayer)

24        2016-07-21 17:38:02    ProcessDisks: One more disk to check

25        2016-07-21 17:38:02    ProcessDisks: One more disk to check

26        2016-07-21 17:38:02    ProcessDisks: One more disk to check

27        2016-07-21 17:38:02    ProcessDisks: One more disk to check

28        2016-07-21 17:38:02    ProcessDisks: One more disk to check

29        2016-07-21 17:38:02    ProcessDisks: One more disk to check

30        2016-07-21 17:38:02    Mark All groups as Root Like Dgs

31        2016-07-21 17:38:02    ------ Volumes Objects ------

32        2016-07-21 17:38:02    LDM initialization complete

33        2016-07-21 17:38:03    Analyzing partition '0-0'...

34        2016-07-21 17:38:03    Analyzing partition 'C:'...

35        2016-07-21 17:38:03    Analyzing partition '0-0'...

36        2016-07-21 17:38:04    Analyzing partition 'H:'...

37        2016-07-21 17:38:04    Analyzing partition '0-0'...

38        2016-07-21 17:38:04    Analyzing partition 'D:'...

39        2016-07-21 17:38:04    Analyzing partition '0-0'...

40        2016-07-21 17:38:05    Analyzing partition 'G:'...

41        2016-07-21 17:38:05    Analyzing partition '0-0'...

42        2016-07-21 17:38:05    Analyzing partition 'F:'...

43        2016-07-21 17:38:05    Analyzing partition '0-0'...

44        2016-07-21 17:38:06    Analyzing partition 'I:'...

45    True Image    2016-07-21 17:38:06    Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

46    True Image    2016-07-21 17:38:06    Operation: Backup

47    True Image    2016-07-21 17:38:06    Priority changed to Low.

48        2016-07-21 17:38:31    Locking partition D:...

49    True Image    2016-07-21 17:38:41    Create Backup Archive From:   D:\Data II\

D:\Finances\

D:\Logiciels Installations\

D:\Mes documents\

D:\Mes images\

 To file: "DisqueD1_full_b2_s1_v1.tib" Compression:    Normal Exclude:              System files 

50    True Image    2016-07-21 17:38:44    Priority changed to High.

51    True Image    2016-07-21 17:38:49    Writing full version to file: DisqueD1_full_b2_s1_v1.tib

52    True Image    2016-07-21 19:34:33    The quotas are violated.

53    True Image    2016-07-21 19:34:33    The quotas are violated.

54    True Image    2016-07-21 19:34:33    Target drive is running out of space.

Delete unnecessary files or choose another archive location.: ⎂Ignore//⎂Cancel//

55    True Image    2016-07-21 19:53:12    Target drive is running out of space.

Delete unnecessary files or choose another archive location.: ⎂Ignore//⎂Cancel//: User response: ⎂Cancel

56        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=2

57        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=1

58        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=4

59        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=2

60        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=1

61        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=3

62        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=4

63        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=3

64    True Image    2016-07-21 19:53:15    Terminated by user.

 

Hope it helps...

All I see is that the disk is out of space in your logs:

message=Target drive is running out of space. Delete unnecessary files or choose another archive location.:

Could you post some screen shots of your backup settings and cleanup rules?  

You probably have them correct.  HOWEVER... once you make a backup task and the first backup runs, if you go back and change the task in anyway and save the changes, that resets the backup chain count.  So... if your first full ran and before the next incremental ran, you went back in and changed something and saved, you'll end up with another full.  Do it again and you'll get another full.  Long story short, try not to change backup settings after it's been configured unless you really need to.  YOu can, but this is the behavior you get.

2nd, cleanup only occurs after the number of set version chains completes.  Technically, you have not completed any version chain since no incrementals have kicked off.  Cleanup will occur when the version chain is complete (1 full + 3 incrementals) and after the next full backup completes.  In your case, this may be a tough squeeze on your drive since you're backing up 1.3TB to start, and not sure how much each incremental will be.  Let's assume it's not much though, but you'll need a bare minimum of 2.6TB just to get through one version chain if there are no changes in any of the incrementals... that's not likely, so let's estimate 3TB.  On a 4TB drive, that doesn't leave a lot of room - although should be enough if your incrementals aren't too big and you stick to 1 version chain to keep.

So, go ahead and post some screenshots just to verify your settings.  If all is well, I would suggest deleting the backup tasks and all existing backups.  Create a new task exactly as you want it, save and run a full backup and don't mess with the script settings again after that.  You should get an incremental 3 more times and after the next full then runs, then the first full and 3 incrementals will clean up.

OK, I've put 3 screen shots of my settings.  On the target drive, there is nothing else than the Acronis backup.  It's it sole purpose.

I understand that I shoud delete the backup in Acronis True Image 2016 and manually delete the existing backup files on my hard drive, correct ?  I would have thought that deleting the backup procedure in Acronis True Image would have deleted the associated files with it but it seems not to be the case.

On this PC, I have five hard drives and a CD-ROM.  The drive 0 is a SSID drive and the others standard Western Digital Hard drives from 4 Tb to 1 Tb.

Thank you for your help. 

 

Roger

Attachment Size
377342-131857.jpg 391.32 KB
377342-131860.jpg 446.49 KB
377342-131863.jpg 429.09 KB

Can you tell me also how to proceed to delete the the backup tasks and all existing backups ?  I wnat to do it correctly and not create more problems for the future backups.

Thanks again.

 

Roger

To the right of your backup task name is a dropdown arrow.  To delete the task and associated backup files, you click that and select delete and then "whole backup".  That should kill the task and associated backups.  Afterwards, if any exist though, you can manually delete those too.  Normally, this method should delete everything associated with the backup, but as there is some problem occurring with this task, it's possible it won't, but most likely will.

When you setup the new backup task, use a new unique name (just change it to something else   -  perhaps add a 2 or something to the end if you want to keep the basic name though).  For each backup task you create, put it in its own folder.  You can have one primary backup folder if you like, but use a different folder inside of it for each backup task to keep them seperate as this is cleaner and may help with overall stability. 

Please make sure that all system drives have a unique drive letter.  A common issue is that Windows may automatically reassign a drive letter for a drive if unplugging and plugging in different drives.  For instance, if you plug in a new external drive and the next avaialble drive letter is D: it will get D: this time.  However, if you unplug it and plug in a new external drive, that will then get D:.  Plug in the first one now and the first one will become E: as assigned by Windows.  This will break your backup tasks.  To avoid this, you can manually assign driver letters further down the alphabet so that they don't get a random letter if another drive already has that letter when it's automatically plugged in.

Start your new backup task, get it set correctly from the start.  Your settings look fine.  Just don't modify it once the backups have started as that will reset teh version chain count and prevent the cleanup task from working until the version chain can complete.  Each time you modify the task and save it, the version chain resets the count.  As long as you leave it alone, you won't have to worry about this and cleanup will occur as expected. 

Proceeded as suggested and waiting for results till next backups.  Thanks again for your help.

 

Roger

Sure thing.  Keep us posted.  

Well it would seem that my Acronis software is Jinxed...

I've joined a file that show what the results were as of yesterday.  This result is incomprehensible to me because it does not respect the options programmed.

This time I did not modify any options once the backeup had started and this is the result.  I also receive an Email from the system:

1    True Image    2016-07-21 17:38:02    Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2    True Image    2016-07-21 17:38:02    Operation DisqueD1 started by schedule.

3        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

4        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

5        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

6        2016-07-21 17:38:02    AcronisLRPCConnect::BEGIN

7        2016-07-21 17:38:02    Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...

8        2016-07-21 17:38:02    Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0

9        2016-07-21 17:38:02    Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0

10        2016-07-21 17:38:02    Fdisk2: Use Disk 3 host= 0 bus = 0 target = 0

11        2016-07-21 17:38:02    Fdisk2: Use Disk 4 host= 0 bus = 0 target = 0

12        2016-07-21 17:38:02    Fdisk2: Use Disk 5 host= 0 bus = 0 target = 0

13        2016-07-21 17:38:02    Fdisk2: Use Disk 6 host= 0 bus = 0 target = 0

14        2016-07-21 17:38:02    Refreshing Drivers...

15        2016-07-21 17:38:02    Enter to process disks in Mbr Driver (id = 17)

16        2016-07-21 17:38:02    Exit from process disks in Mbr Driver (id = 17)

17        2016-07-21 17:38:02    Enter to process disks in Gpt Driver (id = 18)

18        2016-07-21 17:38:02    Try to load Alternate Header from 7814037167

19        2016-07-21 17:38:02    Gpt Disk 8360BC31-ADD2-427D-86F6-1B0DC747551D LBA=7814037167 ALBA=1

20        2016-07-21 17:38:02    try to loading Header from 1

21        2016-07-21 17:38:02    Gpt Disk 8360BC31-ADD2-427D-86F6-1B0DC747551D LBA=1 ALBA=7814037167

22        2016-07-21 17:38:02    Exit from process disks in Gpt Driver (id = 18)

23        2016-07-21 17:38:02    LDM: New ProcessDisks(rawLayer, headLayer)

24        2016-07-21 17:38:02    ProcessDisks: One more disk to check

25        2016-07-21 17:38:02    ProcessDisks: One more disk to check

26        2016-07-21 17:38:02    ProcessDisks: One more disk to check

27        2016-07-21 17:38:02    ProcessDisks: One more disk to check

28        2016-07-21 17:38:02    ProcessDisks: One more disk to check

29        2016-07-21 17:38:02    ProcessDisks: One more disk to check

30        2016-07-21 17:38:02    Mark All groups as Root Like Dgs

31        2016-07-21 17:38:02    ------ Volumes Objects ------

32        2016-07-21 17:38:02    LDM initialization complete

33        2016-07-21 17:38:03    Analyzing partition '0-0'...

34        2016-07-21 17:38:03    Analyzing partition 'C:'...

35        2016-07-21 17:38:03    Analyzing partition '0-0'...

36        2016-07-21 17:38:04    Analyzing partition 'H:'...

37        2016-07-21 17:38:04    Analyzing partition '0-0'...

38        2016-07-21 17:38:04    Analyzing partition 'D:'...

39        2016-07-21 17:38:04    Analyzing partition '0-0'...

40        2016-07-21 17:38:05    Analyzing partition 'G:'...

41        2016-07-21 17:38:05    Analyzing partition '0-0'...

42        2016-07-21 17:38:05    Analyzing partition 'F:'...

43        2016-07-21 17:38:05    Analyzing partition '0-0'...

44        2016-07-21 17:38:06    Analyzing partition 'I:'...

45    True Image    2016-07-21 17:38:06    Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

46    True Image    2016-07-21 17:38:06    Operation: Backup

47    True Image    2016-07-21 17:38:06    Priority changed to Low.

48        2016-07-21 17:38:31    Locking partition D:...

49    True Image    2016-07-21 17:38:41    Create Backup Archive From:   D:\Data II\

D:\Finances\

D:\Logiciels Installations\

D:\Mes documents\

D:\Mes images\

 To file: "DisqueD1_full_b2_s1_v1.tib" Compression:    Normal Exclude:              System files 

50    True Image    2016-07-21 17:38:44    Priority changed to High.

51    True Image    2016-07-21 17:38:49    Writing full version to file: DisqueD1_full_b2_s1_v1.tib

52    True Image    2016-07-21 19:34:33    The quotas are violated.

53    True Image    2016-07-21 19:34:33    The quotas are violated.

54    True Image    2016-07-21 19:34:33    Target drive is running out of space.

Delete unnecessary files or choose another archive location.: ⎂Ignore//⎂Cancel//

55    True Image    2016-07-21 19:53:12    Target drive is running out of space.

Delete unnecessary files or choose another archive location.: ⎂Ignore//⎂Cancel//: User response: ⎂Cancel

56        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=2

57        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=1

58        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=4

59        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=2

60        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=1

61        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=3

62        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=4

63        2016-07-21 19:53:15    ServerLRPC::_CloseConnection id=3

64    True Image    2016-07-21 19:53:15    Terminated by user.

 

When I saw that it did not behave normally, I cancelled the backup procedure.

I'm at a loss on what to do next other than throw away this ... software.

 

Roger

Attachment Size
377826-131941.jpg 496.24 KB

Roger, I have been able to reproduce the "message=The quotas are violated.; " on my own system but only by making a change to the Notifications page and setting the option for "Show notification message on insufficient free disk space" to Notify me when free disk space is less than: xx GB.

From your earlier Acronis System Report data, you have this setting to Notify you when free disk space is less than 100MB - which is the default value.  The fact that this is issuing this notification confirms that free space is the real issue here.

Your latest screen shot of the backup archive files show that your full backup images are each over 840GB in size being written to your drive F: which shows a max size of 1.8TB but at the time of the system report had only around 700GB free space.  Your incremental backup scheme settings show you are trying to keep 3 version chains, so would need 3 x 840GB free space to hold just the full backup version images.

There is a further indication of error handling in play when I look at the time stamps for your incremental backup files, where these are being written approximately every 12 minutes rather than just twice a week as per your schedule settings.

You will need to either write these backups to a different, larger backup drive, or else change your auto-cleanup / retention values to allow your backups to fit on the existing drive, but bearing in mind that auto-cleanup only runs when the next full backup version has been created successfully, thus you would need to set the backup scheme options to Store no more than 1 recent version chains!

Roger_B wrote:

...I have about 1,3 Tb of data on a 4 Tb drive that I want to backup on a 2 Tb drive on my PC.

All the comments and recommendations from fellow MVPs are right, from my point of view.

However, I think your destination disk is still too small for a destination backup. If you had the 2TB backing up to the 4TB, I'd understand. Remember that you don't get to use the full 2TB, but only a portion of it because of NTFS volume information. BTW, make sure you don't have windows shadow files copies on that disk (turn off the system protection for that disk).

Consider the content that you have. If most of the content rarely changes (videos, photos, music files), you can back them up with a sync, a simple copy and/or windows file history (this backup system doesn't comress files, but rename them in the backup destination. So restoring a single file is really easy). Then you use ATI only for the system and application data. This may lead to a much smaller backup.

If you have video games as apps and you want to back this up with other apps, and or you have large changing files (like PST files, database files) then you don't have much options. You will be able to store one full and maybe a couple of incremenetals, and then you will run out of space.

Ok, I will try to backup only my data that is "alive" and try to store the dead data elsewhere.

Good suggestion.

But don't you find it curious the way ATI created the backup files in the first place ?   Two main backupups and two times seven increments in about 5 hours...  Isn't it looking more like a problem with the time on the computer ?  Actually the internal clock of the PC under Windows 7 is synchroized with time.nist.gov.  Would it be possible that this information gets corrupted and creates the problem that we witnessed ?  Just a though...

 

I will keep you posted on the results of my experiment  (I feel like Dr Frankenstein...).  Ok, you're not my Igors but my fellow collegues.

 

Good night...

 

Yes, well I have to admit I didn't look at your picture of the create files.

Definitely something wrong with that. I would uninstall ATI, reboot the computer, reboot, reinstall and start new backup tasks. You could also try to evaluate and fix the ATI schedule tasks using the Acronis schedule manager. But uninstalling/reinstalling might just be faster and easier.