HP ProLiant Storage Server Release Notes (January 2006)

Data Protection Manager

This section describes issues related to HP ProLiant Data Protection Manager (DPM).

Besides the issues listed in this section, additional DPM issues can be viewed at the following web site (see

the Known Issues section): http://www.microsoft.com/technet/prodtechnol/dpm/proddocs/faq.mspx

Issue: DPM Administration tool can overwrite data on a physical disk with no warning given

Description On Data Protection Manager storage servers, if certain steps are followed,

volumes can be created on a physical disk that the DPM Administration tool does

not see. If these physical disks are allocated to DPM, the volumes will be

removed with no warning about data loss given to the user.

Workaround Always click the Rescan option before adding new disks to DPM.

Issue: DON’T ERASE disk can be added to the DPM storage pool

Description The DON’T ERASE disk is displayed in the list of disks that can be added to the

storage pool in DPM. The DON’T ERASE disk is used during a Quick Restore,

and any data on this disk will be deleted in the event of a Quick Restore.

Workaround Do not use the DON’T ERASE disk to store DPM data.

Issue: The Web UI is not functional until DPM mini-setup is complete

Description During the factory installation of DPM, the World Wide Web Publishing Service

is disabled.

Workaround Access the Services Management Console, open the properties of the World

Wide Web Publishing Service, set the Startup Type to Automatic, and start the

service.

Issue: Event ID:1101 SNMP warning displayed in System Event log

Description The following warning may be logged to the System Event log for the Data

Protection storage server:

Event Source: SNMP

Event ID: 1101

The SNMP Service is ignoring extension agent key

SOFTWARE\Microsoft\MSSQLServer\SNMP\Current Version

because it is missing or mis-configured.

Because DPM only installs a named instance of SQL, it does not create the

correct SNMP registry keys.

Workaround See http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q279870&

for

more details about the issue and workaround.