This article lists the frequently asked questions related to a data copy job.
What is Druva Data Seeding?
The Salesforce App enables you to copy the data from a source environment to a destination environment. Data Seeding operation, also known as Sandbox Seeding, helps a Salesforce developer load sandboxes with adequate test data and continue developing features using sandboxes similar to the production sandboxes.
How is data seeding different from a normal backup?
Data seeding focuses on creating a copy of production data in a non-production environment to simulate real scenarios without affecting live systems while data backup primarily focuses on regularly securing production data for disaster recovery and compliance.
How often can I seed my sandbox environment?
Data seeding can be done as frequently as needed, depending on your testing and development cycles.
Is sandbox data seeding secure?
Yes, Druva ensures that all data transferred to a sandbox environment is encrypted and secure, just like regular backups.
Can Druva support multiple sandboxes for different purposes?
Yes, Druva supports seeding multiple sandbox environments for different projects, development teams, or use cases.
How can I exclude Personally Identifiable Information (PII) fields while configuring a data copy template?
You can utilize the Excluded Fields tab in the Data seeding Settings section. For more information, see Exclude Fields.
Is there a limit to the number of records copied from one Org to the other? If yes, how do you overcome it?
Data seeding has a default limit of 2 Million Records, when the source and target orgs are different in a data template. To work around this limitation, you can follow these steps:
First, create a seeding template and set the destination org to be the same as the source org. Allow the discovery process to complete fully. Once that is done, change the destination org to the desired target org before starting the seeding.
How can I copy PII fields without copying the actual values in them? (share the links for Data Mask / Data Translation)
To copy Personally Identifiable Information (PII) fields without copying the actual values in Druva's SFDC sandbox seeding, you can use data masking. This feature allows you to mask sensitive data during the seeding process, ensuring that the actual values are not copied to the destination sandbox.
Please refer to this document for implementation of Data Mask / Data Translation features. For more information see, Data Masking.
How will the licensing work if I want to transfer data from one production to another Production org?
To access data from both production orgs in the Druva Salesforce app, you must authenticate each production org separately. The number of licenses required will match the number of users in each production org. When you authenticate a production org in Druva, you can view its data and the data of its associated sandboxes. However, if you want to view data from another production org, you must authenticate that org as well. This requires additional licenses equal to the number of users in the second production org.
If you have Production Org A with 100 users and Production Org B with 50 users. If you authenticate Production Org A, you can access its data and the data of its sandboxes without needing extra licenses for the sandboxes.
If you want to include Production Org B in Druva to view its data, you must authenticate it separately.
The license requirement is, 100 licenses for users in Production Org A and 50 licenses for users in Production Org B.
Does Druva support the seeding of metadata?
No, Druva does not support the seeding of metadata during the sandbox seeding process. This means that while you can copy data records from one Salesforce org to another, metadata components such as custom objects, picklists, and user profiles need to be manually handled or restored separately.
What to do, if my sandbox org is missing certain objects for which I want to seed the data from the production?
- Create the Missing Objects: Manually create the missing objects in your sandbox org. Ensure that the object structure (fields, relationships, etc.) matches the production org.
- Export the required objects from the production org with the help of any third party tool and then import to the destination sandbox where you want to copy the data.
Reference article: How to Restore / Seed a Full Org using Druva App
How can I exclude Personally Identifiable Information (PII) fields while configuring a data Seeding template?
You can utilize the Excluded Fields tab in the Restore & Seeding Template Settings section. For more information, see Exclude Fields.