none
Does upgrading the DPM agent to 2016 require a restart of the endpoint? RRS feed

  • Question

  • I'm planning an upgrade of the DPM 2012 R2 UR10 server to DPM 2016.  For anyone who has performed the upgrade, did the endpoint require a restart after updating the agent? If so, that definitely changes my timeline.

    Thank you,

    Darryl

    Wednesday, February 15, 2017 4:31 PM

Answers

  • HI,

    After the DPM 2016 upgrade the agents also need to be updated before protection can continue.  This is a something you need to do manually by clicking on the "update available" link.  Once the agent is updated no reboot is required, but as noted, we have seen some servers reboot automatically even if the option to automatically reboot is not checked.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Darryl Wilburn Friday, February 17, 2017 12:27 PM
    Thursday, February 16, 2017 10:45 PM
    Moderator

All replies

  • Hi,

    After the upgrade is complete, all of the agents will also need to be updated as well.  Protection should continue without requiring a reboot of the protected servers.  However we have had a couple reports that unplanned automatic reboots occurred after an agent update and the system event log showed the following.  This is under investigation, so plan accordingly.

    Log Name:      System
    Source:        User32
    Date:          <date>
    Event ID:      1074
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          SYSTEM
    Computer:      <computer_name>
    Description:
    The process C:\Windows\Microsoft Data Protection Manager\DPM\ProtectionAgents\AC\5.0.158.0\vcredist2012_x64.exe (Computer_name) has initiated the restart of computer Computer_name on behalf of user NT AUTHORITY\SYSTEM for the following reason: Application: Installation (Planned)
     Reason Code: 0x80040002
     Shutdown Type: restart
     Comment:


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, February 15, 2017 11:29 PM
    Moderator
  • Thank you for the quick response, Mike.  To make sure I'm clear, DPM 2016 will continue to backup endpoints running the 2012 R2 agent, but updating the endpoints should be a priority?  Or, as part of the upgrade, are the updated agents pushed to the endpoints by the process of upgrading?  Splitting hairs I know, but it determines whether to update during the week (assuming little or no disruption of service) versus updating on the weekend because the agents are automatically updated and may or may not generate a restart of the endpoint.  Thanks again.

    Darryl

    • Proposed as answer by Muyita Friday, February 17, 2017 5:37 PM
    Thursday, February 16, 2017 3:41 PM
  • HI,

    After the DPM 2016 upgrade the agents also need to be updated before protection can continue.  This is a something you need to do manually by clicking on the "update available" link.  Once the agent is updated no reboot is required, but as noted, we have seen some servers reboot automatically even if the option to automatically reboot is not checked.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Darryl Wilburn Friday, February 17, 2017 12:27 PM
    Thursday, February 16, 2017 10:45 PM
    Moderator