Error Code: EPERMS (Permission Denied)
This error occurs when Druva lacks the necessary administrative authority to access the Google Workspace tenant.
Root Causes:
The account used for integration is not a Google Super Administrator.
The Druva App distribution is restricted to specific Organizational Units (OUs) instead of the entire domain.
OAuth permissions are incomplete or the admin was logged into multiple Google accounts during setup.
Resolution Steps:
Verify Administrator Role: Ensure the account used in Druva has the "Super Admin" role assigned in the Google Admin Console.
Enable App for All Users:
Navigate to
admin.google.com> Apps > Google Workspace Marketplace apps > Apps list.Select Druva inSync for Google Workspace.
Under User Access, verify the status is ON for everyone.
Re-authenticate: If the error persists, reconfigure the Druva App while ensuring you are logged into only the Super Admin account in your browser and Ensure you grant all permission under the OAuth client for the Druva app.
Error Code: EAUTH (Authorization Failed - Shared Drives)
This error is specific to Shared Drive backups and usually indicates a lack of "Manager" level access or inactive accounts.
Root Causes:
No active member exists in the Shared Drive (all members are deleted or suspended).
The sync account lacks Content Manager or Manager permissions for that specific drive.
Resolution Steps:
Check Membership: Ensure at least one active user or group is assigned to the Shared Drive.
Assign Permissions: Verify that at least one member has the Manager or Content Manager role.
App Distribution: Confirm the Druva app is enabled for the Organizational Unit (OU) where the Shared Drive is located.
Status Message: "No Content Backed up yet"
This is a configuration state, not an active failure. It occurs in two scenarios:
Scenario | Resolution |
Not Configured | The Shared Drive is discovered but has no assigned storage or backup frequency. Action: To resolve this issue, configure the selected Shared Drive for storage and backup frequency. |
Pending Initial Backup | The drive is configured, but the first backup cycle has not started. Action: Manually trigger a backup by clicking Backup Now. |