Deploying System Center Data Protection Manager 2007 Microsoft Corporation Published: Sep 2007 Abstract Deploying DPM 2007 provides step-by-step instructions for installing and configuring DPM 2007, and includes an introduction to the DPM user interface. Deploying DPM 2007 also provides information on troubleshooting your DPM installation and how to repair and uninstall DPM 2007.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only.
Contents Deploying DPM 2007 ....................................................................................................................... 7 In This Section.............................................................................................................................. 7 Installing DPM 2007 ........................................................................................................................ 7 In This Section............................................................
See Also ..................................................................................................................................... 30 Manually Install SQL Server 2005 ................................................................................................. 30 See Also ..................................................................................................................................... 32 Manually Install SQL Server 2005 SP2 .................................................
Starting the New Protection Group Wizard ................................................................................... 51 Selecting Members for the Protection Group ................................................................................ 52 Specifying Exchange Protection Options ...................................................................................... 54 Selecting a Name and Protection Method for the Protection Group .............................................
Remote SQL Server Issues ........................................................................................................... 72 Troubleshooting Error ID 4307 ................................................................................................... 73 Troubleshooting Protection Agent Installation Issues ................................................................... 74 DPM Administrator Console in DPM 2007 .................................................................................
Deploying DPM 2007 This content provides instructions for deploying Data Protection Manager 2007.
DPM 2007 System Requirements Before you install System Center Data Protection Manager (DPM) 2007, you need to ensure that the DPM server and the computers 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 requirements and software prerequisites.
Windows Server 2003 R2 Server, or Windows Server 2008 operating system (pre-release version). DPM 2007 running on Windows Server 2000 domain controllers does not support the following: • Protecting computers across domains. • Protecting a child Windows Server 2000 domain controller in a domain where Windows Server 2000 is the primary domain controller. • Protecting computers running Exchange Server 2007.
• DPM database files Note You can install DPM on the same volume that the operating system is installed on, or you can install DPM 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, which is a set of disks on which the DPM server stores the replicas and recovery points for the protected data. DPM owns and manages the disks in the storage pool, which must be dynamic.
Component Minimum Requirement Recommended Requirement (http://go.microsoft.com/fwlink/?LinkId=91859). Disk space for DPM installation • Program files drive: 410 megabytes (MB). • Database files drive: 900 MB. • System drive: 2650 MB. • Note 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.
Component Minimum Requirement Recommended Requirement The storage pool does not support Universal Serial Bus (USB)/1394 disks. Logical unit number (LUN) Deployment see Planning the Storage Pool (http://go.microsoft.com/fwlink/?LinkId=91965). N/A • Maximum of 17 TB for GUID partition table (GPT) dynamic disks • 2 TB for master boot record (MBR) disks Note These requirements are based on the maximum size of the disk as it appears to the Windows Server operating system.
Software Prerequisites A complete installation of System Center Data Protection Manager (DPM) 2007 includes the DPM server operating system, the DPM prerequisite software, and the DPM application. Each computer that DPM protects must meet the protected computer software requirements.
DPM Management Shell, an interactive command-line technology that supports task-based scripting is supported on the following operating systems: • Windows XP Service Pack 2. • Windows Vista. • Windows Server 2003 Service Pack 2 (SP2) and subsequent versions. Note DPM Management Shell can be installed on computers other than the DPM server, enabling you to administer multiple DPM servers remotely.
4. After installation is complete, apply all available Windows Server 2003 service packs and updates, including Windows Server 2003 Service Pack 2 (SP2). All Windows updates are available from Microsoft Windows Update (http://go.microsoft.com/fwlink/?LinkID=451). Windows Server 2003 SP2 is available from Windows Server 2003 Service Pack 2 (http://go.microsoft.com/fwlink/?LinkID=90633).
• Windows Deployment Services (WDS) on Windows Server 2003 Service Pack 2 (SP2) servers. -ORSIS on Windows Storage Server 2003 R2. Note If WDS and SIS are not already installed, DPM Setup prompts you for the Microsoft Windows Server 2003 product CD during the installation. • Microsoft .NET Framework 2.0. • Internet Information Services (IIS) 6.0 for Windows Server 2003. (IIS 6.0 is not installed on Windows Server 2003 by default.) • IIS 7.0 for Windows Server 2008 (Pre-Release version). (IIS 7.
Note DPM 2007 contains the Standard Edition of SQL Server 2005. • Microsoft SQL Server 2005 Service Pack 2. See Also Hardware Requirements Network Requirements Security Requirements Protected Computer Software Prerequisites Each computer that System Center Data Protection Manager (DPM) 2007 protects must meet the requirements listed in the following table. Protected volumes must be formatted as NTFS file system. DPM cannot protect volumes formatted as FAT or FAT32.
Protected Computers Computer Requirements • 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 • Windows Server 2008 operating system (Prerelease version). Note DPM supports Standard and Enterprise Editions of all the required operating systems.
Protected Computers Computer Requirements DPM supports Standard and Enterprise Editions of Exchange Server. • Before you can protect Exchange Server 2007 data in a Clustered Continuous Replication (CCR) configuration, you must install hotfix 940006. For more details, see Knowledge Base article 940006, "Description of Update Rollup 4 for Exchange 2007" (http://go.microsoft.com/fwlink/?LinkId=99291). Important Computers running Virtual Server • • The eseutil.exe and ese.
Protected Computers Computer Requirements information, in Configuring DPM 2007, see "Starting and Configuring the WSS VSS Writer Service" (http://go.microsoft.com/fwlink/?LinkId=100247). • Update the instance of SQL Server 2005 to SQL Server 2005 SP2.
DPM Server DPM Processor type Protecting: • Exchange Server 2007 (64-bit) And • Exchange Server 2007 (64-bit) and Exchange Server 2003 • Exchange Server 2007 (64-bit) Copy the Exchange Server Version of Eseutil.exe and Ese.dll from: 32-bit Note The Exchange Server 2007 version binaries work with both versions of Exchange Server 2007 and Exchange Server 2003 databases.
See Also Hardware Requirements Network Requirements Security Requirements Software Prerequisites Install DPM 2007 A System Center Data Protection Manager (DPM) 2007 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 it automatically installs or provides links to install the prerequisite software as part of the integrated DPM installation process.
Important If you choose to install DPM or prerequisite software products from a shared folder, DPM Setup adds the Universal Naming Convention (UNC) path of the shared folder to the Internet Explorer local intranet security zone for the duration of the installation. Note You cannot install DPM 2007 on the same computer on which your Exchange Server is running. DPM supports 32-bit and x64-bit operating systems.
the installation. If you choose to continue with the installation, plan to resolve the issue as soon as possible. Error. Indicates that a required component is missing or noncompliant. You must resolve the error before you can continue with the installation. 7. On the Product Registration page, enter your registration information. In the Protection agent licenses section do the following: a.
domain. • DPM Setup creates the DPMDBReaders$ and DPMDBAdministrators$ local groups on the remote instance of SQL Server. DPM administrators must be added to these groups to use the remote instance of SQL Server. • The remote instance of SQL Server must be running IIS 6.0 and SQL Server 2005 Standard or Enterprise Edition with SP2, including the SQL Server Database Engine and Reporting services components.
Server that you want to use and the appropriate administrator credentials, and then click Next. 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 before continuing with DPM Setup. 11.
Manually Installing Prerequisite Software If you want to use retail copies of one or more of the prerequisite products for your System Center Data Protection Manager (DPM) 2007 installation, or in the event that automatic installation of one or more of the DPM prerequisite software products fails, you can install the prerequisite software manually. If you are installing a prerequisite product from the DPM product DVD, follow the instructions provided in this section.
See Also Hardware Requirements Network Requirements Security Requirements Software Prerequisites Manually Install Required Windows Components Before you install Microsoft SQL Server 2005, you must install the required Windows components. This topic includes the procedures for installing Windows Server 2003 components and the Windows Server 2008 operating system (Pre-release version) components.
click Details. 4. In the Application Server dialog box, select ASP.NET, select Internet Information Services (IIS), and then click OK. 5. If you are installing DPM on a Windows Server 2003 SP2 server, in the Windows Components Wizard, select Windows Deployment Services. - OR If you are installing DPM on Windows Storage Server R2, select Other Network File and Print Services, click Details, click Single Instance Storage, and then click OK. 6. On the Windows Components Wizard, click Next. 7.
4. In the Add Roles Wizard, on the Before You Begin page, click Next. 5. On the Select Server Roles page, select Web Service (IIS). 6. In the Add features required for Web Server (IIS)? message box, click Add Required Features. Note Add the Windows Process Activation service (WAS) when prompted. WAS is the new process activation service that is a generalization of IIS features that work with non-HTTP transport protocols. 7. Click Next, and then click Next again. 8.
• Use the least-privileged user account on the computer running SQL Server. To install SQL Server 2005 1. Insert the Microsoft Data Protection Manager 2007 product DVD in the DVD drive. 2. In Windows Explorer, browse to :\SQLSVR2005\Servers, and then run setup.exe. 3. On the Microsoft SQL Server 2005 End User License Agreement page, review the license agreement. If you accept the terms, click I accept the licensing terms and conditions, and then click Next. 4.
d. In the Service box, select SQL Server Agent. e. Select Use the built-in System account, and then select a domain user account. f. In the Service box, select Reporting Services. g. Select Use the built-in System account, and then select Network service. h. In the Service box, select SQL Browser. i. Select Use the built-in System account, and then select a domain user account. 13. Click Next. 14. Follow the SQL Server wizard instructions on the remaining pages, and accept all default settings. 15.
3. On the Welcome page, click Next. 4. On the Microsoft SQL Server 2005 SP2 End User License Agreement page, review the license agreement. If you accept the terms, click I accept the licensing terms and conditions, and then click Next. 5. Follow the SQL Server wizard instructions on the remaining pages, accept all default settings, and then on the Ready to Install page, click Install to begin the installation.
1. Disable end-user recovery on the DPM server. 2. Run synchronization for each of the volumes in your protection groups. These steps help ensure that users to whom you deny access to the server cannot access the replicas of those files on the DPM server. Protection jobs cannot run successfully during a repair operation. Any jobs scheduled to run while a repair operation is in progress will not succeed. Any jobs that are in progress when the uninstallation portion of a repair operation begins are canceled.
2. Select the \MS$DPM2007$ database, and then click Connect. 3. Expand Databases, right-click the DPMDB database, and then click Delete. 4. Click Yes to confirm the deletion. To install DPM • For information about installing DPM, see Installing DPM 2007. To restore the DPM database using the DpmSync tool 1. From the command prompt, type DpmSync -sync. 2.
Note After you uninstall the DPM system requirements, you must restart the computer to complete the uninstall. Step 1: Uninstalling the DPM application To uninstall DPM 1. In Control Panel, click Add or Remove Programs, and then click Change or Remove Programs. 2. Under Currently installed programs, select Microsoft System Center Data Protection Manager 2007 and then click Change/Remove. The DPM Setup Wizard starts in uninstallation mode. 3.
4. Under Currently installed programs, select the prerequisite software, and then click Remove. 5. Click Yes, to confirm the deletion. To uninstall PowerShell 1.0 on Windows Server 2008 1. Click Start, point to Administrative Tools, and then click Server Manager. 2. Expand Server Manager to the Features node, and then select Features. 3. In the Features pane, click Remove Features. 4. Clear the Windows PowerShell checkbox and complete the uninstall.
optional DPM features at this time, or you can wait and configure optional features at any time after you deploy DPM. The topics in this section provide instructions for opening DPM 2007 for the first time, and then performing each of the required and optional configuration tasks.
Note Adding a disk to the storage pool is not a requirement if you are going to use custom volumes to protect your data sources, or if you are only going to use disk-to-tape protection. • Configure tape libraries and stand-alone tape drives if you want to protect data on tape. • Install a protection agent on each computer that you want to protect.
• DPM prerequisite software • DPM database files Note Adding a disk to the storage pool is not a requirement if you are going to use custom volumes to protect your data sources, or if you are only going to use disk-to-tape protection. 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, a disk on which you install DPM cannot be added to the storage pool.
You use the Rescan operation on the Libraries tab to check for and refresh the state of all new tape libraries and stand-alone tape drives when you make changes to your hardware. Note If the stand-alone tape drives listed on the Libraries tab in DPM Administrator Console do not match the physical state of your stand-alone tape drives, in the DPM 2007 Operations Guide see Managing Tape Libraries (http://go.microsoft.com/fwlink/?LinkId=91964).
If a firewall is enabled on the DPM server, you must configure the firewall on the DPM server. To configure a firewall on a DPM server, you must open port 135 to TCP traffic, and you must enable the DPM service (Msdpm.exe) and the protection agent (Dpmra.exe) to communicate through the firewall.
Note You must open port 5718 to enable communication with the agent coordinator and port 5719 to enable communication with the protection agent. Installing Protection Agents You use the Protection Agent Installation Wizard to install protection agents on servers that are members of the same domain and servers across trusted domains. If you need to install protection agents on servers that reside behind a firewall, see Installing Protection Agents behind a Firewall in this topic.
the Computer name list, click Add, and then click Next. If you know the name of a specific computer on which you want to install the protection agent, you can quickly find and select the computer by typing the name of the computer in the Computer name box, and then clicking Add. DPM will query Active Directory for the computer, and then add it to the Selected computers list. If you do not know the name of the computer, browse the list to find the computer.
a DPM server. If any of the servers you selected are clustered servers, an additional Choose Restart Method page appears that allows you to select the method you will use to restart the clustered servers. You must install the protection agent on all nodes of the server cluster to successfully protect the clustered data. The servers must be restarted before you can start protecting data.
server name>. Note You can also run the executable using Microsoft Systems Management Server (SMS). 2. On the DPM server, from the DPM Management Shell prompt, type AttachProductionServer.ps1 . The password parameter is not required and we recommend that you do not provide it. DPM will prompt you for a password, which will not appear on the screen.
complete the configurations and firewall openings. Specify the fully qualified domain name (FQDN) for the DPM server. For the current domain or for unique names across domains, specify only the computer name. Note You must run SetDpmServer.exe from :\Program Files\Microsoft Data Protection Manager\bin. If you run the executable from any other location, the operation will fail. 5. On the DPM server, from the DPM Management Shell prompt, type AttachProductionServer.
2. To configure the protection agent for the appropriate DPM server and firewall settings, type :\Program Files\Microsoft Data Protection Manager\bin SetDpmServer.exe. This step is not required if you specified the DPM server in step 1. 3. On the DPM server, from the DPM Management Shell prompt, type AttachProductionServer.ps1 . The password parameter is not required and we recommend that you do not provide it.
3. When prompted, enter your Windows SharePoint Services farm administrator credentials. The administrator credentials you provide for the Windows SharePoint Services farm must be a local administrator on the WFE server. Note You must rerun ConfigureSharepoint.exe whenever the Windows SharePoint Services farm administrator password changes Creating Protection Groups A protection group is a collection of data sources that share the same protection configuration.
Product Protectable Data Recoverable Data • • • Storage group • Database • Mailbox Microsoft Exchange Server 2003 with Service Pack 2 (SP2) • Exchange Server 2007 • Microsoft SQL Server 2000 with Service Pack 4 (SP4) • SQL Server 2005 with Service Pack 1 (SP1) or later • Microsoft Office SharePoint Server 2007 • Microsoft Windows SharePoint Services 3.
Product Protectable Data Recoverable Data Windows XP Professional SP2 and Windows Vista operating systems. Before you can start protecting data, you must create at least one protection group. For guidelines about protection groups, in Planning a DPM 2007 Deployment, see Planning Protection Groups (http://go.microsoft.com/fwlink/?LinkId=91849). The Create New Protection Group Wizard guides you through the process of creating a protection group.
Note DPM supports multiple-user access to DPM Administrator Console using Remote Terminal server sessions. To open DPM Administrator Console locally • On the Start menu, point to All Programs, point to Microsoft System Center Data Protection Manager 2007, and then click Microsoft System Center Data Protection Manager 2007. - OR - • Double-click the Microsoft System Center Data Protection Manager 2007 icon on the desktop. To start the Create New Protection Group Wizard 1.
To select the data to protect 1. On the Select Group Members page, verify that all computers that store data you want to protect are displayed in the Available members box. 2. In the Available members box, expand the server nodes to display the available data sources on each server. Note If you have just installed the protection agent, you might experience a delay of up to several minutes before you can expand the node for the server and display its available data sources. 3.
Specifying Exchange Protection Options If you selected an Exchange Server data source to protect, the Specify Exchange Protection Options page appears. You use this page to specify whether you want to check the integrity of the Exchange Server databases and to select the cluster node that you want to protect. To specify Exchange protection options 1.
You can use special characters such as # ? @ \ $ () {} [] in your protection group name. However, you cannot use the following five special characters: & < > ‘ “ 2. In the Protection policy section, select your protection method: • I want short-term protection using. Select this check box for short-term protection and then select the media you want to use from the drop-down list. Note If you do not have a tape library attached to the DPM server, only Disk is available for short-term protection.
2. In the Synchronization frequency section, do one of the following: • Select Every, and then select the frequency at which you want to synchronize the replica on your DPM server with the changes on your protected server. For application data protection, the synchronization frequency also determines the recovery point schedule. You can select a synchronization frequency interval of anywhere from 15 minutes to 24 hours.
5. On the Specify Short-term Objectives page, click Next. Specifying Short-term Tape-based Recovery Goals If you chose to use short-term protection using tape, you need to specify your short-term tapebased recovery goals. Your recovery goals are defined by the configuration of retention range, synchronization frequency, and recovery point schedule. DPM provides default settings for the recovery goals; however, you can modify each or all of the settings.
• Select Encrypt data to encrypt the data before it is written to tape. • Select Do not compress or encrypt data if you do not want DPM to perform data compression or encryption. 6. Click Next. Allocating Space for the Protection Group When you select disk-based protection, you must allocate space on the storage pool for the replicas and recovery points for each data source that you want DPM to protect. You must also allocate space on protected file servers or workstations for the change journal.
DPM cannot manage the space in custom volumes. If DPM alerts you that a custom replica volume or recovery point volume is running out of space, you must manually change the size of the custom volume by using Disk Management. • Calculate. Click this link to calculate the data size for the data source. 3. When you finish specifying the new allocations, click OK, and then click Next. Specifying Your Long-term Protection Goals DPM creates a protection plan using your long-term recovery goals.
stand-alone tape drive for your backups. 3. Click Restore Defaults to restore the defaults back to a three month retention range and a weekly backup frequency. 4. In the Protection Objectives section, click Customize to change the tape label and to customize the schedule of backup jobs for your recovery goals. This schedule will replace the default schedule. 5. To change the long-term backup schedule, click Modify.
For this backup frequency Depending on retention range, you can configure backup Yearly • Date and time for yearly backup • Date and time for yearly backup Selecting Library and Tape Details If you select protection using tape, you must specify the number of copies of each tape that DPM should create and the configuration options for the backup tapes. You also specify whether you want DPM to encrypt and compress the data, and if you want DPM to check the backup for data integrity.
Choosing a Replica Creation Method When you create a protection group, you must choose a method for creating the replicas for the volumes included in the group. Replica creation involves copying all the data selected for protection to the DPM server and then running synchronization with consistency check for each of the replicas. DPM can create the replicas automatically over the network, or you can create the replicas manually by restoring the data from removable media such as tape.
To optimize performance 1. On the Summary page, click optimize performance. 2. In the Optimize Performance dialog box, on the Network tab, select Enable on-thewire compression to reduce the size of the data transfer and increase CPU utilization on the DPM server and the protected servers. 3. In the Start protection jobs box, select the time of hour you want the protection job to start to balance the loads of synchronization jobs across protection groups, thus avoiding possible performance degradation. 4.
• Installing the Shadow Copy Client Software • Subscribing to Alert Notifications • Configuring the SMTP Server • Publishing DPM Alerts • Installing DPM Management Shell Enabling End-User Recovery You can enable end-user recovery so that users can independently recover file data by retrieving shadow copies of their files. To enable end-user recovery, you must: 1. Configure Active Directory Domain Services (AD DS) to support end-user recovery. 2.
administrator privileges, and then click OK. 4. On the confirmation and notification prompts, click Yes, and then click OK. 5. After configuration of Active Directory Domain Services is complete, select the check box for the Enable end-user recovery option, and then click OK. To configure Active Directory and enable end-user recovery for users who are not schema and domain administrators 1.
Note You do not need to download the shadow copy client software to enable end-user recovery on computers running Windows Vista. The following table shows the locations from which you can download the shadow copy client software for each supported operating system. Operating System Shadow Copy Client Software Location Windows XP SP2 http://go.microsoft.com/fwlink/?LinkId=46064 The 64-bit version of Windows XP SP2 http://go.microsoft.com/fwlink/?LinkId=50683 Windows Server 2003 http://go.microsoft.
critical alerts, warning alerts, informational alerts, or any combination of these). • Under Recipients, type the e-mail address for each recipient (including yourself) to whom you want DPM to send copies of the notifications. Use commas to separate the e-mail addresses. 3. To test the notification settings, click Send Test Notification, and then click OK.
appropriate boxes. Note The User Name must be the domain user name (for example, domain\user name). The From address must be the SMTP address of the user. 4. To test the SMTP server settings, click Send Test E-mail, type the e-mail address where you want DPM to send the test message, and then click OK.
Installing DPM Management Shell DPM Management Shell, based on Windows PowerShell, is an interactive command-line technology that supports task-based scripting. Microsoft System Center Data Protection Manager (DPM) 2007 provides its own set of Windows PowerShell commands that can be used in addition to DPM Administrator Console to perform data protection management tasks. A DPM administrator can use DPM cmdlets to perform many of the administrative tasks that can be performed in the console.
under the "Installation" node in the DPM System Recovery Tool Help (the .chm file) on the DPM SRT CD. Troubleshooting Your DPM 2007 Installation The topics in this section provide guidance for troubleshooting issues with your System Center Data Protection Manager (DPM) 2007 and protection agent installations.
Issue Possible Cause Resolution service is restarted. Error 812. This problem Configuration of occurs when both reports failed. SQL Server Reporting Services and Windows SharePoint Services are installed in the same Internet Information Services (IIS) application pool. To resolve this issue, perform one of the following tasks: • Uninstall Windows SharePoint Services by using Add or Remove Programs, uninstall DPM, and then install DPM again.
Issue Possible Cause Resolution ID: 4315. The trust relationship between this workstation and the primary domain failed. is unable to connect to the domain controller during installation, the DPM installation fails. domain controller. In addition, verify that the DNS entries are for the domain controller and that they are correctly configured. Error 820. Setup cannot query the system configuration while performing the prerequisite check on Windows Server 2008 operating system.
Issue Possible Cause Resolution 506). 3. Run DPM setup again. Troubleshooting Error ID 4307 The following table provides guidance for troubleshooting Error ID 4307. This error occurs when you are attempting to connect to a remote SQL Server database when installing System Center Data Protection Manager (DPM) 2007. Troubleshooting Error ID 4307 Possible Cause Resolution Remote connection to the computer running SQL Server is disabled. To enable the remote instance of SQL Server, do the following: 1.
Possible Cause Resolution By default, Microsoft SQL Server 2005 sets the SQL Server Browser service to start automatically. The name of the remote instance of SQL Server is in the incorrect format. Ensure that the remote SQL Server instance name is in the following format: \ Note Only use for the default instance. There is no network connectivity between the DPM server and the computer running SQL Server.
Issue Possible Cause Resolution Call (RPC) server is unavailable. Error 303: Agent operation with specified server failed. • • Another installation is running on the specified server. 17). • Wait for the installation to complete, and then retry the operation. • Convert the boot volume to NTFS file system if you have sufficient space. For more information about using the Convert command for converting FAT volumes to NTFS, see Microsoft TechNet article Convert (http://go.microsoft.
Issue Possible Cause Resolution configuratio n requirement s on the • DPM server. because of a communication error with the DPM Protection Agent service on the specified server. • • Internet Protocol Security (IPSec) configuratio n. • The RPC server is unavailable. DPM Servers (http://go.microsoft.com/fwlink/?LinkId=918 53). IPSec may be configured to block particular IP traffic, such as on a particular port or to particular addresses.
Issue Possible Cause on the server. Error 342: The agent operation failed because the DPM server could not communicate with the specified server. • The system times of the DPM server, the server on which you are installing the agent, and the domain controller are not synchronize d, and therefore the Kerberos authenticati on fails. • The DNS setting on the DPM server or the computer on which you are installing the protection agent is not correct.
Issue Possible Cause Resolution server. Error 348: An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the specified server. Incorrect security settings for the COM object on the computer. Verify COM permissions on the server.
Issue Possible Cause Resolution Error 377: minimum requirements. • Local Access and Remote Access permitted to Self • Local Access permitted to System The agent operation failed because the minimum requirements in the DCOM configuration were not met.
Issue Possible Cause Resolution The RPC server is unavailable. A firewall is enabled on the remote computer. If a firewall is enabled on the remote computer on which you are installing the protection agents, before installation you must run the DPMAgentInstaller.exe executable file. For more information, see Installing DPM 2007 Behind a Firewall (http://go.microsoft.com/fwlink/?LinkId=101313 ). The agent operation failed while creating the local group DPMRADCOMTrustedMachin es.
Issue Possible Cause Resolution installation fails if you are installing it on a non-primary domain controller running Windows Server 2003. Domain Controller (PDC) is running Windows Server 2000, the required Distributed COM Users group will be missing. PDC emulator operations master role holder to Windows Server 2003, and then perform the protection agent installation again.
Using DPM Administrator Console This topic describes the layout of DPM Administrator Console and explains where the controls for general tasks are located. Task Areas and Display Panes A task area is a set of logically related functions grouped together in DPM Administrator Console. The console has five task areas: Monitoring, Protection, Recovery, Reporting, and Management. Each task area, except Recovery, consists of three panes: the display pane (unlabeled), Details pane, and Actions pane.
Navigation Bar The navigation bar enables you to move between the five task areas of the console. To select a task area, click the name of the area. Menu Bar The menu bar contains four menus: File, Action, View, and Help. • File menu. Contains standard Microsoft Management Console (MMC) commands. For information about MMC, see MMC Help. • Action menu. Contains the same commands as those displayed in the Actions pane, as well as an Options command and a Help command.
Information Icon The information icon provides access to complete version and product identification information for DPM, as well as a link to the Microsoft Software License Terms. See Also DPM Administrator Console in DPM 2007 Working with DPM Task Areas DPM Administrator Console contains five task areas: Monitoring, Protection, Recovery, Reporting, and Management. The Actions pane provides access to functionality associated with the current task and, in some cases, the item selected in the display pane.
Task Area Actions protection groups. Recovery Reporting Management • Manage protection schedules, disk allocations, and other options. • Run manual synchronization and consistency check jobs. • Manage recovery points. • Review and respond to results of Auto Discovery. Use the Recovery task area to find and recover data from recovery points. The Recovery task area contains the following tabs: • Browse—Enables you to browse for available recovery points by protected computer.
Task Area Actions you to manage the tapes in the library. See Also DPM Administrator Console in DPM 2007 How to Use DPM Administrator Console to Administer DPM 2007 To use DPM Administrator Console, you must be logged on to the DPM server under a domain account that has administrator privileges. Note You can also add DPM Administrator Console as a snap-in to a custom Microsoft Management Console (MMC).
account that has administrator privileges. 4. On the Start menu, point to All Programs, point to Microsoft System Center Data Protection Manager 2007, and then click Microsoft System Center Data Protection Manager 2007. -OrDouble-click the Microsoft System Center Data Protection Manager 2007 icon on the desktop. See Also DPM Administrator Console in DPM 2007 Deployment Best Practices This topic describes best practices related to the deployment of System Center Data Protection Manager (DPM) 2007.
Software Requirements • DPM is designed to run on a dedicated, single-purpose server that cannot be either a domain controller or an application server. • To administer multiple DPM servers remotely, install DPM Management Shell on computers other than the DPM server. Installing DPM 2007 • You must properly configure Microsoft Windows Server 2003 to support a DPM 2007 installation. For more information about installing Windows Server 2003, see How to Install Windows Server 2003 (http://go.microsoft.
• • Run SQL Server by using the least-privileged user account. If SQL Server Reporting Services is installed on a 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 before continuing with DPM Setup.
• Protected volumes must be formatted as an NTFS file system. DPM cannot protect volumes formatted as FAT or FAT32. To simplify recovery in the event of system partition failure, install DPM to a partition that is separate from the system partition. 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.
Protection for computers running Windows SharePoint Services • Before you can protect Windows SharePoint Services (WSS) data, you must do the following: • Install Knowledge Base article 941422, "Update for Windows SharePoint Services 3.0" (http://go.microsoft.com/fwlink/?LinkId=100392). • Start the WSS Writer service on the WSS Server and then provide the protection agent with credentials for the WSS farm. • Update the instance of SQL Server 2005 to SQL Server 2005 SP2.
• Adding a disk to the storage pool is not a requirement if you are going to use custom volumes to protect your data sources or if you are going to use disk-to-tape protection only. • DPM cannot use space in any pre-existing volumes on disks added to the storage pool. Although a pre-existing volume on a storage pool disk might have free space, DPM can use only space in volumes that it creates.
You must open port 5718 to enable communication with the agent coordinator and port 5719 to enable communication with the protection agent. Installing Protection Agents • Before you install protection agents on the computers you are going to protect, you must apply hotfix 940349.
Creating Protection Groups • To use DPM Administrator Console, you must be logged on to a DPM server with an account that has administrative privileges on that server. Before you can start protecting data, you must create at least one protection group. For guidelines about protection groups, in Planning a DPM 2007 Deployment, see Planning Protection Groups (http://go.microsoft.com/fwlink/?LinkId=91849).
