HP StorageWorks Hardware Providers for VDS/VSS installation guide (T1634-96089, December 2009)

5. Check configuration as explained in the configuration and installation sections:
• VDS/VSS server not connected to the SAN correctly.
• For XP only: Check that a host group named SVOL exists with secondary LDEVs that match
the parameters of the primary LUNs (same emulation type and size). Also check that a host
group named SHADOW exists. No host WWNs should be associated with the SVOL or
SHADOW host groups before installation.
• For EVA only, check the Command View EVA management server and VDS/VSS server
connectivity.
• For EVA only, a firewall may be interfering with connectivity between Command View and
VDS/VSS servers.
6. Review the Windows application event log, Windows system event log, and VSS trace to locate
errors in the snapshot process. See the Microsoft website and Windows help for information
about the log and trace files.
7. Use a process of elimination to determine which components are not working. You can do this
by testing components individually:
• Test VSS and the array by using the Microsoft VShadow utility (or DiskShadow in Windows
Server 2008) available in the Microsoft VSS Software Developer's kit to create snapshots.
For Windows Server 2003, at the command prompt, enter:
vshadow [drive letter]
The drive letter is the production LUN you want to copy. See the Microsoft documentation for
details about using VShadow.
For Windows 2008/2008 R2, at the command prompt, enter:
DiskShadow
Then enter:
Add Volume[drive letter]
Then enter:
Create
The drive letter is the production LUN you want to copy. See the Microsoft documentation for
details about using DiskShadow.
• Test your backup application and VSS together by making a backup copy on a local drive,
bypassing the HP VSS hardware provider and the disk array.
• For XP only: Test array copy capability by using Business Copy to create P-VOL and S-VOL
pairs and copy the P-VOL to the S-VOL. See the HP StorageWorks Business Copy User Guide
for instructions.
VSS copies intermittently fail or time out
VSS allows only 30 seconds for the entire snapshot process, including only 10 seconds for actually
making the copy. This narrow time window can cause a limitation in your system to prevent snapshot
creation. The following issues may affect system performance:
• For EVA only: A firewall or LAN traffic can slow or prevent communication. Reconfigure the firewall
or LAN to increase throughput.
• Viruses can slow server operation. Use a virus scan product to check for viruses.
• The VDS/VSS server is too slow. Use a newer, faster CPU with sufficient memory.
• Privileges are not set correctly. Administrator privileges are required in all applications and on all
hardware used with the HP VSS hardware provider.
Hardware Providers for VDS/VSS installation guide 41