Your OCS Front-End and DPM 2010 Part 3: Recovery
Now would normally be the time where everyone is running around like their head has been cut off because your Front-End server is totally hosed, but because you followed the backup procedures in Part 1 (you did run the backup, right?) restoring service to your OCS server is fairly simple.
Restore the Database
- Open up the DPM console.
- Click the Recovery tab at the top.
- We need to restore the SQL database and files separately, but let’s start with the database. Expand the tree to <Forest Name>\<OCS Server>\All Protected SQL Instances\<OCS Server>\RTC\rtc
- Highlight a suitable recovery date in the calendar and select the RTC database below.
- Right-click and select Recover…
- Press Next.
- We’ve successfully screwed up the server to where we might as well recover to the original SQL server. Select that option and press Next.
- Select Leave database operational and press Next.
- No options needed. Just press Next.
- Yup, those are the files we need. Press Recover.
- Press Close while the recovery operation occurs.
- If you click the Monitoring tab you can view the jobs in process.
Restore the Files
- Now we need to restore files separately. Expand the tree to <Domain Name>\<OCS Server>\All Protected Protected Volumes\<OCS Installation Volume>
- Highlight a suitable recovery date in the calendar and select the Program Files folder below.
- Right-click Program Files and select Recover…
- Press Next.
- Select Recover to the original location and press Next.
- Select to Overwrite the existing versions (if any), and then select to Apply the security settings of the recovery point version. Press Next.
- Now press Recover.
- Press Close while the recovery operation occurs.
- If you click the Monitoring tab you can view the jobs in process.
Fix SQL Database Chaining
One thing DPM won’t restore is an option within SQL. If you miss this step your Front-End services will fail to start.
- Open SQL Management Studio (Express).
- Press the New Query button.
- Enter the following text:
sp_dboption 'rtc','db chaining',TRUE
- Press Execute.
Bounce the Server
If you check your OCS Front-End you’ll find all the files you deleted previously have now returned. You could probably get away with restarting services as this point, but since the machine was completed hosed I’m just going to restart the server and cross my fingers.
Check Functionality
After the restart all of my OCS services started successfully and my errors have gone away. You can see now my Communicator list still has my contacts and access levels defined. Likewise, Device Updates and client auto updates should function normally now.