Update Rollup 9 for System Center 2012 R2 Data Protection Manager

ID KB3112306
Type mskb
Reporter Microsoft
Modified 2016-02-11T17:37:54


<html><body><p>Describes the issues that are fixed in Update Rollup 9 for Microsoft System Center 2012 R2 Data Protection Manager.</p><h2>Introduction</h2><div class="kb-summary-section section">This article describes the issues that are fixed in Update Rollup 9 for Microsoft System Center 2012 R2 Data Protection Manager. It also contains the installation instructions for this update.<br/><br/><span class="text-base">Note</span> Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (version 2.0.8719.0 or greater). If the latest agent is not installed, online backups will fail, and no Data Protection Manager to Windows Azure operation will work<br/><br/></div><h2></h2><div class="kb-moreinformation-section section"><h3 class="sbody-h3">Features implemented in this update rollup</h3><ul class="sbody-free_list"><li><span class="text-base">Automatically repair DPM Filter corruptions without requiring a consistency check for file server backups</span><br/><br/>If the DPM filter goes into a corrupted state (for example, if a production server crashes or there's an abrupt shutdown of a computer from a power failure), the file system data source no longer goes into an inconsistent state. After this update is installed, DPM automatically repairs the filter corruption by triggering an automatic synchronization job within 15 minutes of the previous sync/backup job failure. The corrective synchronization job is much faster than a consistency check job. The new scheduled sync job uses the Windows USN Journal to detect which files changed from the last successful sync. In this case, it performs a block-by-block comparison for the changed files only to rebuild our bitmap filter instead of comparing all the protected files.<br/><br/>The following results show the time that's required by the automatic repair synchronization job for a large volume, based on our internal testing. The amount of time depends on how much churn occurs and how much network bandwidth is available. <br/><br/><div class="table-responsive"><table class="sbody-table table"><tr class="sbody-tr"><td class="sbody-td">File server configuration</td><td class="sbody-td">Stand-alone file server with 3 GB RAM and 1 Intel Xeon CPU (2.67 GHz)</td></tr><tr class="sbody-tr"><td class="sbody-td">Network configurations</td><td class="sbody-td">Ethernet card speed 10 Gbps. Max data transfer speed 12.5 MBps</td></tr></table></div><h4 class="sbody-h4">Setup 1</h4><div class="table-responsive"><table class="sbody-table table"><tr class="sbody-tr"><td class="sbody-td">Size of protected volume</td><td class="sbody-td">2 TB volume with 60 million files</td></tr><tr class="sbody-tr"><td class="sbody-td">Daily churn</td><td class="sbody-td">Static File Server with very few files changing (almost no churn)</td></tr><tr class="sbody-tr"><td class="sbody-td">Time taken to repair bitmap with the new update</td><td class="sbody-td">26 seconds</td></tr></table></div><h4 class="sbody-h4">Setup 2</h4><div class="table-responsive"><table class="sbody-table table"><tr class="sbody-tr"><td class="sbody-td">Size of protected volume</td><td class="sbody-td">2 TB volume with 80 million files</td></tr><tr class="sbody-tr"><td class="sbody-td">Daily churn for test setup </td><td class="sbody-td">2% daily churn with around 40 GB data churn (40,000 files churned randomly).</td></tr><tr class="sbody-tr"><td class="sbody-td">Time taken to repair bitmap with the new update</td><td class="sbody-td">2.5 hours (majority of the time taken for network transfer of 40 GB)</td></tr></table></div><br/><br/><span class="text-base">Notes</span><br/><br/><ul class="sbody-free_list"><li>For a few corner scenarios (for example, USN journal wrap), DPM will still mark the replica as inconsistent. In this situation, a full consistency check will be necessary and will trigger the old behavior by performing a full block-by-block checksum comparison for all the protected files. The consistency check can be triggered manually by a user or through a scheduled consistency check, depending on protection group settings.</li><li>The fix applies only to file servers, not to other DPM workloads.</li></ul><br/><br/></li><li><span class="text-base">No production server restart is required when you upgrade from DPM 2012 R2 Update Rollup 6 or later versions</span><br/><br/>We have performed an extensive review of the DPM architecture to avoid production server restarts when you upgrade the DPM Agent. There were a few cases in which the Agent update was flagging for restart, and these are fixed now. Therefore, if you already upgraded to DPM 2012 R2 Update Rollup 6 or a later version, you will not experience a restart when you upgrade to this update.<br/><br/></li><li><span class="text-base">Removing the Offline/Online tag from Hyper-V VM name in the DPM UI</span><br/><br/>DPM used to display an Offline/Online tag to the VM name for Hyper-V VMs. This was intended was to notify users about whether the VM was paused during backup or was always online. However, this behavior was confusing for the customers because the tag was static and it was determined during first inquiry and not updated later. Moreover, for Hyper-V 2012 R2, the VMs will never be interrupted during backups as per the Hyper-V changes mentioned <a href="http://blogs.msdn.com/b/virtual_pc_guy/archive/2015/02/16/hyper-v-backup-doesn-t-interrupt-running-virtual-machines-anymore.aspx" id="kb-link-2" target="_self">here</a>.<br/><br/>The Offline/Online tag has been removed, and we now display only the Hyper-V VM name. This behavior applies to all existing PGs as well as to new PGs.<br/><br/><span class="text-base">Note</span> If you have any external scripts that rely on the Offline/Online VM tag, the script must be updated before you upgrade to Update Rollup 9.</li></ul><h3 class="sbody-h3">Issues that are fixed in this update rollup</h3><ul class="sbody-free_list"><li>When you perform a recovery for an external data source from an imported tape, and if you try to run a search on the recovery tab, DPM UI may crash.</li><li>If you try to perform an original location recovery from an inactive cloud protection (such as when you remove cloud protection but retain cloud recovery points), the recovery may fail. An alternative location recovery will work in this case.</li><li>If you are protecting client data sources, alternative location recovery may fail. An original location recovery still works in this situation.</li><li>Item level recovery for SharePoint may fail after you upgrade to DPM 2012 R2 Update Rollup 6, 7, or 8.</li><li>If you are already protecting a stand-alone SQL database by using DPM, and then you try to create a mirror database and protect it with DPM, DPM Self Service Recovery Tool does not display the mirror database. However, the DPM recovery wizard shows the mirror database.</li><li>DPM may display the following redundant messages in the event log if End-User Recovery is enabled for any data source and at the same time you configure BMR:<br/><br/><div class="indent"><div class="sbody-error">Failed to update permissions used for end-user recovery on <strong class="sbody-strong">DPM_FQDN</strong>. Permissions update failed for the following reason: (ID: 3123)</div></div></li><li>The DPM console may crash when you open DPM canned reports.</li></ul></div><h2></h2><div class="kb-moreinformation-section section"><h3 class="sbody-h3">Known issue</h3>After you install this update, Data Protection Manager may crash if you protect client workloads. This issue occurs only when client backups are triggered while the client is not located on a corporate network and when you use a VPM or Direct Access (DA) connection. You will not be affected if you don't have any client workloads protected by your DPM server.<br/><br/>To resolve this issue, download the script from the Microsoft Download Center, and then run the script with DPM Administrator credentials on the affected DPM server:<br/><br/><div class="indent"><img alt="Download " class="graphic" src="/library/images/support/kbgraphics/public/en-us/download.gif" title="Download "/><a href="https://www.microsoft.com/en-in/download/details.aspx?id=51096" id="kb-link-3" target="_self">Download the script package now.</a><br/><br/></div><br/><span class="text-base">Note</span> Make sure that SHA-2 support is available on the computer on which you download the workaround script. Otherwise, the download may fail, as the script is SHA-2 signed.<br/><br/>For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: <div class="indent"><a href="https://support.microsoft.com/en-us/help/119591" id="kb-link-4">119591 </a> How to obtain Microsoft support files from online services </div>Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. </div><h2></h2><div class="kb-moreinformation-section section"><br/><h3 class="sbody-h3">How to obtain and install Update Rollup 9 for System Center 2012 R2 Data Protection Manager</h3><h4 class="sbody-h4">Download information</h4>Update packages for Data Protection Manager are available from Microsoft Update or by manual download. <br/><br/><h5 class="sbody-h5 text-subtitle">Microsoft Update</h5>To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Data Protection Manager component installed:<ol class="sbody-num_list"><li>Click <span class="text-base">Start</span>, and then click <span class="text-base">Control Panel</span>.</li><li>In Control Panel, double-click <span class="text-base">Windows Update</span>.</li><li>In the Windows Update window, click <span class="text-base">Check Online for updates from Microsoft Update</span>.</li><li>Click <span class="text-base">Important updates are available</span>.</li><li>Select the update rollup package, and then click <span class="text-base">OK</span>.</li><li>Click <span class="text-base">Install updates</span> to install the update package.</li></ol><h5 class="sbody-h5 text-subtitle">Manual download of the update packages</h5>Go to the following website to manually download the update packages from the Microsoft Update Catalog:<br/><br/><div class="indent"><img alt="Download " class="graphic" src="/library/images/support/kbgraphics/public/en-us/download.gif" title="Download "/><a href="http://catalog.update.microsoft.com/v7/site/search.aspx?q=3112306" id="kb-link-5" target="_self">Download the Data Protection Manager update package now.</a></div><br/></div><h2></h2><div class="kb-moreinformation-section section"><div class="faq-section" faq-section=""><div class="faq-panel"><div class="faq-panel-heading" faq-panel-heading=""><span class="link-expand-image"><span class="faq-chevron win-icon win-icon-ChevronUpSmall"></span></span><span class="bold btn-link link-expand-text"><span class="bold btn-link">Installation instructions</span></span></div><div class="faq-panel-body" faq-panel-body=""><span><div class="kb-collapsible kb-collapsible-collapsed">To install this update for Data Protection Manager, follow these steps:<ol class="sbody-num_list"><li>Before you install this update, make a backup of the Data Protection Manager database.</li><li>Install this rollup package on the server that's running System Center 2012 R2 Data Protection Manager. To do this, run Microsoft Update on the server.</li><li>In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.<br/><br/><span class="text-base">Note</span> This update rollup agent update requires you to restart protected servers in order to create or change protection groups.<br/><br/><h5 class="sbody-h5 text-subtitle">Method 1: Update the protection agents from the Data Protection Manager Administrator Console</h5><ol class="sbody-alpha_list"><li>Open the Data Protection Manager Administrator Console.</li><li>Click the <span class="text-base">Management</span> tab, and then click the <span class="text-base">Agents</span> tab.</li><li>In the <strong class="uiterm">Protected Computer</strong> list, select a computer, and then click <strong class="uiterm">Update</strong> on the <span class="text-base">Action</span> pane.</li><li>Click <strong class="uiterm">Yes</strong>, and then click <strong class="uiterm">Update Agents</strong>.</li></ol><br/><br/><br/><h5 class="sbody-h5 text-subtitle">Method 2: Update the protection agents on the protected servers</h5><ol class="sbody-alpha_list"><li>Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:<br/><br/><div class="indent"><strong class="sbody-strong">Data_Protection_Manager_installation_location</strong>\DPM\DPM\Agents\RA\4.2.1417.0</div><br/><br/>The installation packages are as follows:<ul class="sbody-free_list"><li><span class="text-base">For x86-based updates:</span> i386\1033\DPMProtectionAgent_KB3112306.msp</li><li><span class="text-base">For x64-based updates:</span> amd64\1033\DPMProtectionAgent_KB3112306_AMD64.msp</li></ul><br/><br/></li><li>Run the appropriate DPMProtectionAgent.msp package on each protected server, depending on the architecture of the agent.</li><li>Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.</li><li>Click the Management tab, and then click the <strong class="uiterm">Agents</strong> tab. Select the protected server, update the information, and then verify that the agent version number is <span class="text-base">4.2.1417.0</span>.</li></ol><br/></li></ol><br/></div><br/></span></div></div></div></div></body></html>