Notifications
Announcements
No record found.
One of our customers is a public limited company looking for a data copy of 3 months old for internal data analysis on the issue we identified in logs. But in LCS, we were able to get only for 30 days using Point in time restore Production to the sandbox.
According to the documentation: docs.microsoft.com/.../database-point-in-time-restore
You can use Microsoft Dynamics Lifecycle Services (LCS) to perform the point-in-time restore (PITR) for a sandbox user acceptance testing (UAT) environment. Microsoft maintains automated backups according to Microsoft Azure SQL defaults, up to a maximum of 30 days.
How can we get something older than 30 days as an exception?
SANDBOX is ok. But we want get Production data base copy into sandbox or assert library which is 3 months old
By refreshing data from prod to sandbox every 30 days and exporting it from sandbox to LCS. But you can't access data over 35 days old if you didn't do this.
What kind of data is it that you need? All posted transactions are anyway available in your system from the entire lifetime of the system.
Additionally, you can configure database logging to track changes in setup data.
This is special business case : I provide details below
On 9/XX there was a change in the system which turned off database logging on the vendor table. On 11/XX it was turned back on. XXXX as a public company needs to ensure completeness to their external auditors on every change to the vendor table. In order to ensure completeness they need a dump of the vendor table from 11/XXX one day after we turned logging back on and 9/XX one day before logging was turned off.
From there with excel exports they can do a pivot in excel which will highlight everything that changed and compare to their paper tracking. We need to get a back up as close to 9/XXX as possible to minimize the amount of reconciliation work that XXXX needs to do.
Thanks for sharing the details. As mentioned, unfortunately you can't get such information anymore. In general it's very important to identify these kinds of requirements before the golive and plan a data retention / logging strategy that serves the audit needs. The technical possibilities and limitations can be found in documentation.
The answer to the audit requirement is database log. If you need a second layer behind it, you might need to store exported backups (weekly, daily, hourly, whatever you need). It's possible but requires manual work. Or, evaluate db log setup changes often so that you catch them before 30 days have passed.
What you can see do is to review all vendor payments from that timeslot and check that all bank accounts are correct. And verify all vendor bank accounts.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 544 Most Valuable Professional
André Arnaud de Cal... 450 Super User 2025 Season 2
Sohaib Cheema 250 User Group Leader
