Acronis 12 update 3 - missing promised fix.
Hi, I thought you had confirmed that the "Applying Retention Rules" issue was going to be fixed in this update. This means I still need to micro-manage my backups each day to cancel this part of a backup job. I tried the Disk/Volumes backup workaround but get the same issue when applying retention rules.. ANy news when this will be fixed please?
Hi Mark,
I have double-checked and the bug ABR-109508 which I referred to in the thread you mention was indeed fixed in Acronis Backup 12 Update 3 which was released recently (build #3689). If you still encounter some issues after the update, then they should be investigated separately as they are likely related to a different problem. Can you please attach a log file from hanging "applying retention rules" activity? Have you contacted our support team for assistance with the issue?
Thank you.
The fix isn't mentioned in the release notes, unless I am being silly and cannot see it?
http://dl.managed-protection.com/u/backup/rn/12/user/en-US/AcronisBacku…
Attached a log as requested.
Hi Mark,
Yes, the fix is not mentioned in the release notes, since the bug was not marked to be "relnoted", but still the fix is present in build #3689. According to your log file the backup is performed by agent which is still on old build #3602:
| error 0x70022: Operation canceled by user.
| line: 0xa65ac6a07015b095
| file: k:\3602\resizer\backup\clone.cpp:1595
| function: resizer::BackupImageReaderImp::ClonePoints
| $module: disk_bundle_vsa64_3602
Secondly - you are cancelling retention rules for disk/volume backup, while the fix is applicable to files/folders backup type, so if this activity really hangs then it's a completely different issue (I assume you've switched to disk/volumes backup after following recommendations from my comments in the thread you refer to).
Basing on the current situation I'd suggested the following:
0) Update the backup agent to 3689 build
1) Try to run the plan and let the clean up activity to run until it is finished (failed or successful) - since you're able to cancel the clean up activity - this means that it doesn't hang and does something. It may take some time to run this activity due to previous cancellation attempts (try not to cancell it this time).
2) If the above doesn't help then edit the backup plan and point it to a new folder (subfolder on existing network share). This would allow to eliminate possibility of traces left from multiple previous backup consolidation cancellation activities (since you've cancelled manually the clean multiple times before)
3) Let the backup plan full run and check how retention rules are applied once they become in play _without_ cancelling them.
If the above doesn't help then the problem investigation should be continued with help from our support team (since the problem is definitely unrelated to the originally mentioned bug).
Thank you.