Forum Discussion
Further investigation through other posts about a similar issue say a error should be present with VOLUME_NOT_FOUND.
I checked for this specific error in the log and this points to:
BEREMOTE: [09-25-14 10:36:08] [11884] 2014-09-25T10:35:52.229 [fsys\shadow] - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) for object 'System Files'. Faild to resolve volume path name for 'd:\unit4\bin\' in SHADOW::SetSelectedForBackup
BEREMOTE: [09-25-14 10:36:08] [11884] 2014-09-25T10:35:52.229 [fsys\shadow] - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) returned setting selected for backup for object System Files in SHADOW::AddToSnapshotSet
BEREMOTE: [09-25-14 10:36:08] [11884] 2014-09-25T10:35:52.237 [fsys\systemstate] - AD:Trouble adding to set - Status E_FS_VOLUME_NOT_FOUND (0xE0000352) in SystemState::AddToSnapshotSet:566
It's refering to a volume with letter D:\ but that does not exist on the server.
Would this "d:\unit4\bin\"be the binary path I need to exclude in the KB you provided @VJware ?
Or another way to edit this image path?
Thanks.
Related Content
- 16 years ago