Salta al contenuto principale

ATI 2018 Backup fails due to lack of space - Activity Log Question

Thread needs solution
Beginner
Messaggi: 1
Commenti: 2

I have tried multiple backup schemes, the latest is Full, store no more than two recent versions. I do not have 'Do not delete the first version' selected. It backs up once per week.   The backup size is around 1TB.  My backup drive is 8TB.  ATI just keeps backing up until my backup drive runs out of space and the backup fails.  On checking the Activity Log it reports freeing 20+ TB of space after each backup.  That's correct, it reports it opened up over 20TB of space on a 8TB drive.  I have attached it for reference.  Does this somehow make ATI think it completed its automatic cleanup when it did not? Is this the cause of the insufficient space issues?

Thank you,

Eric Erickson

0 Users found this helpful
Legend
Messaggi: 102
Commenti: 22421

#1

Eric, welcome to these public User Forums.

Just based on the information provided so far, I would suggest that there is a file system issue at work here, i.e. the free space map on one or more of your drives is corrupted or damaged in some way.

Please run CHKDSK /F against all the drives involved in any of your backup tasks, i.e. the Source and Destination drives.
For the Source drive, if this is the C: OS drive, then it will want to schedule the check to run after the computer is restarted.

Beginner
Messaggi: 1
Commenti: 2

#2

Thank you Steve for your reply.  I ran chkdsk /f on my source drives (logical D & G) and destination drive (external hard drive, N).  It reported no errors on any of the drives.  Acronis sent me an email today reporting backup failure due to insufficient space on the destination drive.  I have attached an image of the destination drive.  Is there any other information I can supply?

Eric Erickson

Legend
Messaggi: 102
Commenti: 22421

#3

Eric, sorry but don't see any image per your update above?

I would suggest creating an Acronis System Report zip file and providing a share link to this via a cloud service such as OneDrive, Google Drive etc, then I can take a deeper look for any clues as to what is happening here?

Beginner
Messaggi: 1
Commenti: 2

#4

Hope this is correct Steve.

Eric

https://drive.google.com/file/d/1abkV3DJB_TZVH3We49oQzMicAbWcZtj8/view?usp=sharing

Legend
Messaggi: 102
Commenti: 22421

#5

Eric, thanks for the system report zip file.

I am not seeing any errors being flagged for any of your disk drives which is good.

However, the logs would suggest that there are issues with your D and G backup task to your N: external drive, this is in part due to lack of free space on that drive but also some confusion over the backup scheme.

The backup script for this task shows it as Full backups only but the logs have errors related to Incremental backup files, and these relate to backup sequences which are out of order, i.e. the log is creating D and G_full_b14_s1_v1.tib but is throwing an error for D and G_inc_b20_s6_v1.tib when trying to do automatic cleanup.  This suggests that you have been doing manual file deletions outside of the GUI but have not revalidated the task to reconcile the information held in the internal database for deleted files.

This is where the new 'Clean up versions' tool introduced with ATI 2019 & later versions makes a real difference, as it provides an easier method of removing unwanted files without having this type of issue.

Because you are still running on ATI 2018, then the method that I would recommend you to follow is as below:

  • Delete the current D and G backup task and all of its files. 
    Note: I see that you have another task D and G manual which is making backups to your L: drive that can provide cover while doing the above. 
     
  • Follow the steps in KB 60915: Acronis True Image: repairing program settings - to force a rebuild of the internal database.
     
  • Create a new D and G backup task to your N: drive with the settings wanted.

If you prefer not to do the first step above, then use the Delete option, but take the option to just remove the settings from GUI to keep the files on your N: drive.

After the settings are removed, clean up all unwanted D and G backup files from N: then use the hidden option in the GUI to 'Add existing backup' (click on the caret 'v' to the right of the normal 'Add backup' option) then select the most recent backup file from your N: drive which will create a task in the GUI using that file name.  Rename the task to remove all the extra characters then reconfigure the task settings and either validate or run the task.

Note: I would still recommend forcing a rebuild of the database (as above) after removing the D and G task from the GUI and before adding it back again.  This is to ensure that nothing from the database is carried forward - so starting with a clean database!