In the next 3 posts, an installation guide for System Center Data Protection Manager 2007. Let’s start with explaining the environment I’ve used and the prerequisites.
First, let’s look at the prerequisites as they are provided by Microsoft. (http://technet.microsoft.com/en-us/library/bb808832.aspx)
First, the security requirements
1) Security Requirements
To install DPM you must be a local admin and logon to the computer where you want to install DPM. OK, this can be arranged
After the installation of DPM, you need to have a domain user with administrator access to use the DPM Administrator Console. Basically, this means that when you need to be able to use the administrator console, you need to be a local administrator on the DPM server.
2) Network Requirements
According to Microsoft, you need to have a windows server 2003 or windows server 2008 active directory domain. My testenvironment is a native windows server 2008 domain so no problems there. You also need to have persistent connectivity with the servers and desktop computers it protects and if you are protecting data across a WAN, then you need to have a minimum network bandwidth of 512kbps. So far so good
3) Hardware Requirements
Disks: You should have a disk that contains the storage pool and one that is dedicated to system files, DPM installation files, prerequisite software and database files. Basically, this means that you need an OS and program files just as any other server (you can divide it into multiple volumes) but the storage dedicated for the backups can’t be the same as above. When DPM takes the storage, it allocates it and it is not usable for something else.
CPU: Minimum 1Ghz, Recommended 2.33 Ghz
Memory: Minimum 2 GB RAM, Recommended 4 GB Ram
Pagefile: 0.2 percent the size of all recovery point volumes combined, in addition to the recommended size (1.5 times the Memory)
- Minimum: Program Files: 410 MB, Database: 900 MB, System Drive: 2650 MB
- Recommended: 2 till 3 GB of free space on the program files volume
Disk Space for storage pool: 1,5 Times the size of the protected data, recommended = 2 – 3 times the size of the protected data
LUNS: Maximum of 17 TB for GPT dynamic disks, 2 TB for MBR disks
32-bit servers: 150 data sources
64-bit servers: 300 data sources
Since this will be a test environment, there is no way I’m going to follow the complete requirements for DPM.
4) Operating System Prerequisites
32-bit or 64-bit servers. No ia64 bit is supported
The DPM server cannot be a management server for SCOM
The DPM server cannot be an application server or an DC server.
There is a VSS limitation on 32-bit servers. It can’t outgrow 10 TB of protected data. Preferred is 4 TB on a 32-bit server.
OS: Windows Server 2008 Standard and Enterprise Edition or Windows Server 2003 (R2) SP2 or later or Windows server 2003 Advanced server or Windows Server 2003 Storage server.
The management shell can also be run on windows XP SP2, Vista and Windows Server 2003 SP2 or later.
I will run the server on a Hyper-V platform (Not yet R2) and I’ve created a virtual machine with the following specifications
CPU: 2 * 3.60 GHz Xeon
Memory: 2048 MB
Storage: C:\ 40 GB (OS and application) D:\ 60 GB (Play storage for backup)
OS: Windows Server 2008 x64 SP2, Fully patched
Before I started with the installation, I’ve installed following things first:
- IIS 7 with the following options on:
- Common HTTP Features
- Static Content
- Default Document
- Directory Browsing
- HTTP Errors
- HTTP Redirection
- Application Development
- .NET Extensibility
- ISAPI Extensions
- ISAPI Filters
- Server Side Includes
- Health and Diagnostics
- HTTP Logging
- Request Monitor
- Windows Authentication
- Request Filtering
- Static Content Compression
- Management Tools
- IIS Management Console (not really a prerequisite but handy )
- IIS 6 Management Compatibility
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
- IIS 6 Scripting Tools
- IIS 6 Management Console
- SIS (Single Instance Store)
To enable this, open a command prompt with administrator privileges and run the following command:
start /wait ocsetup.exe SIS-Limited /Quiet /norestart
After this is finished, restart the server. To check if the SIS is enabled, open regedit and check the existence of the following key:
In the next part, the installation of SCDPM 2007