Restoring Data to Dynamics

Requirements

To work with Restore you need to:

• Purchase Recover
• Create a minimum of one service
• The created service has a minimum of two existing data backups

Note For the user roles and permissions that must be assigned to the authenticated user, including write access, refer to User Roles.

Support Limitations

• 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:
  • Any object/table excluded from the scope of a backup
  • Dynamics tables:
    • Audits
    • Principalobjectsaccess (Sharing information)
    • ReadOnly tables, for example, externalparty, interactionforemail
    • Solution aware tables, for example, canvasapp, workflow, role, privilege, msdyn_sequence, fieldpermission, and webresource

Retry Restore Job

After a Repair data loss or a Repair data corruption, it might complete with resulting errors. For example, record’s owner is no longer active in the environment. Review the Bulk Insert and Update Logs to better understand the cause of these errors.

Once you have reviewed the errors and made the necessary adjustments to your environment to resolve them, you can retry the restore job. Select the restore job and click Retry Job at the bottom right.

When you retry a restore job, only the previously failed records are reprocessed. The system skips records that were successfully inserted during the original restore job. This ensures that only the problematic records are addressed, preventing unnecessary reprocessing and the creation of duplicate records.