commvault.com commvault.com
Solved

sucessful backups not protecting files The process cannot access the file because it is being used by another process

  • 8 February 2021
  • 33 replies
  • 3424 views
Show first post

33 replies

S
Rank
Userlevel 2
Badge +6

Same question here. Best guess would be someone didn’t like to see so many Failed or CWE Jobs so they requested this “solution” to hide the minor issues.

Even considers Job ok if CommServe Services failed to be backed up, or most other parts of SystemWriters.Though that bug should finally be fixed in next HPK.

Personal Solution/Workaround: Alert that goes of on specific SystemWriter Events and triggers Workflow to fix Issues , create Ticket with Server-Owner, or just send an Info-Mail to us for further checking.

Henke
Rank
Userlevel 4
Badge +13

Hi @Theseeker ,

Backup jobs can be configured with thresholds, this is so a job with 10s of 1000s of files will still complete, despite 1 or 2 failed files.
The thresholds can be modified here: Home tab > Control Panel > Data > Job Management

https://documentation.commvault.com/commvault/v11/article?p=6190.htm

 

Cheers,

Jase

@jgeorges 
This has always baffeled me.

How can a job be successfull if it miss to backup files? I’ve never understood the reasoning behind it. If that one file missed is the most critical file and it’s lost even though backups been successfull, how would you explain it?

BR
Henke

S
Rank
Userlevel 1
Badge +3

@Theseeker Looks like vss is not is a good shape to take a vss snap and hence it is failing. Can you if there is enough space on the volume to take the snapshot? You can use the below command to see where is the shadow storage located for the volume

vssadmin list shadowstorage

 

If this is good, can you check the event viewer to see if there are any errors from VSS?

Restart vss service to see if the issue can be auto corrected.

 

Thanks,

Karthik 

T
Rank
Userlevel 2
Badge +8

“4600  18f0  02/09 00:42:54 4041670 CsSnapRequestor::AddVolumesToSnapshotSet() - Call m_vss->AddToSnapshotSet  [FAILED, throwing CV exception] - Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR”

 

600  18f0  02/09 00:42:54 4041670 SHADOWSET::CShadowSet::CreateShadowSet(218) - Failed to create shadow, error=0x8004230F

 

4600  18f0  02/09 00:42:54 4041670 CFileBackupFSW2K::CreateOFMSnap(4065) - Failed to create OFM snap, error=0x800704D5:{COpenFileManager::CreateShadow(94)} + {COpenFileManager::CreateShadow1(420)} + {SHADOWSET::CShadowSet::CreateShadow(67)} + {SHADOWSET::CShadowSet::CreateShadowSet(222)} + {SHADOWSET::CShadowSet::CheckIfRetryIsPossible(284)/W32.1237.(The operation could not be completed. A retry should be performed. (1237))-Unable to create a shadow at this time, error=0x8004230F}
4600  18f0  02/09 00:42:54 4041670 FsBackupCtlr::DoFailedFileRetryBackup(10869) - Failed to create OFM snap, error=0x800704D5:{CFileBackupFSW2K::CreateOFMSnap(4066)/Failed to create OFM snap} + {COpenFileManager::CreateShadow(94)} + {COpenFileManager::CreateShadow1(420)} + {SHADOWSET::CShadowSet::CreateShadow(67)} + {SHADOWSET::CShadowSet::CreateShadowSet(222)} + {SHADOWSET::CShadowSet::CheckIfRetryIsPossible(284)/W32.1237.(The operation could not be completed. A retry should be performed. (1237))-Unable to create a shadow at this time, error=0x8004230F}
4600  18f0  02/09 00:42:54 4041670 FsBackupCtlr::DoFailedFileRetryBackup(10896) - Cannot proceed with backup of locked files in FailedFileRetry.cvf due to a previous error. Copying the locked file entries to Failures.cvf for retry in the next job.
4600  18f0  02/09 00:42:54 4041670 FsBackupCtlr::PutInFileTheFailedFilesList(5733) - FailedFileCnt [194]
4600  18f0  02/09 00:42:54 4041670 FsBackupCtlr::DoFailedFileRetryBackup(10912) - Copied locked file entries from FailedFileRetry.cvf to Failures.cvf

 

 

4600  18f0  02/09 01:48:52 4041670 PrintReport(1949) - Component                           Method                              Status
4600  18f0  02/09 01:48:52 4041670 PrintReport(1950) - ---------                           ------                              ------
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - System Info Archive                 Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - COM+ Database                       Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - IIS                                 Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Performance Counter                 Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Registry                            Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - System Protected Files              Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Task Scheduler                      Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Disk Quotas                         Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Event Logs                          Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - WMI Database                        Writer                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - Offline Files                       Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 PrintReport(1960) - One Touch Files                     Legacy                              Successful
4600  18f0  02/09 01:48:52 4041670 CsVssBackupComponents::FreeWriterMetadata() - Free'd all writer metadata

S
Rank
Userlevel 1
Badge +3

@Theseeker Just curious on why you are seeing this error. If a file is locked and vss for locked files is enabled (which is default) we should take a vss snap and protect the file unless vss snap is failing. Can you provide us the backup log to see why the snap is not taken here?

 

Karthik

J
Rank
Userlevel 5
Badge +9

Hi @Onno van den Berg ,

The global level is still IDA Specific so may clear some very specific conditions, however understand there may be FS ida’s used to protect critical systems too.

For this, you can customize error conditions at a client level or a client group level to keep things more granular:
https://documentation.commvault.com/commvault/v11/article?p=6191.htm

 

I think this should cover those scenarios you mentioned, but let me know if not and i’ll do some more digging.

 

Cheers,

Jase

Onno van den Berg
Rank
Userlevel 7
Badge +19

I dislike this approach because you are making a global change here which impact everything. If I recall correctly you cannot override it on a client computer, right?

Thinking about it I would like to be able to turn it around. Have the global default set to one meaning it will already report the job as incomplete if it missed one file. The ability to influence the threshold should be done on a server group level or client computer level. This allows a more granular approach offering more control on it. 

Imagine this one file to be very important which is being filtered out now as the job just completes successfully…. I wouldn't like to be the guy to receive the request to recover the file to discover that it was not protected for months already. 

Other example: customer runs specially tailed application that holds all application files in use. Agreement made to stop application at time X for backup. This works until application grows and time to backup or stop takes to long and backup already kicks in while files are still being in use…...

J
Rank
Userlevel 5
Badge +9

Hi @Theseeker ,

Backup jobs can be configured with thresholds, this is so a job with 10s of 1000s of files will still complete, despite 1 or 2 failed files.
The thresholds can be modified here: Home tab > Control Panel > Data > Job Management

https://documentation.commvault.com/commvault/v11/article?p=6190.htm

 

Cheers,

Jase

Reply


Terms & ConditionsCookie settings