Solved

Error Code: [19:857] The job has failed because the VSS snapshot could not be created

  • 26 July 2021
  • 1 reply
  • 230 views

Userlevel 3
Badge +8

We have a media agent that is failing to backup the DDB because the VSS snapshot could not be created

 

We have rebooted the server

The VSS list writers and list providers have no errors

vssadmin list writers

vssadmin list providers

The C drive is not full

Question: Are there any other items I can look at as a possible solution.

 

 

 

 

 

 

 

 

FsBackupCtlr::getTargetVssDestination(11188) - Empty String received from Subclient.getVSSDestination()
4512  698   07/26 15:13:40 60191 FsBackupCtlr::getTargetVssDestination(11190) - TargetDestination to create shadow copy on is []
4512  698   07/26 15:13:40 60191 CFileBackupFSW2K::InitializeOFM(520) - Checking for VSS/QSnap selection
4512  698   07/26 15:13:40 60191 CFileBackupFSW2K::InitializeOFM(595) - Use VSS for local shared write files: 1
4512  698   07/26 15:13:40 60191 CFileBackupFSW2K::InitializeOFM(619) - VSS/QSnap selected
4512  698   07/26 15:13:40 60191 CFileBackupFSW2K::InitializeOFM(633) - Subclient info suggest immediate VSS shadow creation
4512  698   07/26 15:13:40 60191 COpenFileManager::Initialize(82) - Forcing VSS provider auto detect logic for snapshots
4512  698   07/26 15:13:40 60191 ClBackupLibUtils::GetVolumeListFromFile(43) - Getting list of volumes to snap from [C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\iDataAgent\FileSystemAgent\2\62\scannedVolList.cvf]
4512  698   07/26 15:13:40 60191 COpenFileManagerDDB::CreateShadow1(606) - Shadow volume map not found, so change journal was used for scan and shadow will be created now
4512  698   07/26 15:13:40 60191 CVSSClientBase::Init() - Cluster State=[0] Ret=[0]
4512  698   07/26 15:13:40 60191 CsVolumeList::Add() - Added [F:\] to volume list
4512  698   07/26 15:13:40 60191 CsVssAsync::WaitUntilDone() - Waiting asynchronously for [VSS-Wait_--------------]
4512  698   07/26 15:13:42 60191 CsVssAsync::WaitUntilDone() - Async status for event [VSS-Wait_------------------] returned final code = 0x0004230a, Description = VSS_S_ASYNC_FINISHED.
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::GatherWriterMetadata() - Writer Metadata gathered
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::GatherWriterMetadata() - Gathered all writer metadata
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::SetBackupState() - Committing backup state: SelectComponents: [1], BootableSystemState: [0], BackupType: [5 - VSS_BT_COPY], PartialFileSuppport: [0]
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::SetBackupState() - Committing backup state: SelectComponents: [1], BootableSystemState: [0], BackupType: [5 - VSS_BT_COPY], PartialFileSuppport: [0]
4512  698   07/26 15:13:42 60191 CsSnapRequestor::RunCreateShadow() - Usage list empty, no writers added to the shadow
4512  698   07/26 15:13:42 60191 CsSnapRequestor::Initialize() - Not gathering the writer metadata
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::FreeWriterMetadata() - Free'd all writer metadata
4512  698   07/26 15:13:42 60191 CsVssBackupComponents::SetBackupState() - Committing backup state: SelectComponents: [1], BootableSystemState: [0], BackupType: [5 - VSS_BT_COPY], PartialFileSuppport: [0]
4512  698   07/26 15:13:42 60191 CsSnapRequestor::Initialize() - Shadow Provider='default'
4512  698   07/26 15:13:42 60191 CsSnapRequestor::StartSnapshotSet() - Created shadow set ------------------------
4512  698   07/26 15:13:42 60191 CsSnapRequestor::AddVolumesToSnapshotSet() - Call m_vss->AddToSnapshotSet  [FAILED, throwing CV exception] - Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR
4512  698   07/26 15:13:42 60191 CsSnapRequestor::DeleteSnapshot() - Shadow not created!
4512  698   07/26 15:13:42 60191 CsSnapRequestor::BackupComplete() - Deleted snapshot set
4512  698   07/26 15:13:42 60191 CsSnapRequestor::BackupComplete() - Aborting backup!
4512  698   07/26 15:13:42 60191 Entering [CVSSClientShadow::AbortShadow]
4512  698   07/26 15:13:42 60191 CVSSClientShadow::CreateShadow() - Failed to create shadow.
4512  698   07/26 15:13:42 60191 SHADOWSET::CShadowSet::CreateShadowSet(224) - Failed to create shadow, error=0x8004230F
4512  698   07/26 15:13:42 60191 CFileBackupFSW2K::CreateShadow(4221) - Failed to create volume snapshot, error [0x800704D5:{COpenFileManager::CreateShadow(99)} + {COpenFileManagerDDB::CreateShadow1(882)} + {COpenFileManager::CreateShadow1(428)} + {SHADOWSET::CShadowSet::CreateShadow(66)} + {SHADOWSET::CShadowSet::CreateShadowSet(228)} + {SHADOWSET::CShadowSet::CheckIfRetryIsPossible(290)/W32.1237.(The operation could not be completed. A retry should be performed. (1237))-Unable to create a shadow at this time, error=0x8004230F}]
4512  698   07/26 15:13:42 60191 CFileBackupFSW2K::TakeJobDecisionOnVssFailure(4319) - Continuing job without resetting access time as per chosen snap failure action
4512  698   07/26 15:13:42 60191 FsBackupCtlr::HandleDDBBackupNew(9900) - Shadow Set Id is empty. Seems snap creation failed. will backup from live volume
4512  698   07/26 15:13:42 60191 FsBackupCtlr::HandleDDBBackupNew(9911) - VSS Snapshot could not be created and the registry hook to continue the backup via live volume in this case was not found. Failing the job
4512  698   07/26 15:13:42 60191 The job has failed because the VSS snapshot could not be created

icon

Best answer by Damian Andre 26 July 2021, 19:45

H @gary mcneely  - in this case, it is taking a VSS snapshot of the volume where the DDB is located - that looks to be F: drive from the logs - so the focus should be there in terms of free space etc.

  • Wondering if you have a 3rd party VSS provider installed (which is common when you install array software utilities etc.). Use this command to check which providers are installed
    • vssadmin list providers

      You should only see “Microsoft Software Shadow Copy provider 1.0

    • If there is another provider, use this additional setting to force the use of the microsoft software provider

  • You also want to check that the system writer is stable from your vssadmin list writers output, generally none of the others matter for a DDB volume snapshot

  • You can also try manually create a VSS snapshot using the following series of commands (assuming F: is the correct target)

  • diskshadow /l c:\windows\temp\vsslog.txt
    set verbose on
    set context volatile
    add volume F:
    begin backup
    create
    end backup
    • This will help determine where the issue resides

Lastly, for VSS error, the system / application windows OS logs (eventvwr) will always have more information - look for the ‘volsnap’ component.

 

Hope this helps!

 

View original

1 reply

Userlevel 7
Badge +15

H @gary mcneely  - in this case, it is taking a VSS snapshot of the volume where the DDB is located - that looks to be F: drive from the logs - so the focus should be there in terms of free space etc.

  • Wondering if you have a 3rd party VSS provider installed (which is common when you install array software utilities etc.). Use this command to check which providers are installed
    • vssadmin list providers

      You should only see “Microsoft Software Shadow Copy provider 1.0

    • If there is another provider, use this additional setting to force the use of the microsoft software provider

  • You also want to check that the system writer is stable from your vssadmin list writers output, generally none of the others matter for a DDB volume snapshot

  • You can also try manually create a VSS snapshot using the following series of commands (assuming F: is the correct target)

  • diskshadow /l c:\windows\temp\vsslog.txt
    set verbose on
    set context volatile
    add volume F:
    begin backup
    create
    end backup
    • This will help determine where the issue resides

Lastly, for VSS error, the system / application windows OS logs (eventvwr) will always have more information - look for the ‘volsnap’ component.

 

Hope this helps!

 

Reply