Views:

Applies to Product - Dynamics 365 Lifecycle Services


What’s happening?
Customers are seeking guidance on best practices for performing housekeeping tasks in their Dynamics 365 environment, particularly regarding cleanup routines and the appropriate timing for these tasks.
 

Reason:
The need for housekeeping arises after the environment has been running for an extended period, leading to the accumulation of unnecessary data that may require cleanup.
 

Resolution:

  1. Review Documentation: Refer to the document on Cleanup routines in Dynamics 365 Finance and Dynamics 365 Supply for detailed guidance on the available cleanup actions.
  2. Execution Time: The time required to execute cleanup actions depends on various factors, including the number of records to be cleaned up and the infrastructure of the environment. It is recommended to run a cleanup for a short period to observe and note the time taken for future reference.
  3. Log Retention: The duration for which logs should be kept is contingent upon business requirements, such as the need for historical data and audit purposes. This may vary for different cleanup actions, and it is essential to confirm these requirements internally.
  4. Backup Procedures: If backups are desired before performing housekeeping, it is advisable to restore the database from production to a sandbox environment and then perform the backup. Additionally, there is an auto backup feature that allows for point-in-time restoration, which retains data for 28 days in production.
  5. Follow Recommendations: It is crucial to follow the recommendations outlined in the documentation and confirm business requirements internally before deciding on the cleanup actions and the duration for retaining data. If specific issues arise during cleanup actions, separate tickets can be raised for further assistance.