Hello
I receive this message on this job:
last job update time : 8 minutes ago.
and the job stuck on 95%,there is something to to with that?
Best Regards
Solved
Disaster recovery backup stucks on 95%
+7Best answer by Dheeraj Shetty
Hi
Your DR Backup is stuck at 95% while copying the DR Backup to the Staging location. From the logs, it appears that your DR Sets are copied to the Export path but partially failed while cleaning up older DR SETs from the Network path : \\ecanlp002\commvault
CommServDR.log
==
12532 4c64 02/17 16:06:46 2306254 CommservDR::doBackupRestore() - Phase A: Copying the files from [D:\Commvault\ContentStore\CommserveDR\DR_2306254] to [\\ecanlp002\commvault\SET_20711]
.
12532 3910 02/17 16:07:08 2306254 CommservDR::CopyFileToDRDestination() - Successfully copied the file [D:\Commvault\ContentStore\CommserveDR\DR_2306254\commserv_server_2025_02_17_16_00_FULL.dmp] to [\\ecanlp002\commvault\SET_20711\]
12532 4c64 02/17 16:07:08 2306254 CommservDR::dumpVersion() - Info: Successfully copied the file from D:\Commvault\ContentStore\CommserveDR\DR_2306254\version.txt to \\ecanlp002\commvault\SET_20711\version.txt
.
12532 4c64 02/17 16:07:17 2306254 CommservDR::doPurgeLocal() - Successfully deleted the folder [D:\Commvault\ContentStore\CommserveDR\DR_2306213]
12532 4c64 02/17 16:07:17 2306254 CommservDR::backupCmd() - CommServeDR: Full backup completed Successfully.
12532 4c64 02/17 16:07:17 2306254 jobCleanUp() - Phase B: Update job status to PARTIALSUCCESS
Please check the following:
- In the Commcell Console -> Control Panel->DR Backup, verify the number of metadata retained in the Export Path.
Navigate to the Network Path and ensure that the DR SETs defined in the Export Settings are present. If you find additional SETs, this could be due to recent DR backups that were either "Completed with one or more errors" or "Failed" in the past few days. In such cases, DR backup SET_XXX directories associated with unsuccessful jobs are retained for 90 days by default in the Export Settings location. This retention period can be adjusted via an additional setting. [SetLifeSpanForFailedDR] : https://documentation.commvault.com/additionalsetting/details?name=%22SetLifeSpanForFailedDR%22&id=717.
You may configure this additional setting on the CommServe and set a lower value, then run a new DR Backup to check if older DR SETs are cleared from the Export Path
- In the DR Backup settings, verify if "Upload DR Backup to Metallic Cloud" is enabled.
Check the CVCloudService.log on the Commserve for any failures in uploading the DR Backup to Metallic Cloud. If you encounter issues, uncheck the "Upload backup metadata to Metallic Cloud" option and perform a test DR Backup. If it completes successfully, the issue is likely related to uploading the DR Backup to Metallic Cloud.
Verify that the URLs, https://*.blob.core.windows.net and https://cvdrservices.metallic.io, are added to the allowlist. All endpoints that contain .blob.core.windows.net must be whitelisted.
Ref doc on Configuring Automatic Uploads of Disaster Recovery (DR) Backups to Commvault Cloud Services Portal
Regards,
Dheeraj
- Vaulter
- 47 replies
Hi Ariel,
This would mean the DR Backup is done however it failed to copy the DR copy to a local or network share defined on the DR backup settings.
- If local volume, defined please check there is enough space on the volume.
- if Network share, please ensure the UNC path is accessible by the user defined in the settings.
If needing further assistance, please share DR backup settings screenshot and also a copy of commserveDR.log file.
+15- Vaulter
- 333 replies
Did it eventually complete?
Feel free to check out the size of the CSDB and see how big it is? may explain why it’s taking time.
Regards,
Chris
+4Hello,
I am running Commvault 11.32.76 on a Windows 2019 server.
My case is quite similar since 2 days, suddenly the Disaster Recovery Job completes with one or more errors.
It looks like the job remains stuck at 95 % for a few minutes, the following message is displayed in Commcell Console:
Then, it completes and takes approximately 7 minutes.
No configuration changes occurred recently.
I have stopped/restarted Commvault services on Commcell server, it has no effects.
Commvault server is able to reach and write to network SMB share where are stored DR backups.
I had a look at the “ commserveDR.log “ file, it ends like this:
12532 4c64 02/17 16:07:17 2306254 CommservDR::backupCmd() - CommServeDR: Full backup completed Successfully.
12532 4c64 02/17 16:07:17 2306254 jobCleanUp() - Phase B: Update job status to PARTIALSUCCESS
I attach the job log.
Why this admin job suddenly became partially successful (completes with one or more errors) ?
Any help would be appreciated.
Regards.
- Vaulter
- 24 replies
- Answer
Hi
Your DR Backup is stuck at 95% while copying the DR Backup to the Staging location. From the logs, it appears that your DR Sets are copied to the Export path but partially failed while cleaning up older DR SETs from the Network path : \\ecanlp002\commvault
CommServDR.log
==
12532 4c64 02/17 16:06:46 2306254 CommservDR::doBackupRestore() - Phase A: Copying the files from [D:\Commvault\ContentStore\CommserveDR\DR_2306254] to [\\ecanlp002\commvault\SET_20711]
.
12532 3910 02/17 16:07:08 2306254 CommservDR::CopyFileToDRDestination() - Successfully copied the file [D:\Commvault\ContentStore\CommserveDR\DR_2306254\commserv_server_2025_02_17_16_00_FULL.dmp] to [\\ecanlp002\commvault\SET_20711\]
12532 4c64 02/17 16:07:08 2306254 CommservDR::dumpVersion() - Info: Successfully copied the file from D:\Commvault\ContentStore\CommserveDR\DR_2306254\version.txt to \\ecanlp002\commvault\SET_20711\version.txt
.
12532 4c64 02/17 16:07:17 2306254 CommservDR::doPurgeLocal() - Successfully deleted the folder [D:\Commvault\ContentStore\CommserveDR\DR_2306213]
12532 4c64 02/17 16:07:17 2306254 CommservDR::backupCmd() - CommServeDR: Full backup completed Successfully.
12532 4c64 02/17 16:07:17 2306254 jobCleanUp() - Phase B: Update job status to PARTIALSUCCESS
Please check the following:
- In the Commcell Console -> Control Panel->DR Backup, verify the number of metadata retained in the Export Path.
Navigate to the Network Path and ensure that the DR SETs defined in the Export Settings are present. If you find additional SETs, this could be due to recent DR backups that were either "Completed with one or more errors" or "Failed" in the past few days. In such cases, DR backup SET_XXX directories associated with unsuccessful jobs are retained for 90 days by default in the Export Settings location. This retention period can be adjusted via an additional setting. [SetLifeSpanForFailedDR] : https://documentation.commvault.com/additionalsetting/details?name=%22SetLifeSpanForFailedDR%22&id=717.
You may configure this additional setting on the CommServe and set a lower value, then run a new DR Backup to check if older DR SETs are cleared from the Export Path
- In the DR Backup settings, verify if "Upload DR Backup to Metallic Cloud" is enabled.
Check the CVCloudService.log on the Commserve for any failures in uploading the DR Backup to Metallic Cloud. If you encounter issues, uncheck the "Upload backup metadata to Metallic Cloud" option and perform a test DR Backup. If it completes successfully, the issue is likely related to uploading the DR Backup to Metallic Cloud.
Verify that the URLs, https://*.blob.core.windows.net and https://cvdrservices.metallic.io, are added to the allowlist. All endpoints that contain .blob.core.windows.net must be whitelisted.
Ref doc on Configuring Automatic Uploads of Disaster Recovery (DR) Backups to Commvault Cloud Services Portal
Regards,
Dheeraj
+4Hello,
Brillant analysis !
That was exactly my case, it solved the issue.
Thank you very much for your help
Regards.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.