This topic lists the following Salesforce App-specific frequently asked questions.

For more information about the list of supported Salesforce platforms and cloud editions, see our Support Matrix.

Projects help you to maintain the collection of all of the Restore & Seeding templates and users associated with one project in one place. You can create projects as per a specific use case or business requirement. For example, you can create a project containing sandbox seeding data templates for copying data between organizations.

For more information, see Projects.

Restore and Seeding enable you to selectively configure the data set for Data Copy (Sandbox Seeding) or Data Restore and apply any data transformations, validations, exclusions, and masking. Hence, Restore and Seeding templates help you to trace back the kind of restored data at a later date.

For more information, see Restore and Seeding Templates.

The option to change regions is available with the Salesforce Elite Backup License and Sandbox Seeding License only.

For more information, see Licensing Information.

No, you can’t change the storage region after creating a project. For further assistance, contact Support.

Existing users can continue using their current email and password credentials.

SSO enablement is optional for existing users and does not override old login credentials unless explicitly activated.

Newly invited users are SSO-enabled by default.

Upon app launch, they are automatically authenticated using their Salesforce session (auto-login).

They will not see the traditional login screen.

Yes, but this requires intervention via Druva Support.

Steps to switch from SSO to legacy login:

If the original (incorrect) invite still exists in the system, You cannot send a new invite with the same email.

The system will block it, assuming the user is already invited.

You must first get the bad invite entry deleted via support intervention.

If the user has already accepted an earlier invite and logged in, the Druva App will not allow the new invite to go through.

This is by design to prevent duplication and confusion in onboarding.

Next Steps:

The Druva app is automatically upgraded to the latest version by Druva once it becomes available, ensuring you always have the most current features and security enhancements without any manual intervention.

No, Salesforce backups will not be impacted by storage alerts in Druva. For the Salesforce workload, there is no storage capping applied to backup data. As long as your Salesforce licenses are active and within the licensed limits, backups will continue without interruption.

To address this issue, you can re-authenticate an organization.

For more information, see Re-authenticate Organization Association.

As part of the licensing association, the Salesforce App considers active users with Standard Salesforce user type. This user type also includes Salesforce Platform and Salesforce Platform One user licenses.

For more information, see Licensing Information.

You can associate a license to a different production organization only after completing 14 days of association with the current production organization.

For more information, see Authenticate Production Organization.
​

No, resetting a user's password does not revoke license authentication. The app remains connected because OAuth 2.0 authorization is granted to the application, not directly tied to the password of the individual user who authorized it.

No. The Druva Salesforce App requires an active user license associated with either the Standard Salesforce or Salesforce Platform user types to properly authenticate and run operations. Accounts assigned a restricted Salesforce Integration license cannot log in or authenticate the application.

Using a full Salesforce System Administrator account ensures seamless backup and restore operations. Restricting the app to an Integration license introduces several significant technical limitations:

If your company policy dictates that a personal user account should not be used, you should set up a dedicated Salesforce Service Account. Assign this account a Standard Salesforce user type with full System Administrator permissions. This approach fulfills both your internal security tracking requirements and the technical capabilities required by the Druva application.
​

You can configure High-Frequency backups using the High-Frequency backup scheduling option from the backup definition settings. This configuration performs a backup of your data more than once a day. For more information, see Backup Definition Settings.

High-frequency backups are available with the Salesforce Elite Backup License.

The Salesforce App excludes system objects from the backup by default. For a detailed list of the objects excluded from backup, see Understanding Backup Exclusions.

You can include excluded objects to your backups from the backup definition settings. For more information, see Backup Definition Settings.

Yes, you can create multiple backup definitions, which support full or partial backups for your Salesforce organization.

Partial backups enable you to back up the data set selectively. You can configure partial backups through the exclusion of certain objects and associated fields. You can also select the metadata for backup.

For more information, see Exclude Objects, Exclude Fields, and Metadata Backup.

No, Data Lock/immutability is not currently available for Salesforce backups.

You can restore specific records or metadata from a snapshot with or without comparing snapshots.

For more information, see Compare and Restore Records and Compare and Restore Metadata.

When restoring records, you can specify the level of child records you want to restore. This restores the specified level of child records for this record.

For more information, see Compare and Restore Records.

When you initiate a download from the Druva Console, the system retrieves everything needed to fully reconstruct your data. Instead of providing just a single point-in-time snapshot, the downloaded ZIP file includes your selected snapshot along with all additional snapshots up to the most recent full backup. This guarantees complete data restoration, reflecting the exact state of your data up to that last full backup.

Unlike the Console, downloads initiated from the Druva Salesforce App are specific only to the snapshot you select. The resulting ZIP file contains that exact point-in-time snapshot for your chosen objects, rather than a roll-up of multiple snapshots.

The Salesforce App ensures the deduplication of data through the usage of external IDs. The application determines if the record already exists on the destination org using external IDs. This prevents duplicate inserts by performing an update operation in place of an insert operation.

For more information, see External ID.