none
Problem with secondary server configuration RRS feed

  • Question

  • We have been using DPM for a number of years/versions, with a primary in site #1 and a secondary in site #2.

    We recently rebuilt our entire DPM infrastructure from scratch (new 2012 R2 servers, new 2012 R2 DPM installation).  Everything works EXCEPT our secondary replication.

    In order to set up secondary, or chaining, or whatever you want to call it, you install the DPM agent on the primary server with the secondary server as its protection server.  However with this brand-new install, we are having problems.  If I try to install the DPM agent for DPM 2012 R2 (RTM or even UR6 or UR7), the installation fails.  The error in the MSI installer file is basically that you can't install the DPM agent on a server that DPM is installed on.  See a log snippet below:

    MSI (c) (58:A0) [11:21:18:960]: Doing action: _DetectDPM
    MSI (c) (58:A0) [11:21:18:960]: Note: 1: 2205 2:  3: ActionText 
    Action 11:21:18: _DetectDPM. 
    Action start 11:21:18: _DetectDPM.
    MSI (c) (58:E4) [11:21:18:991]: Invoking remote custom action. DLL: C:\Users\ADMIN-~2\AppData\Local\Temp\3\MSIB1FB.tmp, Entrypoint: DetectDPM
    MSI (c) (58:68) [11:21:18:991]: Cloaking enabled.
    MSI (c) (58:68) [11:21:18:991]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (58:68) [11:21:18:991]: Connected to service for CA interface.
    Detected DPM installed on machine
    Protection Agent cannot be Installed on machine where DPM is installed
    1: __MSDPMSetupError 2: -2137450066 3: 1073745902 
    CustomAction _DetectDPM returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 11:21:19: _DetectDPM. Return value 3.
    Action ended 11:21:19: INSTALL. Return value 3.

    This is how we've been doing this for many, many versions - install the agent on the primary, attach to the secondary, go into the DPM console on the secondary and add the protected datasources from the primary.  

    In case you are wondering, I went into the secondary and was able to attach the primary, but when expanding the datasources in the new/modify PG wizard I do not get the protected datasources - only the C: drive, BMR, System state, etc.

    I looked around to see if 2012 R2 had a new procedure, but have found none, and the official Microsoft technet documentation still says to do it the way we are doing it.


    Monday, September 21, 2015 4:40 PM