Share via

Protected Computer Software Requirements

  • Article

Applies To: System Center Data Protection Manager 2010

Each computer that System Center Data Protection Manager (DPM) 2010 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

Protected computers Computer requirements

File servers

You can protect file servers on any of the following operating systems:

  • Windows Server 2003 with Service Pack 2 (SP2) - Core, Standard, Enterprise, and Datacenter Editions

  • Windows Server 2003 R2 with SP2

  • Windows Server 2008, Core, Standard, Enterprise, and Datacenter Editions

  • Windows Server 2008 with SP2

  • Windows Server 2008 R2, Core, Standard, Enterprise, and Datacenter Editions

  • Windows Server 2008 R2 with SP1, Core, Standard, Enterprise, and Datacenter Editions

  • Windows Storage Server 2008

Note the following:

Computers running SQL Server
  • Microsoft SQL Server 2000 with Service Pack (SP4), Standard, Enterprise, Workgroup, Compact, and Express Editions

    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 (https://go.microsoft.com/fwlink/?LinkId=186465).

  • Microsoft SQL Server 2005 with SP1, SP2, or SP3, Standard, Enterprise, Workgroup, Compact, and Express Editions

    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 (https://go.microsoft.com/fwlink/?LinkId=186465).

  • Microsoft SQL Server 2008

  • Microsoft SQL Server 2008 SP1 or SP2

Important

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
  • Exchange Server 2003 with Service Pack 2 (SP2), Standard and Enterprise Editions

    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 (https://go.microsoft.com/fwlink/?LinkId=186465).

  • Exchange Server 2007, Standard and Enterprise Editions

    Before you can protect Exchange Server 2007 data in a Clustered Continuous Replication (CCR) configuration, you must apply Knowledge Base article 940006: Description of Update Rollup 4 for Exchange 2007 (https://go.microsoft.com/fwlink/?LinkId=99291).

  • Exchange Server 2010

Important

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.

Computers running Virtual Server
  • Microsoft Virtual Server 2005 R2 SP1

  • Microsoft Virtual Server 2008 (non-clustered and clustered)

Note

To protect virtual machines for online backups, we recommend that you install Microsoft Virtual Server 2005 Updated Additions (https://go.microsoft.com/fwlink/?LinkId=84271).

Hyper-V

Windows SharePoint Services
  • Windows SharePoint Services 3.0

    Before you can protect a computer running Windows SharePoint Services 3.0, you must apply the update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0 (https://go.microsoft.com/fwlink/?LinkId=100392).

  • Windows SharePoint Services 3.0 with Service Pack 1 (SP1)

    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 (https://go.microsoft.com/fwlink/?LinkId=110346).

    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:

  • Windows SharePoint Services 4.0

  • Microsoft Office SharePoint Server 2007

    Before you can protect a computer running Office SharePoint Server 2007, you must apply the update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0 (https://go.microsoft.com/fwlink/?LinkId=100392).

  • Microsoft Office SharePoint Server 2007 with Service Pack 1 (SP1)

    If you use the Office SharePoint Server Search service, before you can protect Office SharePoint Server 2007 SP1 data, you must apply the following updates:

  • Office SharePoint Server 2010

Important

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 (https://go.microsoft.com/fwlink/?LinkId=186465).

Shared disk clusters
  • File servers

  • SQL Server 2005 with Service Pack 1 (SP1)

  • SQL Server 2008

  • Exchange Server 2003 with Service Pack 2 (SP2)

  • Exchange Server 2007

  • Exchange Server 2010

  • Hyper-V

Non-shared disk clusters
  • Exchange Server 2007

  • Exchange Server 2010

Workstations

  • Windows XP Service Pack 2 (SP2) or later


    Note

    The end-user restore feature is not enabled on Windows XP computers.

  • Windows Vista or Windows Vista Service Pack 1 (SP1)

  • Windows 7 Client

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.

If you are running a 32-bit edition of Exchange Server 2003, you must download Microsoft Exchange Server 2007 32-bit management tools (https://go.microsoft.com/fwlink/?LinkId=112325). The management tools are supported by all update methods such as Microsoft Update and Microsoft Systems Management Server (SMS).

To maintain up-to-date copies of eseutil.exe and ese.dll

  1. 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.

  2. 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”

See Also

Concepts

Hardware Requirements
Network Requirements

Other Resources

Software Requirements