Applies to Product – Dynamics 365 Lifecycle Services
What’s happening?
While restoring backups to a tier 2 environment, configurations are being deleted, which affects data integrity. Additionally, there are instances where database refresh operations fail, leading to rollback issues and inability to restore environments.
Reason:
The underlying cause of this appears to be related to configuration problems during the backup and restore process, particularly when moving data between environments. There may also be backend configuration issues that contribute to the failure of database refresh operations.
Resolution:
- For restoring backups to a tier 2 environment:
- Ensure that the environments used for moving data have the same code base.
- Refer to the "Refresh database - Finance & Operations | Dynamics 365 | Microsoft Learn" section on data elements that aren't copied during refresh to understand potential data loss.
- In cases of database refresh failures:
- Attempt the refresh operation again after addressing any backend configuration issues that may have caused the initial failure.
- Schedule database movement operations during non-business hours to minimize impact on users, as these operations can take a significant amount of time and may cause environments to go offline unexpectedly.
- For point-in-time restores:
- Follow the procedure for performing a point-in-time restore of the production database to a sandbox environment as outlined in the relevant documentation.
- If further assistance is needed, ensure to provide screenshots and navigation details of the configurations that are being removed during the restore process.