Q. When do backups run? And can I schedule a fixed start time?
A.
You can use the "Back Up Now" option to initiate a backup on demand at any time.
Q. How Does OwnBackup identify deleted/removed records?
A. OwnBackup compares backup snapshots between two points in time - if the record existed in the previous backup and it does NOT exist in the newer backup, OwnBackup will identify it as Deleted. To expand a bit further, if the IsDeleted checkbox is True, it means the record is deleted and resides in the Salesforce Recycle Bin. OwnBackup does not back up the records in the recycle bin. Therefore, there is no situation where the IsDeleted field will be True in the backups.
Q. Can OwnBackup backup Salesforce's weekly exports?
A. Yes. You need to add Weekly exports as an additional service.
Q. What can I do with a Weekly Exports service?
A. The use case for Weekly Exports is to be able to run Compare jobs between this service and any other service.
Q. Does OwnBackup supports backing up and restoring chatter data?
A. Yes, OwnBackup does backup all of the chatter information in the Feeds table for each object and in the FeedItems Table.
Q. Does OwnBackup support Salesforce backups and recovery for accounts with no API access?
OwnBackup is able to backup the data tables including standard and custom objects. However, it does not support metadata backup. In order for customers with no API access to restore data, they must submit a request to salesforce support to have their APIs temporarily enabled. For more information, see here.
Q. How do I delete or archive my backup services?
A. To permanently delete or archive your Sandbox environment backups, simply click on:
OwnBackup recommends to archive services. Archived services no longer back up, but you can still access the backed up data, which is useful for restore purposes or sandbox seeding functions.
For refreshed Sandboxes, see here.
Q. How to find Content Libraries in your Backups?
A. ContentFolder represents a folder in a content library for adding files. Therefore, OwnBackup will query Libraries as ContentFolder object. If you are looking for a specific Library that has been added or deleted. The change will be shown under the ContentFolder object in OwnBackup. * To access Libraries in Salesforce, Salesforce CRM Content must be enabled on the user profile. All users with a content feature license can modify folders in their personal library in Salesforce.
Q. Where can I find my search layouts, record types, list views, validation rules, etc, for any given data object?
A. In order to find your metadata components (aka. search layouts, record types, list views, validation rules, etc.) for any given data object, do the following:
Q. My backup is failing due to ‘inactive user’, how do I resolve this?
A. For OwnBackup for Salesforce to successfully take daily snapshots of your Salesforce data and metadata, a valid Salesforce admin user is required both for the initial authentication as well as on an ongoing basis to enable the daily backups to run.
In the event that you deactivated the Salesforce admin account used for initial authentication, then you will need to re-authenticate the relevant service(s) with an active Salesforce admin user. Login to OwnBackup.com, click on the failing backup service(s), click Re-authenticate Service, and follow the on-screen instructions.
Be sure to authenticate using an admin user that has "Modify All Data" permissions in order to enable the backups to work properly.
Q. How do we restore our Salesforce metadata?
A. OwnBackup backs up your metadata objects via the metadata API.
The Metadata Restore tool is used to restore specific metadata objects from a previous snapshot (or revert changes that took place between two snapshots).
OwnBackup supports the following objects:
We recommend using WorkBench for objects that are backed up, but not available in the pick list.
Q. Is it possible to do a cross environment restore by object and if so, how do we do this?
A. You may use our "Parent & Child" restore tool which works cross-environment. The tool will compare the two selected snapshots from the specified environment. It will then allow you to preview all the identified records before enabling you to proceed to restore the missing records.
Example:
Q. Can OwnBackup restore Audit fields in Salesforce?
A. Yes, Objects in Salesforce have audit fields (CreatedByID, CreatedDate, LastModifiedbyID, LastModifiedDate) that are read-only by default as they are populated by Salesforce upon creation or modifications of records. If you would like to restore Audit fields, you can do that from the Salesforce.com setup page: Enable "Set Audit Fields upon Record Creation" and "Update Records with Inactive Owners" For more information, see here.
Q. If a source object has an additional field, will the restore to a destination object that’s missing the field succeed?
A. You will get the best result if the source and destination match exactly. However, in the case above OwnBackup will "apply" the source schema from the destination org to the data that is being restored. In other words, OwnBackup will automatically remove that field from the source data restore file in order to make the restore work properly.
Q. Does OwnBackup Archive support GDPR Request?
A. Yes, OwnBackup Archive supports GDPR Request via a support case with an SLA of 5 business days.
Q. What if I have triggers on the records I plan to archive/ unarchive?
Q. Is there a limit to the number of records processed in an archive policy?
A. Archive currently limits the number of records that can be processed in a single archiving policy to a maximum of 2 million records.
Users who need to archive more than 2 million records are recommended to set multiple archive policies with the SOQL. When setting multiple policies with the same SOQL it is important to schedule the policies to run at different times to avoid collisions. We recommend scheduling the policies to run at intervals not less than five hours.
Q. What Objects are not supported in Archive?
Q. What are the run times for an archive policy?
A. Archive policy maximum run times are set and configured to ensure that the same policy will not be running simultaneously at any point and attempting to archive the same records.
The maximum run times are:
Daily Policies - 23 hours
Weekly Policies - just less than 1 week
Monthly Policies - 3 weeks
Q. How much time should it take the archiving process to run?
A. Today archiving 100K records takes 15 minutes. A larger data set can be calculated accordingly. Archiving time depends highly on the retrieval of attachments. If you archive a significant number of attachments, as part of the policy, you should expect the archiving time to increase.
Q. Does OwnBackup Archive support GDPR Requests?
Q. Can I seed metadata between environments?
A. No. The system does not support metadata seeding between environments at this moment. Please use the existing Replicate functionality to copy metadata between environments.
Q. What metadata is modified in the Destination Org during seed?
A. OwnBackup will, if selected by the user, automatically disable all possible Validation Rules, Workflows, Triggers (except for triggers that are part of managed packages), and Processes on the destination environment during seeding and automatically re-enable them upon seed completion. Both activities require a “metadata deploy.” Please take that into account if you are seeding to sensitive environments.
Q. What happens with records owned by Portal/Community users?
A. When seeding records owned by portal/community users, the system replaces the owner of the records with the OwnBackup authenticated user for the destination service.
Q. What happens with records owned by Inactive Users?
A. In the case where the OwnBackup authenticated user for the destination has permission to UpdateWithInactiveOwner, the records would seed with the original owning User. Otherwise, the system will replace the records owner with the OwnBackup authenticated user for the destination service.
Q. Can we transfer User records?
A. The seeding of user records is supported. Please contact OwnBackup Support for more information on how to do this. The tool does not support the seeding of Portal users.
Q. Is my sensitive data getting to the destination sandbox when using anonymization?
A. No, data anonymization will occur before being inserted into the destination sandbox.
Q. Why would I want to disable matching users?
A. In case you want to reduce the seed time and you know that the destination contains users that also exist in the source.
NOTE: Any records that are owned by users that do not exist in the destination will fail.
Q. Why would I disable matching Product2, PriceBook & PricebookEntry?
A. In case you want to reduce the seed time and you have no need for these objects in the template.
Q. How can I seed files?
A. For seeding files, you need to add the relevant object to the template (Attachment, Document and/or ContentDocument). You can add Document object to the template and for Attachments and ContentDocument you need to add their parent object. For example, if you want to seed Account’s attachments, you need to select Account and add Attachment and/or ContentDocument objects as Children.
Q. Why don’t I see my original file in the destination?
A. In this phase, the original file will be replaced with a dummy file that correlates to the original file type (matching is by the file name).
Q. Why do I see additional objects when I add ContentDocument to my template?
A. Salesforce uses three objects to store files data: ContentDocument, ContentVersion and ContentDocumentLink. Therefore, all three need to be seeded. The actual "content" of the file is saved as a ContentVersion, and is a child of ContentDocument. ContentDocumentLink is the object that connects ContentDocument to a given record. For example, if you added a file to Account record, the relationships will be: Account → ContentDocumentLink → ContentDocument (required parent of ContentDocumentLink) → ContentVersion (required parent of ContentDocument).
Q. Why do I get duplicate files while I selected “Clean&Insert” (the existing ones should have been deleted prior to seeding new ones)
A. There is a technical limitation. ContentDocument, ContentDocumentLink and ContentVersion cannot be deleted when selecting “Clean&Insert”.
Q. I have an object that I keep failing to seed. It triggers many automations that I cannot disable and the insertion fails on timeout. What can I do to successfully seed this object?
A. You can set a lower batch size for the insertion of this particular object, and that should prevent the timeout issue. This is done in the template’s Advanced Settings.
Q. I added an object to my template, and when trying to add a filter to it, I am missing a field in the fields dropdown.
A. A field can be hidden from the authenticated user (the user that OwnBackup uses to access the org/sandbox) because it is missing read permissions for that field.
To verify this:
Search for the missing file.
Navigate to the Options tab to verify the authenticated user.
Navigate to Salesforce to add the fields permission.
Q. How can I reseed records that I deleted from my sandbox?
If you manually deleted data to the sandbox since the last seed, OwnBackup may not be aware of these changes. For OwnBackup to know what records exist in the selected sandbox, you need to run a reindexing process by clicking Seed in the template builder, and following the steps in the Seed popup. You can select to index the template objects (recommended), or all the destination objects. Indexing all destination objects will increase the duration of the seed.
Q. Why do I see errors when seeding AccountContactRelation?
These errors that occur when seeding AccountContactRelation are a false positive. When you insert a non-private contact in your org that associates a contact to multiple accounts, an AccountContactRelation is automatically created by Salesforce, and its validation rules, database insertion, and triggers are executed immediately after the contact is saved to the database. When you change a contact's primary account, an AccountContactRelation may be created or edited, and the AccountContactRelation validation rules, database changes, and triggers are executed immediately after the contact is saved to the database.
Therefore, although you see errors, please disregard them, as a new object should exist in the destination and it should connect the relevant Contact and Account objects. For more details, see here.
Sometimes you just want to talk to someone. Our customer support team is available by phone: