Skip to main content

Backup fails everytime - Outlook data files locked?

Thread needs solution

We use Acronis TrueImage 2018 as one level of backup on our small office's workstations, running Win10 Pro and MS Office 2013 Pro. We do full system images once a week and daily incremental document backups. We updated our Act! contact manager last week and backups have failed repeatedly since then. We get daily error messages to the effect of:

[WORKSTATION] files task is waiting for user interaction.

Description:

Information: Failed to back up file or folder 'XXXXXXX@XXXXXXX.com.pst'. It may be blocked by another application.

Details:

This happens for each workstation. However, when I use Powershell to check for what process is locking the Outlook data file, nothing shows up. Act! does integrate with Outlook, but there is no sign that it has locked the file--I can exit Act! and close all of its services and backup still fails.

I also get a very long, more detailed error report, which starts like this:

2018-12-05T13:27:24:114-05:00 13144 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2018-12-05T13:27:24:115-05:00 13144 I00640002: Operation [WORKSTATION] encrypted files started manually.
2018-12-05T13:27:25:668-05:00 13144 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2018-12-05T13:27:25:672-05:00 13144 I013C0000: Operation: Backup
2018-12-05T13:27:25:674-05:00 13144 I0064000B: Priority changed to Low.
2018-12-05T13:28:53:196-05:00 13144 W013C0014: Error 0x13c0014: VSS retry: 1
| trace level: warning
| line: 0xd8b61c024c929575
| file: c:\bs_hudson\workspace\431\products\imager\demon\app.cpp:1004
| function: TiDemonDaCommit::OnVssRetryableCallback
| line: 0xd8b61c024c929575, c:\bs_hudson\workspace\431\products\imager\demon\app.cpp:1004, TiDemonDaCommit::OnVssRetryableCallback
| $module: ti_demon_vs_12510
|
| error 0x10c442: Failed to start creating the volume snapshot.
| line: 0x3fec04e376b8a1fd
| file: c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:1287
| function: win_snapshot_core::CallSbLock
| line: 0x3fec04e376b8a1fd, c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:1287, win_snapshot_core::CallSbLock
| $module: ti_demon_vs_12510
|
| error 0x10c46b: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
| line: 0x3fec04e376b89d87
| file: c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:145
| function: `anonymous-namespace'::ObtainVSSFailReasonSuberror
| line: 0x3fec04e376b89d87, c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:145, `anonymous-namespace'::ObtainVSSFailReasonSuberror
| $module: ti_demon_vs_12510
|
| error 0xfff0
| line: 0xbd28fdbd64edb8fb
| file: c:\bs_hudson\workspace\431\core\common\error.cpp:317
| function: Common::Error::AddHResult
| line: 0xbd28fdbd64edb8fb, c:\bs_hudson\workspace\431\core\common\error.cpp:317, Common::Error::AddHResult
| code: 0x800423f4
| $module: ti_demon_vs_12510
2018-12-05T13:30:37:003-05:00 13144 W013C0014: Error 0x13c0014: VSS retry: 2
| trace level: warning
| line: 0xd8b61c024c929575
| file: c:\bs_hudson\workspace\431\products\imager\demon\app.cpp:1004
| function: TiDemonDaCommit::OnVssRetryableCallback
| line: 0xd8b61c024c929575, c:\bs_hudson\workspace\431\products\imager\demon\app.cpp:1004, TiDemonDaCommit::OnVssRetryableCallback
| $module: ti_demon_vs_12510

...

Any help would be appreciated.

Also, it's pretty crappy that TrueImage 2018 is not supported anymore. We bought 4 licenses 8 months ago, and now I can't submit a support ticket just because another version was released? Geez, 8 months to obsolescence is even worse than Apple. So much for a "perpetual" license.

 

 

0 Users found this helpful

Jon, welcome to these public User Forums.

We do full system images once a week and daily incremental document backups. We updated our Act! contact manager last week and backups have failed repeatedly since then.

Do your full system image backups also fail or do they succeed?

What happens if you try creating a new Files & Folders backup task for the same Outlook .PST files?  Does this also fail with the same issue?

The error messages suggest that VSS is not able to lock the files for the snapshot to capture them which in turn suggests a permissions type issue here.

You have the option here of trying a different snapshot method for your backup task - go to the Options > Advanced page for the task, then look at the Performance settings at the bottom of the page where you can select the snapshot method.

2018-12-07 Performance VSS.png

Also, it's pretty crappy that TrueImage 2018 is not supported anymore. We bought 4 licenses 8 months ago, and now I can't submit a support ticket just because another version was released? Geez, 8 months to obsolescence is even worse than Apple. So much for a "perpetual" license.

It is a whole lot better than the previous 30-days of support from date of purchase that Acronis gave with earlier versions of ATI.  Users now get up to around 13 months of free support depending on when they purchase a perpetual license, where this is for 12 months plus 1 month after the next version has been released on sale.

Your perpetual license just means that ATI will continue working for as long as your version of Windows OS will allow it to do so, hence there are users in these forums still posting for their ATI 2010 perpetual licensed product.  If you want continual support from Acronis then they offer a subscription license you can purchase which gives that level of support along with free upgrades to new versions for as long as the subscription is maintained.

Thank you, Steve. Changing the snapshot method from 'VSS without writers' to 'Acronis snapshot' worked. ('VSS' alone did not.) It was a bit of a process of discovery, since when I would start ATI the backup would always be in process but stalled. Pressing STOP did nothing, the program would just hang indefinitely. I followed other forum posts and used the Scheduler Manager app. It would be nice if Acronis put some attention to making the STOP button work properly.

Thanks for clarifying the support policy. The official Acronis website is pretty opaque about support.

Jon, good to hear that changing the snapshot settings have resolved this for you, thanks for taking time to give the feedback.