none
Switching to secondary DPM by PS-Cmdlet does not work (DPM2010) RRS feed

  • Question

  • Hello

    we have an enviroment with two DPM2010 servers. C64DPM001 is the primary, C64DPM002 the secondary server.

    We wanted to switch protection to the secondary (primary server ist down). Using the GUI (Switch disaster protection ...) worked fine, but we also tried to switch some systems by using the Powershell Cmdlet Start-ProductionServerSwitchProtection. The systems we switched by the cmdlet appear now in the section "Inactive protection for previously protected data".

    We used

    $ps = Get-ProductionServer c64dpm002 | where { $_.NetBiosName -eq "NameOfProtectedServer" }
    Start-ProductionServerSwitchProtection -ProtectionType ProtectFromDPM -UserName User -DomainName Domain -ProductionServer $ps

    on system C64DPM002. The cmdlet prompted for the password and completed without any errors.

    Did we miss some steps?

    Is it possible to get the systems back to their old protection group while C64DPM001 is offline?

    Regards Markus Trapp

    Tuesday, June 12, 2012 12:04 PM

All replies

  • Hi Marcus,

    I ran into same issue, my advice is to use "start-switchprotection" Cmdlet that is working fine.

    See my post

    http://social.technet.microsoft.com/Forums/en-US/dpmdrbackup/thread/b01b3dcc-7926-429f-a67a-f48b435ba9cc

    Note: In DPM2012, Start-DPMProductionServerSwitchProtection has been deprecated. You have to use Start-DPMSwitchProtection instead.

    Stephane.

    Tuesday, June 12, 2012 12:27 PM
  • Hello Stephane

    thanks for that information.

    We tried to bring back the systems switched by the cmdlet back to their old protection group without success. Also after the primary DPM was online again we are not able to add the systems to their old protection group. They are not listed in the "Protected Servers" section below the primary DPM.

    Also primary DPM was not able to contact the agent on one of the protected servers switched by the cmdlet. But this could be fixed by using SetDPMServer.exe on the protected server.

    Markus

     

    Thursday, June 14, 2012 8:27 AM
  • We were able to bring back the systems to their old protection group. During our tests the systems were attached to the secondary DPM. After we removed them from the Secondary DPM they appeared in the Protected Servers section of the primary DPM.

    Markus

    Thursday, June 14, 2012 8:46 AM