4.Make sure you configured the VDS/VSS Configuration Utility as explained in Chapter 3 Installation.
5.Check configuration as explained in “Chapter 2 Configuration”:
•Check LAN connectivity between all servers and the array.
•Make sure the firewall is open between all servers and the array.
•Check Command View server NIC bindings: the LAN that connects to the VDS/VSS server must be listed first.
•Make sure you logged into all devices and software using administrator privileges.
•Visit the Microsoft website support knowledge base and search for “VDS logging.” Turn on logging as instructed by Microsoft and use the Microsoft procedure for testing VDS and checking the log.
VSS volume copying not working
1.Is the VSS HWP running? At the command prompt, type: vssadm list providers
You should see the hpEVA VSS hardware provider listed.
2.Verify that the Business Copy license is installed. A BC license is required in order to produce data copies using VSS.
3.Make sure you configured the VDS/VSS Utility as explained in Chapter 3 Installation.
4.Check configuration as explained in Chapter 2 Configuration:
•Check CV workstation and VDS/VSS server connectivity.
•VDS/VSS server not connected to the SAN correctly.
•A firewall may be interfering with connectivity between servers.
5.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.
6.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 available in the Microsoft VSS Software Developer’s Kit to create snapshots. At the command line, type:
vshadow [drive letter]
The drive letter is the production LUN you want to copy. See the Microsoft documentation for details about using vshadow.
•Test your backup application and VSS together by making a backup copy on a local drive, bypassing HWP and the disk array.
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 any limitation in your system to hamper successful snapshots. The following issues may affect system performance:
•Firewall or LAN traffic slowing or preventing communication. Reconfigure the firewall or LAN to increase throughput.
•Viruses slowing server operation. Check for and clean off viruses.
•VDS/VSS server is too slow. Use a fast, late mode CPU with sufficient memory.
•Inadequate privileges. Administrator privileges are required in all applications and on all hardware used with HP VSS HWP.
•Writer application not configured according to best practices. Consult the software manufacturer for recommended practices. For example, keeping database files small by creating more rather
HP StorageWorks EVA Hardware Providers administration guide | 43 |