You are here:
Implement the Restore Application to Recover Data
The Restore application provides a comprehensive solution for restoring data based on backups to your org or instance.
You can address the following data recovery use cases using Own Data Platform's Backup & Restore to recover your data.
- Backup & Restore features and functionality are available for use with Salesforce, ServiceNow, and Microsoft Dynamics CRM, unless otherwise specified.
- This topic contains UI examples from Salesforce.
-
Repair data loss: For a selected service, restore deleted records, any deleted child records, and any deleted attachments. The user can choose to restore lost data of the selected, source service to:
- Itself (the selected, source service)
- A different, active service of the same provider
- Repair data corruption: For a selected service, restore corrupted field data/column data
- Restore full organization [Salesforce only]: For a selected Salesforce data service, whether a production or a sandbox service, restore all data deletions and data updates that occurred in any of the service’s objects
- Restore metadata [Salesforce only]: For a selected Salesforce metadata service, restore a
metadata object. With this use case, the user can choose to restore lost metadata of the
selected, source Salesforce metadata service to:
- Itself (the selected, source Salesforce metadata service)
- A different, active Salesforce metadata service
Requirements
To work with Restore:
- You have purchased Own’s Backup & Recover product
- You have created a minimum of one service
- The created service has a minimum of two existing data backups
For the user roles and permissions that must be assigned to the authenticated user, including write access to objects/tables, refer to the topic RBAC for Recover in Own’s User Guide for your provider.
Limitations and Non-Support
- The Own platform limits each account to a maximum of six jobs of the same type performing in parallel, which means a maximum of six Restore jobs can be performing in parallel. However, additional Restore jobs can be submitted to the job queue, while six Restore jobs are currently being processed
- When restoring data across environments, records can fail due to children (Child 3 in the
example below) that also have dependencies on other objects (Parent 2 below) that aren't also
children of the selected Parent (Parent 1 below).
In the example, if you select Parent 1 which has 3 child objects:
- Records on the selected object Parent 1 will succeed.
- Records on Child 1 and Child 2 will succeed.
- Records on Child 3 will fail because they're dependent on Parent 2 which isn't included in the restore, and doesn't exist in the destination sandbox environment.
- Assets with sharing enabled: To restore an Asset object, either an AccountId or ContactIdn is required. (Salesforce default sharing setting for Assets requires a parent account and/or contact to be defined). If this restriction was removed and the default Asset sharing setting was changed the Own platform cannot restore it.
- ContentDocument objects cannot be restored to private libraries (only to public libraries). Restoring a ContentDocument can only be done if the private library and all the ContentDocument objects belong to the user that runs the restore (and the user has all the permissions required for the restore).
- The Restore application does not support/restore these objects/tables:
- Any object/table excluded from the scope of a backup
- Salesforce objects:
- AccountPartner, ApexClass, ApexComponent, ApexTestQueueItem, ApexLog, ApexPage, ApexPageInfo, ApexTestResult, ApexTrigger, AppMenuItem, AsyncApexJob, AuraDefinitionInfo, AuraDefinitionBundleInfo, AuthSession
- ClientBrowser
- DataType
- EntityDefinition, EventBusSubscriber
- FieldDefinition, FlowInterview
- KnowledgeArticleVersion
- LoginIp
- NavigationLinkSet
- ObjectPermissions, OpportunityPartner, Organization
- PermissionSet, ProcessInstanceWorkitem, Profile, Publisher
- RecentlyViewed
- SetupEntityAccess
- TagDefinition
- UserSetupEntityAccess
- Microsoft Dynamics tables:
- ReadOnly tables, for example, externalparty, interactionforemail
- Solution aware tables, for example, canvasapp, workflow, role, privilege, msdyn_sequence, fieldpermission, and webresource
- The Restore application does not support the following services:
- Salesforce weekly export services
- Workday services
The Restore User Interface
- Restore is located in the Own user interface (UI) menu bar. When clicked, the Restore page displays.
- From the Source field drop-down menu, the available services are listed by provider
(unsupported services are not listed in the Source field drop-down menu).
- If the selected source service is a Salesforce metadata service, the user can only initiate a Restore metadata task.
- Otherwise, based on the selected source service, select from the Type field drop-down menu
any one of the following restore tasks:
- Repair data loss
- Repair data corruption
- Restore full organization [Salesforce only]
- Restoring Data to Dynamics
The Restore application provides a comprehensive solution for restoring data based on backups to your Dynamics environment. - Repair Data Loss and Data Corruption in Dynamics
Retrieve all deleted records, child records, and attachments to maintain accurate and reliable data that minimizes downtime and meets critical compliance requirements. Correct field-level corruption to uphold data integrity and prevent cascading issues across related systems. - SQL Where Clause Examples for Dynamics Data Recovery
Use SQL where clauses during Dynamics recovery, repair, and restore processes to filter and select specific records. SQL where clauses give you precise control over which data is restored or repaired. - Restore Dynamics Data with Precision
The Precision Repair capabilities for Dynamics provide a visual, interactive, and end-to-end experience making it easy to identify and correct only the unwanted changes to your SaaS data. - Restore Environments in Dynamics
Restore environment data to the same environment for repairing data corruption or loss within an environment. You can also restore to different environments for testing or compliance purposes, such as validating production data in a sub-production instance before moving it back to production.
