Summary
This article explains the following Druva backup job statuses you might encounter:
Backed Up Successfully
Backed Up With Errors
Backed Up Successfully
This status indicates a successful backup where all targeted files were backed up without errors.
Note: In rare cases, a backup might be marked successful despite missing files. This can happen when:
The inSync client lacks permission to access certain files ("Unable to read file. Permission Denied.").
The inSync client encounters issues reading local files ("Failed to read local file.").
How to Check for Missed Files
Druva Admin Console: Navigate to Endpoints Workload > Devices. Select a device and check the "Backup Summary" or "Backup" tab for "Files Missed."
Last Backup Status Report: This report can identify successful backups with a limited number of missed files. For more information, see Last Backup Status Report.
Identifying Missed Files
Review the inSyncClient.log file located in:
macOS:
~/Library/Application Support/inSync/logsWindows -
C:\ProgramData\Druva\inSync4\users\<username>\logs
Troubleshooting Missed Files
File Permissions: Verify your user account has sufficient permissions to access the files or folders being backed up.
File Accessibility: Try opening the files with your current user account. If corrupted files are encountered, inSync will report "EMEDIA Error" in the logs and mark them as missing.
Disk Issues: Run chkdsk (Windows) on the drive containing the missed files to check for bad sectors. Repair the file (if possible) and retry the backup.
Backed Up With Errors
This status indicates a completed backup where some files were not backed up due to reasons like:
Files are in use during the backup process.
Environmental issues on the device running the backup job.