It is important to emphasize why you need a reboot of you production environment. When Microsoft makes changes to the drivers that is a part of the deduplication process the DPM team must update their code to adopt to the changes. For DPM to be 100% adoptable the operating system kernel needs to be rebooted due to the fact of re-initializing the deduplication updates made by the Windows Server team. Hence, this is not due to DPM but the fact of re-initializing the code changes for the deduplication engine made by the Windows Server team.
The content of UR4 is a mixture of many good things, the following list provides a description of what has been fixed or added to the product:
- Item level recovery does not restore custom permissions when Microsoft SharePoint is running localized language packs.
You try to back up SharePoint when SharePoint has various files that have custom access permission settings and is using a non-English locale for SharePoint sites. When you try to recover the files, data is recovered successfully. However, the custom permissions may be lost. This causes some users to no longer have access to the file until permissions are restored by the SharePoint administrator.
- The DPM user interface crashes, and you receive the following error message: Connection to the DPM service has been lost.
This issue occurs when you change some protection groups after you upgrade to DPM 2012 R2 Update Rollup 2 or a later version.
- You experience issues when you try to restore a SQL Server database that has error 0x800423f4.
You have a SQL Server database that uses multiple mount points that point to the same volume and that protect it by using DPM. When you try to recover from an existing recovery point, you receive an error message 0x800423f4.
- An instance of SQL Server is missing when you try to create a protection group (PG).
You have two or more instances of SQL Server on same server so that one of the database names in one instance is a substring of another name of an instance of SQL Server. For example, you have a default instance of SQL Server and another instance that is named "contosoinstance." Then, you create a database that is named "contosoins" in the default instance of SQL Server.
In this case, when you try to create or change a protection group, the “contosoinstance” SQL instance and its database do not appear in the Create Protection Group Wizard.
- The DPM console or service crash after VMs are removed from the Hyper-V host.
Several virtual machines on the Hyper-V host are physically removed. Then, the DPM UI crashes when you try to stop protection for these virtual machines.
- DPM crashes with NullReferenceException.
When you protect a SQL database by using long-term protection on tape, the SQL logs are moved to a different disk volume. When you try to make a backup for the first time after you move the logs, the DPM UI crashes. However after you restart the UI, everything works correctly.
- Scheduled backup to tape runs on an incorrect date for quarterly, semi-annually, and yearly backups. In some cases, you see that the backup runs before the specific date.
- The DPM UI sometimes crashes when you change a protection group that has the following error: Connection to the DPM service has been lost. (ID: 917)
The following features has been added in UR4:
- Added support for protecting SQL Server 2014
This update let you protect SQL Server 2014 as a workload. There is no change in the user experience or in scenarios that are supported. Therefore, you can continue to back up SQL Server 2014 by using DPM in the same way that you protected older versions of SQL Server.
Unsupported scenarios in SQL Server 2014:
• You cannot use SQL Server 2014 as the DPM configuration database.
• You cannot back up the data that is stored as Windows Azure blobs from SQL Server 2014.
• The "Prefer secondary backup" preference for the SQL Always On option is not supported completely. DPM always takes a backup from the secondary. If no secondary can be found, the backup fails.
- Added support for SQL Server 2012 Service Pack 2 (SP2)
This update lets you protect the latest SQL Server 2012 SP2 as a workload and also use it as a DPM configuration database. There is no change in the user experience or scenarios that are supported. Therefore, you can continue to back up SQL Server 2012 SP2 by using DPM in the same way that you protected older SQL Server versions.
- Simplified steps for Online backup registration
Note Existing DPM to Azure customers should upgrade to the latest agent (version 2.0.8689.0 or a later version available here). In case this is not installed, online backups fail, and no DPM to Azure operations will work.
By adopting the latest new features and improvements in this update, DPM customers can register for Azure protection in several clicks. These new features and improvements remove the dependency of creating a certificate by usingmakecert and uploading it to the Azure portal. Instead, you can download vault credentials from the vault page on the Azure portal and use those credentials for registration.
To register the DPM server to the Azure backup vault, follow these steps.
You must have a subscription on the Azure portal, and a backup vault must be created on the portal.
If you already use DPM-A
1. From the backup vault page on the portal, download the agent for SC Data Protection Manager.
2. Run the installer on the server. To do this, follow these steps:
a. Select the folder to install the server.
b. Enter the correct proxy settings.
c. Opt in for Microsoft updates, if you are not already opted in. Critical updates are usually propagated through Microsoft updates.
d. The installer verifies the prerequisite software and installs them.
Please be aware that you do not have to register the server again if the server is already registered and backups are in progress. In this case, you have only to upgrade the agent.
Getting started with DPM-A
3. From the backup vault page on the portal, follow these steps:
. Download vault credentials.
a. Download the agent for System Center Data Protection Manager.
4. Run the installer on the server. To do this, follow these steps:
. Select the folder where you want to install the agent.
a. Enter the correct proxy settings.
b. Opt in for Microsoft updates, if you have not already opted in. Critical updates are usually propagated through Microsoft updates.
c. The installer will verify the prerequisite software and installs them.
5. Register the DPM server. To do this. follow these steps:
. In Data Protection Manager, click Online, and then click Register Server.
a. In the Registration window, select the vault credential file that is downloaded from the portal. In the case of a remote scenario, only the network share path is enabled.
b. Follow the rest of the steps, and complete the registration.
Click on the following link to download UR4 (https://support.microsoft.com/en-us/kb/3009516) and remember to reboot your environment.