4.Check Cluster administrator and verify resources are online.

5.Check the Command View server for errors associated with the storage system.

6.Check that the Exchange server can access the data LUNs via My Computer.

7.Check for mount points found under the FRS directory.

8.If Exchange copies fail because of a failed integrity check, verify that eseutil.exe and ese.dll are installed on the recovery server. Integrity checks will not work without them, and a failed integrity check causes a failed copy.

9.The VSS Hardware Provider may not be able to make the copy because it has run out of copy space. Return to the disk array and the HP VSS Hardware Provider Configuration Utility (in Windows Start/Programs/Hewlett-Packard) to create more shadow copy LUNs and then re-populate the configuration utility.

10.Bypass FRS and test VSS, HWP, and the array by using the Microsoft vshadow utility available in the Microsoft VSS Software Developer’s Kit to create snapshots. See the Microsoft documentation for instructions. If you can create snapshots without FRS, FRS may not be properly installed or configured.

FRS does not recognize storage groups

1.Storage groups are not properly set up. See “Chapter 2 Configuration” page 34 to correctly set up production and recovery storage groups.

Troubleshooting

77

Page 77
Image 77
HP Fast Recovery Solution XP SW manual FRS does not recognize storage groups