Skip to main content

Issue related with backup (VSS)

Thread needs solution
Beginner
Posts: 1
Comments: 4

Hello All!

I cannot do a backup using Acronis True Image 2019, because I have these errors.

08/02/2019 20:30:20: +01:00 13932 I00000000: -----
08/02/2019 20:30:20: +01:00 13932 I00000000: ATI Demon started. Version: 23.4.1.14690.
08/02/2019 20:30:20: +01:00 13932 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08/02/2019 20:30:20: +01:00 13932 I00640002: Operation MACJORGE started manually.
08/02/2019 20:30:21: +01:00 13932 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08/02/2019 20:30:21: +01:00 13932 I013C0000: Operation: Backup
08/02/2019 20:30:21: +01:00 13932 I0064000B: Priority changed to Low.
08/02/2019 20:30:22: +01:00 13932 I000B03F0: Create Backup Archive From: To file: D:\Backup_Acronis\MACJORGE.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Jorge\AppData\Local\Temp, C:\Users\Jorge\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Jorge\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Jorge\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Jorge\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Jorge\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Jorge\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC
08/02/2019 20:30:22: +01:00 13932 I000101F8: Pending operation 173 started: 'Creating partition image'.
08/02/2019 20:30:22: +01:00 12368 I00640000: Writing full version to file: MACJORGE_full_b1_s1_v1.tib
08/02/2019 20:30:23: +01:00 13932 I000101F8: Pending operation 173 started: 'Creating partition image'.
08/02/2019 20:30:23: +01:00 13932 E000101F6: Error 0x101f6: Unable to create volume snapshot
| trace level: error
| line: 0x65b5eb7011094703
| file: c:\bs_hudson\workspace\646\processor\diskadm\da_commit.cpp:348
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094703, c:\bs_hudson\workspace\646\processor\diskadm\da_commit.cpp:348, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_14690
|
| error 0x70021: Unable to create volume snapshot
| line: 0xdf81da2c74ec50d5
| file: c:\bs_hudson\workspace\646\core\resizer\backup\output_stream.cpp:275
| function: `anonymous-namespace'::OutputStreamImpl::SetBitmap
| line: 0xdf81da2c74ec50d5, c:\bs_hudson\workspace\646\core\resizer\backup\output_stream.cpp:275, `anonymous-namespace'::OutputStreamImpl::SetBitmap
| $module: ti_demon_vs_14690
|
| error 0x10c44e: Failed to set snapshot bitmap.
| line: 0x3fec04e376b89f58
| file: c:\bs_hudson\workspace\646\core\fdisk\win_snapshot.cpp:610
| function: win_snapshot_volume::SetBitmap
| line: 0x3fec04e376b89f58, c:\bs_hudson\workspace\646\core\fdisk\win_snapshot.cpp:610, win_snapshot_volume::SetBitmap
| blocks: 0x0
| $module: ti_demon_vs_14690
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: c:\bs_hudson\workspace\646\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\646\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x57
| $module: ti_demon_vs_14690
|
| error 0xfff0: El parámetro no es correcto
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\646\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\646\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070057
| $module: ti_demon_vs_14690
08/02/2019 20:30:23: +01:00 13932 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcebf
| file: c:\bs_hudson\workspace\646\products\imager\demon\main.cpp:713
| function: main
| line: 0x9f2c53c72e8bcebf, c:\bs_hudson\workspace\646\products\imager\demon\main.cpp:713, main
| $module: ti_demon_vs_14690

Start: 08/02/2019 20:30:20
Stop: 08/02/2019 20:30:23
Total Time: 00:00:03

 

Also, VSS Doctor show me this: Failed to collect VSS writers status:

vssadmin 1.1 - Herramienta administrativa de línea de comandos del Servicio de instantáneas de volumen.
(C) Copyright 2001-2013 Microsoft Corp.

Nombre de editor: 'Task Scheduler Writer'
   Id. de editor: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Id. de instancia de editor: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'VSS Metadata Store Writer'
   Id. de editor: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Id. de instancia de editor: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Performance Counters Writer'
   Id. de editor: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Id. de instancia de editor: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'System Writer'
   Id. de editor: {e8132975-6f93-4464-a53e-1050253ae220}
   Id. de instancia de editor: {857fd4e3-b0b7-4949-8f26-77286aa52d9b}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'ASR Writer'
   Id. de editor: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Id. de instancia de editor: {b4e04ef4-7a04-4c89-94e4-381564b707ae}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Shadow Copy Optimization Writer'
   Id. de editor: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Id. de instancia de editor: {307de840-3c79-4acb-ac16-2aa122898754}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'WMI Writer'
   Id. de editor: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Id. de instancia de editor: {65f74094-41c2-401c-b27a-69df6934a9bb}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Registry Writer'
   Id. de editor: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Id. de instancia de editor: {cb296ca3-5ae5-439a-a205-230aadcea4c5}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'COM+ REGDB Writer'
   Id. de editor: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Id. de instancia de editor: {026c67f2-e8ab-47af-9ad4-5c6623da9ec4}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'MSSearch Service Writer'
   Id. de editor: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Id. de instancia de editor: {2cff34da-f179-4771-8d57-ab9ae89d6692}
   Estado: [1] Estable
   Último error: Sin errores

 

Where is the problem?

I am using Windows 10 Pro x64 and I have checked my hard disk in Windows and is OK (SO hard disk and destination hard disk).

 

Thank you very much in advance.

0 Users found this helpful
Legend
Posts: 79
Comments: 16784

Welcome to these public User Forums.

What does the full VSS Doctor log show?  Can you attach the log as a text file?

Does VSS Doctor offer you any options to Fix any problems found?

What are the sizes of your Source and Destination drives and how much free space is available on each?

Are both disks local to the computer or is the destination disk an external or a network mapped drive?

Has ATI 2019 been working correctly to make backups previously or has it never worked correctly?

Forum Hero
Posts: 66
Comments: 7760

Not sure, but have seen issues when there is not enough room on a partition to cache the VSS operation. 

As a quick and easy try, go to system protection and disable it on your OS drive. Then move the percentage to 10 or 15% and re-enable again. This will wipe out recovery points, but you can manually make one right then again if desired. This alone may be enough though. I'd also reboot for good measure.

Then see if the error persists or not. 

If still there, open an admin command prompt (tight click and run as administrator even if using an admin account). Type

Vssadmin

Vssadmin delete shadows /all

Vssadmin list writers

and check for any errors. If you find any, report back.

Another alternative is to go into the backup task configuration and under the advanced tab you can switch between VSS with writers or without writers. Not sure what the default is, but switch to the other (I'm on a phone without access to check). 

Beginner
Posts: 1
Comments: 4

Hello all.

Thanks for the fastly answers.

My computer is a Macbook Pro 13", and never I have done a backup using Acronis until today. I have done a bootcamp partition for Windows 10.

All works fine except Acronis backup.

The destination disk is external and has available 400 GB (1TB disk), and my internal disk (source disk) takes about 70 GB used and has available 38 GB.

VSS Doctor does not allow me fix anything in this case. I attached its log.

Recovery in Windows is disabled, and I there are not backups to restore Windows.

 

Regarding these commands:

Vssadmin

Vssadmin delete shadows /all

Vssadmin list writers

This is the result:

Vssadmin delete shadows /all:

Microsoft Windows [Versión 10.0.17763.292]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>Vssadmin delete shadows /all
vssadmin 1.1 - Herramienta administrativa de línea de comandos del Servicio de instantáneas de volumen.
(C) Copyright 2001-2013 Microsoft Corp.

Ningún elemento cumple los criterios de la consulta.

C:\WINDOWS\system32>

Vssadmin list writers:

C:\WINDOWS\system32>vssadmin list writers
vssadmin 1.1 - Herramienta administrativa de línea de comandos del Servicio de instantáneas de volumen.
(C) Copyright 2001-2013 Microsoft Corp.

Nombre de editor: 'Task Scheduler Writer'
   Id. de editor: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Id. de instancia de editor: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'VSS Metadata Store Writer'
   Id. de editor: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Id. de instancia de editor: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Performance Counters Writer'
   Id. de editor: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Id. de instancia de editor: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'System Writer'
   Id. de editor: {e8132975-6f93-4464-a53e-1050253ae220}
   Id. de instancia de editor: {857fd4e3-b0b7-4949-8f26-77286aa52d9b}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'ASR Writer'
   Id. de editor: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Id. de instancia de editor: {3e9baa40-8c96-4cd4-b4f5-52ba62bb4a6c}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Shadow Copy Optimization Writer'
   Id. de editor: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Id. de instancia de editor: {9fe875bf-1397-401e-9c30-75d6654f86fb}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'BITS Writer'
   Id. de editor: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Id. de instancia de editor: {df0bba08-ba0e-45ed-9307-2534c84a9f74}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'Registry Writer'
   Id. de editor: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Id. de instancia de editor: {d2b47f81-f506-4bb4-98c5-ca83f58cf3c5}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'COM+ REGDB Writer'
   Id. de editor: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Id. de instancia de editor: {d118b143-5a95-4b18-8a64-2bc8492d52ad}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'WMI Writer'
   Id. de editor: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Id. de instancia de editor: {65f74094-41c2-401c-b27a-69df6934a9bb}
   Estado: [1] Estable
   Último error: Sin errores

Nombre de editor: 'MSSearch Service Writer'
   Id. de editor: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Id. de instancia de editor: {2cff34da-f179-4771-8d57-ab9ae89d6692}
   Estado: [1] Estable
   Último error: Sin errores

C:\WINDOWS\system32>

There are not errors...

Thanks again.

Strange case...

 

 

Attachment Size
488652-163867.txt 12 KB
Legend
Posts: 79
Comments: 16784

Which version of ATI 2019 are you using here?  Is this the ATI 2019 for Mac version, or are you using  ATI 2019 for Windows version?

For a Mac system, any backups should be performed using the ATI 2019 for Mac version, not the Windows one.

Beginner
Posts: 1
Comments: 4

Windows version, because I am using Windows 10.

 

I understand that Mac version is only for MacOS, not?

Forum Hero
Posts: 66
Comments: 7760

I believe that because the hardware is Apple, even though you have boot camp, you should back up the entire disk with the MacOS version because they are tied together by the firmware on the Mac.

I do not think it's possible to just restore the bootcamp partition by itself as you would need to use the Macintosh recovery media and that only allows you to restore the full disk.

https://kb.acronis.com/content/47222

Beginner
Posts: 1
Comments: 4

Ops!!!

Sorry, I had not readen this article.

OK OK. Then I am going to buy Mac edition of ATI 2019.

 

Thanks for all!

Legend
Posts: 79
Comments: 16784

If you have already bought the Windows version of ATI 2019, then you should be able to download the Mac version from your Acronis Account and install it without the need to buy a new version / license.

Forum Hero
Posts: 66
Comments: 7760

Agreed, Steve.

Jorbus,

The license is good for the hardware of any system which means you can run it in multiple Operating Systems -   potentially still usiing it in bootcamp to backup data (perhaps the user profile, or documents, files, etc.). At least then, you'd be able to more easily restore them from within bootcamp if need be.

Beginner
Posts: 1
Comments: 4

OK you are right.

Thank you very much for all!