Applies To: System Center 2012 - Data Protection Manager, System Center 2012 SP1 - Data Protection Manager
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Each computer that System Center 2012 – Data Protection Manager (DPM) protects must meet the system requirements listed in the following table. Protected volumes must be formatted as NTFS file system. DPM cannot protect volumes formatted as FAT or FAT32. Also, the volume must be at least 1 gigabyte (GB) for DPM to protect it. DPM uses the Volume Shadow Copy Service (VSS) to create a snapshot of the protected data, and VSS will create a snapshot only if the volume size is greater than or equal to 1 GB.
Protected Computer Requirements
Before you can protect a file server running Windows Server 2003 SP2, you must apply the following updates:
Before you can protect a computer running SQL Server 2000 on Windows Server 2003 SP2, you must apply Knowledge Base article 940349: Update for Windows Server 2003
Before you can protect a computer running SQL Server 2005 on Windows Server 2003 SP2, you must apply Knowledge Base article 940349: Update for Windows Server 2003
Before you can start protecting computers running SQL Server 2005 SP1, you must start the SQL Server VSS Writer service. By default, the SQL Server VSS Writer service is turned on for computers running SQL Server 2005. To start the SQL Server VSS Writer service, in the Services console, right-click SQL Server VSS writer, and then click Start.
Computers running Exchange Server
Before you can protect a computer running Exchange Server 2003 on Windows Server 2003 SP2, you must apply Knowledge Base article 940349: Update for Windows Server 2003
The eseutil.exe and ese.dll versions that are installed on the most recent release of Exchange Server must be the same versions that are installed on the DPM server.
In addition, you must update eseutil.exe and ese.dll on the DPM server if they are updated on a computer running Exchange Server after applying an upgrade or an update.
For more information about updating eseutil.exe and ese.dll, see Eseutil.exe and Ese.dll.
Before you can protect Windows SharePoint Services 3.0 data, you must do the following:
Start the Windows SharePoint Services VSS Writer service on the Windows SharePoint Services server and then provide the protection agent with credentials for the Windows SharePoint Services farm.
Install the SQL Server Client components on the front-end Web server of the Windows SharePoint Services farm that DPM is going to protect. For information about installing SQL Server 2008 components, see How to: Install SQL Server 2008
If you use the Office SharePoint Server Search service, before you can protect Windows SharePoint Services 3.0 data, you must apply the following updates:
Before you can protect a computer running any version of SharePoint Services or SharePoint Server on Windows Server 2003 SP2, you must apply the update in Knowledge Base article 940349: Update for Windows Server 2003
Eseutil.exe and Ese.dll
The architecture version of eseutil.exe and ese.dll must match the DPM server architecture. That means, if you are using the 64-bit version of DPM, you must have the 64-bit version of eseutil.exe and ese.dll.
To maintain up-to-date copies of eseutil.exe and ese.dll
Install the Microsoft Exchange Server 2007 management tools on the DPM server. When you install the management tools, ensure that you install the management tools for the latest version of Microsoft Exchange that you are protecting. For example, if one of your mail servers is running Microsoft Exchange 2007 and another mail server is running Microsoft Exchange 2007 SP1, you must install the management tools for Microsoft Exchange 2007 SP1.
At the command prompt, in the <DPM installation folder>\Bin directory, use the following syntax with the fsutil command to create a hard link for eseutil.exe: fsutil hardlink create <link> <target> On a typical installation, the command would look like the following: fsutil hardlink create “c:\program files\microsoft\dpm\bin\eseutil.exe” “c:\program files\microsoft\Exchange\bin\eseutil.exe”