Upgrading the Agents
Once the upgrade of SP1 is complete on your primary DPM 2012 server, you will then need to update any DPM agents that you have deployed in your environment. To do this, open the DPM 2012 SP1 console and click on the Management tab from the wunderbar and then click on the Agents link to display a list of all your agents awaiting upgrade as shown below.
When you click on the Update Available link beside an agent, you will be presented with the following window asking you to confirm if you want to proceed with upgrading the agent to SP1. Click Yes to begin the agent upgrade process.
Once the agent update process completes, you should then be able to verify the SP1 upgrade by confirming that the version of the Protection Agent is set to 4.1.3313.0 as shown below
You might also notice from the Agents list that one or two servers have a status of Restart Pending beside them. These will need to be restarted before you can backup data from them and any downtime due to this will need to be planned for as part of your maintenance schedule.
Run a Manual Consistency Check on Protected Data
Once the primary server and the agents have all been upgraded, you will now need to run a manual consistency check on all of your protection groups. This for me forms the longest part of DPM upgrades when in production environments as the more data you have being backed up, the longer these manual consistency checks will take.
You might also notice from the Agents list that one or two servers have a status of Restart Pending beside them. These will need to be restarted before you can backup data from them and any downtime due to this will need to be planned for as part of your maintenance schedule.
Run a Manual Consistency Check on Protected Data
To run the consistency checks, open up the DPM 2012 SP1 console and navigate to the Protection tab in the wunderbar. Once here, you will see that all of your protection groups are in an inconsistent state. Simply right-mouse click on a protection group and then choose the Perform a Consistency Check option from the resulting menu as shown below to kick off a consistency check of replica's contained in that protection group.
Repeat this task on all protection groups until they are all returned to a healthy state.
Upgrade Stand-Alone Consoles
If you have deployed the DPM 2012 console onto any other servers in your environment (such as to support integration with System Center 2012 Orchestrator for example), you will need to first uninstall the Microsoft System Center 2012 - DPM Remote Administration application from the computer before deploying the upgraded SP1 version.
To uninstall the stand-alone console, logon to the server with an administrative account, click Start and type appwiz.cpl as below.
Now hit Enter to open the Programs and Features applet, find the Microsoft System Center 2012 - DPM Remote Administration program from the list, right-mouse click on it and then choose the Uninstall option to remove it as below
Once you have uninstalled the previous version, browse to the location that you have extracted/mounted the DPM 2012 SP1 media to and then with an administrative account, right-mouse click on the Setup executable and choose the Run As Administrator option to begin the installation
From the Installation splash screen, choose the DPM Remote Administration link as shown below
Accept the licence agreement and click OK
Click Next from the Welcome screen
When all the prerequisites have passed, click Next to move on
Choose your installation location, then click Next to continue
Select your Microsoft Update option and then hit the Install button to begin the SP1 installation of the Remote Administration feature
When the installer is finished, you should see the screen below telling you that it has been successful and you can then hit the Close button to finish
Finally, open up the newly installed stand-alone console, choose the DPM server that you wish to connect with and then ensure that the title bar of the console references Service Pack 1 as below.
Upgrade the Secondary DPM Servers
If you have deployed any additional DPM 2012 servers as a secondary or disaster recovery solution (a DPM server that is backing up another DPM server), then you will also need to run the SP1 upgrade on these. The process is identical to the steps you would have already followed up to this point but for reference, here are the steps again:
On the Secondary Server:
Post Upgrade Tasks
So we're just about finished the SP1 upgrade of DPM 2012 and all that's left to do is to carry out a few quick tasks/checks - some of which may not be applicable to every environment.
Conclusion
That should be all you need to do now to upgrade DPM 2012 to Service Pack 1. Ensure that you refer back to the 'Upgrade Sequencing for System Center 2012 SP1'. guide to ensure that you upgrade any other System Center 2012 products in the correct order.
If you have deployed any additional DPM 2012 servers as a secondary or disaster recovery solution (a DPM server that is backing up another DPM server), then you will also need to run the SP1 upgrade on these. The process is identical to the steps you would have already followed up to this point but for reference, here are the steps again:
On the Secondary Server:
- Close Administrator Console and Management Shell
- Carry out the tasks in the Upgrade Primary DPM Server section in Part 1 of this series
- Upgrade any protection agents on the secondary server by following the Upgrading the Agents section earlier in this post
- Run a consistency check on all protected data by following the steps in the Run a Manual Consistency Check on Protected Data section earlier in this post
Post Upgrade Tasks
So we're just about finished the SP1 upgrade of DPM 2012 and all that's left to do is to carry out a few quick tasks/checks - some of which may not be applicable to every environment.
- If you have previously configured tape library sharing and had to remove it as part of the initial pre-upgrade tasks for SP1, you can now go ahead and reconfigure it again using the How to Setup Tape Library Sharing link on TechNet for information.
- If you had SCVMM Hyper-V Live Migration configured before doing the upgrade, you must run Set-DpmGlobalProperty -KnownVmmServers <VmmServerName> to continue protection
- If you were protecting system state and you have customized the location of the backup that is staged, this customization will be lost in the PSdataSourceConfig.xml file during the upgrade. The staging location will be set to the drive with the largest available disk space. This will need to be reconfigured again.
Conclusion
That should be all you need to do now to upgrade DPM 2012 to Service Pack 1. Ensure that you refer back to the 'Upgrade Sequencing for System Center 2012 SP1'. guide to ensure that you upgrade any other System Center 2012 products in the correct order.
No comments:
Post a Comment