--- schema_version: "1" id: 8fcee7160c13f4064d43a514b92f1f58cada19ba01829021d377e996f117676a title: Backup & Recover for Salesforce FAQs collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/backup_recover_o_faqs.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.backup_recover_o_faqs.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 54cf0ed4dc208edb3bf8cca0bf80bb90c1cc16b3c92f5f55fc0657ba87229a7e description: Find answers to common questions and optimize your strategy for Backup & Recover for Salesforce. products: - Security - Salesforce Platform release: "264" --- # Backup & Recover for Salesforce FAQs Find answers to common questions and optimize your strategy for Backup & Recover for Salesforce. ## Why do I have to reauthenticate if I change the username for Salesforce Authenticated User? Changes to the Salesforce Authenticated User username break the authentication connection and require you to reauthenticate in Own to restore backup service. Examples of username changes are: - Renaming the user - Deleting the user - Changing the email address or domain - Modifying the username ## Is backing up redundant if we sync Salesforce to an on-premises SQL database? Local synchronization involves costs and labor to maintain servers and verify backups. Before relying on this for recovery, consider these factors: - How frequently is the data pulled from Salesforce? - How frequently is the local database backed up? What is the retention policy of those local backups? - Does your local database include your Salesforce attachments? - Does your backup include your Salesforce Metadata (e.g., Reports, Layouts, AppexCode, Workflows, Dashboards, etc.)? - How would you restore from a user-inflicted Salesforce data loss scenario? Would a potential Salesforce data corruption or deletion propagate to your local database (thus corrupting the local database)? - If so, would the restore process then involve an additional step of first restoring a good snapshot from the backup to the local database before ultimately restoring from the local database to a Salesforce org? - How long will it take to complete this two-phase restore procedure? - Can you easily practice your DR procedure? Does your local database include a sandbox environment for DR testing purposes? - How would you restore from a parent > child (cascading delete) scenario? - How would you restore your Metadata? ## Why can't I restore History objects? Enable field history tracking on your custom objects, and on most standard objects. When enabled, Salesforce tracks field value changes on that record through a dedicated History Object. It's useful for giving a history of changes over time but has limitations through the API on restoration. When enabled, every time Salesforce detects a field value change, a new record is created in the related History record. This record stores information such as date and time of the field value change, name of field changed, user making the change, original field value, and new field value. Behind the scenes, it also stores the RecordID for the parent object record to which the History record belongs. Although you can backup History tables with the Own application, the Salesforce API excludes 'create' and 'upsert' calls for History tables, to keep their integrity and time relation intact with the parent object/record. What is the importance of History tables in the backup then? History tables can reveal important information that can be useful for investigation purposes if you're trying to ascertain “the what” during a recovery scenario. They can also be handy for audit purposes and the safekeeping of transactional information over time. You can export the History objects via the Backup History page. By default, History tables are excluded, but can be included if you want them in the backup. See [Include History Tables in Backups](https://help.salesforce.com/s/articleView?id=platform.backup_recover_o_include_history.htm&type=5&language=en_US). ## Why do the number of retried records not match the failed records in the initial Restore job? When running a Restore, the log states the number of records read for every restored object. The log specifies the number of records that were successfully restored, how many failed, and how many were skipped. When retrying a Restore job, the number of successful cases and failed cases may not add up to the number of failed cases in the initial Restore job. This is because the retry will only attempt to restore failed cases that were caused by four “retryable” errors: - DELETE\_FAILED - UNABLE\_TO\_LOCK\_ROW - SF\_BATCH\_FAILED - CANNOT\_INSERT\_UPDATE\_ACTIVATE\_ENTITY Any failed records caused by another type of error are not retried, and not included in the final count of the retried Restore job. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/images/icon_example.png) Example In the initial Restore, 434464 cases failed. In the following Restore attempt, 419693 succeeded, while 14762 continued to fail. We can assume that 9 cases were not “retryable” errors, and therefore were not attempted in the second Restore. ## When do backups run? And can I schedule a fixed start time? You can schedule the backup service start time using the Start Backups at drop-down fields in the middle of the Options menu. Configure your time zone correctly in your profile. You can use the Back Up Now option to initiate a backup on demand at any time. ## How Does Own identify deleted/removed records? The Own application 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, Own 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. The Own application does not back up the records in the recycle bin. Therefore, the IsDeleted field can not be True in the backups. ## Can the Own application backup Salesforce's weekly exports? Yes. You need to add Weekly exports as an additional service by exporting the backup from Salesforce and then adding Service & Weekly Exports in the Own application. ## What can I do with a Weekly Exports service? The use case for Weekly Exports is to be able to run Compare jobs between this service and any other service. ## Does the Backup & Recover application support backing up and restoring chatter data? Yes, the Backup & Recover application does back up all of the chatter information in the Feeds table for each object, and in the FeedItems table. ## Does Backup & Recover support backing up and restoring nCino data? Yes. We support the nCino managed package for Loan management. ## What Salesforce API version does Own support? Salesforce API version 63 is supported. ## Does Own support Salesforce backups for accounts with no API access? The Own application 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. ## How do I delete or archive my backup services? There's an option to permanently delete or archive a Sandbox environment service in Backup Service. For deleting or archiving a production environment service, open a ticket with our Support Team. We recommend to archive services, when feasible. Archived services no longer back up, but you will still have full access to the backed up data, which is useful for restore purposes or seeding functions. ## How do I find Content Libraries in my Backups? ContentFolder represents a folder in a content library for adding files. Therefore, the Own application 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 Own. 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. ## My backup is failing due to “inactive user”, how do I resolve this? For the Own application to successfully take daily snapshots of your Salesforce data and metadata, a valid Salesforce admin user is required both for the initial authentication, and 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. The Re-authenticate Service option is available from the failing backup service. Be sure to authenticate using an Admin user that has "Modify All Data" permissions, in order to enable the backups to work properly. ## Can Own restore Audit fields in Salesforce? 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. The options to restore Audit fields, Set Audit Fields upon Record Creation and Update Records with Inactive Owners, are on the Salesforce setup page. See [Enable the 'Create Audit Fields' Permission in Salesforce](https://help.salesforce.com/articleView?id=000386699&type=1&language=en_US). Salesforce has limitations around this feature. See [Considerations and Activation of "Create Audit Fields" in Salesforce](https://help.salesforce.com/articleView?id=000386065&type=1&language=en_US). Own uses the latest available backup to determine the schema of the Org, and accordingly whether certain fields/sObjects are read-only. Therefore, make sure to force a backup upon Salesforce’s enabling read-write access to the audit fields. ## If a source object has a field that's not in the destination object, will the restore succeed? You will get the best result if the source and destination match exactly. However, in the case above, the Own application will "apply" the source schema from the destination org to the data that is being restored. In other words, the Own application will automatically remove that field from the source data restore file in order to make the restore work properly.