DPM and Production Server Pre-requisites (Exhaustive) - System Center: Data Protection Manager Engineering Team Blog - Site Home - TechNet Blogs

DPM and Production Server Pre-requisites (Exhaustive)

DPM and Production Server Pre-requisites (Exhaustive)

  • Comments 1
  • Likes

DPM V2 Beta 2 Installation Requirements  

A Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) installation involves installing the DPM prerequisite software and the DPM application. The DPM Setup Wizard guides you through the process of specifying the DPM installation settings, and automatically installs or provides links to install the prerequisite software as part of the integrated DPM installation process.  The information below specifies the system requirements for the DPM server and protected server along with instructions for specifying the non-default settings when installing the operating system before installing DPM.

 

DPM V2 Beta 2 System Requirements            

Before you install Microsoft System Center Data Protection Manager V2 Beta 2 (DPM), you need to ensure that the DPM server and the servers and applications it is going to protect meet network and security requirements. You must also ensure that they are running on supported operating systems and that they meet the minimum hardware and software requirements.

DPM is designed to run on a dedicated, single-purpose server and cannot be either a domain controller or an application server. The DPM server must not serve as a management server for Microsoft Operations Manager 2005 (MOM) or Microsoft System Center Operations Manager 2007 (Operations Manager); you can, however, monitor the DPM server and the servers that it protects in MOM or Operations Manager.

 

Security Requirements            

You must have the following permissions requirements before you install Microsoft System Center Data Protection Manager V2 Beta 2 (DPM):

·         Logon as a domain user who is a member of the local administrators group.

Note: In this Beta 2 release of DPM V2, after you install DPM, you must be a domain user with administrator access to use DPM Administrator Console.

 

Network Requirements            

Following are the Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) network requirements:

·         The DPM server must be deployed within a Windows Server 2003 Active Directory domain. The domain controllers must be running either Windows Server 2003 or Windows Server 2003 R2 Server.

Note: DPM supports protecting servers across domains; however, you must establish two-way trust across the domains.

·         The DPM server requires persistent connectivity with the servers and desktop computers it protects.

 

Hardware Requirements            

Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) requires a disk that is dedicated to the storage pool and to the following:

·         System files

·         DPM installation files

·         DPM prerequisite software

·         DPM database files

Note: You can install DPM on the same volume that the operating system is installed on, or on a different volume that does not include the operating system. However, you cannot install DPM on the disk that is dedicated to the storage pool. The storage pool is a set of disks on which the DPM server stores the replicas and recovery points for the protected data. If you require additional disk space in the storage pool, you can create custom volumes from your existing disk and allocate them to your storage pool.

 

Component

Minimum Requirement

Recommended Requirement

Processor

·         1 GHz or faster

   

Memory

·         1 GB RAM

   

Disk space for DPM installation

·         Program files drive: 410 MB

·         Database files drive: 900 MB

·         System drive: 2650 MB

Note: The system drive disk space requirement is necessary if you chose to install the instance of SQL Server from the DPM download package. If you are using an existing instance of SQL Server, this disk space requirement is considerably less.

   

Disk space for storage pool

Note: The storage pool does not support USB/1394 disks.

·         1.5 times the size of the protected data

·         2 to 3 times the size of the protected data

 

Note: DPM requires a minimum of 300 MB of free space on each protected volume for the change journal. Additionally, before archiving data to tape, DPM copies the file catalog to a DPM temporary installation location; therefore, we recommend that the volume on which DPM is installed contains 2-3 gigabytes (GB) of free space.

 

Software Requirements            

A complete installation of System Center Data Protection Manager V2 Beta 2 (DPM) includes the DPM server operating system, the DPM prerequisite software, and the DPM application. Additionally, each server that DPM protects must meet the protected server software requirements.

 

DPM Server Operating System Requirements            

The following are the Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) operating system requirements:

·         Windows Server 2003 with Service Pack 2 (SP2)

·         Windows Server 2003 R2 with SP2

·         Windows Storage Server 2003 with SP2

To obtain SP2 for Windows Storage Server 2003, contact your original equipment manufacturer.

·         Windows Storage Server 2003 R2 with SP2

Note: DPM supports Standard and Enterprise Editions for all supported DPM operating systems.

Note: DPM supports 32-bit and x64-bit operating systems. This release of DPM does not support ia64-bit operating systems.

 

Installing Windows Server 2003            

You must properly configure Windows Server 2003 to support a Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) installation. Perform the following steps to specify nondefault settings during an installation of Windows Server 2003 on a DPM server.

 

To install Windows Server 2003:

1. When Setup prompts you to format the Windows installation partition, choose the NTFS file system.

2. In the Computer Name dialog box, type a name for the DPM server. The name must be unique within the Active Directory domain. Once you select a computer name it cannot be changed after installing DPM 2007.  If you decide to change the computer name after DPM 2007 is installed you will need to completely uninstall DPM 2007 them perform a complete installation of DPM 2007 again.

3. In the Workgroup or computer domain dialog box, add the DPM server to the domain that contains the servers that you plan to protect.

4. After installation is complete, apply all available Windows Server 2003 service packs and updates including Windows Server 2003 Service Pack 2 (SP2).

 

After installing Windows, you must be logged on as a domain user who is a member of the local administrators group.

 

Installing the required components for Windows Server 2003

Following are the Windows Server 2003 components you must install before installing DPM:

·         Windows Deployment Services (WDS) on Windows Server 2003 Service Pack 2 (SP2) servers

- OR -

·         Single Instance Storage (SIS) on Windows Storage Server R2

 

DPM Server Software Requirements            

The Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) server must be a dedicated, single-purpose server, and it cannot be either a domain controller or an application server. The DPM server cannot be the Management Server for Microsoft Operations Manager 2005 (MOM) or Microsoft System Center Operations Manager 2007. Before you install DPM, you must install Windows PowerShell 1.0 from http://go.microsoft.com/fwlink/?LinkId=87007. DPM Setup will then install the additional required prerequisite software.

 

Following is the DPM server prerequisite software that DPM Setup installs before installing the DPM application:

·         Microsoft .NET Framework 2.0

·         Internet Information Services (IIS) 6.0 for Windows Server 2003

Note: By default, Windows Server 2003 does not install IIS after you install Windows Server 2003. If you do not install IIS before installing SQL Server 2005, SQL Server will not install SQL Server Reporting Services.

·         Microsoft SQL Server 2005 Workstation components.

Note: You can use an existing remote instance of SQL Server for your DPM database. If you choose to use a remote instance of SQL Server, you must install sqlprep.msi to create and configure the DPM database on the remote SQL Server. To install sqlprep.msi, after you download the DPMV2Beta2 download package, double-click sqlrep.msi located in the DPM2008\msi folder.

·         Microsoft SQL Server 2005 with Reporting Services

Note: If SQL Server Reporting Services is installed on the remote SQL Server, DPM Setup will use that Reporting Service. If SQL Server Reporting Services is not installed on the remote computer running SQL Server, you must install and configure the service on the remote computer running SQL Server.

·         Microsoft SQL Server 2005 Service Pack 1 or Service Pack 2 for Windows Server 2003

Note:  DPM V2 Beta 2 contains the Evaluation Edition of SQL Server 2005.

 

Protected Server Requirements            

Each server Microsoft System Center Data Protection Manager V2 Beta 2 (DPM) protects must meet the requirements listed in Table 1.2.

Note: Protected volumes must be formatted as NTFS file system. DPM cannot protect volumes formatted as FAT or FAT32.

Note: The volume must be at least 1 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.

Table 1.2   Protected Server Requirements

 

Protected Servers

Server Requirements

File servers

·         Windows Server 2003 with Service Pack 1 (SP1) or later

·         Windows Server 2003 x64

·         Windows Server 2003 R2

·         Windows Server 2003 R2 x64

·         Windows Storage Server 2003 with SP1 or later

Note: To obtain SP1 for Windows Storage Server 2003, contact your original equipment manufacturer.

·         Windows Storage Server 2003 R2

·         Windows Storage Server 2003 R2 x64

Note: DPM supports Standard and Enterprise Editions of all the required operating systems.

Computers running SQL Server

·         Microsoft SQL Server 2000 with Service Pack 4 (SP4)

- OR -

·         Microsoft SQL Server 2005 with SP1 or Service Pack 2 (SP2)

 

Note: DPM supports Standard, Enterprise, Workgroup, and Express Editions of SQL Server.

 

Important: On computers running SQL Server 2005 SP1 you must start the SQL Server VSS Writer Service on the SQL Server before you can start protecting SQL Server data. On computers running SQL Server 2005 the SQL Server VSS Writer Service is turned on by default.

To start the SQL Server VSS Writer Service

1. Click Start, point to Administrative Tools, and then click Services.

2. On the Services screen, scroll down and right-click SQL Server VSS writer, and then click Start.

Computers running Exchange Server

·         Exchange Server 2003 with SP2

- OR -

·         Exchange Server 2007

 

Note: DPM supports Standard and Enterprise Editions of Exchange Server.

Computers running Virtual Server

·         Microsoft Virtual Server 2005 R2 SP1

 

Note: We recommend that you install version 13.715 of Virtual Machine Additions (http://go.microsoft.com/fwlink/?LinkId=84271) to protect virtual machines for online backups.

Windows SharePoint Services

·         Windows SharePoint Services 3.0

·         Microsoft Office SharePoint Server 2007

 

Important: Before you can protect Windows SharePoint data, you must start the Windows SharePoint Writer Service on the Windows SharePoint Server, and then provide the protection agent with credentials for the Windows SharePoint Services farm.

Shared disk clusters

·         File servers

·         SQL Server 2000 with SP4

·         SQL Server 2005 with SP1

·         Exchange Server 2003 with SP2

·         Exchange Server 2007

 

Note: Only one Network Name resource can exist for the resource group that you are protecting. If there is more than one Network Name resource for a single resource group, DPM can support this configuration only if all dependant resources are associated with the same Network Name resource. For example, if you attempt to protect a SQL shared disk cluster, the physical disk resource that SQL uses must be associated with the same Network Name resource as the computer running SQL Server and the SQL Server Agent.

Non-shared disk clusters

·         Exchange Server 2007

Workstations

·         Windows XP Professional SP2

·         All Windows Vista editions except Home (must be member of a domain)

- Tom Malley

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment