Skip to main content


 

 

How can we help you?

 

 
Druva Documentation

Troubleshoot common scenarios

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

Enterprise Workloads Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

This topic lists the scenarios that you might frequently encounter while executing backup and restore for File servers.

Enterprise Workloads agent is unable to create VSS recovery point

Resolution: If you are using Microsoft native VSS, ensure that the VSS service is running. You can access Windows Task Manager and verify that the status of Volume Shadow Copy (VSS) service is running.

If you are using third-party VSS provider, ensure that you have configured Enterprise Workloads agents to recognize the third-party VSS provider. For more information, see Configure Hybrid Workloads agent to recognize a VSS provider.

Discrepant current source details for Windows 2012 File server

Resolution: Druva supports backups and restores of the data deduplication-enabled volumes on Windows 2012 File server and later. If you have enabled the data de-duplication feature on your server and observe any disparity between the total used space on the server and the current source size displayed on the Servers details page, run the following Windows PowerShell commands.

Get-DedupVolume
Get-DedupVolume | format-list

Backup fails for shared network drives mounted as a nested folder

If a network drive or a shared drive is mounted as a folder within another folder on a computer, Hybrid Workloads agent fails to recognize it and its backup fails. 

Resolution: To back up a  network drive, mount the drive as a shared drive on your computer and ensure that the Enterprise Workloads agent recognizes it. 

Backup completed with errors

The following table lists the error messages that you may encounter upon the completion of backup and their corresponding details and resolution.

Error message Description and/or resolution
Failed to read encrypted file Enterprise Workloads agent does not support backup of encrypted files. The admin users can exclude encrypted files from the backup.
Failed to open file If an application has an exclusive lock, then Hybrid Workloads agent does not back up the file. 
Failed to read at offset This is a generic OS error and indicates that the file might be corrupt. Check file system integrity.
File/Folder inaccessible during estimation Usually, this error comes up for temporary files and indicates that the files were removed during the backup cycle from their location. The admin users can exclude temporary files from the backup.

File Server backup job behavior due to
VM recovery points

If a customer reverts to a {{rpoint) of a VM, then a full scan will be performed to prevent any loss of data. This operation will take more time, as it is performing a full scan.

Job logs show socket error

Issue: Job logs show socket error (error number 10060) while creating the connection between the client and server and cause multiple issues. The following error is displayed:
socket error while create_connection with Error 10060

Cause: Network issue, possibly related to firewall.

Resolution: For more information, see KB.

File Server backup is not progressing

Issue: After upgrading the agent to the latest version, the File Server backup is not progressing.

Description: This issue can occur because of self-signed certificate. The following error is displayed:

"Failed to create backup agent" error="x509: certificate signed by unknown authority".

Resolution: Ensure you have no self-signed certificate, which can block the traffic. To verify whether there is any self-signed certificate, run the following command:

openssl s_client -showcerts -connect backup-phoenix.druva.com.com:443

The output contains the following verification errors in the case of any self-signed certificate:

verify error:num=19:self signed certificate in certificate chain
verify return:1

SSL handshake has read 5808 bytes and written 492 bytes
Verification error: self signed certificate in certificate chain

Error 1935

Issue: Error 1935 occurred during the installation of the assembly.

Description: The issue is observed for machines that have Windows Server 2022 set up as a Microsoft SCCM server.

Resolution: Ensure the following:

  • Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package and the latest Visual C++ packages are on the server.
  • Check with your internal security team if any security tools are enabled, for example, intrusion detection s/w or antivirus.
  • Refer to the article for further details.

Server connection error

Issue: Server connection lost with error code WSAECONNRESET.

Description: The following error message is shown when the SSL handshake is not happening properly and the connection to the server is lost:
"Error validating server certificate: (10054, 'WSAECONNRESET')"

Resolution: Ensure that:

  • MTU configurations are correct. Contact your internal network team if MTU configurations are missing or incorrect.

Data scan issue

Issue: Data scan reported is more than the size of the folder on the disk.

Description: Default folder exclusions of $Recycle.Bin, System Volume information, and .snapshot are removed from the content rule.

Resolution: For more information, see article.

Server activation issue

Issue: Unable to activate the server

Description: The marketplace Amazon Machine Image (AMI) has issues. When the agent is installed, the configuration file is not created.

Resolution: Use the latest AMI to resolve the error.