I get your point. But you know Microsoft support case need cost and Managment will not paid this just for testing. So I need to collect information from internet….
Correct they do cost money, but you also don't willy nilly restore a site without there be consequences.
There is a lot more to it that just restoring the db, particularly for an older db. e.g. the older the db the more consequences there are. Just take this simple case.
- 8 pm a backup happened
- 9 pm SU was installed on a client. the client reported it status back to ConfigMgr.
- 1 am something happens to your db
- 8 am you restore the db from 8 pm.
You would think no big deal the client will report back again that it has the SU installed, right? No that is wrong, it will never report back that the SU is installed.
So how do you fix this issue?
That is the wrong question to start with: How do you know it happened? What other things could have happened between the backup and restore? What other gotchas are there (and there are lots)? How long will it take you to find all of the issues particularly if you don't call support?
It is a perfectly valid answer to give management, "If we ever need to restore a site, we will want to open a support case with MS to ensure that not only our site server is healthy but all of our site roles and client. And yes this cost money but What is the cost of downtime to us? How quickly will be offset those cost by reducing downtime and support time?"
Personally, I would contact my TAM as ask them for what are the recommended restore procedures for ConfigMgr. Yes, that would cost money but are you really going to trust a random stranger's blog or forum post to something as important as ConfigMgr. It has a ton of moving parts, without knowing all of them, will you ever be sure that things are working perfectly?
