*The following steps have been performed with DPM07. I have also worked with DPM06 which the console interface might look the same but some features are different. Nevertheless, troubleshooting is the same. Let's go and take care of this error!
1)This error should be visible in the Monitor Tab Under Alerts Tab once highlighting your protection member error.
2)Open the command prompt. Go to
Start then
Run then type
cmd on the text box or Press Ctrl + R(at the same time) then type
cmd on the text box and click the
OK button or press the
Enter Key on your keyboard. Next, type
net view in the command promt. Your window should look similar to the image below. Finally, check to make sure the server having the error is in your network. I see the
server-
name-
1 which i need to remote log into. If you see the server then move on to step 3. If you don't see the protected server having the error then you need to see the network administrator to get that server on the network.
3)Ping the server having the error to make sure you can use Remote Desktop Protocol (RDP). In the command prompt type
ping then
server name then press the
Enter Key on your keyboard (example. ping
server-
name-
1 then press the
Enter Key ). The result should be similar to the image below. Next, move to step 4.
4)Remote Login to the Server having the error. Go to
Start then
Run (CTRL+R) type
mstsc then click the
OK button or press the
Enter Key on your keyboard. The image below illustrates this step. Next, move to step 5.
5)RDP should look similar to the image below. Enter the credentials to your server and click the
Connect button. Next, move to step 6.
6)The login window to your server should look similar to the image below. Enter your credentials and click on the
OK button. Next, go to step 7.
7)Once you are logged in to the Server go ahead and open the command prompt. Go to
Start then
Run and type
cmd in the text box then press the
OK button or press the
Enter Key on your keyboard. Your screen should look similar to the image below. Go to Step 8.
8) We need to make sure and check the VSS Writers are working properly. In command prompt type: vssadmin list writers. The image below illustrates how your screen should look. Next, go to step 9.
9)In the command prompt screen you can see all the writers. We are interested in the microsoft exchange writer. Scroll down until you see
"Microsoft Exchange Writer". Notice the state
" Failed". This is what we need to change to
"stable". Next, go to step 10.
10)We need to open the services window. Go to
Start then
Run then type
services.msc on the textbox then click the
OK button or press the
Enter Key on your keyboard. Next, go to step 11.
11)
Caution! When dealing with exchange it is critical that this step should be performed after business working hours because if you perform this while at the peak of business hours you run the chance of creating heavoc to your end users. It will not be pretty. Once you get the approval from your senior network administrator continue to the next steps. We need to stop the dpmra agent to relieve the traffic to the exchange files. Highlight
DPMRA Service and click on the
Stop square icon right above Services (Local). The image below illustrates how it should look on your screen. Next, go to step 12.
12)We need to restart Microsoft Exchange Information Store. Scroll down the list of services until you see
"Microsoft Exchange Information Store". Highlight Microsoft Exchange Information Store Service and click on the
Restart icon right above Services (Local) Label. The image below shows the options that can be performed which are stop, pause and restart. Once you Restart the service go to step 13.
13)The Microsoft Exchange Service should Restart with no problem. If you don't see any change wait a couple of minutes and check again on the service. Once microsoft exchange service is back again
Start the
DPMRA Service agent. Next, go to step 14.
14)Perform step 7-9. We are looking for the
"Microsoft Exchange Writer" state
"Stable". The image below illustrates what you should see. You can stay logged in to the exchange server for now. Finally, we need to check on the dpm server. Next, go to step 15.
15)On the DPM Server, Monitor Tab Under Alerts Tab higlight the protected member with the DPM VSS Retryable error and click on
Create Recovery Point/Consistency check. Next, got to the
Jobs Tab. Wait until you see data being transferred. The image below illustrates when everything has been performed properly. If nothing happens then you need to
Reboot the Exchange Server and Try again starting from step 14.
