Working with the Restore Application to Recover Data

Work with Own's Restore application to recover your data.

Unless specified otherwise, Restore features and functionality that are presented in this topic are available for use with all of the following provider data environments: Salesforce, ServiceNow, and Microsoft Dynamics CRM.
This topic presents user interface images that use Salesforce examples.

Restore provides you the ability to address the following data recovery use cases:

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 the Restore application:

You have purchased Own’s 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 user role permissions that must be assigned to the Own 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
The Restore application does not support/restore the following 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:
  - Audits table
  - Principalobjectsaccess table (Sharing information)
  - 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

Generating a Restore Preview

In the Own user interface (UI) menu bar, click Restore. The Restore page displays.

From the Source field drop-down menu, select from among the available services, grouped 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]

Repair Data Loss

When data loss occurs in a production service/instance, Own recommends the following best practice: First perform a repair data loss to a sandbox/sub-prod instance, verify that the restored data is complete and correct, and only then perform a repair data loss to the affected production service/instance.

You can restore the selected, source service’s data to:

The same service - meaning to itself (source service <AbC>). This is the default option. The enabled Restore to a different service link displays below the Source field.

A different, active service of the same provider (source service <AbC> → destination service <xYz>). The enabled Restore to the same service link displays below the Source field.

Before restoring lost data to a different, active service of the same provider, apply the following best practices:
* Make sure that the destination’s object/table schema matches that of the source. Doing so prevents processing errors
* Include referenced records by selecting their associated object/table in the Objects/Tables field or, alternatively, make sure that their associated object/table exists in the destination organization

When restore to the same (source) service is the current treatment, you can change to restore to a different service by doing the following:

Click Restore to a different service. The Destination field appears, in addition to the Source field.
From the Destination field drop-down menu, select the (destination) service that will receive the restored data of the source service.

When restore to a different (destination) service is the current treatment, you can change to restore to the same (source) service by doing the following:

Click Restore to the same service. The Destination field disappears and only the Source field remains displayed.
Click in the Objects/Tables field and select from the drop-down menu the specific objects/tables whose lost data you want restored.
In the Object/Tablelevel depth slider, select how many levels deep of data you want restored for the objects/tables that are entered in the Objects/Tables field. By default, the data depth is 3 levels deep.

A depth greater than 6 may increase the processing time of the restore task.

In the Backups field:
1. From the CORRECT field drop-down menu, select a backup of source service <AbC> that was produced prior to the date of the data loss and that you know to contain the correct and complete data.
2. From the DAMAGED field drop-down menu, select the backup of source service <AbC> that was produced on or after the date of the data loss and that you know/speculate experienced data loss.
Click Preview Restore. The application launches a restore job in which it performs a comparison between the CORRECT backup of source service <AbC> and the DAMAGED backup of source service <AbC> to identify lost data. During comparison processing, the UI transfers the user to the Jobs tab > Restore Pre-Process finished page of the restore job (Job ID #<nnnnn>) and presents the job’s initial processing results.

Refer to Data Restore, in the User Guide for your provider, for details about the following:

The initial processing results
Filtering the results (identified lost data, if any) and executing an UpdatePreview
Required actions that you must perform before proceeding with the actual data restore into the recipient service, this being either source service <AbC> or destination service <xYz>

Repair Data Corruption

You restore the selected, source service’s data to itself (source service <AbC>).

Note: Use Own’s Seeding and Anonymize applications to repair corrupted data to a different service. Refer to Seeding Data Using Accelerate.

Click in the Objects/Tables field and select from the drop-down menu the specific objects/tables whose corrupted field/column data you want repaired.
In the Backups field:
1. From the CORRECT field drop-down menu, select a backup of source service <AbC> that was produced prior to the date of the data corruption and that you know to contain the correct and complete data.
2. From the DAMAGED field drop-down menu, select the backup of source service <AbC> that was produced on or after the date of the data corruption and that you know/speculate experienced data corruption.
Click Preview Restore. The application launches a restore job in which it performs a comparison between the CORRECT backup of source service <AbC> and the DAMAGED backup of source service <AbC> to identify corrupted data. During comparison processing, the UI transfers the user to the Jobs tab > Restore Pre-Process finished page of the restore job (Job ID #<nnnnn>) and presents the job’s initial processing results.

Refer to Data Restore, in the User Guide for your provider, for details about the following:

The initial processing results
Filtering the results (identified corrupted data, if any) and executing an UpdatePreview
Required actions that you must perform before proceeding with the actual data restore into source service <AbC>

Repair Full Organization [Salesforce only]

Perform this restore task only when widespread data corruption and/or data loss occurred in a production service or a sandbox service.

You restore the selected, source Salesforce service’s data to itself (source service <AbC>).
In the Backups field:
1. From the CORRECT field drop-down menu, select a backup of source service <AbC> that was produced prior to the date of the widespread data corruption/loss and that you know to contain the correct and complete data.
2. From the DAMAGED field drop-down menu, select the backup of source service <AbC> that was produced on or after the date of the widespread data corruption/loss and that you know/speculate experienced widespread data corruption/loss.
Click Preview Restore. The application launches a restore job in which it performs a comparison between the CORRECT backup of source service <AbC> and the DAMAGED backup of source service <AbC> to identify corrupted/lost data. During comparison processing, the UI transfers the user to the Jobs tab > Restore Pre-Process finished page of the restore job (Job ID #<nnnnn>) and presents the job’s initial processing results.

Refer to Data Restore, in the User Guide for Salesforce, for details about the following:

The initial processing results
Filtering the results (identified corrupted/lost data, if any) and executing an UpdatePreview
Required actions that you must perform before proceeding with the actual data restore into source service <AbC>

Restore Metadata [Salesforce only]

You can restore the selected, source Salesforce metadata service’s metadata to:

The same Salesforce metadata service - meaning to itself (source metadata service <AbC>). This is the default option. The enabled Restore to a different service link displays below the Source field.
A different, active Salesforce metadata service (source metadata service <AbC> → destination metadata service <xYz>). The enabled Restore to the same service link displays below the Source field.

When restore to the same (source) Salesforce metadata service is the current treatment, you can change to restore to a different Salesforce metadata service by doing the following:

Click Restore to a different service. The Destination field appears, in addition to the Source field.
From the Destination field drop-down menu, select the (destination) metadata service that will receive the restored metadata of the source metadata service.

When restore to a different (destination) Salesforce metadata service is the current treatment, you can change to restore to the same (source) Salesforce metadata service by doing the following:

Click Restore to the same service. The Destination field disappears and only the Source field remains displayed.

Click in the Object field and select from the drop-down menu a single (1) metadata object whose metadata you want restored.
In the Backups field:
1. From the CORRECT field drop-down menu, select a backup of source metadata service <AbC> that was produced prior to the date of the metadata corruption/loss and that you know to contain the correct and complete metadata.
2. From the DAMAGED field drop-down menu, select the backup of source metadata service <AbC> that was produced on or after the date of the metadata corruption/loss and that you know/speculate experienced metadata corruption/loss.
Click Preview Restore. The application launches a restore job in which it performs a comparison between the CORRECT backup of source metadata service <AbC> and the DAMAGED backup of source metadata service <AbC> to identify corrupted/lost metadata. During comparison processing, the UI transfers the user to the Jobs tab > RestorePre-Process finished page of the restore job (Job ID #<nnnnn>) and presents the job’s initial processing results.

Refer to Metadata Restore, in the User Guide for Salesforce, for details about the following:

The initial processing results
Filtering the results (identified corrupted/lost metadata, if any) and executing an UpdatePreview
Required actions that you must perform before proceeding with the actual metadata restore into the recipient metadata service, this being either source metadata service <AbC> or destination metadata service <xYz>