Disaster Recover / High Availabity
Does anyone have any recommendation in regards to DR or HA for a primary? We have had 2 cases in the last few months in which drives went bad and primaries had to be restored from backup. It's a whole long story and if the region had the HW we suggested (Raid 10 vs Raid 5) it wouldn’t have been as issue. Taking HW out of the equation what / is their a best way to recover from a primary failure that won' take hours? In the case of the last primary, it took us about 8 hours to get back up and running:
1) Install SQL - 30 mins
2) Install SCCM - 1 hour
3) Run site repair wizard. We noticed the amount of adverts will impact how long this step takes to fnish. We had around 8k adverts and the repair would do around 1500 adverts and hour (you can see this is smsprov.log while the restore is going) - 6 hrs
The problem with the primary going down is that all of my secondaries below the primary (in this case 10) are also useless until the primary is restored. I think 8 hours is pretty good to get everything going again, but business doesn't agree.
Business keeps pushing us to go to SAN, since all our primaries have direct attached storage, but we believe SAN will impact performance. Does anyone have any input on SAN ?
Thank you.
All Replies
This question is being answered over on myITforum site.
http://www.myitforum.com/forums/m_208740/mpage_1/key_/tm.htm#208758
http://www.enhansoft.com/- 8 hours doesn't seem half bad to me.
And SAN might actually hurt performance, but is one of the only ways to go HA for sccm that I know off.
If you have ALL data, included boot & system partition on a replicated san, than you have HA.
Anything else would be DR, and getting that below 8 hours with 8000??? advertisements is going to be pretty difficult.
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
