Backup of VM using vshadow fails if exchange server 2003 is installed in VM (Host OS win2k8 RC2)


hostos:- windows server 2008 rc-2

 

i  have installed exchange server 2003 on vm (win2k3 -sp2).

i tried backup using vshadow tool.

backup of vm fails in running state with error message

 

error: selected writer 'microsoft hyper-v vss writer' in failed state!
   - status: 8 (vss_ws_failed_at_prepare_snapshot)
   - writer failure code: 0x800423f3 (<unknown error code>)
   - writer id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   - instance id: {f626102c-c846-4b9a-8f6a-b8f76db34636}

 

in paused state backup works properly. idea reason?


 

fyi:- screen display

 

c:\program files (x86)\microsoft\vsssdk72\testapps\vshadow\x64\release x64>vshadow.exe  -bc=pg.xml -p c:\

vshadow.exe 2.2 - volume shadow copy sample client
copyright (c) 2005 microsoft corporation. rights reserved.


(option: saving xml file 'pg.xml')
(option: persistent shadow copy)
(option: create shadow copy set)
- setting vss context to: 0x00000009
(gathering writer metadata...)
(waiting asynchronous operation finish...)
initialize writer metadata ...
discover directly excluded components ...
- excluding writer 'bits writer' since has no selected components restore.
- excluding writer 'shadow copy optimization writer' since has no selected components restore.
discover components reside outside shadow set ...
discover excluded components ...
discover excluded writers ...
discover explicitly included components ...
verifying explicitly specified writers/components ...
select explicitly included components ...
 * writer 'system writer':
   - add component \system files
 * writer 'microsoft hyper-v vss writer':
   - add component \backup using saved state\3ea0d102-acb8-47e7-bf78-0a1ac39f95c9
   - add component \backup using child partition snapshot\89204272-ac38-443d-994d-9e495b3362cd
   - add component \backup using child partition snapshot\fddc4fc6-46d3-4664-bec
f-8347280be3b9
 * writer 'asr writer':
   - add component \asr\asr
   - add component \volumes\volume{3a59a31f-b4dc-11dc-835b-001aa00b616e}
   - add component \volumes\volume{4e116049-b4c6-11dc-bdba-806e6f6e6963}
   - add component \bcd\bcd
   - add component \disks\harddisk0
   - add component \disks\harddisk1
   - add component \disks\harddisk2
   - add component \disks\harddisk3
 * writer 'registry writer':
   - add component \registry
 * writer 'com+ regdb writer':
   - add component \com+ regdb
 * writer 'wmi writer':
   - add component \wmi
creating shadow set {d8302635-0d1f-480b-9853-196a6ba84c23} ...
- adding volume \\?\volume{4e116049-b4c6-11dc-bdba-806e6f6e6963}\ [c:\] s
hadow set...
preparing backup ...
(waiting asynchronous operation finish...)
(waiting asynchronous operation finish...)
creating shadow (dosnapshotset) ...
(waiting asynchronous operation finish...)
(waiting asynchronous operation finish...)

error: selected writer 'microsoft hyper-v vss writer' in failed state!
   - status: 8 (vss_ws_failed_at_prepare_snapshot)
   - writer failure code: 0x800423f3 (<unknown error code>)
   - writer id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   - instance id: {f626102c-c846-4b9a-8f6a-b8f76db34636}

thanks,

prashant

i going doing testing vss week , try repro of this.

 

thank report.

 



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS