Now Available in Community - New TechTalk Videos for 2020
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
If I would like to request a point-in-time restore for my config environment, how often the DB backup was taken, can we request a backup only an hour earlier?
Each 15 minutes for 30 days. So for example, you can restore to a backup taken at 6.00, 6.15, 6.30 and 6.45
What is the lead time for point-in-time restore? A couple of hours?
It depends on your db size. For a size of 300 gb database it completes between in 2-5hours.
Is the article still valid?
It mentioned Five hour lead time and Five hours downtime for Point-in-time restore.
Just heard the same numbers from MS team last week as mentioned in thread above 5 + 5 hours.
Is every 15 minutes snapshot configurable? To change it to every 10 minutes.
You can not , if you try to do point in time restore less than 15 mins you get error.
If I did a point-in-time restore back to four days earlier, can I restore the point-in-time to today again?
What does the statement means below? If I restored to 17 Jan 2020 8AM, I could not restore to the same time again? But I can still restore to 17 Jan 2020 8:15AM?
"Point-in-time restore breaks the chain of available restore points
The restore database process always creates a new database based on a previous point-in-time snapshot. Because of this, the new database does not have any restore history, but does begin to accrue new restore points going forward. This means that after performing point-in-time restore you will not be able to do so again using the same restore date and time."
If you have done restore at 17 Jan at 8 AM , why would you do same restore on same environment again ? Anyways you can not do another one on the same environment until first one finishes. After first one finishes , you can do another one by selecting any time after 8.15 .
Suppose you restore finishes at 1 PM . on 17th Jan , you cna again start another restore on same environment with any time on or before 12.45 PM.
"Because of this, the new database does not have any restore history, but does begin to accrue new restore points going forward."
It seems to me that once I did one Point-in-time restore, we will lose all the restore points for the old database.
Yes, that's how it works, according to the documentation. When you do a PITS, you lose old history.
Business Applications communities