HP DL160 HP ProLiant Storage Server release notes (5697-7750, November 2008) - Page 9

C:\Program Files\HP\Data Protector

Page 9 highlights

Data Protector Express Check the dpconfig.ini file at C:\Program Files\HP\Data Protector Express\config. In particular, the isDatabaseServer setting should be Yes. Other entries may vary depending on your configuration. The file should have a [configuration] section similar to the following: [configuration] lastUser=ASMbackup Workaround nodeGuid={00001001-44BF7770-0010D9E7-0018CAB0} nodeName=STORAGEWORKSAIO databaseServerAddress=localhost isDatabaseServer=Yes databaseServerName=Data Protector Express Storage Domain disableNetwork=Yes remoteAdmin=No Issue: Backup job fails for Exchange storage groups that were manually migrated to the storage server. Description It is possible to manually create a virtual hard disk on the storage server using the Microsoft Software iSCSI Target snap-in. This disk may then be assigned to a target, allowing an iSCSI initiator on the Exchange server to access the disk as a local volume. If the logs and database(s) of an Exchange storage group are then moved to this iSCSI volume, All-in-One Storage Manager (ASM) will discover the Exchange Storage Group, and present it as an application in the ASM user interface. This will allow you to configure data protection for the application and schedule a DPX backup; however, when the backup job runs, it fails. The job status in DPX will be operator canceled, and the following error is written to the Windows application event log on the storage system: Stopping backup job '' due to checksum verification failure. The error occurs because ASM performs checksum verifications using the eseutil.exe utility on Exchange databases and logs before backing up the files. Databases and logs are expected to be found in separate volumes as a best practice method employed by ASM when a wizard is used to migrate an Exchange storage group to the storage server. When the logs are not found, the checksum fails and ASM cancels the backup job and notifies Exchange that the backup did not complete successfully. 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13

Data Protector Express
Workaround
Check the
dpconfig.ini
le at
C:\Program Files\HP\Data Protector
Express\config
. In particular, the
isDatabaseServer
setting should be
Yes
.
Other entries may vary depending on your con
guration.
The
le should have a [con
guration] section similar to the following:
[configuration]
lastUser=ASMbackup
nodeGuid={00001001-44BF7770-0010D9E7-0018CAB0}
nodeName=STORAGEWORKSAIO
databaseServerAddress=localhost
isDatabaseServer=Yes
databaseServerName=Data Protector Express Storage Domain
disableNetwork=Yes
remoteAdmin=No
Issue:
Backup job fails for Exchange storage groups that were manually migrated to the storage server.
Description
It is possible to manually create a virtual hard disk on the storage server using
the Microsoft Software iSCSI Target snap-in. This disk may then be assigned to
a target, allowing an iSCSI initiator on the Exchange server to access the disk
as a local volume.
If the logs and database(s) of an Exchange storage group are then moved to this
iSCSI volume, All-in-One Storage Manager (ASM) will discover the Exchange
Storage Group, and present it as an application in the ASM user interface. This
will allow you to con
gure data protection for the application and schedule a DPX
backup; however, when the backup job runs, it fails.
The job status in DPX will be
operator canceled
, and the following error is written
to the Windows application event log on the storage system:
Stopping backup job '<job name>' due to checksum
verification failure.
The error occurs because ASM performs checksum veri
cations using the
eseutil.exe utility on Exchange databases and logs before backing up the
les.
Databases and logs are expected to be found in separate volumes as a best
practice method employed by ASM when a wizard is used to migrate an Exchange
storage group to the storage server. When the logs are not found, the checksum
fails and ASM cancels the backup job and noti
es Exchange that the backup
did not complete successfully.
10