Data Protection Manager 2006 - Technical Frequently Asked Questions

A.

A. For product information, see the Data Protection Manager Web site. Also, you can find DPM Help, the DPM Planning and Deployment Guide, and the DPM Operations Guide on the Microsoft TechNet Web site. For details about the updates included in DPM Service Pack 1 (SP1), see "What's New in DPM 2006 SP1?" (http://go.microsoft.com/fwlink/?LinkID=71313).

A. The DPM Planning and Deployment Guide and DPM Help are included in the DPM product and on the Microsoft TechNet Web site. Because this documentation was included with DPM, it cannot be updated.

This FAQ and the DPM Operations Guide are available on the World Wide Web only, and will be updated as required. Issues that occur after the release of DPM will be reflected in the FAQ or theDPM Operations Guide.

DPM supports the following languages:

• Chinese (Simplified)
• Chinese (Traditional)
• English
• French
• German
• Italian
• Japanese
• Korean
• Spanish

A. Network Requirements

DPM Server Requirements

File Server Requirements

A. Yes. You can install DPM on a computer running Windows Server 2003 R2 or Windows Storage Server 2003 R2, and you can protect servers running Windows Server 2003 R2 or Windows Storage Server 2003 R2 by using DPM. You can also upgrade existing DPM servers and protected file servers to Windows Server 2003 R2 or Windows Storage Server 2003 R2.

Important: A new installation of Windows Storage Server 2003 R2 includes Single Instance Store (SIS) by default. Do not enable SIS on the DPM server or protected file servers. However, DPM SP1 can protect file servers on which SIS is enabled. For details about the updates included in DPM Service Pack 1 (SP1), see "What's New in DPM 2006 SP1?" (http://go.microsoft.com/fwlink/?LinkID=71313).

A. DPM can protect the files on a computer that is configured as a web server only if the computer has fewer than 20 IP addresses assigned to it.

A. To obtain the DPM Volume Shadow Copy Service (VSS) SDK, send an e-mail message to dpspart@microsoft.com. The software development kit will also be available for download on the Microsoft Storage Partner Extranet. You must register on that site to be able to download software.

A. DPM has been tested successfully in our labs with a single DPM server protecting 30 servers with 6 terabytes (TB) of data. However, this is not a hard limit on what DPM can support in terms of capacity. Some customers are using a single DPM server to protect more than 10TB of data spread between 50 servers. The exact number of servers that can be protected by a single instance of DPM will vary with server configuration, network bandwidth and the data profile (distribution and churn).

A. The DPM installation will install Internet Information Services (IIS) 6.0 if it is not already installed; you may be prompted for the Windows Server 2003 CD or installation share. When you install DPM, both the DPM application and the following prerequisite software are installed:

• Microsoft SQL Server 2000 (Standard or Enterprise Edition)
• Microsoft SQL Server 2000 Service Pack 3a (SP3a)
• Microsoft SQL Server 2000 Hotfix 859
• Microsoft SQL Server 2000 Reporting Services (Standard or Enterprise Edition)
• Microsoft SQL Server 2000 Reporting Services Service Pack 1 (SP1)

A. Yes, you can install the prerequisite software manually before you install DPM.

To install IIS

1. In Control Panel, open Add/Remove Programs and then click Add/Remove Windows Components.
2. In the details for Application Server, selectASP.NET, enablenetwork COM+ access, and Internet Information Services (IIS) for installation.

To install SQL Server and SQL Server Reporting Services manually, see the instructions in the "Installing DPM" chapter in the DPM Planning and Deployment Guide.

A. You can perform a semi-unattended installation of DPM. A semi-unattended installation relieves you of the requirement to change CDs or specify individual installation folders during the Setup process. For instructions on performing a semi-unattended installation of DPM, see the "Installing DPM" chapter in the DPM Planning and Deployment Guide.

A. You can run DPM Setup from a network share by using a Universal Naming Convention (UNC) path. However, you cannot run DPM Setup by using a drive that maps to a network share.

If you experience errors when running DPM Setup from a network share by using a UNC path, follow these steps:

1. Exit DPM Setup.
2. Copy the DPM installation folder to a local folder on the DPM server.
3. Restart the DPM installation from the local installation folder.

A. Yes, if you do not want to retain any existing replicas. However, if you uninstall DPM using the Retain Data option, you must reinstall DPM to the same directory path.

A. You can repair your DPM installation by uninstalling DPM with the retain data option and then reinstalling DPM.

When you uninstall DPM with the retain data option, the databases, replicas, and other information that is used by DPM (such as security groups, registry settings, files, storage pool, and so on) remain on the DPM server drives. You cannot restore the DPM server to its original state or recover the retained data if you change or reformat any one of the drives before reinstalling DPM.

To repair a DPM installation

1. Create a backup of the DPM server. For instructions on backing up the DPM server, see the "Archiving and Restoring Data" chapter (http://go.microsoft.com/fwlink/?LinkId=46368) in the DPM 2006 Operations Guide.
2. Uninstall DPM with the retain data option.
3. Reinstall the same version of DPM. 
   Note Do not use this method to upgrade to a later version of DPM.
4. Install all DPM updates that were applied to the previous installation.

You must follow these guidelines during the repair process:

• Do not remove or change any DPM-related registry entries.
• Do not delete any users and groups that DPM created.
• Do not uninstall SQL or SQL Reporting Services.
• Do not delete the DPM databases.
• Do not format/delete/remove the disk drives where the storage pool keeps its data.

You cannot use uninstall with the retain data option to repair a corrupted database. For instructions on restoring DPM databases from tape, see the Archiving and Restoring Data chapter in the DPM 2006 Operations Guide. For instructions on troubleshooting database issues, see the Troubleshootingchapter in the DPM 2006 Operations Guide.

A.You can enable Shadow Copies of Shared Folders, a Windows Server 2003 feature, on the DPM server. However, never use Shadow Copies of Shared Folders to revert any volume on the DPM server. Reverting a DPM server volume causes data corruption and requires a manual consistency check.

A. Yes. However, if Shadow Copies of Shared Folders are enabled on the protected file server, the end-user recovery client will display shadow copies that are located on the protected file server rather than the shadow copies that are located on the DPM server. This can provide quicker file recovery for end-users from file servers in a branch office. For file servers in a datacenter, you should consider disabling Shadow Copies of Shared Folders on protected file servers in order to maximize the benefit from DPM.

A. No, you can only upgrade DPM Beta to DPM 2006 (full retail version).

A. You can upgrade the beta version of DPM to DPM 2006 and retain the data and settings from the beta test. Because of changes and improvements made to DPM as a result of the beta test, the upgrade process requires that you download and run DPM Consistency Checker (http://go.microsoft.com/fwlink/?LinkId=55831), a tool that will ensure that replicas created with DPM Beta are compatible with DPM 2006.

DPM 2006 Setup upgrades:

• The Beta version of DPM
• SQL Server Evaluation Edition
• SQL Reporting Services Evaluation Edition

Before you start DPM 2006 Setup, make sure that no DPM jobs are scheduled to run and that DPM Administrator Console is closed.

To upgrade DPM Beta

1. Install hotfix 891957 (http://go.microsoft.com/fwlink/?LinkId=48584) and then restart the computer.
2. Insert the DPM 2006 CD.
3. On the launch screen, click Install Data Protection Manager.
4. On the Welcome page, click Next.
5. On the End-User License Agreement page, review the license agreement. If you accept the terms, click I accept the terms of this agreement, and then click Next.
6. After DPM checks for prerequisites, on the Product Registration page, enter your registration information, and then click Next.
7. On the Security Settings page, specify a strong password for the Microsoft$DPM$Acct and Microsoft$DPMWriter$ accounts, and then click Upgrade.
8. On the Installation page, verify that the Open DPM 2006 Administrator Console when the wizard closes check box is selected, and then click Close.
9. In DPM Administrator Console, in the Management task area, on the Agents tab, update the file agents by selecting the file servers and then clicking Update Available.
10. Close DPM Administrator Console.
11. Download DPMConsistencyChecker.exe (http://go.microsoft.com/fwlink/?LinkId=55831), and then run DPMConsistencyChecker.exe. Be aware that running this tool can take as much time as creating an initial replica.

The first synchronization job that runs after the upgrade will mark the replica as inconsistent. Schedule or manually run synchronization with consistency check for all the replicas to make them consistent.

After the upgrade, you must reestablish report schedules and report history settings. If report history generated before the upgrade is lost, you can run each report with the appropriate granularity of weeks or months to capture in a report the data that was present before the upgrade.

After all agents are updated, examine the Monitoring task area for any jobs that may have failed during the upgrade.

If DPM Help will not open after upgrade, delete c:\Documents And Settings\All Users\Application Data\Microsoft\HTML Help\hhcolreg.dat, and then reopen DPM Help.

A. The evaluation edition of DPM expires 120 days after it is installed. After 120 days, when you open DPM Administrator Console, you will see an error message that DPM has expired. You can upgrade the evaluation edition to the licensed version of DPM 2006.

DPM 2006 Setup will upgrade:

• The DPM Evaluation Edition
• SQL Server Evaluation Edition
• SQL Reporting Services Evaluation Edition

Before you start DPM 2006 Setup, make sure that no DPM jobs are scheduled to run and that DPM Administrator Console is closed.

To upgrade DPM Evaluation Edition

1. Insert the DPM 2006 CD.
2. Click Install Data Protection Manager on the launch screen.
3. On the Welcome page, click Next.
4. On the End-User License Agreement page, review the license agreement. If you accept the terms, click I accept the terms of this agreement, and then click Next.
5. After DPM checks for prerequisites, on the Product Registration page, enter your registration information, and then click Upgrade.
6. On the Installation page, verify that the Open DPM 2006 Administrator Console when the wizard closes check box is selected, and then click Close.

After DPM is upgraded, examine the Monitoring task area in DPM Administrator Console for any jobs that may have failed during the upgrade.

After the upgrade, you must reestablish report schedules and report history settings. If report history generated before the upgrade is lost, you can run each report with the appropriate granularity of weeks or months to capture in a report the data that was present before the upgrade.

To upgrade the prerequisite software manually

If DPM Setup cannot upgrade the prerequisite software, you can upgrade the prerequisite software manually and then run DPM Setup again to upgrade DPM. Manually upgrading the prerequisite SQL Server products from the DPM product CD involves creating an installation folder on the DPM server, and extracting the Setup package in the installation folder. You can select any name and location for the installation folder; for example, C:\DPMPrereqs. The Setup package includes the following folders:

• CD 1
  Contains Setup files for SQL Server 2000 hotfix 859 and SQL Server 2000 Reporting Services Service Pack 1
• CD 2
  Contains Setup program files for SQL Server 2000
• CD 3
  Contains Setup program files for SQL Server 2000 Service Pack 3a
• CD 4
  Contains Setup program files for SQL Server 2000 Reporting Services

To extract the Setup package

1. Insert the Microsoft Data Protection Manager 2006 product CD in the CD drive.
2. Open the command prompt, and change directories to the CD drive.
3. At the command prompt, type: DPMPrerequisites.exe /x: <installation folder>
   This command extracts the contents of the self-extracting Setup package to the specified folder.

To manually install SQL Server 2000

1. If you have not extracted the Setup package, do so now.
2. Run the Setup program <installation folder>\CD2\Autorun.exe.
   The Setup wizard for SQL Server 2000 starts.
3. Select Upgrade, remove, or add components to an existing instance of SQL Server.
4. Select the instance to upgrade.
5. Select the Upgrade your existing installation option.
6. Select the Yes, upgrade my programs box.
7. Select No in the Do you want to install additional components? dialog box.
8. Click Finish.

To manually install SQL Server 2000 Reporting Services

1. If you have not extracted the Setup package, do so now.
2. Run the Setup program <installation folder>\CD4\Setup.exe.
   The Setup wizard for SQL Server 2000 Reporting Services starts.
3. In the Setup wizard, select Upgrade.
4. Follow the wizard instructions. Accept all default settings.

After you upgrade SQL Server and SQL Server Reporting service, start the DPM Setup from the DPM CD. Follow the steps in the upgrade.

A. By using the Microsoft System Center Data Protection Manager 2006 Management Pack for Microsoft Operations Manager 2005 (MOM), you can centrally monitor the state of data protection and recovery for multiple DPM servers and the file servers that they protect. The DPM Management Pack also monitors key health and performance indicators on DPM servers.

From the MOM Operator console, you can monitor DPM and network infrastructure at the same time, analyzing data protection failures in the context of other network failures. From the same console, you can monitor other mission-critical applications, such as Microsoft SQL Server.

For DPM servers, the DPM Management Pack monitors the state of DPM database and service health, server performance, and key indicators such as disk availability and configuration changes to volumes protected by DPM.

For protected file servers, the DPM Management Pack monitors the state of connectivity with DPM, data recovery operations for protected volumes, and replicas and shadow copies that are stored on the DPM server.

A. To deploy the DPM Management Pack in MOM, you must import the DPM Management Pack onto the MOM Management Server and then install the MOM agent on the DPM servers that you will monitor in MOM. Through proxying, the MOM agent monitors the files servers that the DPM servers are protecting.

For information about downloading the DPM Management Pack, visit the DPM Management Pack download site (http://go.microsoft.com/fwlink/?linkid=50208).

For installation instructions and a detailed product overview, see the Microsoft System Center Data Protection Manager 2006 Management Pack Guide. The guide is available from two sources:

• The guide can be viewed or downloaded from the TechNet site MOM 2005 Management Pack Guides (http://go.microsoft.com/fwlink/?LinkId=50206).
• The guide is also included in the files that are downloaded with the DPM Management Pack.

A. If the DPM server is running Windows Server 2003 with SP1 and has the firewall enabled, see Microsoft Knowledge Base article 885726 for special instructions for installing the MOM agent.

A. To provide continuous mirroring of DPM alerts in Microsoft Operations Manager 2005, Beta customers for the DPM Management Pack must upgrade to the release version of the DPM Management Pack immediately after they upgrade their DPM servers to the retail version of DPM 2006.

If time elapses between the DPM server upgrades and the DPM Management Pack upgrade, the DPM alerts that are generated during that period are not mirrored in MOM. To update the MOM display with the missing alerts, you can republish active alerts on each DPM server to MOM.

The following procedures list the steps to upgrade the DPM Management Pack and ensure that the Alerts view in MOM is synchronized with the alerts in DPM after the upgrade.

Before you start: Upgrade all DPM servers that are managed in MOM to the release version of DPM 2006. It is important to upgrade all managed DPM servers before you upgrade the DPM Management Pack, because the release version of the DPM Management Pack is not compatible with the beta version of DPM 2006.

To upgrade the DPM Management Pack

1. Download the DPM Management Pack from the DPM Management Pack download site, and extract the files to a folder on the MOM Management Server.
2. Open the MOM Administrator console: On the Start menu, point toPrograms, point to Microsoft Operations Manager 2005, and then click Administrator Console.
3. Import the new DPM Management Pack: In the console tree on the left side of the console, right-click Management Packs, and then click Management Pack Import/Export. Then perform the steps in theManagement Pack Import/Export Wizard, entering the settings described in the following table.
   
   

   Wizard Page	Instructions
   Import or Export Management Packs	Select Import Management Packs and/or reports.
   Select a Folder and Choose Import Type	Browse to the folder that stores the Management Pack (MicrosoftSystemCenterDataProtectionManager*.akm, where * represents a three-letter code that indicates the language of the Management Pack). Under Type of Import, select Import Management Packs only.
   Select Management Packs	Select MicrosoftSystemCenterDataProtectionManager*.akm in the list. Select Replace existing management pack.

To ensure continuous mirroring of alerts after you upgrade the DPM Management Pack

Follow these steps to determine whether MOM failed to mirror any DPM alerts that were generated during your DPM upgrades and, if alerts were dropped in MOM, how to synchronize the Alerts view in MOM view with the alerts on the DPM servers.

1. Open the MOM Operator console: On the Start menu, point toPrograms, point to Microsoft Operations Manager 2005, and then click Operator Console.
2. To determine whether MOM failed to mirror any DPM alerts during the DPM and Management Pack upgrades, see if there are active “A management pack script failed to execute successfully” alerts in MOM:
   
   • Display alerts for computers managed in MOM: In Alert Views, expand All: Alert Views, and then click Alerts.
   • See whether there are active “A management pack script failed to execute successfully” alerts for the DPM servers that you upgraded. The alert details identify the computer on which the error occurred and the source of the error.
     Note  If no active "A management pack script failed to execute successfully" alerts are present for the DPM servers, you do not need to complete the remaining steps in this procedure.
3. If active “A management pack script failed to execute successfully” alerts are present, resolve all alerts for the DPM servers and the file servers that they protect:
   
   • Display all alerts for DPM: In Alert Views, expand Microsoft System Center Data Protection Manager (DPM), and then click Alerts.
   • In the Results pane, select the complete set of alerts, right-click anywhere in the selection, click Set Alert Resolution State to, and then click Resolved.
4. To synchronize the MOM display with the alerts in DPM, on each DPM server that is managed in MOM, republish alerts to MOM: In DPM Administrator Console, select Options on the Action menu, click the Alert Publishing tab, and then click Publish Active Alerts.
   Note  After you upgrade to the release version of the DPM Management Pack, check to make sure that the DPM Protected role is displayed in State Views. Sometimes, a MOM discovery error prevents the DPM Protected role from being populated. To determine whether this error has occurred, look in the Application log in Windows Event Viewer on the MOM server for the following event: Event ID: 25652, Category: MOM Server, Source: Microsoft Operations Manager. If the event has been logged, contact Microsoft product support for help. For information, see the Microsoft Product Support Web site at http://go.microsoft.com/fwlink/?linkid=46538.

A. No. The server running DPM and the file servers protected by DPM must be members of the same domain.

A. Yes, if you have continuous connectivity.

A. Yes. However, this creates the potential for performance issues. When protecting data over a wide-area network (WAN), you should consider doing the following:

• Enabling on-the-wire compression.
• Setting synchronization to occur only before snapshots, to avoid using up valuable bandwidth every hour.
• Enabling network throttling.

For information about how to perform these tasks, see How to modify protection options in DPM Help

A. You can enable end users to recover previous versions of files and folders that are protected by DPM. Users select an earlier version of a file or folder by using the familiar Windows Explorer interface or any one of the Microsoft Office 2003 applications. This capability increases productivity and significantly lowers administrative costs.

A. To enable the end-user recovery feature, a member of the Schema Admins group on the domain must configure Active Directory. Then, you enable the end-user recovery feature on the DPM server and install the shadow copy client software on the client computers. You must install the shadow copy client provided for DPM instead of the Shadow Copies of Shared Folders shadow copy client.

The shadow copy client software can be installed on computers running Microsoft Windows XP with SP2 or later and Windows Server 2003 with or without SP1. The following table shows the locations from which you can download the shadow copy client software for each supported operating system.

For more information about end-user recovery, see DPM Help. For detailed instructions, see the "Configuring Data Protection Manager" chapter in the DPM Planning and Deployment Guide.

A. The schema is extended only once; however, you must configure the Active Directory schema extension for each DPM server. Enabling end-user recovery for any DPM server requires schema administrator permissions. The first time that you enable end-user recovery on a DPM server in a domain, the action:

1. Extends the schema
2. Creates a container
3. Grants the DPM server permissions to change the contents of the container
4. Maps source shares and replica share

When you enable end-user recovery for additional DPM servers in the domain, the process performs steps 3 and 4 for each additional server. DPM will update the share mapping (step 4) after each synchronization, if needed. For instructions on configuring end-user recovery, see Enabling End-User Recovery in the DPM 2006 Planning and Deployment Guide.

A. When you enable end-user recovery by using DPM Administrator Console, the configuration process updates the required permissions in Active Directory.

To view an earlier version of a file, users need Read permission. To recover an earlier version to its original location, users need Read and Write permissions. To recover an earlier version to an alternate location, users need Read permission on the file and Write permission on the alternate location.

A. Yes. End-user recovery uses Common Internet File System (CIFS), the same protocol that clients use to access shared folders on the file server.

A. When you uninstall DPM with the Retain Data option, users can continue to recover files from the existing shadow copies. Changes made to files after DPM is uninstalled, including changes to share and file permissions, are not reflected in the shadow copies, and no new shadow copies are created.

A. End-user recovery can be configured or disabled for all file servers protected by a DPM server only. You cannot enable or disable end-user recovery for a single protected file server.

A. End-user recovery can be configured for users in the same domain as the DPM server and protected file servers only.

A. After you create a protection group by using the New Protection Group wizard, you can modify the protection options. The following table matches administrative tasks with the object that you select to perform the task.

Note In the Modify disk allocation dialog box, you will select the protected volume or share.

A. If you protect a share that resides under a mount point, you cannot use a DPM-enabled backup application or DPMBackup to back up DPM to tape. You can work around this issue by protecting the share by using the Volumes and folders view.

A. For instructions, see Knowledge Base article 909644, "How to use Microsoft System Center Data Protection Manager 2006 to help protect an Exchange server" (http://support.microsoft.com/kb/909644/en-us).

A. For instructions, see Knowledge Base article 909644, "How to use Microsoft System Center Data Protection Manager 2006 to help protect a SQL Server database" (http://support.microsoft.com/kb/910401/en-us).

A. DPM supports use of any of the following sources for file server storage:

• Direct attached storage (DAS).
• Fibre Channel storage area network (SAN).
• Internet SCSI (iSCSI) storage device or SAN, providing that the iSCSI storage device has received Windows Hardware Certification.

A. You cannot add mapped drives to a storage pool.

A. If synchronization frequency is set to run only before each shadow copy is created, you should not schedule the daily consistency check to run at the same time. When synchronization before shadow copy and consistency check are scheduled for the same time, a log overflow on the file server can result in two missed shadow copies.

For example, synchronization before shadow copy and consistency check for file server A are both scheduled to occur at 4 P.M. daily. On Tuesday, the synchronization log on file server A overflows. At 4 P.M., the consistency check does not run because the replica is marked consistent. Synchronization runs, and then marks the replica inconsistent due to the log overflow; therefore, the shadow copy for Tuesday is not created.

On Wednesday, at 4 P.M., the consistency check runs because the replica is marked inconsistent. However, the synchronization job fails because the replica is inconsistent; therefore, the shadow copy Wednesday is not created either.

Instead, schedule the consistency check to run an hour after the synchronization. With this schedule, if the replica is inconsistent before the consistency check runs, the consistency check will make it consistent, and then the subsequent synchronization and shadow copy should succeed. .

A. When you add volumes or shares that can be accessed through both the Network File System (NFS) and Common Internet File System (CIFS) to a protection group and anonymous user access is enabled for the volumes or shares, the bypass traverse checking privilege must be granted to anonymous user accounts on the file server. Otherwise, the replica can become inconsistent when files in the volumes or shares are edited.

To grant the bypass traverse checking privilege

• In Administrative Tools, open Local Security Policy.
• Expand Local Policies, and then click User Rights Assignment.
• Right-click Bypass traverse checking, and then click Properties.
• Click Add User or Group.
• In the Select Users or Groups dialog box, add ANONYMOUS LOGON, click Check Names, and then click OK.
• Click OK to close the Bypass traverse checking properties dialog box.
  Note The Bypass traverse checking user right determines which users can traverse directory trees even though the user may not have permissions on the traversed directory. This privilege does not allow the user to list the contents of a directory, only to traverse directories.

A. DPM installs IIS as a prerequisite for SQL Server Reporting Services. For security, DPM Setup restricts remote access to the virtual directories of all Web sites that reside on the DPM Server. This affects the Windows Storage Server Administration Web site on computers running Windows Storage Server 2003.

If you require remote Web access to IIS-hosted sites on your DPM server, run the DPMIISConfiguration.vbs script provided in this section. This script restores the settings for AccessNoRemoteExecute, AccessNoRemoteScript, AccessNoRemoteRead, and AccessNoRemoteWrite to the IIS defaults. These settings are contained in the AccessFlags attribute of the virtual directory and cannot be changed by using the Internet Information Service Manager snap-in.

Restoring these settings to the IIS defaults by using this script does not expose any known security issues.

To create the DPMIISConfiguration.vbs script

1. Copy or type the following text into Notepad.
   for each item in GetObject
("winmgmts://localhost/root/MicrosoftIISv2").ExecQuery
("SELECT * FROM IIsWebVirtualDirSetting")
' Update the remote permissions
if 0 = InStr(item.Name, "ReportServer") then
WScript.Echo "Updating remote permissions for " & item.Name
'unset AccessNoRemoteExecute, AccessNoRemoteScript,
AccessNoRemoteWrite, AccessNoRemoteRead
'for information about the AccessFlags property,
see the Metabase Property Reference at http://go.microsoft.com/fwlink/?LinkId=52021
item.AccessFlags = item.AccessFlags and &HFFFF8BFF
item.Put_()
end if
next
2. Save the file as DPMIISConfiguration.vbs on the DPM server.

To run the script

• Open a command prompt and type:

The results of the script are displayed on completion.

A. Administrators can enable the Web sharing feature in Windows Storage Server to provide HTTP access to users for shares on the server. However, the default port for Web sharing is port 80. This port conflicts with the default port for IIS which is required for DPM reporting services.

If you install DPM on a Windows Storage Server with Web sharing enabled and use the default port, Setup provides the following message during the prerequisite check:

"The Default Web Site used by Internet Information Services (IIS) is disabled. SQL Server Reporting Services cannot be installed or run unless this Web site is available. From the command line, run inetmgr.exe. To enable the Default Web Site, expand the Web Sites folder, right-click Default Web Site, and then click Start."

To install DPM on a computer running Windows Storage Server with Web sharing enabled, configure Web sharing in Windows Storage Server to use a port other than port 80, and then start the Default Web Site.

A. If the language for non-Unicode programs on the DPM server is changed after DPM is installed, scheduled reports are not produced. To generate scheduled reports, reset the language for non-Unicode programs to the language that was configured for the computer when DPM was installed.

A. If the SMTP server name is deleted from the SMTP Server tab in the Options dialog box and you open the Schedule dialog box for a report and then click OK to close it, DPM Administrator Console may close unexpectedly. If this problem occurs, restart DPM Administrator Console.

A. You should not run Disk Defragmenter on disks that are members of the storage pool on the DPM server because you might lose shadow copies. Knowledge Base article 312067 explains the issue with Defrag and shadow copies as follows

"The System Shadow Copy provider uses a copy-on-write mechanism that operates at a 16-KB block level. This is independent of the file system's cluster allocation unit size. If the file system's cluster size is smaller than 16 KB, the System Shadow Copy provider cannot easily determine that disk defragmentation I/O is different from typical write I/O, and performs a copy-on-write operation. This might cause the Shadow Copy storage area to grow very quickly. If the storage area reaches its user-defined limit, the oldest shadow copies are deleted first."

For more information about this issue, see the Microsoft Knowledge Base article "Shadow copies may be lost when you defragment a volume" (http://go.microsoft.com/fwlink/?LinkId=65210).