If you are getting Commvault Error Code [13:85] with the description Failed to save the backup information for [<String>] to CommServe database. . Then you need to follow this guide.
What is Commvault Error Code [13:85]:
Error Code:
[13:86]
Description:
The job is pending because The destination encountered an error while processing the data from the source.
Error Code: [13:86] SQL or Exchange sub client fails to backup, A time-out has occurred while initializing data transfer with MediaAgent [ ]
SCSI Operation:
Open Drive Device. Reason: Encountered an I/O error while performing the operation. Advice: Please use the following troubleshooting utilities
1.TapeTool for Tape device-related problems.
LibraryTool for Library-related problems is provided in MediaAgent’s installation folder to perform diagnostics on this device.
Source:
Backup, Performance Diagnostic and Processing Data.
Intermittent Network issues between Client, CommServe host, and/or MediaAgent.
A large number of SQL or Exchange databases in single subclient.
Process:
MediaManager
It looks like you’re encountering an issue with your Commvault server related to mounting media.
Here are some steps to troubleshoot and potentially resolve the error:
Commvault Error Code [13:85] typically indicates a problem related to the backup job, often involving an inability to access or read a file or resource. This error can occur due to several reasons, including file system issues, permissions, or network problems.
Here’s a step-by-step guide to troubleshoot and resolve this error:
Fix for Commvault Error Code [13:85]
Error Description:
The error indicates that data could not be written to the destination media, potentially due to communication failures between the CommServe processes, JobManager, MediaManager, or within nodes of a HyperScale cluster.
Causes
Communication failure with CommServe processes (JobManager or MediaManager).
Communication failure within a HyperScale cluster.
Persistent communication errors after retries can lead to a job entering a pending state.
Fixing the Commvault Error Code [13:85]
Method 1 Quick Fix:
Restart services on the associated MediaAgent and Client.
Kill any bad jobs and then set a one-way Firewall tunnel between clients and MediaAgent.
Redistribute subclient content into other subclients.
Retry jobs.
Method 2:
Retry the Job
Often, this error is temporary. Simply re-attempting the job may resolve the issue.
Check CommServe Services
Ensure all necessary CommServe services are running. You can do this by:
Opening the CommServe Console.
Navigating to the “Services” tab.
Confirming that all relevant services (e.g., JobManager, MediaManager) are active.
Verify MediaAgent Services
On all nodes in your HyperScale cluster:
Access the server where the MediaAgent is installed.
Check that the MediaAgent services are running without issues.
Restart the MediaAgent service if it is not responding.
CommServe Sizing
Ensure that your CommServe is adequately sized to handle your workloads. Refer to the Hardware Specifications for the CommServe Server to confirm if your setup meets the recommended configurations.
If the CommServe is under-resourced, consider scaling up resources such as CPU, RAM, or storage.
Check Network Connectivity
Ensure that there are no network issues between the CommServe and MediaAgents. This includes verifying firewalls, routers, and any other network devices that could disrupt communication.
Monitor Logs for Additional Insights
Review the CommServe and MediaAgent logs for any specific errors or warnings that might provide further insight into the issue. Logs can often pinpoint exact communication failures or resource limitations.
Contact Support if Necessary
If the problem persists after following these steps, consider reaching out to Commvault support for further assistance. Provide them with detailed logs and error messages to expedite the troubleshooting process. If the error still presists, you can contact Commvault Support.
Start by using the TapeTool and LibraryTool for diagnostics to fix this commvault Error Code [13:85], check physical connections and configurations, and ensure that all software is up to date. Keep an eye on logs for any further insights. If issues continue, consider seeking help from Commvault support.
Is a freelance tech writer based in the East Continent, is quite fascinated by modern-day gadgets, smartphones, and all the hype and buzz about modern technology on the Internet. Besides this a part-time photographer and love to travel and explore. Follow me on. Twitter, Facebook Or Simply Contact Here. Or Email: [email protected]
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptPrivacy Policy
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.