HP AiO400t HP StorageWorks All-in-One Storage System Release Notes (434690-006 - Page 10
Different Location Restore
View all HP AiO400t manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 10 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: The Restore Wizard does not allow the "Overwrite Restore" option when restoring data backed up prior to upgrading to AiO 1.3 or later. Description Due to object model changes in AiO 1.3 and later, it is not possible to perform an overwrite restore when restoring data that was backed up prior to AiO 1.3. The data may be restored to an alternate location and then manually moved to the original location. Workaround Use the Different Location Restore option to restore the data to an alternate location of your choice. The data can then be moved manually, overwriting the existing files. Issue: Backup job fails for Exchange storage groups that were manually migrated to AiO. Description It is possible to manually create a virtual hard disk on AiO 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 AiO 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 AiO. 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