Not able to backup Generation 2 VM

I was very disappointed when I tried to backup my Generation 2 VM with the last version of DPM and I saw that DPM is not able to make a backup. Of course the next step was to backup the same machine (bare metal) from Windows backup, because a lot of times you can see more detailed error in this step. In this case it was exactly as I hoped. From the Windows backup I received an explanation of error – there is not a enough free space of volume \\?\Volume{7ab7a499-9013-4f22-90a7-f8fb2f70e349}\.
What is this volume? I checked it from Administrator command prompt and I saw that this is the 300MB boot partition and of course there is not enough space.
To solve the problem we will execute all commands from the elevated command prompt.

The first step you have to take is to find the volume label. To do this, we have to use the command mountvol. You have to look in the results and there you will find a non mapped volume:
        *** NO MOUNT POINTS ***
At this point we have to move the location of shadow copies with this command:
vssadmin add shadowstorage /for=\\?\Volume{7ab7a499-9013-4f22-90a7-f8fb2f70e349}\ /on=c: /maxsize=500MB
This will move the location of shadow copies to drive C:. Of course, you can choice any other drive where you have enough free space. You can test if the location has really changed with vssadmin list shadowstorage.
After this change, the Windows backup was successful, but I still had problems to perform backup with DPM but it is simple to make it work. Just delete the current protection (Stop protection of the member…), remove the data from the storage and recreate the protection. It will work..

Problems Upgrading DPM 2012 to SP1

SP1 for DPM 2012 is available, so this is the best practice to upgrading your software.
I upgraded my software and I had some problems, or mismatches in some cases. We always talk about agents, not about DPM server as itself.
Upgrading server is easy. You have to download System Center 2012 with SP1 ISO image and launch the installation (before this step backup your SQL database!!!). Just follow the steps that are described and at the end you will have to restart the DPM server.
Until there everything is OK and easy. After this you will need some attention with agents. In addition the agents needs to be updated to SP1 version and it will be possible to upgrade them from DPM console, but DON’T DO THAT! If you protect Windows 8 or Windows Server 2012, it will not work. No replicas will be synchronized and agents will not start. Here you have almost three types of problems:

1. On Windows 8 or Windows server 2012 the agent won’t start and in event log you will have two errors:

Error 10005 – Distributed COM
DCOM got error “1053” attempting to start the service DPMRA with arguments “Unavailable” in order to run the server:

Error 7009 – Service control manager
A timeout was reached (30000 milliseconds) while waiting for the DPMRA service to connect.

Also, if you try to start manually DPMRA.EXE from command prompt, you will receive a more accurate error as it is shown in picture (VSSRequestor.dll is missing)

2. If your DPM 2012 is installed on Windows Server 2012 (I know, that this solution is not supported by Microsoft …), you will not be able to synchronize replicas. After a close look to the event viewer, you will find the same situation as in the first issue.

3. On the workgroup protected hosts with Windows Server 2012 system, the issue is similar. Here you have to upgrade agents manually, but this is not necessary enough. In this case you may receive error in DPM that agents are not reachable. You have to reregister your host as I wrote in one of my previous posts, but you will receive the second error:

Configuring dpm server settings and firewall settings for dpm server =[DPM_ServerName]
Failed! SetDpmServer failed with errorcode =0x8007041d, error says: The service did not respond to the start or control request in a timely fashion.

To further troubleshoot failures with SetDpmServer, go to

To solve the first and the second issue, you have two possibilities:

1. The best is to upgrade agents manually on protected hosts by coping installation files from [Program FilesDPM INSTALTION FOLDER]DPMProtectionAgentsRA4.1.3313.0 and launch DPMAgentInstaller from elevated command prompt. This will work.

2. Copy VssRequestor.dll from another computer to [Program FilesDPM INSTALTION FOLDER]DPMbin folder.

To solve the third problem, you have to uninstall the agent from the protected host in Control Panel – Uninstall a program. After this, perform the clean installation and configure the agent as I’ve mentioned in my previous post. This will work.

I hope, that I helped someone with this post.


Agent not reachable in DPM 2010 and workgroup protected member

If you have a workgroup computer protected with DPM 2010, you will receive an “Agent not reachable” sometimes. This happens because the password, used for communication between DPM and protected host, expires. So, you must renew the password.

To do this, you first have to change the password at the protected host:

  • Navigate to folder C:Program FilesMicrosoft Data Protection ManagerDPMbin
  • Execute the command SetDpmServer.exe -dpmServerName <HostName> -isNonDomainServer -userName <UserName>
    HostName is the name of the protected host (it colud be a Netbios or a FQDN name)
    UserName is the user, the one who is used for communication between Host and DPM

After this, you must logon to the DPM server, start DPM Management Shell and write a command:
Update-NonDomainServerInfo –PSName <HostName> –dpmServerName <DPMServer>
(also here HostName is the name of the protected host and DPMServer is the name of the DPM server – FQDN or Netbios name).

Now you will be prompted for the password and you must specify the same password as in the protected host.

That”s all. Now the servers will communicate without any problems. To be sure, you can refresh the agent state in the DMP console (you will see, that the agent is reachable).