HP StorageWorks SAN Virtualization Services Platform administrator guide This guide provides information about managing the HP StorageWorks SAN Virtualization Services Platform solution and explains the concepts of running administrative tasks.
Legal and notice information © Copyright 2008-2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 SAN Virtualization Services Platform overview ...................................... 11 Data Path Modules ................................................................................................................... Virtualization Services Manager ................................................................................................. Administrator tasks ....................................................................................................................
Creating the user defined host (UDH) ............................................................................. 42 Creating VSM virtual disks ............................................................................................ 42 Defining hosts in SVSP .................................................................................................. 42 3 Zoning ........................................................................................... 45 Zoning overview .........................
Boot Boot Boot Boot from SAN with OpenVMS .................................................................................................. from SAN with Solaris ........................................................................................................ from SAN with VMware ..................................................................................................... from SAN with Windows Server ..........................................................................................
Storage pool size considerations ........................................................................................ 116 Using thinly provisioned virtual disks ......................................................................................... 116 12 Backup and restore ...................................................................... 119 Backing up and restoring the VSM configuration .........................................................................
Mechanical and electrical ................................................................................................. 145 Characteristics ................................................................................................................. 146 D Regulatory compliance and safety ................................................... 147 Federal Communications Commission notice .............................................................................. Class A equipment ....................
Figures 1 SAN Virtualization Services Platform overview ............................................................ 12 2 The basics .............................................................................................................. 13 3 Management interface ............................................................................................ 14 4 Install/Restore License Key screen of the Launch AutoPass window ................................. 21 5 License dialog box .....................
32 Backup policy attributes ........................................................................................... 93 33 VSS selected as the snapshot method ........................................................................ 93 34 Synchronous mirroring across sites with stretched DPMs .............................................. 103 35 Synchronous mirroring in one stretched domain ........................................................ 105 36 Recovery tab—Attempt to become active ..............
Tables 1 VSM license types ................................................................................................... 19 2 License capacities ................................................................................................... 22 3 Example naming convention for zone types ................................................................ 47 4 Example naming convention for device port types ....................................................... 48 5 Troubleshooting Perfmon ............
1 SAN Virtualization Services Platform overview Figure 1 shows the relationships of the major components that comprise the HP StorageWorks SAN Virtualization Services Platform (SVSP) solution. In describing the solution, this document uses the following terms: • SVSP domain—The two Data Path Modules (DPMs), two Virtualization Services Manager (VSM) servers, and the arrays that are providing block-based storage services to the host servers and SVSP devices.
1 Customer servers 6 Non-virtualized I/O 2 Customer SAN, dual-fabric 7 VSM servers 3 Virtualized I/O as seen by server 8 SVSP domain 4 Virtualized I/O as seen by array 9 HP Command View management platform 5 Data Path Modules Figure 1 SAN Virtualization Services Platform overview . Data Path Modules One way to think of the pair of DPMs is as being similar to a pair of array controllers, only with 8 host ports and 8 back-end ports per controller.
• Local replication (point-in-time copies, snapshots, and snapclones) • Asynchronous remote replication In addition to creating and managing the many objects that exist within the SVSP domain, another purpose of the VSM user interface is to define the virtualization maps used by the DPM to perform the virtualization of the I/O. These virtualization maps exist for each SVSP-defined virtual disk, plus all point-in-time copies, snapshots, snapclones, and remote asynchronous mirrors.
Figure 3 Management interface . The following sections describe steps that need to be performed in creating the initial pool of SVSP blocks, creating a virtual disk or LUN out of those blocks, and then presenting that virtual disk to a server. Common SVSP tasks to get started These tasks allow you to make new virtual disks available for use.
Presenting hosts in SVSP See “Presenting SVSP virtual disks to servers” on page 42. Installing the VSM CLI The VSM CLI packages are located on the Virtualization Services Manager CD. To install the CLI onto a Windows server: 1. If connected, disconnect the Fibre Channel cables from the VSM server. 2. Insert the Virtualization Services Manager CD into the DVD drive. A message asks if you want active content on your computer.
Creating snapclones using HP Business Copy SVSP See the “Using snapclones” chapter in the HP StorageWorks SAN Virtualization Services Platform Manager user guide for information on creating snapclones. Creating remote mirrors using HP Continuous Access SVSP See the “Using mirroring” chapter in the HP StorageWorks SAN Virtualization Services Platform Manager user guide for information on using asynchronous mirroring.
domain, only the interswitch links may use approved single-mode fiber. All other connections, such as VSM-to-switch or DPM-to-switch, must use approved multi-mode fiber. See the HP StorageWorks SAN design reference guide for Fibre Channel specifications. Provided utilities and files The Virtualization Services Manager (VSM) installation CD that is provided with the media kit contains files and utilities that perform important functions. The VSM opening menu shows a list of these files.
• To obtain the VSM CLI packages for HP-UX, Linux, or Windows, click the hyperlink named Browse to VSM CLI Packages to open a Windows Explorer window. Right-click a CLI package and select Save as to copy the package elsewhere. The CD can be used to install the CLI packages on other client servers. • To run the SVSP upgrade patch, select Utility to upgrade from SVSP 2.1x. This upgrade is performed by HP Services.
2 Adding devices to the domain This chapter describes how to expand your SVSP domain by the addition of licensed capacity, arrays, DPMs, and servers. Adding servers requires that you consider the appropriate multipathing for the operating system and switch zoning. Only presentation for an HP Enterprise Virtual Array (EVA) and Modular Storage Array (MSA) is discussed. Please consult the vendor documentation for other types of arrays.
License type Description Migration Allows you to oversubscribe to the current Volume Manager license limit for 90 days for the amount added. For example, if you add 10 TB to the VM license, then for 90 days you can use 20 TB of capacity (10 TB at the source and 10 TB at the destination). NOTE: No physical license is installed.
3. Click Install/Restore License Key. Figure 4 Install/Restore License Key screen of the Launch AutoPass window . 4. In the File path field, enter the path name of the license key file. Alternatively, click Browse to search for the file. 5. Click View file contents. The properties of the license key file appear in the License Contents table. 6. In the Select column of the License Contents table, select the checkbox of the license you want to install. 7. Click Install. The license is now installed.
The following table describes the capacities listed in the License dialog box. Each capacity features its total amount, the amount used, and the amount available. Table 2 License capacities Property Description Basic capacity The amount of licensed capacity allotted for basic operations (for example, the maximum size of all pools). See Table 1 on page 19). BC capacity The amount of licensed capacity allotted for local replication (for example, the size of all parents).
noted that with the exception of striping, the SVSP does not change the performance of the back-end array, and with the exception of synchronous mirrors, SVSP does not change the availability of a back-end array. All physical LUs presented from any array should have the “preferred path” balanced between controllers (for arrays with such a concept; this may not be applicable to HP XP arrays). NOTE: • Do not expand back-end LUs that are already configured in the SVSP.
1. Configure the MSA Storage Management Utility for an MSA2012fc and run the utility. A status message screen is displayed. 2. Click the Manage option, click Create a vdisk from the drop-down menu, and then select Automatic Virtual Disk Creation (Policy-based). The following screen appears.
3. Enter a virtual disk name, tolerance level, size of virtual disk, and number of volumes. Click Create virtual disk. The following screen is displayed. 4. Click Create New Virtual Disk and a processing message appears, as shown on the following screen.
5. After the virtual disk and volumes are created successfully, the volumes can be discovered as back-end LUs from VSM GUI as shown below. 6. Create a storage pool using the MSA back-end LUs. Use this pool to create SVSP virtual disks based on your requirements. Adding HP XP arrays To prevent an issue where pools with LUNs of HP XP arrays go into a partial state and some LUNs in the VSM GUI are marked as failed, create a pool for the HP XP LUNs, but only place one instance of each LU in the pool.
3. Create the new back-end LU. 4. Present the new back-end LU to at least one and not more than two DPM quads per DPM group and VSM servers. NOTE: On some arrays, the term present is also known as permission for allowing access. To discover new back-end LUNs, perform a rescan from Computer Management on the VSM server. Do not use the Rescan devices option from the Windows Management GUI. Use this general procedure when assigning a new storage array LUN: 1.
Deployment steps Before actually configuring the environment it is very important to carefully plan the environment and the deployment steps after taking all the requirements into consideration. The deployment steps include configuring of all the storage components that provide storage services for the VMware environment: • Fibre Channel zoning—Configure the appropriate SAN zoning. • Storage systems—Configure the LUNs and LUN masking.
Supported VSM software versions SVSP 2.0 or higher is required for proper interoperability with VMware ESX server. Configuration Fibre Channel zoning The basic zoning requirement includes at least two zones: front-end and back-end. • The front-end zone includes the ESX server's HBA ports and the DPM target ports (by default DPM port 0 and port 2).
2. Follow the HP StorageWorks SAN Virtualization Services Platform Manager user guide for instructions on how to create a storage pool. 3. Follow the HP StorageWorks SAN Virtualization Services Platform Manager user guide for instructions on how to create a virtual disk from that storage pool. 4. Follow the HP StorageWorks SAN Virtualization Services Platform Manager user guide for instructions on how to configure a UDH for the VMware server (choose VMware for the OS type). 5.
1. Using the VMware VI client GUI, choose the ESX server, select the Configuration tab, and then click the Advance Settings link. On the left menu window choose Disk. • Disk.UseDeviceReset—Make sure this setting is set to 0. This setting forces VMware to not send a target reset to the DPM port when initiating a failover, allowing the failover to be done on a more granular, per-LUN basis (see Disk.UseLunReset below). • Disk.UseLunReset—Make sure this setting is set to 1.
4. Under the Storage Adapters window, chose QLA/LP HBA and then select Rescan. Make sure Scan For New Storage Devices and Scan for New VMFS Volumes are checked in the Rescan window. Under the Details window you should see targets and paths within a target for every VSM virtual disk. 5. Using the VMware VI client GUI, choose the ESX server, select the Configuration tab and then click Storage. 6. Select Add Storage and follow the VMware wizard to create a DATASTORE.
NOTE: At this time, the only supported multipath policy is Most Recently Used (default). VMware storage administration best practices Rescan SAN operations HP recommends that whenever a change is made to the front-side zone a “Rescan SAN” operation is performed on all ESX servers. This is particularly important after recovery of a path failure or when an DPM is replaced. If “Rescan SAN” is not performed, the ESX server may not know about new available paths and will operate in a single path mode.
Using VSS with Windows 2003 SP2 running on a virtual machine Using the Microsoft Virtual Shadow Copy Service (VSS) with Windows 2003 SP2 running on VMware Virtual Machines is supported with ESX 3.5 update 2 or higher and ESXi 3.5 update 2 or higher. Generally this service is needed when there is a need for a synchronized snapshot (also known as consistent quiescent).
1. From the VSM GUI: a. Verify that you can see the LUN presented by the storage array as back-end LUs. b. Follow the HP StorageWorks SAN Virtualization Services Platform Manager user guide procedures to create a storage pool. c. Follow the HP StorageWorks SAN Virtualization Services Platform Manager user guide procedures to create a virtual disk from the storage pool. d.
2. Select the Disk configuration option and scroll down to the Disk,DiskMaxIOSize option, and change the value in the field to 1024. 3. Apply the changes and reboot the ESX server. Using Windows Guests on VMware with VSS The DPM VSS hardware provider installed on a Windows Virtual machine does pass the request to create a VSS snapshot properly to the VSM, and the VSM does respond properly to this request by creating the PIT and the snapshot and assigning it back.
http://h18006.www1.hp.com/products/sanworks/multipathoptions/index.html. HP-UX 11iv2 requires a purchase of the appropriate number of Secure Path licenses. (HP-UX 11iv3 does not require the addition of a new multipath driver.) You should upgrade to the latest multipath drivers on all systems in the SAN as soon as possible, so as not to have different versions of multipath running on various servers.
HP-UX multipathing HP-UX 11iv2 NOTE: Secure Path requires a right-to-use license per server. Secure Path for HP-UX 11iv2 is no longer available, therefore support is only available to existing users that have Secure Path. HP-UX 11iv3 Use native multipathing. Linux multipathing NOTE: Only the QLogic multipathing driver is supported at this time. 1. Go to http://h18006.www1.hp.com/products/sanworks/softwaredrivers/multipathoptions/ linux.html. 2. Select the QLogic driver. 3.
6. Refresh the SANsurfer GUI and change the target ID of one target (for example, change it to 3). Observe that the rest of the targets are grayed out. 7. Create a new initrd image using mkinitrd . 8. Edit the file /boot/grub/menu.lst to boot with the new initrd image and reboot. During the reboot, observe that the new target ID is used for all the LUNs. This can be verified when we display all the LUNs using lssd.
2. 3. Disable AutoFailback: a. Open the /kernel/drv/scsi_vhci.conf file in a text editor. b. Disable the automatic failback capability by changing the auto-failback entry to: auto-failback="disable"; c. Save and exit the file. d. Reboot the system with the # shutdown -g0 -y -i6 command. Verify the system is working: # cfgadm –al # devfsadm –Cv # format (to see all the volumes mapped) 4. Make sure you are using the correct HBA driver.
5. Bind the WWPN to a Target ID. 6. Click Save, and enter the password on the security check popup. If this is the first time you have used the SanSurfer application, and you have not changed the default password, the password is config. 7. Restart the server to make the changes effective. The HBA saves this information. It makes no difference in what order the arrays are scanned. The HBA assigns the saved target ID to the WWPN.
5. Restart the server activate the changes. Presenting SVSP virtual disks to servers The HBAs of a server need to be defined so that the DPM can customize its interface to the operating system of the server that will be using the virtual disk. This is done by creating a user defined host (UDH), which is an alias definition for the server's HBAs with a common property that sets the operating system. The DPMs use the UDH for selective LUN presentation to one or more UDHs.
2. Create HP-UX user-defined hosts (UDHs) from absent HBAs. 3. Right-click on HP-UX UDHs and set the host to offline. 4. Present volumes to the offline HP-UX hosts. 5. Run ioscan on all HP-UX hosts. 6. Right-click on HP-UX UDHs and set the hosts to online. Linux servers It may be necessary to reboot the Linux server to allow the discovery of HBAs by the VSM application. OpenVMS servers Not available at the time of publication. Solaris servers Not available at the time of publication.
Adding devices to the domain
3 Zoning Zoning is a critical part of the configuration process for HP SVSP since it can directly impact the capacity, stability, and performance of the overall system. Failure to implement a correct zoning configuration can lead to a nonfunctioning configuration or one that operates in a reduced state with respect to capacity, performance, and high availability. Zoning overview Any given device port on the SAN can communicate with every other device port when zoning is disabled.
• Use zoning objects on the switch as zone members. Zoning objects allow you to create logical representations on the switch of physical devices and ports in the SAN. These objects can be modified or removed as the physical topology changes and are easier to manage. • Follow a logical naming convention for zoning objects and zones that is readable and can be understood by anyone with knowledge of the HP SVSP.
Zoning components in HP SVSP This section describes zoning between specific components in HP SVSP. Given the complex nature of the HP SVSP with multiple devices and interactions, the overall zoning configuration can be difficult to understand if presented in its entirety. By examining each type of zone and providing general zoning templates, the material in this section can be applied to a wide range of configurations with different devices.
Zone type Naming template Example DPM-VSM __ DPM1_0321_VSM1 VSM-Storage __ VSM1_5a14_EVA1 VSM-VSM _ VSM1_VSM2 Table 4 Example naming convention for device port types Port Type Naming Template Example DPM port _ DPM1_0321 VSM port _ VSM1_5a12 Storage port _
Figure 7 Dual-fabric port configuration for 4–port and 8–port dual-controller back-end storage devices . Figure 8 DPM dual-fabric port configuration . Notice how each DPM quad has a target and initiator on both the red and blue fabrics. Figure 9 Single VSM dual-port configuration . Figure 10 Host server dual-port configuration . DPM-host zoning A DPM-Host front-end zone is used to give a host access to the virtual disks created in HP SVSP and presented through the DPM front-end target ports.
If the DPM pair is in an active/passive relationship (a relationship used in all HP SVSP releases up to and including v2.1), only the paths through the active DPM for a virtual disk are used at any given time while passive paths are used only in failover scenarios. The number of front-end paths that a host can have through a single DPM is directly dependent on the number of host ports in the configuration that are zoned to that DPM.
Figure 12 Zoning between two servers and two quads of a DPM pair . Figure 13 illustrates zoning between two servers with two dual-port HBAs and the first two quads of a DPM pair with the servers being zoned to the same DPM front-end target ports. Figure 13 Zoning between two servers with two HBAs and two quads of a DPM pair . DPM-storage zoning A DPM-Storage back-end zone is used to give the DPM access to the back-end storage used to create virtual disks managed by HP SVSP.
• Each zone has a maximum of four storage device ports. (This rule is necessary when zoning larger arrays with more storage device ports and controllers such as the XP array.) Using these rules, each zoned DPM back-end initiator port has exactly one back-end path to each controller in a storage device. In the case of the HP EVA being the storage device, the dual-controller configuration translates into two paths to the EVA through each DPM back-end initiator port.
Figure 15 Zoning between 2 quad-port controllers and two quads of each DPM . If greater control over the available paths to each LUN is required (for example, to improve load balancing), use a combination of more restrictive zoning and LUN presentation to the DPM from the back-end storage device. DPM-VSM zoning A DPM-VSM back-end zone is used to give the VSM access to the back-end initiator ports of the DPM to manage the DPM LUN mapping information and facilitate data mover functions.
Figure 16 Zoning between VSMs and first quad of a DPM pair . VSM-storage zoning A VSM-Storage back-end zone is used to give the VSM access to the ports of the back-end storage device to manage the storage being virtualized by SVSP, and facilitate data mover functions involving the “slow path” such as mirroring, local snapshots, and remote replication. A back-end path between the VSM and the storage device consists of a single port on the VSM and a storage device port.
VSM-VSM zoning The VSM-VSM zone allows the VSMs in an HP SVSP configuration to communicate with each other over the SAN in order to determine VSM connectivity state and manage failover behavior between the VSMs. This special purpose zone is not classified as a front-end or back-end zone since it does not involve any storage devices or hosts. In this type of zone, a VSM is not strictly classified as a target or initiator.
3. Browse to Entities > HBAs. 4. • Look for HBAs with a status of Partial. • For each Partial HBA, select the Access Path tab, right-click on each failed or absent path (indicated with a red X in the icon), and click Delete. • Repeat this for all Partial HBAs. Browser to Entities > Data Path Modules. • Look for DPMs with a status of Partial. • For each Partial DPM, select the Back-end HBA tab, right-click on each failed or absent path (indicated with a red X in the icon), and click Delete.
4 Monitoring the SVSP domain This chapter describes how to set up monitoring for an SVSP domain using administrative tools. Array workload concentration SVSP relies on the back-end arrays to handle the I/O workload. The volume management capabilities permit focusing the workload of multiple front-end virtual disks onto one back-end virtual disk. The DPMs can unintentionally concentrate front-end I/O workload from multiple front-end hosts and front-end paths down a single back-end path.
VSM graphical user interface For best maintenance performance, open the VSM GUI on a daily basis and look for changes to the objects status. Object status should be Normal (for logical objects like volumes or pools) or Present (for physical devices like disk drives or HBAs). Figure 19 shows an VSM GUI in which the logical objects have a status of Normal and the physical devices have a status of Present. Figure 19 VSM GUI showing status of normal and present .
Figure 21 Quick Query Parameters window . 3. Enter this information: • Query name – This is the name that you want for the query. In this example, the search is for information about HBAs, so the name of the query is HBA. You can use any name that is meaningful to you. You must complete this field. • Comment – Use this field to add descriptive information about the query, such as why you needed to create this query. This field is optional.
Figure 23 The results of a query when objects have status other than normal or present . To determine the status of an object, click on the object in the In Query pane. The status of the object is displayed in the Properties pane. VSM event log You can review the VSM event log for this information: • Critical events • Errors • Warnings Figure 24 shows the entries in the VSM event log. Figure 24 Event log entries .
Alerts automated notification In addition to using the VSM GUI to manually monitor the VSM system, you can configure the VSM to provide alerts. The VSM system includes an automated alert feature. You can configure the VSM to send alerts for specific events to an email address or to syslog servers. Configuring the Alert Destination To configure the alert destination perform these steps: 1. Use the VSM monitor icon on the system tray to open the VSM monitor GUI. 2. Right-click the VSMmonitor icon.
For the Syslog pane: • Server IP—Enter the IP address of the syslog server to which the VSM needs to send the events • Server port—Enter the UDP port on which the VSM communicates with the syslog server. UDP port 514 is the default port for syslog communications. 6. Use the Send test notification after update check box to run a test notification. Make sure that the settings you have configured work properly.
• Specify messages—Use this option to send the notification group emails about specific types of events. Select the event notification criteria in the following tabs. The VSM client sends an event notification email when the selected event notification criteria are met. • By Message Groups—Use this tab to send all of the notification emails in a set of message groups. Select one or more message groups. You can hold down the Ctrl key and randomly select several message groups.
5. In the log settings window, click Add Counters. 6. In the drop-down box under select counters from computer, choose or enter the IP address of the VSM server that is to be monitored. Add any counters you want to monitor. 7. Click Close. 8. In the Interval field, select the time interval for data to be sampled. You can start with 15 seconds, but you may need to occasionally use 3 seconds for more precise data. 9. In the Run As: field, enter the user name and password needed to access the VSM.
Using Perfmon counters to log Perfmon has many counters available, but your data becomes harder to monitor if you have to sort through too much. To learn about a counter, select it, and then click the Explain button. Choose the category from the Performance object drop-down menu. Some counters with similar purposes (for example, Processor: %, Processor Time, and System: Processor Queue Length) are in different categories.
Troubleshooting Perfmon Table 5 describes potential Perfmon problems and possible corrective actions. Table 5 Troubleshooting Perfmon Problem Perfmon log does not start or is not working Cannot change Perfmon settings Corrective action • Check that the correct username and password are used for the VSM server. • Check that the time period is correct. For example, you may have chosen 6 days instead of 6 hours. Ensure that Apply is selected.
monitored objects (Pages/sec, Avg. Disk Queue Length and % Processor time). They can be removed by using the Delete key or clicking the delete icon (X). Add the dedicated performance objects of the VSM agent. Click the '+' icon (or use Ctrl+I) to launch the Add counters interface. On the Performance object drop-down list, locate 'Sync. Mirror Group Performance' and 'Sync. Mirror Job Performance'.
The following table describes the available counters and what they measure. Counter name Explanation Sync.Mirror Job Average Read Response Time (microSec) Measures the average time it takes to complete a write for a mirror job Sync.Mirror Job Average Write Response Time (microSec) Measures the average time it takes to complete a write for a mirror job When evaluating the access capabilities of a VSM to the setup volume, it is recommended to start with the Sync.Mirror Average Write Response Time.
Recommendations Practical measurements with the VSM show that it behaves properly as long as the average write response time to the setup volume does not exceed 20mSec (or 20000 micro seconds in the Performance Monitor counter). Monitoring DPM performance You can use the Diagnostics panel in the DPM Management GUI to monitor the performance of a DPM. Use a web browser to access the GUI and log in with a user name and password.
Monitoring license use To monitor license use, routinely check the License dialog box with the VSM GUI. The access the dialog box, click Tools > License (see Figure 5 on page 21). Monitoring capacity utilization To monitor pool utilization, use the VSM GUI as described in the “Working with storage pools” chapter in the HP StorageWorks SAN Virtualization Service Platform Manager user guide. Monitoring event logs Use the VSM GUI to view and configure event logs.
5 Installing the VSM command line interface The Virtualization Services Manager (VSM) command line interface (CLI) provides scripting capabilities that you can use to automate creation and modification of VSM objects or entities. You may see references to the VSM CLI on some menu screens as SANAPI. The VSM CLI package is separate from the VSM software and the DPM image.
Install the appropriate VSM CLI package for the host operating system The VSM CLI packages are on the Virtual Services Manager CD that is part of the media kit. At the main screen, choose Browse to VSM CLI Packages. The actual version number of the package may be different than the version numbers shown here. AIX operating system Run this package: VSMCLI.AIX.5.1.29.1.LA.bff HP-UX operating systems Run this package: VSMCLI.HPUX.V5.R1.29.0.depot Linux operating system Unzip and untar this file: VSMCLI.V5.
6 Removing devices from the domain This chapter provides a set of steps or checklists for what is to be done when deleting objects or devices from the domain. See the referenced material to get the exact steps needed to perform the indicated action. Deleting or reusing capacity In general, the process of deleting virtual disks is the reverse or opposite of the process used to create and present those same virtual disks. 1.
Deleting back-end LUs 1. Follow the Deleting or reusing capacity procedure above to first identify all affected virtual disks. 2. Delete the PiTs and snapshots associated with those virtual disks. 3. Delete the pool and any associated stripes sets. 4. At this point, it is possible to unpresent and delete the back-end LU. Deleting front-end virtual disks and hosts 1. Stop all applications using the virtual disks. 2.
NOTE: See the chapter on migration in the HP StorageWorks SAN Virtualization Services Platform Manager User Guide, and notes on the migration license in that chapter. Deleting hosts From a VSM perspective, the only requirement for deleting a host is to have the host in an absent status. This status can be achieved by powering the host down. Once deleted on the VSM management GUI, VSM automatically removes the permission for that host on all the objects that it used.
Removing devices from the domain
7 Boot from SVSP devices This chapter outlines the process for booting from the SAN with the various operating systems supported by the SAN Virtualization Services Platform (SVSP). Please see the http://h18006.www1.hp.com/ storage/networking/bootsan.html website for a link to detailed boot from SAN documentation, where application notes are available for each operating system. Boot from SAN with AIX Not currently supported as of the publication date for this document.
7. Continue installing the OS on the new root disk. If previous network settings are not being reused, configure the network settings when prompted during the OS install and setup. 8. If previous network settings are being reused, wait until the OS installation has been completed. Log in as root and use the settings recorded from the original /etc/rc.config.d/netconf file to configure the LAN interfaces for the newly installed OS. 9. Ping a known IP address to confirm network connectivity.
2. Map a LUN to the virtual machine as described in the chapter titled “Creating Virtual Machines.” Specifically, follow the instructions in the section titled “Mapping a SAN LUN.” NOTE: The ESX Server has two methods of presenting SAN storage to virtual machines: • With disk files, a virtual machine can use part of a VMFS-formatted virtual disk on a presented SAN LUN as its storage drive.
14. When a Windows cannot verify the digital signature for this file message appears on the Windows Boot Manager screen, press Enter, followed by F8. Choose Disable Driver Signature Enforcement. (To prevent repeating these actions, you can run following command from a command prompt: Bcdedit.exe -set TESTSIGNING ON). 15. Verify that the host appears in the VSM GUI host list. 16. Add the second host HBA to the original zone from step 5. The host should now see all required front-end ports of both DPMs. 17.
8 Microsoft Volume Shadow Copy Service The Volume Shadow Copy Service (VSS) captures and copies stable images for backup on running systems, particularly servers, without unduly degrading the performance and stability of the services they provide. The VSS solution is designed to enable developers to create services (writers) that can be effectively backed up by any vendor's backup application using VSS (requesters).
set will be created with the same time stamp and will present the same disk state for a multivolume disk state. • Native shadow copy support. Beginning with Windows XP, shadow copy support is available through VSS as a native part of the Windows operating system. As long as at least one NTFS disk is present on a system, these systems can be configured to support shadow copies of all disk systems mounted on them.
1. Run the SVSP VSS installation file. You can find the SVSP VSS installation file on the VSM installation CD or you can download the file on the web. From the VSM installation CD, click Browse to SVSP VSS Provider on the main menu. For your type of installation (ia64, x64, or x86), select the SVSPVssProviderSetup file. The Welcome screen appears. 2. Click Next. The Select Installation Folder window appears.
3. Click Next. The Confirm Installation window appears. 4. If you want to make changes to your installation, click Back until you arrive at the window where you can make the change. If you are satisfied with your installation choices, click Next to start the installation. After the SVSP VSS hardware provider is installed, the Installation Complete window appears. 5. Click Close to exit the installation wizard.
6. Make sure that the SVSP VSS hardware provider is recognized by VSS by opening a DOS command prompt window (click Start > Run, and type cmd), typing vssadmin list providers, and pressing Enter. The information returned by the vssadmin list provider command is similar to the information shown in Figure 25. Figure 25 SVSP VSS hardware provider in a DOS window . Make sure that the SVSP VSS hardware provider appears in the list. 7.
8. To add a user that the SVSP VSS hardware provider will use for interfacing with the VSMs, type SaHwConfig AddUser and press Enter. Adding a user succeeds if these conditions are met: • The server can access a SAN CLI virtual disk from the domain with which you are trying to connect. • The user exists in that domain.
7. In the DOS command prompt window on the host server, type vshadow.exe -p m: and press Enter. This command creates a persistent shadow copy on drive m:. The drive label is the letter that you gave to the new drive in step 6. The shadow copy is a read-only point-in-time replica of the original volume contents. A persistent shadow copy remains in the system until you, or the backup application, initiates an explicit command to delete the shadow copy.
Figure 27 Results of the vshadow.exe -p m: command in the DOS command prompt window . Figure 28 shows an example of the hierarchical snapshot structure that is created on the VSM. Both the PiT name and the snapshot name include the initial part of the shadow copy set number.
Figure 28 Results of the vshadow.exe -p m: command in the VSM GUI . The full shadow copy set number appears in the comment field of the PiT and snapshot in the VSM. Figure 29 shows information that appears in the comment field. Figure 29 Shadow copy set number information in the PiT Comment field . To see views that are created by VSS, select Tools > Options > General > Data presentation and select the Show VSS Views checkbox. 8.
9. Open the newly mounted snapshot. Make sure that the snapshot has the data of the original virtual disk at the time you created the snapshot. 10. Remove the VSS shadow copy by typing vshadow.exe -ds={SnapShotID} and pressing Enter. The vshadow.exe -ds={SnapShotID} command unmounts the snapshot on the host and deletes the snapshot and PiT on the VSM. 11. To create a persistent VSS shadow copy with a snapshot that can be presented to another host, type vshadow.exe -p -t=export.xml m: and press Enter.
storage provider on the backup client server where the application, the writer, exists. Exposing the servers to the SAN CLI virtual disk makes the servers ready to service the VSS command that the backup software initiates. The following images show a configuration example of Veritas NetBackup software that uses VSS snapshots. The configuration consists of two servers: • One server runs the application and has an adequate backup client installed.
Figure 31 Example of a disk drive acting as a media server . Figure 32 shows the attributes of the backup policy. Note that this policy is configured to perform snapshot backups.
Figure 32 Backup policy attributes . Figure 33 shows that VSS was selected as the snapshot method for use. VSS was selected through the Advanced Snapshot Options... button shown in Figure 32. Figure 33 VSS selected as the snapshot method . VSS deployment with VSM virtual disk groups To reference multiple VSM virtual disks as a single entity, you must place the VSM virtual disks in a virtual disk group (VDG).
on all VDG members. VDGs are often used to encapsulate data files and log files of the same database into a one entity. From a server perspective, the data files and the log files reside on two separate drives. From a backup and recovery perspective, the data files and the log files are two components of a single entity. A backup snapshot must be synchronously captured on both the data drive and the log drive.
9 Site failover recovery with asynchronous mirrors The asynchronous mirror decision table When using an asynchronous mirror group pair, some actions and properties require that you specify either the source or destination. See the following tables: creating and deleting, adding and deleting virtual disks, editing (setting) properties, and controlling. Creating and deleting Task Create an asynchronous mirror group pair. Delete an asynchronous mirror group or pair.
Editing (setting) properties Task Async mirror group to specify Result on source async mirror group Result on destination async mirror group Edit (general) an asynchronous mirror group. Either Properties are changed. Properties are changed. Auto suspend on links down mode for an asynchronous mirror group pair. Source Auto suspend on links down is disabled or enabled. Auto suspend on links down is disabled or enabled. Comment for an asynchronous mirror group.
Task Resume remote replication in an asynchronous mirror group pair. Revert an asynchronous mirror group pair to its home configuration. Suspend remote replication in an asynchronous mirror group pair. Async mirror group to specify Result on source async mirror group Result on destination async mirror group Source Remote replication from the source is allowed. If applicable, begins log merging or full copy from the source. Remote replication to the destination is allowed.
11. Each SVSP domain now sees the VSM servers of the other SVSP domain with status degraded because the FC HBAs that previously used to connect the SVSP domains are no longer used. Delete the FC HBAs that previously used to connect the SVSP domains from the HBA lists on both SVSP domains. You can access the HBA list from the HBA node in the tree.
7. Wait until the PiT you created is copied to the destination. 8. Suspend the group. 9. Split the group. 10. Log in to the DR site's SVSP domain. 11. Assign the host permission to use the mirrored virtual disk. 12. Merge the mirrored virtual disk without enabling rollback. Specify the name of the original virtual disk on the main site as the destination. VSM creates an async mirror group, mirroring from the DR site to the main site. To fail back from the disaster recovery site to the main site: 1.
1. Connect to the main site's SVSP domain and prepare the virtual disk for a merge, as follows: a. Verify that the virtual disk exists. b. Detach the task. c. Remove host presentations from the virtual disk. d. Delete any snapshots on the virtual disk. The virtual disk is now ready to become the destination virtual disk of a new group created by merging the current production virtual disk on the DR site. 2.
4. Assign the host permission to use the recovery virtual disks. You can do either of the following: a. Right-click the specific DR element that you want to recover, and select Manage > Add Host Permission to assign permission to a host to use the DR element. The host will then use the most recent PiT available on that DR element. There is a chance, however, that the application will not be able to use the PiT as it is.
3. 102 Perform a controlled failback of each virtual disk to the new main site, as follows: a. Plan a downtime window for the application, based on the organization’s needs and any data that was not yet mirrored. b. At the scheduled time, shut down the application, which is currently using a virtual disk on the DR site. c. Unmount the virtual disk on the host. d. Connect to the DR SVSP domain. e. Remove the host permission from the virtual disk.
10 Site failure recovery with synchronous mirroring The Virtualization Services Manager (VSM) synchronous mirroring feature provides continuous access to a virtual disk even if one of the underling physical storage component fails. Synchronous mirroring is done with the local domain only, but can be two sites as in a stretched domain.
NOTE: When using synchronous mirrors to protect multiple virtual disks that belong to the same application, it is best practice to have all of the virtual disks active on the same DPM. This is especially true when in the stretched domain, so as to have all virtual disks of that application fail over together or not at all. Site failures In this topology, each site failure affects the surviving site. The recovery order, however, depends on the site that fails.
Figure 35 Synchronous mirroring in one stretched domain . Configuration requirements The setup virtual disk of the domain is synchronously mirrored with up to five tasks, including the original virtual disk. While the requirement is to have at least one synchronized task of the setup virtual disk on each site, best practice has at least two setup volumes per site. This allows the active VSM server to keep on working when the connection with the other site is broken.
The end result is the same: the surviving site loses connectivity with the VSM server, the DPM, application servers, and the storage arrays at the other site.
Recovering synchronous mirror volumes from site disconnection 1. 2. Recover the inter-switch link connection between the sites, if possible. Then, initiate a resynchronization (right-click the group, and select Resume) for the synchronous mirror groups after the restoring the inter-switch link connection. If you cannot recover the connection between sites within a reasonable time, consider appointing one of the sites as the surviving site and apply the recovery procedure for site failure.
Whenever you select an entry and click the Yes button or the OK button, make sure that the status of the VSM is Passive. The entries from the Recovery tab are not accepted when the VSM is stopped. The first window on the Recovery tab asks your permission to use the surviving copy of the boot data and to ignore the missing ones. Figure 36 shows the Recovery tab message asking if you want the VSM to attempt to become active. Figure 36 Recovery tab—Attempt to become active .
3. 4. On the surviving site, for every failed synchronous mirror group, right-click the mirror group, and select Manage > Recovery > Force Resume. To run Force Resume on all of the failed synchronous mirror groups, right-click the synchronous mirror entity in the left pane, and select Recovery > Force Resume All.
Figure 38 Recovery tab—Attempt to become active . The second window on the Recovery tab (see Figure 39) notifies you that the synchronous mirror of the setup virtual disk has a status of Partial. A status of Partial means that some of the setup volume mirror tasks are missing, and that the mirror cannot decide which task to use. The window offers these options: • Resume—Use this option after you have fixed the problem that prevented the access to some of the mirror tasks.
Module > Change Active DPM. Make sure that the failover succeeds and the DPM with a status of Present becomes the active DPM for that synchronous mirror group. 4. At the surviving site, for every failed synchronous mirror group, right-click the mirror group, and select Manage > Recovery > Force Delete. The Force Delete option deletes of the synchronous mirror objects on the selected groups.
Site failure recovery with synchronous mirroring
11 Configuration best practices Best configuration practices are the recommended and field tested approach to configuring SVSP. These best configuration practices are formulated to enable SVSP storage administrators to create and operate an environment that does not require constant attention to assure that all components are operating without congestion and below saturation.
to get it out of that state. If ISLs are being used, it is best practice to set up alert levels in the switches to ensure that notification of problems are realized. Limit the number of switch hops from the servers to the DPMs, and from the DPMs to the storage, to a maximum of three hops. In no case should the server-to-storage route exceed a total of seven switch hops.
A simple concatenated pool should have all of its volumes presented from a single back-end array. The volumes should have the same RAID type, and similar performance and capacity characteristics. The pool is constructed of at least as many volumes as there are paths from the DPMs to the array (16 for an 8–host port array).
avoid going over all the back-end LUNs in the pool to find the best match (for example, the smallest contiguous free area that is greater than or equal to the required capacity) in order to save time (at least for PiT expansions time is a critical factor). When additional virtual disks are configured, a back-end volume is selected at random, and the algorithm seeks to find a contiguous free space. This applies to the temporary volumes used to support PiTs, snapshots, thin provisioning, and so on, too.
write. This may be observed after the creation of a thinly provisioned virtual disk when random writes may trigger many expansions, and is less likely to occur after a volume has been used for a while. To avoid this first write penalty, pre-write a significant portion of the volume and then delete the data. SVSP allows for an initial allocation of up to (the smaller of) 10% of the size of the virtual disk or 32 GB. Growth of the allocation is based on the size of the initial allocation.
Configuration best practices
12 Backup and restore This chapter describes how to backup and restore the VSM configuration database and the DPM configuration information. Backing up and restoring the VSM configuration The VSM runs an automatic backup of the setup configuration at predefined intervals and places it in the C:\Program Files\Hewlett-Packard\SVSP\Core\Backup directory. The default backup interval is every 60 minutes. You can define when the backup occurs through the VSM management GUI.
Application > Trace tab > Folder size > Backup For best operation, use a backup application to back up this folder to another disk or tape. CAUTION: Possible loss of data access—You can safely restore the VSM setup database from backup only if the system does not have PiTs. If PiTs exist, either created by users or create by multi applications, the metadata for the PiTs is in the setup backup. The metadata in the setup backup might be invalid and can result in the loss of data access if restored.
For additional backup protection, use an SFTP or an SCP utility to copy the saved configuration file to an external host. To restore the backup configuration file, perform these steps: 1. Login to the DPM as kadmin. 2. To upload the saved config file you want use, type this command and press Enter. load config where is the name of the configuration file that you saved using the save config command. The configuration file is retrieved from /common/ images/configs. 3. 4.
Backup and restore
13 Basic maintenance and troubleshooting This chapter describes how to solve problems you might encounter after installing and configuring the HP StorageWorks SAN Virtualization Services Platform. Diagnostic tools HP Command View EVA and the Array Configuration Utility (ACU) for the MSA will report hardware and configuration problems after storage has been presented to the HP StorageWorks SAN Virtualization Services Platform domain.
Problem Corrective action Check the DPM status LEDs. An amber LED may show as solid or blinking. The DPM powers on but does not boot • A solid amber indicates the DPM failed to complete the boot up process. • A blinking amber indicates the DPM detected a chassis failure or impending chassis failure (such as a fan or power supply). In either case, contact HP Services. • Check if the second VSM is active. The VSM does not become active on startup. • Check the status of VSM service in the VSM monitor.
Problem Corrective action • Verify that there is adequate free space in the pool. • Verify that the pool is in a normal status. Missing EVA or MSA virtual disks can cause a volume creation failure. Cannot create a new virtual disk. • Verify the presented capacity is available. • Verify that the license capacity has not been exceeded. • Check the Disabled Operations tab on the pool for a potential cause. Cannot delete a virtual disk. The virtual disk is running on the secondary DPM.
Presentation problems Table 9 Presentation problems Problem Corrective action • Verify that the correct preferred path is configured with HP Command View EVA or the ACU for each LUN that is exposed. If so, reboot the VSM server. Back-end LUNs cannot be seen, even after a rescan using the VSM GUI.
Administrative problems Table 10 Administrative problems Problem Corrective action Cannot remember the administrator account password. Report the problem to HP support. The setup database will have to be modified to reset the password to a known value. Cannot remember non-administrative account password. Log in with the administrator user name and password and reset the user password to a known value.
VSM server LUN masking To verify a proper LUN masking configuration on the VSM server, open the VSM management interface and go to the back-end LUs. Make sure that VSM can see all the back-end LUs provisioned to the VSM HBAs. For each back-end LU, verify that the number of paths is correct. To check the settings of the second VSM, failover the passive VSM server, and then repeat the process.
14 Support and other resources Contacting HP Before you contact HP Be sure to have the following information available before you contact HP: http://www.hp.
Creating and submitting an SaSnap A VSM SaSnap icon has most likely already been installed on your server. If not, the following procedure begins by describing how to install the icon. 1. Add VSM SaSnap icon to the desktop. a. Click the Windows Start button. b. Highlight All Programs. c. Highlight SVSP. d. Right-click on SVSP SaSnap, highlight Send To, and select Desktop. A VSM SaSnap icon appears on the desktop. 2. Launch VSM SaSnap by clicking the icon created in the previous step. 3.
c. Select Full and click OK. d. Repeat these steps for all other VSMs at the second site. NOTE: If you are not using HP Continuous Access SVSP, you still have to enter the administrator user name and password for the second VSM at the local site. The user name must have administrative privileges for the VSM. 4. Ensure that the check box is selected next to the names of the Local SVSP. 5. Check the box next to the DPMSnap under Local SVSP. 6. Click the + button next to parameters and select full.
8. Click the ... button to set the output path. NOTE: The SaSnap process can cause the local drive to run out of free space over time as files accumulate. Consider putting SaSnap files onto another partition, such as the backup partition. The status window shows the log collection progress. When the process is complete, the abort button will change to a Start button.
9. Upload the collected log files to HP support. a. Open Windows Explorer. b. Navigate to the output directory selected during the VSM SaSnap process. c. Contact your local support center, and get the appropriate FTP site to use for uploading the SaSnap files. d. Upload the files to the site. E-mail the pointer to HP Support and send a copy of the message to SVSPHealthCheck@hp.com.
Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/wwalerts After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.
Document conventions and symbols Table 11 Document conventions Convention Element Blue text: Table 11 Cross-reference links and email addresses Blue, underlined text: http://www.hp.
HP websites For additional information, see the following HP websites: • • • • • • http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/go/svsp http://www.hp.com/support/manuals http://www.hp.com/go/sandesignguide http://www.hp.com/support/downloads Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
A Using VSM with firewalls To protect you system against unauthorized access from outside your network, enable Windows Firewall. However, a number of ports need to be opened to allow SVSP to communicate properly. Windows 2003 To enable Windows Firewall on Windows 2003: 1. Click Start > Control Panel > Windows Firewall. 2. On the General tab, verify that the firewall is On (enabled). 3. Click the Exceptions tab. 4. Select File and Printer Sharing and click the Edit button. 5.
10. Enter a name and port number for the entries below. NOTE: The VSM Status Monitor is already displayed by default. Program/service name TCP port ftp_tcp_20 20 ftp_tcp_21 21 ssh_tcp_22 22 telnet_tcp_23 23 iscsi_tcp_3260 3260 corba_tcp_4102 4102 smis_tcp_5989 5989 http_tcp_8080 8080 SVM Status Monitor NA 11. Click OK.
Windows 2008 To enable Windows Firewall on Windows 2008 through Server Manager: 1. Open Server Manager. 2. Select Configuration > Windows Firewall With Advanced Security > Windows Firewall Properties. 3. Under each the first three tabs, select Settings > Customize. 4. Under the Firewall settings, ensure that Display a notification is set to Yes. In addition, the SVSP must be added to the Exceptions tab in the Windows Firewall Settings. 1. Go to Control Panel > Windows Firewall Settings. 2.
7. Enter a name and port number for the entries below. NOTE: The VSM Status Monitor is already displayed by default. 8. 140 Program/service name TCP port ftp_tcp_20 20 ftp_tcp_21 21 ssh_tcp_22 22 telnet_tcp_23 23 iscsi_tcp_3260 3260 corba_tcp_4102 4102 smis_tcp_5989 5989 http_tcp_8080 8080 SVM Status Monitor NA Program/service name UDP port UDP 137137 20 Click OK.
B Configuration worksheets Use these worksheets to document the names, IP addresses, and other important information for your SAN Virtualization Services Platform configuration.
Configuration worksheets
C Specifications This appendix contains the specifications for the HP StorageWorks SAN Virtualization Services Platform Data Path Module (DPM) and the HP StorageWorks SAN Virtualization Services Platform Virtualization Services Manager (VSM) Server.
Device management Feature Description Access Serial port, SSH, telnet, web browser, SOAP/XML, SNMP interfaces Interfaces Supported protocols • 10/100/1000 Ethernet RJ-45 for management (optional) • 1 serial DB-9 RS232 for configuration and basic management ssh, telnet, ftp, http, SNMP, NTP, and net syslog Mechanical Characteristic Value Dimensions 17 in. (W) x 1.75 in. (H) x 26 in. (D) Enclosure 1U rack-mountable Weight 10.
Regulatory The Data Path Module has the following certifications: • • • • • UL CE cUL FCC TUV VSM server Environmental Specification Value Temperature range1 Operating 10°C to 35°C (50°F to 95°F) Shipping –40°C to 70°C (–40°F to 158°F) Maximum wet bulb temperature 28°C (82.4°F) Relative humidity (noncondensing)2 Operating 10% to 90% Non-operating 5% to 95% 1 All temperature ratings shown are for sea level. An altitude derating of 1°C per 300 m (1.
Specification Value Input requirement Rated input voltage 100 VAC to 240 VAC Rated input frequency 50 Hz to 60 Hz Rated input current 7.1 A (at 120 VAC); 3.5 A (at 240 VAC) Rated input power 852 W BTUs per hour 2910 (at 120 VAC); 2870 (at 240 VAC) Power supply output Rated steady-state power 700 W Characteristics Component Characteristic Processor Dual-Core Intel Xeon 5130 2.
D Regulatory compliance and safety Federal Communications Commission notice Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules.
Declaration of conformity for products marked with the FCC logo, United States only This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. For questions regarding your product, contact: Hewlett-Packard Company P. O.
WARNING! Use of controls or adjustments or performance of procedures other than those specified herein or in the installation guide of the laser product may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation: • Do not try to open the module enclosure. There are no user-serviceable components inside. • Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.
• • • • EC 61000–4–3:2006 - “Radiated, Radio-Frequency, Electromagnetic Field Immunity Test” EC 61000–4–4:2004 - “Electrical Fast Transient/Burst Immunity Test” EC 61000–4–5:2005 - “Surge Immunity Test” EC 61000–4–6:2004 - “Immunity to Conducted Disturbances, Induced by Radio-Frequency Fields” • EC 61000–4–8:2001 - “Power Frequency Magnetic Field Immunity Test” • EC 61000–4–11:2004 - “Voltage Dips, Short Interruptions and Voltage Variations Immunity Tests” • EN 61000–3–2:2000 +A2:2005 - “Limits for Harmoni
Class B equipment Safety Battery replacement notice WARNING! The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury: • Do not attempt to recharge the battery. • Do not expose the battery to temperatures higher than 60˚C (140˚F). • Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water.
NOTE: Route power cords so that they will not be walked on and cannot be pinched by items placed upon or against them. Pay particular attention to the plug, electrical outlet, and the point where the cords exit from the product. Japanese power cord notice Electrostatic discharge To prevent damage to the system, be aware of the precautions you need to follow when setting up the system or handling parts.
Waste Electrical and Electronic Equipment (WEEE) directive Czechoslovakian notice Danish notice Bortskaffelse af affald fra husstande i den Europæiske Union Hvis produktet eller dets emballage er forsynet med dette symbol, angiver det, at produktet ikke må bortskaffes med andet almindeligt husholdningsaffald. I stedet er det dit ansvar at bortskaffe kasseret udstyr ved at aflevere det på den kommunale genbrugsstation, der forestår genvinding af kasseret elektrisk og elektronisk udstyr.
This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for recycling of waste electrical and electronic equipment.
German notice Entsorgung von Altgeräten aus privaten Haushalten in der EU Das Symbol auf dem Produkt oder seiner Verpackung weist darauf hin, dass das Produkt nicht über den normalen Hausmüll entsorgt werden darf. Benutzer sind verpflichtet, die Altgeräte an einer Rücknahmestelle für Elektro- und Elektronik-Altgeräte abzugeben.
Questo simbolo presente sul prodotto o sulla sua confezione indica che il prodotto non può essere smaltito insieme ai rifiuti domestici. È responsabilità dell'utente smaltire le apparecchiature consegnandole presso un punto di raccolta designato al riciclo e allo smaltimento di apparecchiature elettriche ed elettroniche. La raccolta differenziata e il corretto riciclo delle apparecchiature da smaltire permette di proteggere la salute degli individui e l'ecosistema.
Portuguese notice Descarte de Lixo Elétrico na Comunidade Européia Este símbolo encontrado no produto ou na embalagem indica que o produto não deve ser descartado no lixo doméstico comum. É responsabilidade do cliente descartar o material usado (lixo elétrico), encaminhando-o para um ponto de coleta para reciclagem.
eliminación contribuirá a conservar los recursos naturales y a garantizar el reciclado de estos residuos de forma que se proteja el medio ambiente y la salud. Para obtener más información sobre los puntos de recogida de residuos eléctricos y electrónicos para reciclado, póngase en contacto con su ayuntamiento, con el servicio de eliminación de residuos domésticos o con el establecimiento en el que adquirió el producto.
Glossary This glossary defines acronyms and terms used with the SVSP solution. access path A specific series of physical connections through which a device is recognized by another device. active boot set The boot set used to supply system software in a running system. Applies to the DPM. See also boot set. active path A path that is currently available for use. See also passive path, and in use path.
Business Copy SVSP An HP StorageWorks product that works with SAN storage systems to provide local replication capabilities within the SVSP domain, providing local point-in-time (PiT) copies of data, using snapshots of data, based on changes to virtual disks. CLI Command line interface. The Data Path Module provides a CLI through the local administrative console (serial port console), telnet, or SSH.
HBA See host bus adapter. host In VSM, every server that uses VSM virtual disks. Servers that run as VSM servers are also considered hosts. host bus adapter A device that provides input/output (I/O) processing and physical connectivity between a server and a storage system. In order to minimize the impact on host processor performance, the host bus adapter performs many low-level interface functions automatically or with minimal processor involvement.
mirroring The creation and continuous updating of one or more redundant copies of data, usually for the sake of fault or disaster recovery. OpenVMS Unit ID Abbreviated as OUID. A storage element identifier that is necessary for hosts running OpenVMS to interact with the storage elements presented to them. This identifier is relevant to virtual disks, snapshots, and synchronous mirror groups.
SFP Small form-factor pluggable. The 2 Gbps or faster form factor of the removable optical transceiver used by the Data Path Module, HBAs, and most Fibre Channel switches. It uses the LC-type connector. snapclone A VSM service that creates physical copies of VSM virtual disks without using host resources.
thick provisioned A quality of virtual disks wherein the virtual disk’s allocated capacity is always equal to its total capacity. See also virtual disk. thin provisioned A quality of virtual disks wherein the virtual disk’s allocated capacity is set to a small initial value that can expand up to the virtual disk’s total capacity according to actual usage. transceiver A device that provides an interface between the Data Path Module hardware and the external network cable.
WWNN World Wide Node Name. The globally unique identifier for a system containing Fibre Channel ports. A WWN is a 64–bit value, typically represented as a string of 16 hexadecimal digits. WWPN World Wide Port Name. The globally unique identifier for an individual Fibre Channel port. A WWPN is a 64–bit value, typically represented as a string of 16 hexadecimal digits. zone A collection of devices or user ports that are permitted to communicate with each other through a fabric.
Glossary
Index A adding array, 22 EVAs, 23 MSAs, 23 new back-end LUs, 26 servers, 27 administrative problems, 127 array adding, 22 non-HP branded, 26 retiring, 74 array workload concentration, 57 asynchronous mirrors decision table, 95 B back-end LUs, 13, 22, 23 back-end LU deleting, 74 battery replacement notice, 151 boot from SAN HP-UX, 77 Linux, 78 VMware, 34 Vmware, 78 Windows, 79 C cables, regulatory, 148 capacity, adding, 26 Class A equipment, 147 Class B equipment, 147 configuration problems, 124 worksheets
F M failover DR site after problem, 99 main site lost, 100 fault isolation, 123 FCC notice, 147 firewalls, 137 Force Delete, 109 Force Resume, 107 Microsoft VSS deployment with VDGs, 93 installing SVSP hardware provider, 82 integrate with async mirrored virtual disks, 90 integrate with backup software, 90 model, 81 test functionality, 86 uninstalling DPM hardware provider, 94 monitoring capacity utilization, 70 event logs, 70 license use, 70 SAN, 70 system performance, 57 monitoring VSM setup volume, 66
reusing capacity, 73 S safety, 151 SaSnap, 130 Solaris, multipath, 39 specifications, 143 startup problems, 123 Storage VMotion, 33 stretched domains, 103 Subscriber's Choice, HP, 134 supported configurations, 16 SVPS characteristics, 143 specifications, 143 SVSP configuration worksheets, 141 overview, 11 topology, 104 symbols in text, 135 synchronous mirrors across SVSP sites, 103 site recovery, 104 stretched domain, 104 T technical support HP, 129 service locator website, 136 text symbols, 135 troublesh
