Aller au contenu principal

Acronis 2021 Automatic Old Version Cleanup Fails

Thread needs solution

I previously posted about this issue, and the suggestion was instead of using space as a limiting criteria, I change to using the number of backup versions.  OK, I did that, and it still fails.

I've attached the errors returned when the job runs.  I tried to save a screenshot of the configuraiton in PNG and JPG format, but I get an error that the file can't be uploaded.

The parameters are set as DIFFERENTIAL backup, crease a full version after every 6 differential versions, and store no more than 4 recent version chains.

Fichier attaché Taille
Acronis Error.txt 2.08 Ko
0 Users found this helpful

John, the log shows the error:

Error 0x4001d: The quotas are violated.

Please check the Notifications page for your backup task settings and see if you have set the option at the top of the page for:

Show notification message on insufficient free disk space

Notify me when free disk space is less than: xxx  MB/GB/TB

This setting can cause this type of quota error.

If you haven't set the above option, then more information is needed, i.e. how many files have been created, of what sizes, how much free space is available on the storage drive etc?

The option does work John but not always as users expect it to do!  If you have it enabled, then try disabling it and see if the quotas error is resolved.

I guess I don't understand Steve.  I have plenty of room on the backup drive, hundreds of gigabytes.  The limit is set to 50GB.  Why would that come up as a problem?  If the option "works", why would I get the error?

John, if you set the option to 50GB then Acronis immediately subtracts that amount from the available free space of your backup drive then checks whether there is still sufficient space for the size of the backup you are attempting to create?  If not, then you get the quota exceeded error.

I get that Steve, but the full backup is around 35GB, the low limit is set to 50GB, and the backup drive has 369GB free space.  I may not be a math major, but it seems to me that it shouldn't be complaining about the limits!

John, I agree that there shouldn't be an issue given the backup size and free space available after taking into account the value set. 

What does the actual backup log say in terms of any error messages?

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?

The latest version of the new log viewer tool is at the link below.
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.3.2) BETA Version 2.4.0.1 available, see posting below.

If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.

If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.

Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.

The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.

The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.

Well, I apparently solved it.  I turned off all the space management features and just told it to only keep a specific number of old backups for each backup task.  That appears to be working, and it's deleting the oldest backup that exceeds that limit whenever it finishes a run.

I still don't understand why it got confused about space management, but the net result is I can run the automated backups and all is well.

I still have half of my 5TB disk left after the space management, so that should hold me for a lot of growth.  I consider this one solved.