No automatic delete when destination folder is full

Hello Dean,

Thank you for finding time to open the thread regarding this issue, I will be glad to help you.

First of all, please notice that the build you're using is an outdated one.

Please install the latest update according to these instructions, and check whether the issue remains. Should it be present, please gather Acronis Info, submit a case with the information attached, and let us know its number.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

Did you explicitly set retention rules to perform cleanup?

As per Dev had reported. I would suggest checking your cleanup rules for your backups job... Also I find an option allot of people miss is the one WHEN to apply the cleanup rules (Eg, before a backup, after a backup or on schedule..etc..etc).. You have to select something else the clean up rules will never be applied so this might be your issue..

Also ensure you never delete files manually out of a managed vault (it’s only asking for trouble).. let Acronis manage the backups and setup the rules correctly and you should be good...

I would also strongly take Yana’s advice and update to the latest ABR10 build as there has been many fixes/updates done since the version you have which is basically a very early ABR10 release, I’m sure the details that have been posted above and by others will fix your issues.

Data said:

"As per Dev had reported. I would suggest checking your cleanup rules for your backups job... Also I find an option allot of people miss is the one WHEN to apply the cleanup rules (Eg, before a backup, after a backup or on schedule..etc..etc).. You have to select something else the clean up rules will never be applied so this might be your issue.."

I checked, and the "Clean up archive" setting is "When there is insufficient space while backing up".

I've upgraded to version 10.0.13545 this week, so we'll see how it goes at the next scheduled backup this weekend.

Thanks for your tips, everyone.

Dean

Well, I upgraded to 10.0.13545, and the problem still exists.

I've attached a snapshot of the backup plan.

Here's what the log says:

Log Entry Details

------------------------------------------------------------------------------------------------------------------------------------------------------------------

Type:          Information

Date and time: 7/25/2011 9:13:45 AM

Backup plan:   Backup 3/3/2011 3:37:55 PM

Task:          Differential backup

Code:          262,148(0x40004)

Module:        4

Owner:         dpm@dpm-xp

Message:       

  There is not enough space in the backup destination.

Free up additional disk space to continue. You can either empty the Recycle Bin or delete old data files.

Click Retry to try again or click Cancel to cancel the operation.: User response: Cancel

------------------------------------------------------------------------------------------------------------------------------------------------------------------

Have I missed anything?  Where do I go from here?

Thanks for your advice.

dpm

Apparently this is the case (userguide 6.2.10.6) , "Clean up archive" row of the table -
> If there is only one full backup left, and an incremental or differential backup is in progress, an error occurs saying there is a lack of available space

Probably you need to put some full backups to have several chains. By schedule, or triggered somehow by a script (e.g. generating windows event+scheduled by windows event when free space is nearing expected full backup size). Or even less than expected full backup size - even if full backup doesn't fit, it will delete previous chain because it will be the full backup that is in progress

dev-anon,

How about specifying retention rules? Say, I specify a maximum archive size (I use differential backup, so I assume the size is that of the full plus the differentials), and apply the rules before the scheduled backup?

Thanks,
dpm

May be. However note that infinite set of incrementals where the first full is always kept, and the older differential are removed, will over time have the size of differentials. If you chose to consolidate instead of remove, it will require a free space of the size of the consolidated full backup, that it will create before removing old backups.