HP StorageWorks SAN Virtualization Services Platform Manager user guide Part number: AG781–96017 Second edition: March 2009
Legal and notice information © Copyright 2008-2009 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 About this guide ................................................................................. 21 Intended audience .................................................................................................................... Related documentation .............................................................................................................. Document conventions and symbols .............................................................................................
Working with VSM servers ................................................................ 51 Viewing the VSM server list per domain ....................................................................................... 51 Viewing VSM server information ................................................................................................. 52 VSM server information—DM Task tab ..................................................................................
Storage pool information—Disabled Operations tab ............................................................... Creating storage pools .............................................................................................................. Expanding storage pools ........................................................................................................... Shrinking storage pools .............................................................................................................
Managing VDG permissions .................................................................................................... 136 Adding host permission to VDGs ........................................................................................ 136 Changing host permissions ................................................................................................ 139 Removing host permissions ................................................................................................
DPM information—Disabled Operations tab ........................................................................ Failing over virtual disks from a DPM ......................................................................................... Failing back virtual disks from a DPM ........................................................................................ Replacing a DPM ....................................................................................................................
Changing the active DPM for a snapshot or VDG snapshot .................................................... 224 Renaming snapshots or VDG snapshots ............................................................................... 225 Deleting snapshots or VDG snapshots ................................................................................. 225 Working with VSS snapshots and PiTs .......................................................................................
Creating asynchronous mirror groups on VDGs .............................................................. 270 Working with user PiTs ...................................................................................................... 273 Creating user PiTs ...................................................................................................... 273 Releasing user PiTs .....................................................................................................
Creating subfolders .......................................................................................................... Renaming folders ............................................................................................................. Moving folders ................................................................................................................. Deleting folders ................................................................................................................
Deleting user groups ......................................................................................................... Configuring security permissions for entities ................................................................................ Adding users or user groups to entities ................................................................................ Changing security permissions for entities ............................................................................
Index ...............................................................................................
Figures 1 The VSM client window ........................................................................................... 26 2 VSM client window elements .................................................................................... 28 3 Display area elements ............................................................................................. 31 4 Format Columns of: dialog box .................................................................................
33 Set Preferred Path wizard—Select Preferred Path screen .............................................. 154 34 HBAs list .............................................................................................................. 160 35 Replace wizard—Select DPM screen ........................................................................ 179 36 Create DPM Group wizard—DPM Group parameters screen ....................................... 187 37 Create DPM Group wizard—Select DPM(s) screen ...............
69 The Maintenance dialog box .................................................................................. 360 70 The Manage Multi Domain Access Path dialog box ................................................... 364 71 Manage limits definition dialog box ........................................................................
Tables 1 Document conventions ............................................................................................. 22 2 Menu options ......................................................................................................... 28 3 Toolbar icons ......................................................................................................... 29 4 Data presentation settings ........................................................................................
33 Stripe set Disabled Operations tab fields .................................................................... 76 34 Storage Pool properties ............................................................................................ 86 35 Storage pool Back-End tab fields ............................................................................... 87 36 Storage pool Virtual Disk tab fields ...........................................................................
70 Back-End HBA properties ....................................................................................... 173 71 HBA properties ..................................................................................................... 175 72 DPM virtual disks fields .......................................................................................... 176 73 DPM personality tab fields .....................................................................................
107 Migration group Disabled Operations tab fields ........................................................ 252 108 Async mirror groups properties ............................................................................... 261 109 Async mirror group Async Mirror Task tab field ......................................................... 264 110 Async mirror group Source Domain's PiTs tab fields ...................................................
About this guide This guide describes how to use the Virtualization Services Manager (VSM) client graphical user interface to manage a storage area network (SAN) in which VSM distributed software components have already been installed. This guide includes the use of VSM to allocate storage to servers and the use of VSM services snapshot, snapclone, migration, and mirror.
Document conventions and symbols Table 1 Document conventions Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
Rack stability Rack stability protects personnel and equipment. WARNING! To reduce the risk of personal injury or damage to equipment: • Extend leveling jacks to the floor. • Ensure that the full weight of the rack rests on the leveling jacks. • Install stabilizing feet on the rack. • In multiple-rack installations, fasten racks together securely. • Extend only one rack component at a time. Racks can become unstable if more than one component is extended.
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/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.
1 Getting started In order to run the Virtualization Services Manager (VSM) client, the VSM software must be installed on a computer dedicated as a VSM server. To get started using the VSM client: 1. 2. 3. Launch the VSM client, logging into the SVSP domain you want to manage. See “Launching the VSM client” on page 25 Enter a valid license key, if necessary. For information about license keys, see the HP StorageWorks SAN Virtualization Services Platform administrator guide.
5. If this is the first time you are connecting to a specific VSM server, select Connect to Server and enter the IP address of the VSM server in the Connect to Server field. If this is not the first time you are connecting to a specific VSM server, do either of the following: 6. • Select Connect to Domain and select the SVSP domain name from the dropdown box. • Select Connect to Server, and then select the IP address of the VSM server from the dropdown box.
5. Click Finish. Your password is changed. Reconnecting to a VSM server Once you are running the VSM client, you can connect to a different active VSM server or reconnect to the server to which you were connected. To reconnect to a VSM server: 1. From the File menu, select Connect. The Login screen appears. 2. In the User Name field, enter your user name. 3. In the Password field, enter your password. 4.
Figure 2 VSM client window elements The VSM client window features: • Menu—Provides the following menu options.
Menu item Description Manage license keys. License For more information, see the HP StorageWorks SAN Virtualization Services administrator guide. Maintenance Perform maintenance operations Configure Properties Manage VSM server IP addresses. Help Help Topics Open online help About SVSP Display information about your version of VSM • Toolbar—Provides the following toolbar buttons: Table 3 Toolbar icons Menu item Description Standard Navigate backward through the recently displayed screens.
Menu item Description Detach an asynchronous mirror group or task. Split an asynchronous mirror group. Help Open the online help. Display information about your version of VSM. • Location area—Displays the name of the local domain and the currently active VSM server. • Navigation tree—An expandable and collapsible tree of manageable objects. You use the tree to navigate to an object that you want to manage. • Display area—The display area displays information related to the node selected in the tree.
Using the display area Figure 3 shows the appearance of the display area when you select a node in the tree to which objects belong. Figure 3 Display area elements The display area features: • Action menu—Provides access to the operations that can be performed on any of the listed objects. • List area—Displays a list of the objects that belong to the selected node. • Tabs area—Displays detailed information about the object selected in the list.
• Double-click an object to display detailed information about the object in the tabs area. The name of the object you double-clicked now appears at the top left of the tabs area, and the tabs displayed are now specific to that object. Changing the number of objects per page To change the number of objects per page: From the Number of objects per page dropdown box, select the number of objects you want to display per page. The number of objects displayed per page is changed.
2. Right-click any column heading. The “Format Columns of:” dialog box appears. Figure 4 Format Columns of: dialog box 3. Do any of the following: 4. Control which fields are displayed by checking or unchecking Visible for each available field. Edit a field label by double-clicking the Label text and overwriting. Change the width of a column by double-clicking the Width (in pixels) value and overwriting. Right-align a field label by checking Align to right.
Printing and saving You can print the contents of the display area or save them to a text file. • To print the contents of the display area, select File > Print. • To save the contents of the display area to a text file, select File > Save to file. Customizing the user interface The following aspects of the user interface are configurable: • Data presentation—The way data is presented. • Appearance — The general look and feel and the layout of the tabs in the tabs list.
Setting Description Show VSS Views Check to include VSS generated snapshots and PiTs when the snapshots list or a list of PiTs is displayed. Capacity presentation Display capacity in From the dropdown box, select the measurement units in which you want VSM to display storage capacity. Decimal places From the dropdown box, select the number of decimal places you want to be displayed when storage capacity is displayed.
3. Change any of the settings, as required. Table 5 describes the settings. Table 5 Appearance settings Setting Description Change Time Zone From the dropdown box, select a location that has the time zone you want. Tab appearance Tab placement From the dropdown box, select the position in which you want the tabs to appear in the tabs area. Tab layout From the dropdown box, select a layout with which to display the tabs in the tabs area.
2. Select the Configuration tab. The configuration options appear.
3. Change any of the settings, as required. Table 6 describes the settings. Table 6 Configuration settings Setting Description Turn on VSM services alerts Enables alerts for cases in which the number of mirror PiTs on the group source element exceeds the expected limits. SAN API Virtual Disk Size The size (MB) of the SAN API virtual disk. This size is independent of the original size of any physical storage component or any logical unit (LU) exposed by any storage system on the SAN.
From the Tools menu, select Configure Properties. The VSM Properties dialog box appears. The VSM Properties dialog box displays the following information. Table 7 VSM properties fields Property Description Web Server IP The IP address of a VSM server. Port The TCP port used to send and receive information to and from the VSM server. Default: 8004. Is secure Indicates if the connection to the VSM server is a secure HTTP (HTTPS) connection by default. Otherwise, the connection is an HTTP connection.
Getting started
2 Allowed operations This chapter provides you with a matrix that shows which operations can be performed using an existing task from the VSM GUI. In Table 8, a “Y” means the operation is allowed, and an “N” means the operation is not allowed. A leg used in context with sync mirrors is defined as a single sync mirror task. The term thick virtual disk is used to denote a virtual disk that is fully allocated or not thin provisioned (a standard virtual disk).
Table 8 SVSP allowed-operations matrix Allowed to create: Start with: Vdisk Snapshot: create PiT Snapshot: create snapshot Snapclone Migrate Sync Mirror Async Mirror VSS Thick Y Y Y Y Y Y Y Thin Y Y Y Y N Y Y VDG Y Y Y Y N Y Y Vdisk with PiT Y Y Y Y N Y Y Vdisk with snapshot Y Y Y Y N Y Y VDG with PiT Y Y Y Y N Y Y VDG with snapshot Y Y Y N N Y Y On Vdisk Y1 Y N N N Y Y On snapshot Y Y N N N Y N On VDG Y Y N N N Y Y On
3 Working with SVSP domains A SAN Virtualization Services Platform (SVSP) domain is a collection that consists of: • • • • VSM servers. An SVSP domain has two VSM servers to manage the back-end LUs in the domain. Data Path Modules (DPMs). DPM groups Back-end LUs. Every back-end LU under VSM management belongs to a specific SVSP domain and is managed only by the active VSM server of the domain.
Figure 6 The SVSP domains list The following properties are displayed, by default, for each SVSP domain. Table 9 SVSP domain properties Property Description No The row number. Name The name of the SVSP domain that you are managing appears in the VSM client title bar. The current state of communication between the SVSP domain and the active VSM server of the local domain.
Property Description The type of connection over which the SVSP domain is recognized by the local domain. Possible values: • Local—The SVSP domain is the local domain (the domain to which you are currently connected for management). Connection Type • FC—All VSM servers in the SVSP domain are recognized over a Fibre Channel connection by all VSM servers in the local domain. • iSCSI—All VSM servers in the SVSP domain are recognized over an iSCSI connection by all VSM servers in the local domain.
Domain information—VSM tab The VSM tab displays the VSM servers that comprise the selected domain. Table 10 Domain VSM tab fields Property Description No The row number. Name The name of a VSM server in the domain. The state of the VSM server. Possible values: • Active—The VSM server is actively managing the domain. • Passive—The VSM server is not actively managing the domain. It is standing by ready to become active if the current active VSM server fails.
Property Description No. of Tasks The number of data moving tasks currently being handled by the VSM server. This enables you to see the distribution of tasks between the two VSM servers in the local domain. The information is only available for the local domain (the domain to which you are connected). No. of Virtual Disks in Tasks The total number of virtual disks in data moving tasks. If a task is performed on a VDG, for example, the task performs the data movement for all members of the VDG.
Property name Description No. of Data Movers HP StorageWorks VSM does not support the use of data movers. This number should always be zero. LUNs No. of LUNs The number of LUNs under the management of the domain. Lists of storage devices types The types of storage systems managed in the domain. Hosts No. of Hosts The total number of hosts exposed to the domain. This includes the VSM servers of the local domain. List of OSs The operating systems running on hosts connected to the domain. HBAs No.
Domain information—Remote Pool tab The Remote Pool tab displays status and capacity information for the storage pools on the selected domain. You can use this tab, for example, to check if you have enough free capacity on a remote domain to mirror a virtual disk. Table 13 Domain Remote tab fields Display field Description No The row number. Name The name of the storage pool. The status of the storage pool. Possible values: • Normal—All of the storage pool members are present and accessible.
Working with SVSP domains
4 Working with VSM servers A VSM server performs both management and data moving tasks. You can: • View the VSM server list per domain (view the VSM server that comprise the local domain and each of the domains exposed to the local domain) • View VSM server information (view information about each VSM server) • Delete VSM servers (delete physically absent VSM servers that will not be reconnected) Viewing the VSM server list per domain You can view a list of the VSM servers that comprise each domain.
Property Description The type of connection over which the remote VSM server is recognized by the local VSM servers in the local domain. If the VSM server belongs to the local domain, this is the type of connection over which the other VSM servers in the domain recognize the VSM server. Possible values: Connection Type • FC—The remote VSM server is recognized by the local VSM servers in the local domain over an FC connection.
3. Select a VSM server from the list. The following tabs are displayed: • Properties—Displays the VSM server properties described in Table 15. • DM Task—Displays the tasks currently being performed by the VSM server. • DM Source—Displays the virtual disks, VDGs, and snapshots that are sources of data moving tasks in the domain. • Disabled Operations—Shows which operations you cannot currently perform on the VSM server and the reason for each.
Property Description Name The name of a source, which may be a virtual disk, VDG, snapshot, or VDG snapshot on which the selected VSM is currently running a data moving task. The status of the virtual disk, VDG, snapshot, or VDG snapshot that is the source of a data mover task. Possible values: • Normal—All back-end LUs on which the virtual disk, VDG, snapshot, or VDG snapshot is mapped are present and accessible.
5 Working with back-end LUs Virtualization Services Manager (VSM) detects all back-end logical units (LUs) that the SAN presents to the VSM server. The VSM client can display all LUs with capacity greater than 100 MB as back-end LUs. NOTE: The HP Enterprise Virtual Array only builds LUs of 1 GB or greater. In order to manage back-end LUs under VSM, you must first place them in a storage pool.
2. Click the Back-End LU node. The Back-End LUs list appears in the list area. The following properties are displayed for each back-end LU. Table 19 Back–End LU properties Property Description No The row number. The name of the back-end LU. If the back-end LU is presented to the VSM server through an FC fabric switch, the name is the world wide port name (WWPN) of a storage system that is exposing the back-end LU, concatenated with the LUN.
Property Description Vendor The vendor of the physical storage system exposing the back-end LU. Model The model of the physical storage system exposing the back-end LU. Capacity The storage capacity on the back-end LU available for allocation. Signature The signature written to the back-end LU by the VSM server when the back-end LU is configured as a storage pool member.
• Security—Shows which permissions are assigned to users and user groups for managing the backend LU. • Disabled Operations—Shows which operations you cannot currently perform on the back-end LU and the reason for each. These tabs are described in the following sections. Back-end LU information—Storage Pool tab If the selected back-end LU is a member of a pool, the Pool tab displays the properties of the pool to which the back-end LU belongs. If no pool is listed, the back-end LU is not a member of a pool.
Display field Description The status of the stripe set. Possible values: • Normal—All of the back-end LUs in the stripe set are present and accessible. • Partial—At least one of the back-end LUs in the stripe set is either absent or inaccessible. • Absent—All back-end LUs in the stripe set are either absent or inaccessible. Status NOTE: Even if the VSM status of the stripe set is partial or absent, there is a possibility that data stored across the stripe set is still accessible to hosts.
Property Description The state of the virtual disk. Possible values: • Create—The active VSM server is creating the virtual disk. The VSM server allocates the required capacity from the selected storage pools and updates the setup database. • Normal—The virtual disk is in a normal operational state. • Delete—The virtual disk is being deleted. The VSM server marks the virtual disk for deletion and waits for an acknowledgement from all the hosts that use it.
Back-end LU information—Back-End LU Segment tab The Back-End LU Segment tab shows the mappings of virtual disks to segments of the selected back-end LU. Each line represents a back-end LU segment. Table 23 Back-End LU Segment tab Property Description No The row number. Virtual Disk The name of a virtual disk mapped to a segment of the selected back-end LU. If no name appears, the segment is empty.
Property Description Target ID An ID that the HBA on the VSM server assigns to each storage system controller port. Windows reports the target ID on back-end LU properties. The target ID, together with the path ID, identifies the back-end LU. Port Number The SCSI port number assigned to the HBA on the VSM server by Windows. Each HBA has a different port number. LUN The logical unit number with which the back-end LU is presented by the controller.
Display field Description The type of access permitted to the user or user group. Possible values: • Full—The user or user group has permission to modify the back-end LU configuration. • Modify—The user or user group has permission to modify the back-end LU configuration. For back-end LUs, there is no difference in access permissions between Full and Modify. Permission • Read—The user or user group has permission to view back-end LU information but not to modify back-end LU configuration.
• Displaces some data to the backup space and writes a VSM signature to the back-end LU. • Configures the imported back-end LU as a member of the same specified storage pool. • Imports the data to a new, fully manageable, standard VSM virtual disk with a specified name. Use the host’s operating system with VSM for a complete import procedure, including all the tasks you need to perform on the host side.
8. Click Add. The storage pool you selected appears in the list in the lower right area of the screen. If you want to change your selection, select the storage pool in the lower list, click Remove, and add another storage pool. 9. Click Next. A confirmation screen appears. The confirmation screen describes the operation that will be performed if you proceed. 10. Check the details on the confirmation screen.
2. Select Manage > Resume Import-in-Place. A confirmation screen appears, describing the operation that will be performed if you proceed. 3. Click Finish. The Import-in-Place is resumed. Performing a failback If a VSM server fails to access a back-end LU through an access path through the storage system’s primary controller, it issues a failover command. The storage system makes the back-end LU available on an alternate (secondary) controller.
2. Select Manage > Rename. The New Name wizard appears. Figure 8 New Name wizard 3. In the New name field, enter the new name for the back-end LU. 4. Click Next. The Confirmation screen appears, describing the name change you are about to perform. 5. If you do not want the name change displayed on the screen, click Back to go back to the previous screen and change the new name. If you want the name change, click Finish. The name of the back-end LU is changed.
Working with back-end LUs
6 Working with stripe sets Striping helps with load distribution, which might improve performance in some cases. With striping, an application can concurrently write data on multiple back-end LUs. Striping is appropriate for applications with predictable, close to uniform input/output (I/O) size. You implement striping by creating a stripe set, or a set of back-end LUs across which data can be striped.
2. Click the Stripe Set node. The stripe sets list appears in the list area. The following properties are displayed for each stripe set. A partial set of properties appears in the list area. The full set of properties appears in the Properties tab. Figure 9 Stripe set properties Table 27 Stripe set properties Property Description Name The name of the stripe set. The status of the stripe set. Possible values: • Normal—All of the back-end LUs in the stripe set are present and accessible.
Property Description Stripe Set Offset The number of sectors on each LUN that are not virtualized by VSM. VSM leaves these sectors free for native operating systems to write data if necessary, without conflicting with VSM virtual disk mappings. Creation Time The time at which the stripe set was created. Created By The user who created the stripe set. Modification Time The last time a user added or removed a back-end LU from the stripe set. Modified By The user who last modified the stripe set.
Display field Description The name of the back-end LU. If the back-end LU is exposed to VSM through an FC fabric switch, the name is the world wide port name (WWPN) of a storage device that is exposing the back-end LU, concatenated with the LUN. Name If the back-end LU is exposed to VSM through an iSCSI fabric switch, the name has no meaning. You may be able to use the management software provided by the storage device vendor to identify each back-end LU, and then rename the back end LU.
Display field Description Modification Time The time of the last modification to the back-end LU configuration in VSM. The modification may be the addition or removal of the back-end LU from a storage pool. Modified By The name of the user who made the last modification to the back-end LU configuration in VSM.
Stripe set information—Virtual Disk tab The Virtual Disk tab displays information about all virtual disks that are mapped to the selected stripe set. A virtual disk is mapped to a stripe set if you add the stripe set to a storage pool and allocate a virtual disk from the storage pool to a host. For information about allocating a virtual disk to a host, see “Managing virtual disk permissions” on page 115. Table 30 Stripe set Virtual Disk tab fields Property Description No The row number.
Property Description Clustered Yes indicates that the virtual disk is defined as a cluster resource. This setting tunes the SVSP system behavior when the virtual disk is permitted to multiple hosts (configured as a resource in a cluster application). For a description of configuring virtual disks for cluster applications, see “Defining virtual disks as clustered” on page 121. Owned by Host Shows which hosts have permission to access the selected virtual disk.
Display field Description LBA Count The number of the LBAs in the stripe set mapped to the virtual disk. Modification Time The time of the last modification of the virtual disk. Modified By The user who last modified the virtual disk. Stripe set information—Security tab The Security tab displays the access permissions of users and user groups for the selected stripe set. For information about configuring permissions, see “Configuring security permissions for entities” on page 337.
Creating stripe sets You can create a new stripe set from back-end LUs with the status present. This status means that the back-end LU is present on the SAN and accessible to VSM and the back-end LU has not been configured as a member of a stripe set or storage pool. The number of back-end LUs per stripe set is limited to 4. A stripe set must be added to a storage pool before you can allocate the stripe set’s capacity to hosts.
6. Click Next. The Select Back-End LU(s) screen appears. Figure 11 Create Stripe Set wizard—Select Back-End LU(s) screen 7. Select a back-end LU that you want to add to the stripe set. Back-end LUs that are already configured, absent, or not accessible are not selectable. 8. Click Add. The selected back-end LU is added to the list in the lower area of the screen. 9. Repeat steps 7 and 8 until the lower list displays all the back-end LUs that you want to include in the stripe set.
1. From the navigation tree, navigate to the back-end LU you want to add to a stripe set. To list all back-end LUs, select the Back-End LU node. To list back-end LUs that you have copied to a folder, navigate to the folder. 2. Right-click the back-end LU. 3. Select Manage > Stripe Set relations > Add to Stripe Set. The Add to Stripe Set wizard opens to the Select Stripe Set screen. Figure 12 Add to Stripe Set wizard—Select Stripe Set screen 4.
3. Select Manage > Back-End LU relations > Add Back-End LU. The Striped Disks wizard opens to the Add Back-End LU screen. Figure 13 Striped Disks wizard—Add Back-End LU screen 4. In the navigation tree on the left of the screen, navigate to the Back-End LU node or to a folder in which you have copied the back-end LU that you want to add to the stripe set. A list of back-end LUs appears. 5. Select the back-end LU you want to add to the stripe set.
1. From the navigation tree, navigate to the back-end LU you want to remove from a stripe set. To list all back-end LUs, select the Back-End LU node. To list back-end LUs that you have copied to a folder, navigate to the folder. 2. Right-click the back-end LU. 3. Select Manage > Stripe Set relations > Remove from Stripe Set. A confirmation screen appears. 4. Click Finish. The back-end LU is removed from the stripe set to which it previously belonged.
Adding stripe sets to storage pools A stripe set must belong to a storage pool before you can allocate virtual disks from the stripe set. A stripe set can belong to one storage pool only. To add a stripe set to a storage pool: 1. From the navigation tree, navigate to the stripe set that you want to add to a storage pool. To list all stripe sets, select the Stripe Sets node. To list stripe sets that you have copied to a folder, navigate to the folder. 2. Right-click the stripe set. 3.
2. Right-click the stripe set. 3. Select Manage > Storage Pool Relations > Remove from Storage Pool. A confirmation screen appears. 4. Click Finish. The stripe set is removed from the storage pool to which it previously belonged. Deleting stripe sets You can delete a stripe set only if it is not a member of a storage pool. To delete a stripe set: 1. From the navigation tree, navigate to the stripe set that you want to delete. To list all stripe sets, select the Stripe Sets node.
Working with stripe sets
7 Working with storage pools A storage pool is a set of back-end LUs from which you can create virtual disks and assign them to hosts. Storage pools enable you to classify storage elements into classes of service and provide different classes of service to different hosts. Your pooling criteria may be storage model, RAID level, performance requirements, physical location, user groups, or any other criteria that suits your requirements.
2. Click the Storage Pool node. The storage pools list appears in the list area. The following properties are displayed for each storage pool. Table 34 Storage Pool properties Property Description No The row number. Name The name of the storage pool. The status of the storage pool. Possible values: • Normal—All of the storage pool members are present and accessible. Status • Partial —At least one of the storage pool members is either absent or inaccessible.
• Virtual Disk—Provides information about each virtual disk that is allocated from the storage pool. • Storage Pool Segment—Shows the mapping of logical block addresses (LBAs) on storage pool members to virtual disks and virtual disk segments. • Security—Shows which permissions are assigned to users and user groups for managing the storage pool. • Disabled Operations—Shows which operations you cannot currently perform on the storage pool, and the reason for each.
Display field Description The status of the back-end LU or stripe set. Possible values for the status of the back-end LU: • Present—VSM recognizes the back-end LU on the SAN. • Absent— VSM does not recognize the back-end LU on the SAN. • Failed— VSM recognizes the back-end LU on the SAN, but cannot access the back-end LU. Status Possible values for the status of the stripe set: • Normal—All back-end LUs in the stripe set are present and accessible.
Property Description The state of the virtual disk. Possible values: • Create—The active VSM server is creating the virtual disk. The VSM server allocates the required capacity from the selected storage pools and updates the setup database. • Normal—The virtual disk is in a normal operational state. • Delete—The virtual disk is being deleted. The VSM server marks the virtual disk for deletion and waits for an acknowledgement from all the hosts that use it.
Storage pool information—Storage Pool Segment tab The Storage Pool Segment tab shows the mapping between logical block addresses (LBAs) on each back-end LU in the storage pool and LBAs on virtual disks and virtual disk segments created from the selected storage pool. The mapping information is displayed in a tabular format. Each line in the table represents a mapping between all or part of a back-end LU and all or part of a virtual disk.
Display field Description The type of access permitted to the user or user group. Possible values: • Full—The user or user group has permission to modify and delete the storage pool. • Modify—The user or user group has permission to modify but not to delete the storage pool. Permission • Read—The user or user group has permission to view storage pool information but not to modify or delete the storage pool. • None—The user or user group does not have permission to access the storage pool.
3. Select New. The Create Storage Pool wizard opens to the Enter storage pool parameters screen. Figure 16 Create Storage Pool wizard—Enter Storage Pool parameters screen 4. 5. In the Storage Pool name field, enter a name for the storage pool. The following naming conventions are suggested: • Pools—Create a name that identifies the array, disk type, and VRAID level (for example, EVA8000_FC_RAID5).
14. Click Next. The Select folder screen appears. 15. If you want to add the storage pool to a folder, enter the folder name in the Folder field or click Browse to browse to the folder. The folder must already be created. For information about creating folders, see “Creating folders” on page 305. 16. Click Next. A confirmation screen appears. 17. Click Finish. The new storage pool is created and is displayed in the storage pools list.
3. Select Manage > Expand. The Expand wizard opens to the Select Back-End LU(s) screen and displays the list of available back-end LUs. Figure 17 Expand wizard—Select Back-End LU(s) screen 4. If you do not want to add a back-end LU to the storage pool, skip to step 9. 5. If you would like to select a back-end LU from a folder, navigate to the folder in the tree on the left of the screen. The Select Back-End LU(s) screen displays the list of back-end LUs in the selected folder. 6.
1. Right-click the back-end LU. 2. Select Manage > Storage Pool relations > Remove from Storage Pool. The Remove from Storage Pool wizard opens to a confirmation screen. 3. Click Finish. The back-end LU is removed from the storage pool to which it belonged. To remove a single stripe set from a storage pool: 1. Right-click the stripe set. 2. Select Delete. The stripe set is removed from the storage pool to which it belonged.
Changing storage pool free capacity alert threshold If the free capacity of a storage pool drops below a configurable percentage of the total capacity, a notification is sent to any notification groups configured to receive this type of alert. For information about configuring notification groups, see “Configuring event log notifications” on page 355. The alert threshold is configurable for each storage pool, and is displayed for each storage pool in the storage pools list.
NOTE: Disk allocation includes snapshots and snapclones, as well as virtual disks. To delete a storage pool: 1. From the navigation tree, navigate to the storage pool you want to delete. To display all storage pools, select the Storage Pool node. To display storage pools that you have copied to a folder, navigate to the folder. 2. Right-click the storage pool. 3. Select Delete. A confirmation screen appears. 4. Click Finish. The storage pool is deleted.
Working with storage pools
8 Working with virtual disks A virtual disk is disk capacity allocated from one or more storage pools to one or more hosts. To create a standard virtual disk, you need at least one storage pool with available free capacity. Cluster virtual disks are created as standard virtual disks and then defined as clustered. For a description of creating SAN API virtual disks, see “Creating the setup virtual disk” on page 361.
Property Description The status of the virtual disk. Possible values: • Normal—The initialization phase was completed and all the back-end LU(s) onto which the virtual disk is mapped is/are present (accessible). Status • Partial—The back-end LU(s) onto which the virtual disk is mapped is/are missing. The state of the virtual disk. Possible values: • Create—The active VSM server is creating the virtual disk.
Property Description Application Type The application associated with the virtual disk. For information about adding application types and associating them with virtual disks, see “Adding applications to virtual disks” on page 122. Yes indicates that the virtual disk is a thin provisioned virtual disk type. Is Thin Provision No indicates that the virtual disk is not a thin provisioned virtual disk type. SAN API Virtual Disk This setting indicates whether the virtual disk is a SAN API virtual disk.
Virtual disk information—Storage Pool tab The Storage Pool tab provides information about the storage pool(s) from which the virtual disk capacity is allocated. Table 41 Virtual disk Storage Pool tab fields Property Description No The row number. Name The name of the storage pool. The status of the storage pool. Possible values: • Normal—All of the storage pool members are present and accessible. Status • Partial—At least one of the storage pool members is either absent or inaccessible.
Virtual disk information—PiT tab The PiT tab provides information about any snapshot PiTs created for the selected virtual disk. For more information about PiTs, see “Working with PiTs” on page 194. Table 42 Virtual disk PiT tab fields Property Description No The row number. Name The name of a PiT. The status of the PiT. • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal.
Property Description Capacity The size of the temporary virtual disk which holds the modifications made on the PiT. This field shows you how much capacity from the storage pool is used by the PiT. Comment A free text display field. Is Mirror User PiT Indicates if the PiT is used with an asynchronous remote mirror PiT created by the user. For information about asynchronous mirror PiTs, see “Asynchronous mirroring” on page 259.
Property Description The status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host. However, the host is polling properly through at least one HBA.
Property Description The status of the DPM. Possible values: • —Present status. The DPM is recognized and communicating properly with the active VSM server. The VSM agent on passive VSM servers and fabric agents on DPMs are polling to the active VSM server through all HBAs as expected. • —Failed status. The DPM is recognized on the SAN but not communicating with the active VSM server. The agent running on the DPM stopped polling to the active VSM. • —Degraded status.
Property Description Device Start LBA The first LBA of the back-end LU on which the virtual disk segment is allocated to which the virtual disk is mapped. Modification Time The time at which the segment was last modified. Modified By The user who last performed an operation that modified the segment. Virtual disk information—User Quota tab The User Quota tab provides information about the users whose quotas are used by the selected virtual disk.
Virtual disk information—Virtual Disk Copy tab The Virtual Disk Copy tab displays information about all virtual disks which are related to the selected virtual disk. Table 48 Virtual disk Virtual Disk Copy tab fields Property Description No The row number. Virtual Disk Name The name of the related virtual disk. Is Source Whether the related virtual disk is the source of the selected virtual disk. Task Domain The name of the destination domain for the task.
Figure 20 Hierarchy tab The following are represented in the hierarchy: • The selected virtual disk—This is displayed even if no snapshot PiTs or snapshots are associated with the virtual disk. • PiTs associated with the virtual disk—A PiT created directly on the virtual disk appears as a child node of the virtual disk. A PiT created on a snapshot appears as a child node of the snapshot.
1. In the navigation tree, expand the Entities node. 2. Right-click the Virtual Disk node. 3. Select New. The Create Virtual Disk wizard opens to the Enter Virtual Disk parameters screen. Figure 21 Create Virtual Disk wizard—Enter Virtual Disk parameters screen 4. In the Virtual Disk name field, enter a unique name for the virtual disk. 5. From the “Set permission to Host with” dropdown box, select one of the following: 6.
9. Click Next. The Select Storage Pool(s) screen appears, displaying the list of available storage pools. Figure 22 Create Virtual Disk wizard—Select Storage Pool(s) screen 10. If you would like to select a storage pool from a folder, navigate to the folder in the tree on the left of the screen. The Select Storage Pool(s) screen displays the list of storage pools in the selected folder. 11. Select a storage pool from which you want to allocate capacity to the virtual disk.
16. Click Next. If you selected Set permission later in step 5, skip to step 28. If you selected VSM Server or UDH in step 5, the Select host(s) screen appears, displaying the list of available hosts. Figure 23 Create Virtual Disk wizard—Select Host(s) screen 17. If you would like to select a host from a folder, navigate to the folder in the tree on the left side of the screen. The Select Host(s) screen displays the list of hosts that have been copied to the selected folder. 18.
23. Select the LUN through which you want VSM to expose the virtual disk. You may use the Next free LUN option or specify a number. This must be a unique LUN for each host that will be accessing the virtual disk. 24. Click Next. The Select DPM Group screen appears. The upper area of the screen displays the DPM groups through which the host is recognized. Figure 24 Create Virtual Disk wizard—Select DPM Group screen 25. Select a DPM group and click Add.
26. Click Next. The Select preferred path screen appears. Figure 25 Create Virtual Disk wizard—Select preferred path screen 27. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. NOTE: • Use care in selecting the primary and secondary DPMs to prevent over subscribing one and under utilizing the other. • If you click Finish without defining the primary and secondary DPMs, VSM defines these roles automatically. 28. Click Next. The Select folder screen appears. 29.
Expanding virtual disks You may need to expand a virtual disk if the host application using the virtual disk is running low on virtual disk capacity. When you expand a virtual disk, you can allocate the additional storage capacity from any storage pool(s) that has/have enough free capacity. NOTE: Because the segments come from different sources and are concatenated together, the performance characteristics of the segments may vary.
• Remove Host Permission—You can remove permission from a host that currently has permission to access the virtual disk. • Change LUN—If a virtual disk is set to allow permission only to UDH hosts, you can change the LUN that the DPM uses to expose the virtual disk to the host. These options are not available for a virtual disk that belongs to a virtual disk group or that has components associated with it that were created by VSM services, such as the snapshot service.
2. Click the Virtual Disk node. The virtual disks list appears in the list area. 3. Right-click the virtual disk to which you want to add host permission. 4. Select Manage > Manage Permission > Add Host Permission. The Add Permission wizard opens to the Select type of host screen. 5. From the “Set permission to host with” drop-down list, select one of the following: 6. • UDH—Select this value to assign virtual disk permission to UDHs.
13. Click Next. The Select DPM Group screen appears. 14. In the upper area of the screen, select a DPM group and click Add. The DPM group you selected is displayed in the lower area of the screen. 15. Click Next. The Select preferred path screen appears. 16. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. NOTE: • Use care in selecting the primary and secondary DPMs to prevent over subscribing one and under utilizing the other.
4. Select Manage > Manage Permission > Change Host Permission. The Change Host Permission wizard opens to the Select host(s) screen. 5. Select a host whose permission you want to change. 6. Click Add. The host you selected appears in the lower area of the screen. If you want to deselect the host, select the host in the lower area, and click Remove. 7. Click the Permission field for the host. 8. Select one of the following from the dropdown list: 9.
8. Click Finish. The host permission is removed. Changing the virtual disk LUN If a virtual disk is set to allow permission only to UDH hosts, you can change the LUN that the DPM uses to expose the virtual disk to the host. This option is not available for a virtual disk that belongs to a VDG or that has components associated with it that were created by VSM services, such as the snapshot service.
4. Select Manage > Manage Data Path Module > Change Primary/Secondary Data Path Module. The Change Primary/Secondary Data Path Module/VSM wizard opens to the Set preferred path screen. 5. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. NOTE: • Use care in selecting the primary and secondary DPMs to prevent over subscribing one and under utilizing the other. • If you click Finish without defining the primary and secondary DPMs, VSM defines these roles automatically.
5. Check the Support cluster option. 6. Click Next. A confirmation screen appears. 7. Click Finish. The virtual disk is defined as clustered. Adding applications to virtual disks You can associate the type of application using a virtual disk so that the application is displayed with the virtual disk properties in the Application Type display field. NOTE: The application type is a special type of comment and does not imply any changes to the properties of the virtual disk.
2. From the applications list, select the application that you want to add to one or more virtual disk(s). If the application is not listed, add the application to the list as follows: a. Click Add New. The VSM dialog box appears. b. In the Application Type field, enter the application type name that you want to add. c. Click OK. The VSM dialog box closes and the application type you added is added to the applications list. 3.
Working with virtual disks
9 Working with virtual disk groups A virtual disk group (VDG) is an entity that you can create to encapsulate multiple virtual disks into one entity. Every operation that you then perform on the VDG is performed simultaneously on all VDG members.
Property Description The states of the VDG members. Possible values: • Normal—Each virtual disk is in normal operational state. • Delete—Each virtual disk is being deleted. The VSM server marks the virtual disk for deletion and waits for an acknowledgement from all the hosts that use it. Once acknowledged, the VSM server deletes the virtual disk and marks the capacity that it used as free space available for allocation. When the deletion is complete, the virtual disk disappears from the virtual disk list.
VDG information—Members tab The Members tab displays the members of the VDG. Members can be virtual disks or snapshots. Table 51 VDG Members tab fields Property Description No The row number. Name The name of a member of the selected VDG. The icon next to the name indicates whether the member is a virtual disk or a snapshot. The status of the virtual disk or snapshot. Possible values: • Normal—The back-end LU(s) for the mapped virtual disk is/are present (accessible).
Property Description The status of the PiT. Possible values: • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal. This includes an original virtual disk, the temporary virtual disk created for the PiT, and any PiTs and snapshots between the original virtual disk and the PiT in the hierarchy. Status • Partial—The status of one of the virtual disks from which the PiT is constructed is partial. The current state of the PiT.
VDG information—Host Presentation tab The Host Presentation tab displays the hosts that have permission to access the VDG or members of the VDG. Permissions to VSM servers must be identical for all members of the VDG. A VDG member may be presented to a UDH without other members being presented to that host. Table 53 VDG Host Presentation tab fields Property Description A host with permission to access the VDG.
Property Description The current status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host.
Property Description Primary This indicates whether the DPM is configured as the primary DPM for presenting the VDG members to hosts. Active Indicates whether the DPM is currently active in presenting the VDG members to a host. VDG information—Security tab The Security tab displays the access permissions of users and user groups for the selected VDG. For information about configuring permissions, see“Configuring security permissions for entities” on page 337.
Figure 27 Hierarch tab VDG information—Disabled Operations tab The Disabled Operations tab shows which operations you cannot currently perform on the selected VDG and the reason for each. See the release notes for a current list of disabled operations. Table 56 VDG Disabled Operations tab fields Display field Description Operation name The name of an operation that is disabled. Reason The reason why the operation is disabled.
• A virtual disk that has a snapshot PiT. NOTE: You can add a virtual disk that has no PiTs to a VDG that has PiTs. • • • • • A temporary virtual disk. A setup virtual disk. A virtual disk in the process of failing over or failing back from one DPM to another. A snapshot of another VDG. A virtual disk or snapshot that is defined as clustered if the VDG has host presentations and the VDG is defined as not clustered.
16. If you want to add the VDG to a folder, enter the folder name in the Folder field or click Browse to browse to the folder. The folder must already be created. For information about creating folders, see “Creating folders” on page 305. 17. Click Next. A confirmation screen appears. 18. Click Finish. The VDG is created. Adding members to virtual disk groups You can add new members to a VDG after the VDG is created.
Adding any combination of members to a VDG To add members to a VDG: 1. Right-click the VDG to which you want to add members. 2. Select Manage > Add/Remove Members > Add Members. The Add Members wizard opens to the Select Virtual Disk(s) screen, and displays the list of available virtual disks. 3. If you would like to select a virtual disk from a folder, navigate to the folder in the tree on the left of the screen.
2. Select Manage > Add/Remove Members > Remove Members. The Remove Members wizard opens to the Select Virtual Disk(s) screen. 3. If you want to remove a virtual disk from the VDG, select the virtual disk from the upper area of the screen. 4. Click Add. The virtual disk you selected is added to the lower area of the screen. If you want to deselect the virtual disk, select it, and click Remove. 5.
3. From the “Set permission to Host with” drop-down list, select one of the following: 4. • UDH—Select this value to assign permission to UDHs. The wizard enables you to select specific hosts and set related parameters in later screens. • VSM Server—Select this value to assign permission to a VSM server. Click Next. The Select Host(s) screen appears, displaying the list of available hosts. Figure 28 Add Host Permission wizard—Select Host(s) screen 5.
11. Click Next. The Set Select DPM Group screen appears. The upper area of the screen displays the DPM groups through which the host is registered. Figure 29 Add Host Permission wizard—Select DPM Group screen 12. In the upper area of the screen, select a DPM group and click Add. The DPM group you selected is displayed in the lower area of the screen.
13. Click Next. The Select preferred path screen appears. Figure 30 Add Host Permission wizard—Select preferred path screen 14. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. NOTE: • If another host that is connected to the domain through DPMs already has permission to access the VDG and you configure different primary and secondary settings for the new host, VSM overrides your selection and applies the current settings used by the VDG.
4. Click Add. The host you selected appears in the lower area of the screen. If you want to deselect the host, select the host in the lower area and click Remove. 5. Click the Permission field for the host. 6. Select one of the following from the dropdown list: 7. • Full—Assigns read/write permission to the host. • Read—Assigns read-only permission to the host. • None—Assigns no permission to the host. If required, repeat steps 3 through 6 to change permission for additional hosts. 8. Click Next.
3. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. NOTE: • Use care in selecting the primary and secondary DPMs to prevent over subscribing one and under utilizing the other. • If you click Finish without defining the primary and secondary DPMs, VSM defines these roles automatically. 4. Click Next. A confirmation screen appears. 5. Click Finish. The primary and secondary Data Path Module settings are changed.
2. Select Manage > Set Clustered. The Set Clustered screen appears. 3. Check the Support cluster option. 4. Click Next. A confirmation screen appears. 5. Click Finish. All VDG members are configured for cluster support. Deleting VDGs When you delete a VDG, you can also delete the VDG members at the same time. Deletion of each member is only supported if the deletion operation is not disabled for the member for any reason. To delete a VDG: 1. Right-click the VDG that you want to delete. 2.
10 Working with hosts A host is connected to two DPMs in a DPM group using a dual-fabric SAN. Each host requires operating system specific multipath software to perform the necessary path management. A host that is connected to the fabric through two DPMs requires operating system–specific multipath software, available from HP, to perform path management and, if supported by the multipath driver, load balancing.
• Change preferred path (change the primary path through which virtual disks are presented to a host) • Change LUN range (change the range of LUNs used by the SVSP domain to present virtual disks through a DPM to a host) • Add and remove host HBAs (add HBAs to a host in situations in which the VSM cannot learn automatically that an HBA has been added to the host and remove HBAs from a host to inform VSM that a given HBA is no longer installed on a given host) • Manage host online/offline state (switch a hos
2. Click the Host node. The hosts list appears in the list area. The following properties are displayed for each host. Table 58 Host properties Property Description No The row number. The name of the host, as defined in the host operating system. The icon next to the name reflects the operating system (OS) of the host: Host • —Windows 2003 • —Windows 2008 • —HP-UX 11.23 • —HP-UX 11.31 • —VMWare ESX 3.5 • —Solaris 10 • —AIX 6.
Property Description The current status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host.
Property Description The primary path through which virtual disks are presented to the host. Preferred Path is applicable to hosts with the following agent types: • No Agent (UDH)—For a UDH that is connected to more than one DPM and running multipath software, the preferred path specifies a primary DPM for presenting all assigned virtual disks to the host. • No Agent (HBA)—The host entity was created by the VSM server to represent an HBA that is not registered as belonging to a host.
Viewing host information You can display detailed information related to each host in the tabs area below the hosts list. To view information related to a host: In the hosts list, select a host. The following tabs are displayed in the tabs area below the hosts list: • Properties—Provides the general information about the selected host described in Table 58 on page 145. • HBA—Provides information about the HBAs through which the host is connected to the SAN.
Property Description Vendor The vendor of the HBA. The status of the HBA. Possible values: • Present—For VSM server hosts, this indicates that the host is polling to the VSM server through this HBA, as expected. For other hosts, this indicates that the DPMs recognize this HBA on the fabric and that the HBA is active. • Failed— For a VSM server host, this means that the HBA is recognized on the fabric but the host is not polling through the HBA to the VSM server.
Display field Description An icon representing a VSM storage element assigned to the host. Possible values: • • Type —A virtual disk. —A VDG. • —A snapshot. • —A VDG snapshot. • —A synchronous mirror group. Name The name of the VSM storage element. Status The status of the VSM storage element. Clustered Yes indicates that the virtual disk or VDG is defined as a cluster resource.
Display field Description An icon indicating either a user or user group. Possible values: Type Name • —A user. • —A user group. The name of the user or user group. The type of access permitted to the user or user group. Possible values: • Full—The user or user group has permission to modify and delete the host. • Modify—The user or user group has permission to modify the host but not to delete the host.
7. Click Next. The Select HBA(s) screen appears, displaying the list of available HBAs. Figure 31 Create UDH wizard—Select HBA(s) screen 8. If you would like to select an HBA from a folder, navigate to the folder in the tree on the left of the screen. The Select HBA(s) screen displays the list of HBAs that have been copied to the selected folder. 9. Select one of the HBAs you want to add to the host. HBAs that already belong to other hosts are not selectable. 10. Click Add.
20. Click Finish. The UDH is created with the parameters you provided, and appears in the hosts list. Changing the UDH operating system or personality You can change the operating system or personality of a UDH. To change the operating system or personality of a host: 1. Right-click the host. 2. Select Manage > Change Features. The Edit Host Parameters screen appears. 3. To change the operating system, select the host’s operating system in the OS type dropdown box. 4.
2. Select Manage > Manage Preferred Path > Set Preferred Path. The Set preferred path wizard opens to the Select DPM Group screen. Figure 32 Set Preferred Path wizard—Select DPM Group screen Since the host is recognized through DPMs, the Set Preferred Path screen enables you to select the preferred DPM group for the host. 3. Select a DPM group and click Add. The DPM group that you selected is displayed in the lower area of the screen. 4. Click Next. The Select preferred path screen appears.
Removing the path preference Removing the path preference for the host specifies that VSM distributes virtual disks evenly between DPMs for static load balancing. To change the preferred path for a host: 1. Right-click the UDH. 2. Select Manage > Manage Preferred Path > Change Preferred Path. The Remove preferred path wizard appears in the Select DPM Group screen. 3. Click Next. A confirmation screen appears. 4. Click Finish. The preferred path is changed.
CAUTION: Before switching the host to the offline state and performing operations on the VSM elements (virtual disks, VDGs, and snapshots) that belong to the host, shut down the host or disconnect the host from the SAN. If you do not shut down or disconnect the host, the host may attempt to write to the virtual disk at the same time that VSM makes changes to the virtual disk structure (deletes a PiT, deallocates a temporary virtual disk, and so on), which may cause data corruption.
you know that you do not intend to reconnect the host that was removed. When a host is deleted, the permissions that the host had to access VSM storage elements are removed. To delete a host: 1. Right-click the host. 2. Select Delete. A confirmation screen appears. 3. Click Finish. The host is deleted.
Working with hosts
11 Managing host bus adapters Each VSM server detects the host bus adapters (HBAs) installed on itself and the HBAs reported by the DPMs on the SAN. When more than one node (DPM or VSM) reports the same HBA to the VSM server, the VSM server has more than one access path to the HBA. When a user creates a user-defined host (UDH) and adds the HBA to the UDH, the VSM server learns that the HBA belongs to the UDH.
2. Click the HBA node. The HBAs list appears in the list area. Figure 34 HBAs list The following properties are displayed for each HBA. Table 64 HBA properties Property Description The World Wide Port Name (WWPN) of the HBA, as detected by the VSM when the HBA is connected to the SAN fabric. The icon next to the name reflects the status of the HBA and the number of access paths through which VSM can access the HBA: Name • —The HBA has a single access path and present status.
Property Description The status of the HBA. Possible values: • Present—The VSM server detects the HBA on the SAN. • Failed—The HBA is recognized over Fibe Channel (FC) or iSCSI but the HBA didn't poll to the VSM server within the last three minutes (or more). Status • Absent—The HBA was previously detected by the VSM server, but is currently not recognized. This could be due to the zoning configuration, the absence of a cable, or the absence of the HBA.
HBA information—Host tab The Host tab displays the properties of the host or DPM to which the selected HBA belongs, if known. The host may be the VSM server to which you are connected. The host is known either if the host registered itself automatically to VSM or if a user added the HBA to a host definition. Table 65 HBA Host tab fields Property Description No The row number. The name of the host or DPM to which the HBA belongs.
Property Description The current status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded— For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host. However, the host is polling properly through at least one HBA.
Property Description The primary path through which virtual disks are presented to the host. Preferred path is applicable to hosts with the following agent types: • No Agent (UDH)—The HP SVSP requires that all UDHs be connected to more than one DPM and running multipath software, therefore, the preferred path specifies a primary DPM for presenting all assigned virtual disks to the host.
HBA information—Access Path tab The Access Path tab describes the connectivity between the VSM server and the HBAs discovered by the VSM server. The Access Path tab displays the following connections, depending on the HBA: • For an FC HBA on a UDH, the Access Path tab shows the DPMs that recognize the HBA and report it to the VSM server.
HBA information—Security tab The Security tab displays the access permissions of users and user groups for the selected HBA. For information about configuring permissions, see “Configuring security permissions for entities” on page 337. Table 67 HBA Security tab fields Display field Description No The row number. An icon indicating either a user or user group. Possible values: Type Name • —A user. • —A user group. The name of the user or user group.
Adding HBAs to a host by right-clicking the host This procedure adds one or more HBAs to a UDH host. To add HBAs to a host: 1. Right-click the host. 2. Select Manage > HBA relations > Add HBA(s). The Add HBA(s) wizard opens to the Select HBA(s) screen. 3. Navigate to the HBA node or to a folder in which you have copied an HBA that you want to add to the host. A list of HBAs appears in the upper right area of the screen. 4. Select the HBA that you want to add to the host.
Removing HBAs from hosts Removing an HBA from a host informs VSM that a given HBA is no longer installed on a given host. Removing HBAs from hosts is supported for UDH hosts. Removing an HBA from a UDH is the only way to inform VSM that a given HBA is no longer installed on the UDH. CAUTION: Removing HBAs from hosts is supported independently of HBA status. If you remove an HBA from a host, DPM stops presenting virtual disks assigned to the host through the HBA you removed.
Deleting HBAs When an HBA is physically removed from the SAN, VSM detects the removal and changes the HBAs status to absent ( ). VSM enables you to delete HBAs if they are absent. You would normally do this if you know that you do not intend to replace the HBA that was removed. If a host has more than one HBA, and one of the HBAs moves into absent status, the host’s status is changed from present to degraded (indicated by in the top right corner of the host icon).
Managing host bus adapters
12 Working with Data Path Modules A Data Path Module (DPM) is a device deployed in a split-path architecture that is responsible for the data flow between the host application and the storage systems. The DPM is both a SCSI target that presents virtual disks to the hosts and a SCSI initiator for routing all I/O from the virtual disks to their physical destinations. A VSM fabric agent running on the DPM is responsible for getting metadata from the VSM and providing it to the DPM.
1. In the navigation tree, expand the Entities node. 2. Click the Data Path Module node. The DPMs list appears in the list area. The following properties are displayed for each DPM. Table 69 DPM properties Property Description No The row number. The name of the DPM. The icon next to the name indicates the status. Name • —Present status. • —Failed status. • —Degraded status. • —Absent status. The current status of the DPM.
Property Description Created By Always displays “system,” since the DPM as an entity is automatically created after being detected by the VSM server. The last time one of the following was last done: Modification Time • The comment was edited. • A back-end HBA was removed from the DPM. • A back-end HBA was added to the DPM. Modified By The user who last modified the DPM entity.
Property Description The World Wide Port Name (WWPN) of a DPM port, as detected by the VSM application upon connection to the SAN fabric. The icon next to the name reflects the status of the HBA and the number of access paths through which VSM can access the HBA: Name • —The HBA is recognized through a single access path and the HBA’s status is Present. • —The HBA is recognized through a single access path and the HBA’s status is Absent.
DPM information—Front End HBA tab The Front End HBA tab displays the host HBAs that are connected to the selected DPM. HBAs installed on hosts are connected to the front-end ports of the DPM and are reported to the VSM server by the fabric agent on the DPM. Table 71 HBA properties Property Description No The row number. The WWPN of the host HBA, as detected by the DPM and reported to VSM by the fabric agent.
DPM information—Virtual Disks tab The Virtual Disks tab displays the virtual disks, snapshots, virtual disk groups, and VDG snapshots that are presented to hosts by the selected DPM. Table 72 DPM virtual disks fields Display field Description No The row number. An icon representing the type of a VSM storage element exposed by the selected DPM. Possible icons: • • Type —A virtual disk. —A virtual disk group. • —A snapshot. • —A VDG snapshot. • —A synchronous mirror group.
DPM information—Security tab The Security tab displays the access permissions of users and user groups for the selected DPM. For information about configuring permissions, see “Configuring security permissions for entities” on page 337. Table 74 DPM Security tab fields Display field Description No The row number. An icon indicating either a user or user group. Possible values: Type Name • —A user. • —A user group. The name of the user or user group.
3. Right-click the DPM whose storage elements you want to failover. 4. Select Manage > Failover all. A confirmation screen appears. 5. Click Finish. NOTE: There may be a performance impact if all virtual disks are presented through only one DPM. Failing back virtual disks from a DPM After a failover, you can attempt to switch back the storage elements from their secondary DPMs to their primary DPMs. You can do this using the “Failback all” operation.
4. Select Manage > Replace. The Replace wizard opens to the Select DPM screen. The upper area of the screen displays the available DPMs. Figure 35 Replace wizard—Select DPM screen 5. Select a DPM and click Add. The DPM you selected is displayed in the lower area of the screen. 6. Click Next. A confirmation screen appears. 7. Click Finish. The new DPM group is created and is displayed in the DPM groups list.
Working with Data Path Modules
13 Working with DPM groups Each Data Path Module (DPM) group contains one primary and one secondary DPM.
Property Description The current status of the DPM group. Possible values: • Present—For both DPMs in the DPM group, the fabric agent is polling to the VSM server through all back-end HBAs, as expected. The VSM server and the fabric agent are communicating properly. • Degraded—One of the DPMs in the DPM group is present, and one DPM is absent or has failed. Status • Failed— For both DPMs in the DPM group, polling of the fabric agent to the VSM server has stopped.
• Disabled Operations—Shows which operations you cannot currently perform on the selected DPM group and the reason for each. See the release notes for a current list of disabled operations. These tabs are described in the following sections. DPM group information—DPM tab The DPM tab displays information about each DPM in the selected DPM group. Table 77 DPM group DPM tab fields Property Description No The row number. Name The name of the user or user group. The current status of the DPM.
DPM group information—Host tab The Host tab displays information about each host to which the DPM group exposes objects. Table 78 DPM groups Host tab fields Property Description No The row number. The name of the host or DPM to which the HBA belongs. If the HBA belongs to a host, the icon next to the name reflects the operating system (OS) of the host: • Name —Windows 2003 • —Windows 2008 • —HP-UX 11.23 • —HP-UX 11.31 • —VMWare ESX 3.5 • —Solaris 10 • —AIX 6.
Property Description The current status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host. However, the host is polling properly through at least one HBA.
DPM group information—Virtual disk tab The Virtual Disk tab displays information about each VSM storage element that the selected DPM group exposes to a host, including virtual disks. Table 79 DPM groups Virtual Disk tab fields Property Description No The row number. The type of VSM storage element. Possible values: • Type —A virtual disk. • —A VDG. • —A snapshot. • —A VDG snapshot. • —A synchronous mirror group. Name The name of the VSM storage element.
DPM group information—Disabled Operations tab The Disabled Operations tab shows which operations you cannot currently perform on the selected DPM group and the reason for each. See the release notes for a current list of disabled operations. Table 81 DPM group Disabled Operations tab fields Display field Description Operation name The name of an operation that is disabled. Reason The reason why the operation is disabled. Creating DPM groups To create a DPM group: 1.
6. Click Next. The Select DPM(s) screen appears. The upper area of the screen displays the available DPMs. Figure 37 Create DPM Group wizard—Select DPM(s) screen 7. Select a DPM and click Add. The DPM you selected is displayed in the lower area of the screen. Repeat this to add a second DPM to the DPM group. 8. Click Next. A confirmation screen appears. 9. Click Finish. The new DPM group is created and is displayed in the DPM groups list.
4. Select Manage > DPM relations > Add DPM. The Add DPM wizard opens to the Select DPM screen. The upper area of the screen displays the available DPMs. Figure 38 Add DPM wizard—Select DPM screen 5. Click Next. A confirmation screen appears. 6. Click Finish. The new DPM group is created and is displayed in the DPM groups list. Renaming a DPM group To rename a DPM group: 1. In the navigation tree, expand the Entities node. 2. Click the DPM Group node. The DPM group list appears in the list area. 3.
4. Select Manage > Rename. The Rename wizard opens to the New name screen. Figure 39 Rename Wizard—New name screen 5. n the New name field, enter a new name for the DPM group and click Next. A confirmation screen appears. 6. Click Finish. The DPM group’s name is changed to the new name. Redistributing storage elements within a DPM group The DPMs in a DPM group may each function as the primary DPM for different storage elements.
5. Click Finish. The DPM group is deleted.
Working with DPM groups
14 Using snapshots The snapshot service is a facility for making low-capacity snapshots. Snapshots can be made available to any host for purposes such as testing or backup, while production data continues to be updated without interruption. The snapshot service enables you to create two types of entities: • Point-in-Time (PiT)—An image of a Virtualization Services Manager (VSM) storage element, such as a virtual disk.
• Accelerated application testing—Snapshots enable you to radically reduce the time needed to prepare data for test runs. Copying and staging data is reduced to minutes for each test run, resulting in faster testing and faster time-to-market. Instead of copying data for each test run, you create a PiT of the development virtual disk. This enables you to create up to 32 snapshots of the PiT, and test modifications in parallel on the snapshots.
Creating PiTs You can create a PiT on the following storage elements: • • • • A A A A virtual disk. However, you cannot create a PiT on one of the domain’s setup virtual disks. snapshot. VDG. VDG snapshot. See the HP StorageWorks SAN Virtualization Services Platform release notes for the number of PiTs and snapshots that can be created on a virtual disk, and the minimal interval between PiTs.
8. Click Finish. The PiT is created and is listed in the PiT tab for the element on which the PiT was created. If the PiT was created on a snapshot, the PiT is listed in the Dependent PiT tab for the snapshot. For information about viewing PiTs, see “Viewing PiTs” on page 196. Viewing PiTs You can view the PiTs created on each virtual disk or VDG in the PiTs tab below the virtual disk or VDG list. You can view the PiTs created on each snapshot in the Dependent PiTs tab below the snapshot list.
4. In the tabs area, select the PiT tab. The following information is displayed for each PiT. Table 82 Virtual Disk/VDG/Snapshot/VDG Snapshot PiT tab fields Property Description No The row number. Name The name of a PiT. The status of the PiT. • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal.
5. Property Description Capacity The size of the temporary virtual disk which holds the modifications made on the PiT. This field shows you how much capacity from the storage pool is used by the PiT. Comment A free text display field. To modify the text that appears here, right-click the PiT and select Manage > Edit Comment. You can use this field for any purpose. Is Mirror User PiT Indicates if the PiT is an asynchronous mirror PiT created by the user.
1. Right-click the PiT. 2. Select Delete. A confirmation screen appears. 3. Click Finish. The PiT status changes to Resync and disappears after the synchronization is complete.
7. Click Next. The Select PiT screen appears. Figure 40 Create Snapshot wizard—Select PiT screen 8. From the list in the upper area of the screen, select the PiT for which you want to create a snapshot. 9. Click Add. The PiT you selected appears in the lower area of the screen. If you want to change your choice, select the PiT in the lower area and click Remove. 10. Click Next. The Select Storage Pool screen appears, displaying the list of available storage pools.
14. If you selected Set permission later in step 4, continue with step 26. Otherwise, click Next. The Select Host(s) screen appears, displaying the list of available hosts. 15. If you would like to select a host from a folder, navigate to the folder in the tree on the left of the screen. The Select Host(s) screen displays the list of hosts that have been copied to selected folder that satisfy the permission criteria you set in step 4. 16.
Viewing the snapshots list The snapshots list displays all snapshots managed in the domain. To display the snapshots list: In the navigation tree, click the Snapshot node. The snapshots list appears in the list area. The following information is displayed for each snapshot. Table 83 Snapshot Properties tab fields Property Description No The row number. Name The name of the snapshot. The status of the snapshot.
• Properties—Provides general information about the selected virtual disk, as described in Table 83. • Storage Pool—Shows the properties of the storage pool on which the temporary virtual disk which holds the data modifications made on the snapshot resides. • Temporary Virtual Disk—Shows the properties of the temporary virtual disk which holds the data modifications made on the snapshot. • Source PiT—Shows the properties of the PiT from which the selected snapshot was created.
Property Description Creation Time The time at which the storage pool was created. Created By The user who created the storage pool. Modification Time The last time a user made a modification to the storage pool. This includes expanding the storage pool, shrinking the storage pool, changing the free capacity alert threshold for the storage pool, and editing the comment field for the storage pool. Modified By The user who last modified the storage pool.
Property Description Owned by Host Shows which hosts have permission to access this virtual disk. If a single host has access permission for the virtual disk, the name of that host is displayed. If multiple hosts have access permission, the word “multiple” appears. Comment A free text display field. To modify the text that appears here, right-click the virtual disk and select Manage > Edit Comment. You can use this field for any purpose.
Property Description The current state of the PiT. Possible values: • Normal—The temporary virtual disk is in normal operational state. • Resync—The PiT is being deleted. The modifications held in the temporary virtual disk of the PiT are being merged back into the entity that would have received those modifications had the PiT not been created. This may be the virtual disk or snapshot on which the PiT was created or an earlier PiT on the same virtual disk or snapshot.
Property Description The status of the PiT. • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal. This includes an original virtual disk, the temporary virtual disk created for the PiT, and any PiTs and snapshots between the original virtual disk and the PiT in the hierarchy. Status • Partial—The status of one of the virtual disks from which the PiT is constructed is partial. The current state of the PiT.
Snapshot information—Host Presentation tab The Host Presentation tab displays the hosts that have permission to access the selected snapshot. Table 88 Snapshot Host Presentation tab fields Property Description A host that has permission to access the virtual disk. The icon next to the host name reflects the operating system (OS) of the host: Host • —Windows 2003 • —Windows 2008 • —HP-UX 11iv2 (11.23) • —HP-UX 11iv2 (11.31) • —VMWare ESX 3.5 • —Solaris 10 • —AIX 6.
Property Description The current status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host.
Property Description Primary Indicates whether the DPM is the primary DPM for the snapshot. The primary DPM for the snapshot is the preferred DPM through which a permitted DPM host accesses the snapshot. In case of failure or manual switchover, the secondary DPM, if there is one, takes over. Active Indicates whether the DPM is currently active for the snapshot. Snapshot information—Security tab The Security tab displays the access permissions of users and user groups for the selected snapshot.
Figure 42 Hierarchy tab Snapshot information—Disabled Operations tab The Disabled Operations tab shows which operations you cannot currently perform on the selected snapshot, and the reason for each. See the release notes for a current list of disabled operations. Table 91 Snapshot Disabled Operations tab fields Display field Description Operation name The name of an operation that is disabled. Reason The reason why the operation is disabled.
Property Description Clustered Yes indicates that the virtual disk or VDG is defined as a cluster resource. This setting tunes the SVSP system behavior when the virtual disk is permitted to multiple hosts (configured as a resource in a cluster application). For a description of configuring virtual disks for cluster applications, see “Defining virtual disks as clustered” on page 121. Comment A free text display field.
VDG snapshot information—Members tab The Members tab displays the snapshots that are members of the VDG snapshot. Table 93 VDG Snapshot Members tab fields Property Description No The row number. Name The name of the snapshot. The status of the snapshot. Possible values: Status • Normal—The status of all the virtual disks from which the snapshot is constructed is normal.
Property Description The current state of the PiT. Possible values: • Normal— The temporary virtual disk is in a normal operational state. • Resync—The PiT is being deleted. The modifications held in the temporary virtual disk of the PiT are being merged back into the entity that would have received those modifications had the PiT not been created. This may be the virtual disk or snapshot on which the PiT was created or an earlier PiT on the same virtual disk or snapshot.
Property Description The status of the PiT. Possible values: • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal. This includes an original virtual disk, the temporary virtual disk created for the PiT, and any PiTs and snapshots between the original virtual disk and the PiT in the hierarchy. Status • Partial—The status of one of the virtual disks from which the PiT is constructed is partial. The current state of the PiT.
VDG snapshot information—Host Presentation tab The Host Presentation tab displays the hosts that have permission to access the selected VDG snapshot. Table 96 VDG snapshot Host Presentation tab fields Property Description A host that has permission to access the virtual disk. The icon next to the host name reflects the operating system (OS) of the host: Host • —Windows 2003 • —Windows 2008 • —HP-UX 11iv2 (11.23) • —HP-UX 11iv2 (11.31) • —VMWare ESX 3.5 • —Solaris 10 • —AIX 6.
Property Description The status of the host. Possible values: • Present—For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host. However, the host is polling properly through at least one HBA.
Property Description Primary Indicates whether the DPM is the primary DPM for the VDG snapshot. The primary DPM for the VDG snapshot is the preferred DPM through which a permitted DPM host accesses the VDG snapshot. In case of failure or manual switchover, the secondary DPM, if there is one, takes over. Active Indicates whether the DPM is currently active for the VDG snapshot.
Figure 43 Hierarch tab VDG snapshot information—Disabled Operations tab The Disabled Operations tab shows which operations you cannot currently perform on the selected VDG Snapshot, and the reason for each. See the release notes for a current list of disabled operations. Table 99 VDG snapshot Disabled Operations tab fields Display field Description Operation name The name of an operation that is disabled. Reason The reason why the operation is disabled.
4. Select Manage > Manage Permission > Add Host Permission. The Add Host Permission wizard opens to the Select type of Host screen. 5. From the “Set permission to host with” dropdown list, select one of the following: 6. • UDH—Select this value to assign permission to UDHs. The wizard enables you to select specific hosts and set related parameters in later screens. • VSM Server—Select this value to assign permission to a VSM server. The wizard enables you to select a host in the next screen.
12. Select one of the following: • Next free LUN (recommended)—VSM assigns the next free LUN available for presenting the snapshot or VDG snapshot to permitted host(s). • Specified LUN—VSM assigns the LUN that you specify for presenting the snapshot or VDG snapshot to permitted host(s). 13. Click Next. The Select DPM Group screen appears. The upper area of the screen displays the DPM groups through which the host is registered. 14. In the upper area of the screen, select a DPM group and click Add.
6. Select one of the following from the dropdown list: 7. • Full—Assigns read/write permission to the host. • Read—Assigns read-only permission to the host. • None—Assigns no permission to the host. If required, repeat steps 3 through 6 to change permission for additional hosts. 8. Click Next. A confirmation screen appears. 9. Click Finish. The host permission is changed for the snapshot or VDG snapshot.
2. Select Manage > Manage Permission > Change LUN. The Change LUN wizard opens to the Select host(s) screen. 3. In the upper area of the screen, select the host(s) for which you want to change the LUN used to present the snapshot to the host. 4. Click Next. The Select LUN screen appears. 5. Select one of the following: 6. • Next free LUN (recommended)—VSM assigns the next free LUN available for presenting the snapshot to permitted host(s).
2. Select Manage > Manage Data Path Module/VSM > Change Primary/Secondary Data Path Module/VSM. The Change Primary/Secondary Data Path Module/VSM wizard opens to the Select preferred path screen. The upper area of the screen displays the DPM groups through which the host is registered. Figure 45 Add Host Permission wizard—Set Primary/Secondary Data Path Module or VSM screen 3. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary.
To change the active DPM for a snapshot or VDG snapshot: 1. Right-click the snapshot or VDG snapshot. 2. Select Manage > Manage Data Path Module > Change active Data Path Module. A confirmation screen appears. 3. Click Finish. The active DPM is switched, unless the currently inactive DPM is not available. Renaming snapshots or VDG snapshots To rename a snapshot or VDG snapshot: 1. Right-click the snapshot or VDG snapshot that you want to rename. 2. Select Manage > Rename.
Displaying VSS snapshots and PiTs To display VSS snapshots and their PiTs within VSM: 1. From the toolbar, select Tools > Options > General. The Options window appears displaying the Data Presentation tab. 2. Select the Show VSS Views checkbox and click OK. The Options window closes and VSS snapshots and PiTs are now displayed within VSS. NOTE: For hosts running Windows 2008, VSM supports the following operations: • You can convert VSS PiTs to regular PiTs.
Figure 47 VSS snapshot—source PiT—example NOTE: For hosts running Windows 2008, VSM supports the following operations: • You can convert VSS PiTs to regular PiTs. • Yoy can grant read-write permission for VSS snapshots in the operating system.
4. Select the Source Virtual Disk/Snapshot/VDG tab. The Source Virtual Disk/Snapshot/VDG tab displays the virtual disk, snapshot, or VDG on which the PiT was created. 5. Double-click the source virtual disk, snapshot, or VDG. The tabs area now displays tabs relating to the source virtual disk, snapshot, or VDG. You have reached the root of the hierarchy. 6. Select the Hierarchy tab.
3. Either: a. Right-click the PiT to which you want to roll back a virtual disk, VDG, or VDG snapshot. b. Select Manage > Rollback PiT. The Rollback PiT wizard opens to a confirmation screen. or: a. Right-click the virtual disk, VDG, or VDG snapshot that you want to roll back. b. Select Manage > Snapshot Service > Rollback. The Rollback wizard opens to the Select PiT screen. Figure 48 Rollback wizard—Select PiT screen c.
Restoring from snapshots Instant restore is an operation that replaces a virtual disk or VDG with a snapshot that was created from the virtual disk or VDG. The original element is deleted, and only the snapshot remains. This option is only enabled for a single snapshot created from a single PiT on a source element. If there is more than one snapshot on the PiT, or more than one PiT on the source element, instant restore is disabled. Instant restore enables you to implement the following testing scenario: 1.
• • • • • The number of virtual disks on which you are creating PiTs. How much data is modified over a period of time (for example between successive PiT creations). How many PiTs are maintained on each virtual disk. Which virtual disks you are allocating from which storage pools. The frequency of PiT creation. Built-in capacity protection VSM features built-in protection mechanisms for storage pools running out of free capacity.
2. Select the Configuration tab. The configuration options appear. Figure 49 Options dialog box—Configuration tab 3. In the Storage Pool Protection Threshold area, set the capacity thresholds for each warning level. For each warning level, define the threshold by percentage (%) of storage pool capacity remaining on the left and total (GB) capacity remaining on the right. 4. Click OK.
15 Using snapclones The snapclone service enables you to create multiple physical copies of any Virtualization Services Manager (VSM) virtual disk or snapshot. The snapclone process is carried out without any use of host resources. Each copy can be made independently accessible and instantly available for both read and write operations, even while being created.
• High performance LAN-free and server-free backup — Administrators can create an independent physical snapclone, allocate it to a backup server and execute the organization’s backup activities through that server. No LAN traffic is needed (LAN-free backup), the original application server is not involved (server-free backup), and the backup server may access a separate storage system.
Property Description The status of the snapclone group. Possible values: • Normal—All tasks in the group are progressing normally. • Suspended—All tasks in the group are suspended. • Failed— All tasks in the group have failed. • Degraded—At least one task in the group has failed and at least one task is in normal status. Status • Deleting—The group is in the process of deletion, either because all tasks are complete, or because a user deleted the group before all tasks were completed.
Snapclone group information—Snapclone Task tab The Snapclone Task tab displays the tasks running on the selected snapclone group. Table 101 Snapclone group Snapclone Task tab field Property Description No The row number. Name The name of the snapclone task. The status of the snapclone task. Possible values: • Init— Indicates the task is in the initial stage immediately after definition.
Snapclone group information—Security tab The Security tab displays the access permissions of users and user groups for the selected snapclone group. For information about configuring permissions, see “Changing security permissions for entities” on page 339. Table 102 Snapclone group Security tab fields Display field Description No The row number. An icon indicating either a user or user group. Possible values: Type Name • —A user. • —A user group. The name of the user or user group.
• • • • Conditions must be such that a PiT can be created on the virtual disk. The virtual disk must not be the setup virtual disk for the domain. No other snapclone or migration tasks can be running currently on the virtual disk. The virtual disk must not be a destination virtual disk of any VSM service task. (The virtual disk can be a source element for a VSM service task.) • A • • • snapshot.
7. From the Data mover mode dropdown box, select one of the following: NOTE: Currently, dedicated data movers are not supported in HP StorageWorks VSM. 8. 9. • Any node—Select this option to allow VSM to select the VSM server that will handle the group’s tasks. • Suggested node—Select this option if you want to specify a preferred VSM server to handle the group’s tasks. In the Comment field, optionally enter text. You can use this field for any purpose.
23. If you selected Without permissions in step 6, continue with step 28. If you selected Local domain: VSM Server or Local domain: UDH in step 6, click Next. The Select Host(s) screen appears, displaying the list of available hosts. 24. If you would like to select a host from a folder, navigate to the folder in the tree on the left of the screen. The Select Host(s) screen displays the list of hosts that have been copied to the selected folder. 25.
1. Do one of the following: a. Right-click the VDG that you want to snapclone. b. Select Manage > Snapclone Service > Create Snapclone Group. The Create Snapclone wizard opens to the Enter Snapclone Group parameters screen. or: a. Right-click the Snapclone Group node. b. Select New > On VDG. The Create Snapclone Group wizard opens to the Enter Snapclone Group parameters screen. 2. In the Group name field, enter the name of the group. 3.
12. If you selected 'Local domain: VSM Server or Local domain: UDH' in step 5, continue with step 15. If you selected Without permissions in step 5, click Next. The Select destination domain screen appears. The upper right area of the screen displays the local domain and any domains exposed to the local domain. NOTE: Snapclones are only supported within the domain. 13. Select the destination domain for the group’s first task.
22. If you selected Without permissions in step 5, continue with step 32. If you selected 'Local domain: VSM Server or Local domain: UDH' in step 5, click Next. The Select Host(s) screen appears, displaying the list of available hosts. 23. If you would like to select a host from a folder, navigate to the folder in the tree on the left of the screen. The Select Host(s) screen displays the list of hosts that have been copied to the selected folder. 24.
3. In the Task name field, enter a name for the task. 4. In the Destination name field, enter the name of the destination virtual disk that will be created. 5. From the “Set permission to host with” dropdown list, select one of the following: 6. • Without permissions—Select this option if you do not want to assign permission to any host to be able to access the destination virtual disk before the task is complete.
19. If you selected a VSM Server host, continue with step 25. Otherwise, click Next. The Select LUN screen appears. Select one of the following: • Next free LUN (recommended)—VSM assigns the next free LUN available for presenting the destination virtual disk to permitted host(s). • Specified LUN—VSM assigns the LUN that you specify for presenting the destination virtual disk to permitted host(s). 20. Click Next. The Select DPM Group screen appears.
11. In the Destination Name column, specify names for the destination virtual disks that will be created by the task. You may do any or all of the following: • Click Set default destination names to set all destination names to be identical to the source names. You cannot use this option when snapcloning to the local domain, since all objects within the same domain must have unique names. • Click Clear destination names to clear all destination names.
20. Select a DPM group and click Add. The DPM group you selected is displayed in the lower area of the screen. 21. Click Next. The Select preferred path screen appears. 22. Use the checkboxes to set one DPM in the DPM group as primary and one DPM as secondary. 23. Click Next. The Select folder screen appears. 24. If you want to add the task to a folder, enter the folder name in the Folder field or click Browse to browse to the folder. The folder must already be created.
2. Select the Snapclone Task tab. 3. Right-click a task. 4. Select Manage > Resume. A confirmation screen appears. 5. Click Finish. The task resumes. To resume all suspended tasks on a snapclone group: 1. Right-click the group. 2. Select Manage > Resume. A confirmation screen appears. 3. Click Finish. Any tasks on the group that were previously suspended resume. To resume all suspended tasks on all snapclone groups: 1. In the navigation tree, right-click the Snapclone Group node. 2.
16 Using migration The migration service is the facility that copies and moves the data within VSM virtual disks from one storage pool to another. During migration, host applications remain online and continue to read and write from the migrating virtual disk. The migration service keeps the data continuously online while implementing Information Lifecycle Management (ILM) or while upgrading hardware. Host applications using the migrating virtual disk are not disrupted.
• Information Lifecycle Management (ILM)—As the value of data changes over time, migration enables you to migrate virtual disks to appropriate storage pools, in terms of performance, capacity, and availability. The migration service can only be used within the same domain. If you need to migrate virtual disks to storage systems managed by another domain, create an asynchronous remote mirror group and perform the Detach operation on the group after performing a planned failover to the remote copy.
Property Description Modification Time The time at which the group was last modified. Modified By The user who last modified the group. Viewing migration group information You can display detailed information related to each migration group in the tabs area below the migration groups list. To view information related to a migration group: In the migration groups list, select a migration group.
Property Description Destination The temporary name of the destination virtual disk of the task, specified as the auxiliary name when the migration group was created. When the task is complete, the destination virtual disk will receive the name of the original virtual disk and the original virtual disk will receive this name. Progress The percentage progress of the task. Num of Source Virtual Disks The number of virtual disks being migrated by the task.
Display field Description Reason The reason why the operation is disabled. Creating migration groups A migration group defines a source element for migration and the migration task that will run on the source element. A source element can be either a virtual disk or a VDG. Creating migration groups on virtual disks In order to support the creation of a migration group, a virtual disk must fulfill the following conditions: • • • • • • • • • The virtual disk status must be Normal.
8. If you right-clicked the virtual disk that you want to migrate in step 1, continue with step 12. Otherwise, click Next. The Select Virtual Disk screen appears, displaying the list of available virtual disks. 9. If you would like to select a virtual disk from a folder, navigate to the folder in the tree on the left of the screen. The Select Virtual Disk screen displays the list of virtual disks in the selected folder. 10. Select the virtual disk that you want to migrate. 11. Click Add.
1. Do one of the following: a. Right-click the VDG that you want to migrate. b. Select Manage > Migration Service > Create Migration. The Create Migration wizard opens to the Enter Migration Group parameters screen. or a. Right-click the Migration Group node. b. Select New > On VDG. The Create Migration Group wizard opens to the Enter Migration Group parameters screen. 2. In the Group name field, enter a name for the group. 3.
15. In the Auxiliary Virtual Disk column, specify the names for all the auxiliary virtual disks. You may do any or all of the following: • Click Set default auxiliary names to set the names of all auxiliary virtual disks to be identical to the names of the source virtual disks. You cannot use this option alone, since the source virtual disks and auxiliary virtual disks reside on the same domain and must have unique names. • Click Clear auxiliary names to clear all auxiliary names.
To suspend all tasks on a migration group: 1. Right-click a migration group. 2. Select Manage > Suspend. A confirmation screen appears. 3. Click Finish. All tasks on the group are suspended. To suspend all tasks on all migration group: 1. In the navigation tree, right-click the Migration Group node. 2. Select Suspend all Migration Groups. A confirmation screen appears. 3. Click Finish. The tasks of all migration groups are suspended.
Built-in capacity protection VSM features a built-in protection mechanisms for storage pools running out of free capacity. The objective of the protection mechanisms is to ensure that storage pools always have enough free capacity to handle the expansion requests of snapshot temporary virtual disks (or else, write I/Os will fail). For details, see “Built-in capacity protection” on page 231.
17 Using mirroring The mirror service enables you to mirror virtual disks asynchronously between domains, and synchronously within a domain. In asynchronous mirroring, the host application writes data to an original virtual disk and the data is copied to mirror virtual disks in the background while the application continues to write.
are created, you can create up to two additional tasks for additional destination virtual disks. Multiple tasks can be defined per group, representing multiple destinations for the same source element. Each source element can only belong to one VDG. When you create an async mirror task with up to three remote copies for added disaster tolerance, the mirror service creates a snapshot PiT on the source element.
The mirror service enables you to specify the number of PiTs to maintain on the source domain, per group, and the number of PiTs to maintain on the destination domain, per task. When a new PiT is created on a source or destination, an old PiT is deleted if the new PiT increases the total number of PiTs to a higher number than the maximum permitted. Standard PiTs are deleted before user PiTs. Older PiTs are deleted before newer PiTs.
Property Description The status of the group. Possible values: • Normal—All tasks in the group are progressing normally. • Suspended—All tasks in the group are suspended. In this case, the mirror stops the creation of new standard PiTs because they cannot be copied anywhere. • Failed— All tasks in the group have failed. • Degraded—Tasks in the group have different statuses, of which at least one is failed. • Detaching—The group is in the process of detaching.
Property Description A configurable value that determines when an alert is triggered for cases in which the number of mirror PiTs on the group source element exceeds the expected limits. The number of mirror PiTs on the group is expected to go beyond the Required Source PiTs limit since only after a new PiT is created, and the Required Source PiTs limit is reached, a mirror triggers a deletion for the oldest mirror PiT which by itself is a process that takes time.
Async mirror group information—Async Mirror Task tab The Async Mirror Task tab displays the tasks running on the selected async mirror group. Table 109 Async mirror group Async Mirror Task tab field Property Description No The row number. Name The name of the task. The status of the task. Possible values: • Init—The task is in the initial stage in which the destination virtual disk is created. • Normal—The task is progressing normally.
Async mirror group information—Source Domain's PiT tab The Source Domain’s PiTs tab displays the mirror PiTs on the group source element. The tab shows this information only on the domain in which the source element resides. On domains to which the group is mirrored, this tab is empty. Table 110 Async mirror group Source Domain's PiTs tab fields Property Description No The row number. Name The name of a PiT. The status of the PiT. • Init—The PiT is being created.
Property Description Capacity The size of the temporary virtual disk which holds the modifications made on the PiT. This field shows you how much capacity from the storage pool is used by the PiT. Comment A free text display field. Is Mirror User PiT Yes indicates that this PiT was a user created mirror PiT. Async mirror group information—Source & Destination PiTs tab The Source & Destination PiTs tab shows which PiTs are currently available on the source domain and on each task destination.
• The virtual disk must not be a member of a VDG. (You can, however, create an asynchronous mirror group on a VDG.) • The virtual disk must not be the destination virtual disk of any other data moving task that is running, such as a snapclone task or a migration task. • The virtual disk must not be a temporary virtual disk. • The status of the virtual disk must be Normal. • If the virtual disk has PiTs, the status of the most recent PiT must be Normal.
5. 6. 7. From the Data Mover mode dropdown box, select one of the following: • Any node–Select this option to allow VSM to select the VSM server that will handle the group’s tasks. • Suggested node—Select this option if you want to specify a preferred VSM server to handle the group’s tasks. In the Required Source PiTs field, enter the number of mirror PiTs that should be maintained on the group source element at any time.
10. In the “Minimum creation time between two PiTs” field, enter the interval at which the mirror service should check for conditions suitable for creating a new standard PiT. Select the units from the dropdown box. This will be the minimum time difference between two successive mirror standard PiTs. NOTE: The supported minimum interval is 10 minutes. 11. In the Required destination PiTs field, enter the number of mirror PiTs that should be maintained on each task’s destination virtual disk at any time. 12.
28. If you would like to select a storage pool from a folder, navigate to the folder in the tree on the left of the screen. The Select Storage Pool screen displays the list of storage pools in the selected folder. 29. Select a storage pool from which you want to allocate capacity to the destination virtual disk. 30. Click Add. The storage pool you selected appears in the lower right area of the screen.
8. Uncheck Create standard PiTs if you do not want the mirror service to create standard PiTs on the group source element. If you uncheck Create standard PiTs, the destination VDG will only be updated when you create a user PiT. 9. From the User PiT Copy mode dropdown box, select a user PiT copy mode. The user PiT copy mode determines the mirror service’s copying policy when more than one user PiT is waiting to be copied to a destination. The user PiT copy mode affects all tasks in the group.
19. Select the destination domain for the group’s first task. 20. Click Add. The domain you selected appears in the lower right area of the screen. If you want to deselect the domain, select the domain in the lower right area, and click Remove. 21. If you selected Any node in step 5, continue with step 27. If you selected Suggested node in step 5, click Next. The Select local data mover screen appears. 22.
Working with user PiTs A user PiT is a mirror PiT, the creation of which is triggered by a user, which is copied to the destinations of all tasks running on an async mirror group. User PiTs enable you to save a snapshot image of the data on a virtual disk at the exact time you need.
To release the user PiTs on an async mirror group source element: 1. Right-click the group. 2. Select Manage > Release source User PiTs. A confirmation screen appears. 3. Click Finish. The user PiTs on the group source element are now handled as standard mirror PiTs. To release a specific user PiT: 1. Right-click the user PiT that you want to release. Do one of the following to locate the PiT: 2.
3. Modify any of the following parameters, if required. Table 113 Async mirror group parameters Property Description From the dropdown box, select one of the following modes for copying user PiTs: User PiT Copy mode • Copy newest PiTs—When the time comes to start a copy of a new PiT to a destination, the mirror service copies only the newest user PiT. This means that some user PiTs may be skipped.
Suspending asynchronous mirror groups When you suspend an async mirror group, all tasks are suspended and standard mirror PiT creation stops. While a group is suspended, you can still create a user PiT. To suspend an async mirror group: 1. Right-click a group. 2. Select Manage > Suspend. A confirmation screen appears. 3. Click Finish. The group is suspended. To suspend all async mirror groups: 1. Right-click the Async Mirror Groups node. 2. Select Suspend all Async Mirror Groups.
enables you to transfer production from a virtual disk to a mirror of the virtual disk without losing application data. Split is enabled only under the following conditions: • No host has permission to access the source element of the async mirror group on which you perform the split. • The next to last PiT created on the group was fully copied to all task destinations. • The last PiT created on the group is empty. There were no data modifications on the group since the last PiT was created.
back the destination virtual disk to that PiT, erasing other PiTs as necessary. The merge fails if the mirror service cannot find any synchronized PiT. If the former source element still has host presentations, remove the presentations before you merge the virtual disk. If you do not remove the host presentations, the merge fails. For complete typical procedures involving Merge, see the HP StorageWorks SAN Virtualization Services Platform administrator guide. To merge an async mirror group: 1.
11. From the User PiT Copy mode dropdown box, select one of the following modes for copying user PiTs: • Copy newest PiTs—When the time comes to start copying a new PiT to the destination, the mirror service copies only the newest user PiT to the destination. This means that some user PiTs may be skipped. • Copy all PiTs—The mirror service copies all user PiTs to the destination, even if there is more than one waiting to be copied at a time when conditions become suitable for the mirror service to copy.
23. In the upper area of the screen, select the VSM server on the remote domain that you want to handle the group’s tasks on the remote side. 24. Click Add. If you want to deselect the VSM server that you selected, select the VSM server in the lower right area, and click Remove. 25. Click Next. The Select folder screen appears. 26. If you want to add the async mirror group to a folder, enter the folder name in the Folder field or click Browse to browse to the folder. The folder must already be created.
8. If you would like to select a snapshot from a folder, navigate to the folder in the tree on the left of the screen. The Select Snapshot(s) screen displays the list of snapshots in the selected folder. 9. Select a snapshot that you want to add to the VDG. 10. Click Add. The snapshot you selected appears in the lower right area of the screen. If you want to deselect the snapshot, select the snapshot, and click Remove. 11. Repeat steps 8 through 10 to add more snapshots as necessary. 12. Click Next.
1. Right-click the group to which you want to add a task. 2. Select Manage > Add Task. The Add Task wizard opens to the Enter Task parameters screen. 3. In the Task name field, enter a name for the task. 4. In the Destination name field, enter a name for the destination virtual disk of the task. 5. In the Required destination PiTs field, enter the number of mirror PiTs that should be maintained on the task’s destination virtual disk at any time. 6.
5. In the Required destination PiTs field, enter the number of mirror PiTs of the source element that should be maintained on the destination storage pool at any time. 6. In the Destination PiTs Alert field, enter the number of PiTs above the number specified in the Required destination PiTs field to allow before triggering an alert.
Deleting async mirror tasks Deleting an async task deletes the task, the destination virtual disk of the task, and the PiTs on the destination virtual disk. To delete an async mirror task: 1. Right-click the task. 2. Select Manage > Delete. A confirmation screen appears. 3. Click Finish. The task is deleted. Synchronous mirroring Synchronous mirroring helps you keep applications online in case of storage failures on the local site.
Viewing sync mirror groups You can view all sync mirror groups in the sync mirror groups list. To display the sync mirror groups list: In the navigation tree, click the Sync Mirror Groups node. The sync mirror groups list appears in the list area. The following information is displayed for the sync mirror group. Table 114 Sync mirror groups properties Property Description No The row number. Name The name of the group. Original Virtual Disk Name The name of the virtual disk.
Property Description The mode of maintaining reallocation table virtual disks for the group’s tasks. Possible values: • Dirty Regions—The mirror service is keeping track of the virtual disk regions which the host updated recently, so that, in case of an unexpected host failure, task synchronization can be restored quickly by handling only the specific regions which might not have been updated on all tasks. Dirty Mode • No dirty—The mirror service considers the entire virtual disk as one region.
Sync mirror group information—Sync Mirror Task tab The Sync Mirror Task tab displays the tasks running on the selected sync mirror group. Table 115 Sync mirror group Sync Mirror Task tab fields Property Description No The row number. Name The name of the task, which indicates the name of the task’s destination virtual disk. The task name is constructed from the name of the local domain and the name of the destination virtual disk, which resides on the local domain. The status of the task.
Property Description The status of the PiT. • Init—The PiT is being created. • Normal—The status of all the virtual disks from which the PiT is constructed is normal. This includes an original virtual disk, the temporary virtual disk created for the PiT, and any PiTs and snapshots between the original virtual disk and the PiT in the hierarchy. Status • Partial—The status of one of the virtual disks from which the PiT is constructed is partial. The current state of the PiT.
Sync mirror group information—Host Presentation tab The Host Presentation tab displays information about the host with permission to access the sync mirror group. If a cluster of hosts has permission to access the group, all cluster nodes are listed in this tab. Table 117 Sync mirror group Host Presentation tab fields Property Description The name of the host, as defined in the host operating system.
Property Description The current status of the host. Possible values: • Present— For VSM servers, this indicates that the host is polling to the active VSM server through all the HBAs associated with the host. For other hosts, this indicates that the DPMs report that all HBAs associated with this host are recognized and active. • Degraded—For VSM servers, this indicates that the host is not polling through all the HBAs associated with this host.
Property Description Primary This setting indicates whether the DPM is the primary DPM for the virtual disk. The primary DPM for the virtual disk is the preferred DPM through which permitted hosts access the virtual disk. In case of failure or manual switchover, the secondary DPM takes over. Active This setting indicates whether the DPM is active for the virtual disk.
• The virtual disk has host permissions. To add host permissions to a virtual disk, see “Adding host permissions” on page 293. • The status of the virtual disk is normal. • The virtual disk cannot have any PiTs. To create a sync mirror group on a virtual disk: 1. Do one of the following: • Right-click the Virtual Disk node, and the virtual disks list appears; or select the virtual disk from a folder that contains the virtual disk, and the folder list appears.
Working with synchronous mirror groups Adding host permission to a group You can add host permission to a sync mirror group under the following conditions: • You cannot add permission to a group that already has any permissions. • You can add permission to multiple hosts when the group is defined as clustered. To add host permission to a sync mirror group: 1. In the Sync Mirror Groups list, right-click a group name. 2. Select Manage > Manage Permission > Add Host Permission.
Removing host permissions from a group To remove permissions from a host, delete the host. If a host fails and cannot recover, you can replace the host by deleting the host and adding permission to a new host. Changing the synchronous local mirror group mode A sync mirror group can operate in either an Always Synchronized mode or Continue-on-Fail mode. For a description of the two modes, see the explanation in “Synchronous mirroring” on page 284.
the Resync operation. Resync is blocked during dirty progress. For information about how to try to recover from failures, see “Troubleshooting” on page 298. To resync a synchronous mirror group: 1. Right-click the group. 2. Select Resync. A confirmation screen appears. 3. Click Finish. The fabric agent running on the DPM tries to resynchronize the failed group. Check the group state to see if the resynchronization was successful.
Working with synchronous mirror tasks Adding synchronous mirror tasks This section describes how to add tasks to a synchronous mirror group. To add a task to a synchronous mirror group: 1. Right-click a sync mirror group 2. Select Manage > Add Task. The Add Task wizard opens to the Enter Sync Mirror Task parameters screen. 3. In the Virtual Disk name field, enter the name of the virtual disk that the task will create and continually update. 4. In the Comment field, enter any text you want. 5.
Using snapshots with synchronous mirrors You can create a snapshot PiT on a synchronous mirror group or on the destination virtual disk of a synchronous mirror task. When you create a PiT on a group, a PiT is created on the virtual disk of each task. When you create a snapshot PiT on a virtual disk, the PiT is created only on that virtual disk. To create a PiT: 1. Select the entity on which to create the PiT. 2.
Troubleshooting The following tables suggest possible actions you can take when the status of a task or group indicates a problem. Table 121 Possible actions according to task status Task status Description Possible action Normal The status of the task’s destination virtual disk is normal and the task is synchronized with the other tasks in the group. None required. Snapsync The task is in the process of synchronizing with the other tasks in the group. None required.
Task status Description Possible action Try to fix any failed tasks. Once fixed, try to resume the group (see “Detaching synchronous mirror tasks” on page 296). If all tasks are not fixed, do either of the following: Failed The group is paused because at least one of the tasks is failing, and the group is running in Always Synchronized mode. • Change the group mode to Continue-on-Fail (see “Changing the synchronous local mirror group mode” on page 294). The group status changes to Journal.
Task status Description Possible action Journal One of the tasks is failing, but the group remains functional because it is running in Continue-on-Fail mode and has tasks whose statuses are normal. Try to fix any failed tasks. Once fixed, try to resync the group (see “Resynchronizing synchronous mirror groups” on page 294). If you cannot fix the failed tasks, you can detach the failed tasks. This returns the group status to normal (see“Detaching synchronous mirror tasks” on page 296).
Task status Description Possible action SnapSync The group is in the process of copying data from one task to another in the background. This process is initiated when a new task is created or when the mirror recovers a task after it failed. Wait until the group’s status returns to normal. After the group’s status returns to normal, new management operations are enabled. Check the mirror state reported in the Host Presentation tab for the group for each cluster node.
Using mirroring
18 Working with folders Virtualization Services Manager (VSM) enables you to create folders in order to manage your entities. Many users find it difficult to locate specific entities because the VSM client can contain thousands of entities of each entity type. Folders provide a powerful tool for organizing your entities. You can customize your own folders in a hierarchical folder structure with multiple subfolders. You can add entities to folders and access entities from within folders.
Viewing folder information You can display detailed information about any listed folder or subfolder in the tabs area below the folders list. To view folder information: In the folder list, select a folder or subfolder. The following tabs are displayed: • Properties—Provides the general information about the selected folder or subfolder (see Table 124). • Security—Shows the permissions which are assigned to users and user groups for managing the folder or subfolder.
Display field Description Reason The reason why the operation is disabled. Creating folders When you create a new folder, you create a shell with no contents. After creating the folder, you can add contents. To create a folder: 1. In the navigation tree, right-click the Folders node. 2. Select New. The Create folder wizard opens to the Folder parameters screen. 3. In the Folder name field, enter a name for the folder. 4. In the Comment field, optionally enter text.
2. Click Browse. The Select Folder dialog box appears. 3. Navigate to and select the folder to which you want to copy the folder you are moving. 4. Click OK. The Select folder dialog box closes. 5. Click Next. A confirmation screen appears. 6. Click Finish. The folder is moved to the destination folder. NOTE: You can also move a folder by dragging it from the list area to a folder in the navigation tree. Deleting folders To delete a folder: 1. Right-click a folder. 2. Select Delete.
• Add entities to folders • Move entities between folders • Remove entities from folders Viewing folder contents You can view the entities contained in folders. To open a folder: Under the Folders node in the navigation tree, select the folder you want to open. The entities in the folder are displayed in the list area. The following properties are displayed, by default, for each entity in a folder. Table 127 Folder content properties Property Description Type An icon indicating an entity.
In the folders list area, select an entity. In the tabs area, tabs appear that are relevant to the type of entity you selected. Adding entities to folders To add an entity to a folder: 1. In the navigation tree, expand the Entities node. The entities list appears in the list area. 2. Do one of the following: • Right-click an entity and select Folder > Copy to Folder. • Select an entity and click in the toolbar. The Copy to Folder wizard opens to the Select folder screen. 3. Click Browse.
CAUTION: If you right-click an entity in a folder and select Folder > Remove From Folder, the entity is removed from the folder, but not deleted from the domain. However, if you right-click an entity in a folder and select Delete, the actual entity is deleted from the domain.
Working with folders
19 Searching VSM The VSM client enables you to search for objects of a specific type in the local SVSP domain. You can save your search criteria to a query for later use. You can also save your search results to a folder. NOTE: If you want to search for more than one type of object at a time, use the query function. For more information, see “Working with queries” on page 317. Searching for objects in the local domain To search for objects in the local domain: 1.
2. Specify your search criteria. You can do the following: Figure 50 The Search dialog box • Specify an exact object name, as follows: Enter the name in the Name field. Check Match whole word. To make the search case sensitive, check Match case. • Specify text to search for in objects’ names, as follows: Enter the text in the name field. Do not check Match whole word. The search will return objects whose names include the text that you entered in the Name field.
NOTE: Click Reset at any time to clear your search criteria. 3. If you want to save your search criteria to a folder, do the following: a. Check Add selected items to folder. b. Click Browse to the right of the Folder field. The Select folder dialog box appears. c. Select the name of the folder in which you want to save your search results. The folder must already have been created. For information about creating folders, see “Creating folders” on page 305. d. Click OK.
5. Click Find. Your search results appear in a separate window. If you checked Add selected items to folder, your search results are saved to the selected folder. If you checked Add selected items to query, your search criteria are saved to the selected query. Figure 51 Search result window 6. To print the search results, select File > Print. 7. To save the search results to a file, select File > Save to file.
Figure 52 The Search dialog box—Advanced tab You can add multiple advanced search criteria to the “Find items that match this criteria” box. When you click Find, the VSM client searches for objects that match the criteria in the “Find items that match this criteria” box. To add an advanced criterion to the search: 1. From the Field dropdown box, select an object type to which you want to specify a relationship.
Searching VSM
20 Working with queries The VSM client enables you to query the objects on the local SVSP domain to find objects that match criteria that you define. Queries are not limited to one type of object. To use the query feature, you first create a query. You then add criteria to the query. Once a query is created, you can run the query as many times as you want. You can also modify the query by adding or removing criteria.
Figure 53 The query list The following properties are displayed, by default, for each query. Table 128 Query properties Property Description No The row number Name The name of the query. Comment A free text display field. To modify the text that appears here, right-click the query information row and select Manage > Edit Comment. You can use this field for any purpose. Viewing query information You can display detailed information about any query in the tabs area below the query list.
Query information—Security tab The Security tab displays the access permissions of users and user groups for the selected query. For information about configuring permissions, see “Configuring security permissions for entities” on page 337. Table 129 Query Security tab fields Display field Description No The row number. An icon indicating either a user or user group. Possible values: Type Name • —A user. • —A user group. The name of the user or user group.
6. Click Finish. The new query is created. To add criteria to your query, go to “Adding criteria to queries” on page 320. Creating quick queries Quick queries are queries that are partially predefined and quick to create. There is one type of quick query called Objects not in normal status. This type of quick query returns objects of a type that you specify whose statuses are not normal. To create a quick query: 1. Right-click the Queries node. 2.
3. Select the object type that you want to modify in your query. The Edit parameters dialog box appears.
4. Specify your query criteria. You can do the following: • Specify an exact object name, as follows: Enter the name in the Name field. Check Match whole word. To make the query case sensitive, check Match case. • Specify text to query for in objects’ names, as follows: Enter the text in the name field. Do not check Match whole word. The query will return objects whose names include the text that you entered in the Name field. To make the query case sensitive, check Match case.
Figure 55 The Edit Parameters dialog box—Advanced tab You can add multiple advanced query criteria to the “Find items that match this criteria” box. When you click Find, the VSM client queries objects that match the criteria in the “Find items that match this criteria” box. To add an advanced criterion to the query: 1. From the Field dropdown box, select an object type to which you want to specify a relationship.
4. If you want to remove all criteria, click Reset. 5. If you want to remove specific criteria, clear the specific criteria fields. 6. Click Apply. The selected criteria are removed from the query. Running queries To run a query: Double-click a query name. The query results appear in the list area. CAUTION: If you right-click on an object in the query results list and select Delete, the actual object is deleted from the domain. Renaming queries To rename a query: 1. Right-click a query. 2.
21 Managing security and users The VSM client provides a trusted and secure computing platform that enables you to protect your information from a wide range of threats. Users and user groups can only perform actions that administrators give them permissions to perform. Permission templates enable you to easily copy security permissions to entities, users, and user groups. The VSM client has a default user account with the user name admin.
2. Select the Security tab. Figure 56 The Options dialog box—Security tab 3. Specify your general security options. Administrators and user managers can do the following: 4. • Export security settings to a different domain, as follows: Click Export Info. The Save dialog box opens. In the File Name field, enter a complete path on the VSM server in which to save your user information file with a name for the file.
• • • • • • • • View the users list View user information Create new users Configure user permissions Configure users Change user passwords Delete users Reassign users’ quotas Viewing the users list To view the users list: 1. In the navigation tree, expand the Users Management node. 2. Click the Users node. The users list appears in the list area.
Property Description Snapshot Reserved Capacity The amount of the user’s quota that is reserved for creating snapshot PiTs and snapshots. The percentage of the user’s quota that is reserved for creating snapshot PiTs and snapshots. For example, if the Snapshot Reserved Percent is 30%, the user can only use 70% of the user quota for virtual disk creation. CAUTION: Snapshot Reserved Percent The Snapshot Reserved Percent value is only enforced if the Snapshot Reserved Capacity value is greater than zero.
Property Description Type An icon indicating an object. Possible values: —Permission template —Back-end LU • —Snapclone group —Storage pool • —Snapclone task • —Migration group —SVSP domain • • • Name • • —Virtual disk • —VDG • —Migration task • —PiT • —Async Mirror group • —Snapshot • —Async Mirror task • —VDG snapshot • —Sync Mirror group • —Host • —Sync Mirror task • —HBA • —Folder • —DPM • • —User —DPM Group • —User group The name of the entity.
1. Do one of the following: • In the navigation tree, right-click the Users Management node and select New. • In the navigation tree, expand the Users Management node. Right-click User and select New. The Create User wizard opens to the User parameters screen. 2. In the User name field, enter a name for the user. 3. In the User password field, optionally enter a password for the user. 4. If you entered a password in Step 3, reenter the password in the Confirm new password field. 5.
8. Repeat steps 6 and 7 if necessary until all the objects you want to add to the user are listed in the lower area of the screen. 9. Click Next. A confirmation screen appears. 10. Click Finish. The user now has permission to access the objects you specified. Configuring users Once you have created a user, you can configure the user’s quota for creating virtual disks, as well as other parameters such as e-mail address and session timeout. To configure a user: 1. Right-click a user.
2. Select Manage. The Manage User dialog box appears. Figure 59 Manage User dialog box 3. In the General tab, you can configure any of the following: • The user’s e-mail addresses, as follows: Enter the e-mail address in the E-mail field. • The user’s session timeout, as follows: Enter the value you want to set in the Session timeout field. Select the time unit from the dropdown box. • The user’s My Objects folder.
4. In the 'Member of' tab, you can add the user to user groups or remove the user from user groups. To add the user to a user group: a. Click Add user to group. The Add To User Group wizard opens to the Select user group to add user screen. b. In the upper area of the screen, select the user group to which you want to add the user. c. Click Add. The user group you selected appears in the lower area of the screen.
Reassigning users’ quotas If you are going to delete a user and the user created virtual disks, you can reassign the quota from which the user created virtual disks to another user. The user to which you reassign the virtual disks receives permission to manage these virtual disks as if that user had created them. The user to which you reassign the quota must have at least as much unused quota as the original user has used quota. The reassigned quota is subtracted from the user’s total quota.
You can: • • • • • • • View the user groups list View user group information Create user groups Configure user group permissions Add users to user groups Remove users from user groups Delete user groups Viewing the user groups list To view the user groups list: 1. In the navigation tree, expand the Users Management node. 2. Click the User Group node. The user groups list appears in the list area. Figure 60 User groups list The following properties are displayed, by default, for each user group.
To view user group information: In the user groups list, select a user group. The following tabs are displayed: • Properties—Provides the general information about the selected user group (see Table 136). • Users—Shows the users in the user group. • Security—Shows the objects for which the user group has permissions. These tabs are described in the following sections. User group information—Users tab The Users tab displays the users in the user group (see Table 131 on page 327).
8. Repeat steps 6 and 7 if necessary until all the objects you want to add to the user group are listed in the lower area of the screen. 9. Click Next. A confirmation screen appears. 10. Click Finish. The users in the user group now have permissions to access the objects you specified. Adding users to users groups To add users to a user group: 1. Right-click a user group. 2. Select Manage. The User Group dialog box appears. 3. Click Add user to group. 4.
for each user and user group. A user or user group can be assigned any of the following types of permission for an entity. Table 137 Security permission types Permission type Description Full Permission to delete, modify, and view an entity. Read/write Permission to modify and view an entity, but not to delete the entity. Read Permission to view an entity, but not to modify or delete the entity. None No permission to access an entity.
2. Click Add user/user group. The Add user/user group permission wizard opens to the Select user(s) screen. Figure 61 Add User/User Group permission wizard—Select User(s) screen 3. If you want to add a user to the entity, select the user in the upper area of the screen. 4. Click Add. The user you selected appears in the lower area of the screen. If you want to deselect the user, select the user in the lower area and click Remove. 5.
To change a user or user group’s permission for an entity: 1. Do one of the following: • Right-click the entity and select Security. • Select the entity and click in the toolbar. The Security dialog box appears. Figure 62 The Security dialog box 2. Select the user or user group whose permission type you want to change. 3. Do one of the following: 4. • To give the selected user or user group full access to the entity, check Read, Modify, and Delete.
3. Click Remove user/user group. The users or user groups are removed from the list. 4. Click OK. The Security dialog box closes. CAUTION: If you remove all users from an entity, the entity cannot be managed until a user is granted permission to manage the entity. Working with permission templates A permission template is a set of users and/or user groups with specified access types.
2. Select Permission Templates. The permission templates list appears in the list area. Figure 63 The permissions templates list The following properties are displayed, by default, for each permission template. Table 138 Permission Template properties Property Description No The row number. Name The name of the permission template. Comment A free text display field. To modify the text that appears here, right-click the virtual disk and select Manage > Edit Comment.
Permission template information—Security tab The Security tab displays the users and user groups included in the permission template and the access types assigned to each user and user group in the template. Whenever the permission template is copied to an object, these users and user groups receive permission to access the object. Table 139 Permission template information—Security tab fields Display field Description No The row number. An icon indicating either a user or user group.
7. If you want to add the permission template to a folder, click Browse to browse to the folder. The folder must already be created. For information about creating folders, see “Creating folders” on page 305. 8. Click Next. A confirmation screen appears. 9. Click Finish. The new permission template is created. Copying permissions from permission templates to entities Copying permissions from a permission template gives the entity the same user permissions as defined in the permission template.
Exporting permissions from entities to new permission templates You can create new permission templates by exporting existing permissions from entities. To export permissions from an entity to a new permission template: 1. Do one of the following: • Right-click an entity and select Security. • Select an entity and click in the toolbar. The Security dialog box appears. 2. Click Export permission to template. The “Create Template with current object permissions” wizard opens to the Create template screen.
Managing security and users
22 Using the VSM event viewer The VSM client features an event viewer, which enables you to view and manage event logs. Event logs provide detailed histories of the events that occur in the VSM environment. You can use event logs as audit trails to diagnose problems in the VSM environment. An event log can store up to 500,000 events. There is one active event log per domain. You can use the event viewer to view the event log of the domain to which you are connected.
Viewing the event log for the local domain The event log for the local domain is accessed through the Event Viewer node in the navigation tree. You can choose between two sub-nodes underneath the Event Viewer Node: • Recent Logs—Displays one page that shows the most recent event logs (up to 1,000 events). • All Logs—Displays all event logs. To view the event log for the domain to which you are connected, do one of the following: • In the navigation tree, click the Event Viewer node.
Property Description Description A description of the event. ID The event ID number. Viewing event logs for specific entities The VSM client enables you to view a log of the events related to a specific entity. To view an event log for a specific entity, do one of the following: • Right-click an entity and select Event Log. • Select an entity and click in the toolbar. An event log for the entity is displayed in a separate window. The properties in Table 141 are displayed for each event.
2. Select Filter. The Filter Event Log dialog box appears. Figure 65 Filter Event Log dialog box 3. 4. Specify your filter criteria. You can do the following: • Specify modules related to events, as follows: From the Module dropdown list, select a module. • Specify sources from which events originated, as follows: From the Source dropdown list, select a source. • Specify users who initiated events, as follows: From the User dropdown list, select a user.
Viewing, copying, and printing event details When you are displaying an event log in the display area, you can view the details of any specific event. To view details of a specific event: 1. Right-click an event. The Informational Properties dialog box appears, displaying the event details. Figure 66 Informational Properties dialog box 2. • To view the details of a different event in the event log, click • To copy event details to your clipboard, click . • To print event details, click . Click Cancel.
Exporting event logs The VSM client enables you to export event logs. The exported event logs can be imported into different domains. For more information, see “Importing event logs from exported files” on page 353. To export an event log: 1. In the navigation tree, right-click the Event Viewer node. 2. Select Export Log. The Export Event Log dialog box appears. 3. Do one of the following: 4.
6. Click Close. The event file is saved. Saving a selection of events You can save one or more events from an event log to a text file. The resulting file is suitable for reading by a human and cannot be imported to the VSM client as an event log. This feature is useful if you want to e-mail a few specific events to a system administrator or a support person. To save events to a text file: 1. Open an event log. 2. Select the events that you want to save.
6. Click Close. The imported event log appears in the expanded Event Viewer node in the navigation tree. Importing event logs from VSM servers The VSM client enables you to import event logs from VSM servers. If you want to import event logs from exported files, see “Importing event logs from exported files” on page 353. To import an event log from a VSM server: 1. In the navigation tree, right-click the Event Viewer node and select Import Log (native). The Import Event Log dialog box appears. 2.
2. Select Reload Web Server Log. A confirmation screen appears 3. Click Finish. The web server log is cleared and the events are reloaded. If you navigate away from the event log and then return, the reloaded events are displayed. Deleting event logs The VSM client enables you to delete an event log from a VSM server. To delete an event log: 1. In the navigation tree, right-click the Event Viewer node and select Delete Log on VSM. The Save dialog box appears. 2.
3. Click Add New e-Mail Group. The Create notification group dialog box appears. Figure 67 Create Notification Group dialog box 4. In the Name field, enter a name for the new event log notification group. 5. In the e-mail field, enter a single common e-mail address or Outlook contact group for the event log notification group. 6. In the Comment field, optionally enter text. You can use this field for any purpose. 7. From the Select options for create dropdown box, select one of the following: 8.
Editing event log notification groups To edit an event log notification group: 1. From the Tools menu, select Options > Event Log. The Options dialog box appears. 2. Click the Notifications tab. 3. From the Event log notification group dropdown list, select an event log notification group to edit. 4. Click Edit e-Mail Group. The Edit notification group dialog box appears. 5. Edit the event log notification group parameters.
2. Click the Event Log Parameters tab. Figure 68 The Options dialog box—Event Log Parameters tab 3. Configure your event log parameters. You can do the following: • Specify the maximum size of the event log file, as follows: Select a file size from the Maximum Log size in MB dropdown list.
23 Performing maintenance activities The VSM client enables you to perform maintenance activities on VSM servers. Maintenance activities enable you to configure not only the VSM client but the VSM server environment itself.
1. From the Tools menu, select Maintenance. The Maintenance dialog box appears. Figure 69 The Maintenance dialog box 2. Click Erase Configuration. The Save dialog box opens. 3. In the File Name field, enter a complete path on the VSM server in which to save your backup file with a name for the file. 4. Click Save. The Erase Configuration wizard opens to the Backup Folder name screen. The name of the backup file path you entered in the Save dialog box appears in the Backup Folder name field. 5.
8. Click Finish. The VSM server configuration is backed up. Creating the setup virtual disk When you first install VSM software on a VSM server, the domain setup database is stored on the local hard disk of the VSM server. One of the first operations you need to perform when establishing a domain, is to create the setup virtual disk. This moves the setup database to a VSM virtual disk on the SAN, so that the setup database becomes a resource that both VSM servers on the domain can share.
Creating SAN API virtual disks The VSM client enables you to create SAN API virtual disks (also called SAN CLI virtual disks). SAN API virtual disks enable hosts to direct SAN API commands to VSM through a DPM. For more information about SAN API commands, refer to the HP StorageWorks SAN Virtualization Services Platform Manager command line interface user guide. To create a SAN API virtual disk: 1. From the Tools menu, select Maintenance. The Maintenance dialog box appears. 2.
Performing manual VSM server elections The VSM client enables you to perform manual VSM server elections. An election examines the VSM servers and determines which server should be deployed in active mode and which server should be deployed in passive mode. To perform a manual VSM server election: 1. From the Tools menu, select Maintenance. The Maintenance dialog box appears. 2. Select Force VSM Election. A confirmation dialog box appears. 3. Click OK. The VSM server election is performed.
2. Click Manage Multi Domain Access Path. The Manage Multi domain Access Path dialog box appears. Figure 70 The Manage Multi Domain Access Path dialog box 3. You can do the following: • View back-end LU signature properties, as follows: Select a back-end LU signature row and click the Properties tab. • View a back-end LU signature access path, as follows: Select a back-end LU signature row and click the Access Path tab.
2. Click Manage Limits. The Manage limits definition dialog box appears. Figure 71 Manage limits definition dialog box 3. You can do the following: 4. • Set Limits to Default—sets all the configuration limits to their default values. • Set New Limits—displays a dialog box that enables you to import a file. After you import the file, you must click Refresh in the Manage Limits definition dialog box to display the new limits.
Performing maintenance activities
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. I/O Input/Output.
passive path A path that must have some operation (for example, a SCSI start unit command that is issued by the server) performed on it to make it active. See also active/active RAID, active/passive RAID, and secondary path. patch file Incremental update to an existing system image. personality The way in which a DPM exposes LUNs to the hosts that use them.
purposes such as data recovery, backup and testing, while the original virtual disk stays online and continues to be updated. • A read-write entity that makes PiT data available to any host as a logical drive. SNMP Simple Network Management Protocol. The protocol used by the Data Path Module to report exception conditions to third-party network management applications. SSH Secure Shell. A protocol and application for communicating with a remote computer system.
virtual disk In VSM, a unit of storage allocated to one or more hosts from a storage pool. A virtual disk can range in size from 1 GB to 2 TB. DPMs present allocated virtual disks to hosts as logical drives. Volume Shadow Copy Service A backup infrastructure for the Microsoft Windows Server 2003/2008 operating systems, as well as a mechanism for creating consistent point-in-time copies of data known as shadow copies. VSM Virtualization Services Manager.
Index A Access Path tab back-end LU information, 61 HBA information, 165 access paths refreshing, 66 SVSP domain, 363 adding tasks to VDG snapclone groups, 245 tasks to virtual disk or snapshot snapclone groups, 243 adding application to applications list, 122 async mirror tasks, 281 back-end LUs to stripe sets, 78 DPM to DPM group, 188 entities to folders, 308 host permission to VDGs, 136 members to VDG, 135 permission to sync mirror group, 293 stripe sets to storage pools, 82 sync mirror tasks, 296 users
changing active DPM, 121 active DPM for snapshot, 224 active DPM for VDG, 141 host permissions, 118, 139 host personality, 153 password, 26 preferred path, 153 primary and secondary DPM, 120 security permissions for entities, 339 storage pool free capacity alert threshold, 96 sync local mirror group mode, 294 user passwords, 333 virtual disk LUN, 120 clustered virtual disks, 121 configuring data presentation, 34 event log file, 357 event log notifications, 355 general security options, 325 security permissi
Disabled Operations tab async mirror group information, 266 back-end LU information, 63 domain information, 49 DPM group information, 187 DPM information, 177 folder information, 304 HBA information, 166 migration group, 252 permission template information, 343 query information, 319 snapclone group information, 237 snapshot information, 211 storage pool information, 91 stripe set information, 76 sync mirror group information, 291 VDG information, 132 VDG snapshot information, 219 virtual disk information,
F failback performing, 66 virtual disks from DPM, 178 failover virtual disks from DPM, 177 VSM server, 363 filtering event logs, 349 folder information Disabled Operations tab, 304 Security tab, 304 folders adding entities, 308 creating, 305 deleting, 306 moving, 305 moving entities between, 308 My Objects, 306 removing entities, 308 renaming, 305 viewing contents, 307 viewing list, 303 Front End HBA tab DPM information, 175 G getting started, 25 H HBA information Access Path tab, 165 Disabled Operations
migration group creating, 253 creating on VDGs, 254 creating on virtual disks, 253 deleting, 257 Disabled Operations tab fields, 252 property tab fields, 251 Security tab fields, 252 viewing list, 250 Migration Group Task tab, 252 migration tasks resuming, 257 suspending, 256 mirroring asynchronous, 259 synchronous, 259 modifying async mirror group, 274 async mirror tasks, 282 permission templates, 345 moving folders, 305 My Objects folder, 306 PiTs creating, 195 deleting, 198 planning storage capacity, 23
renaming back-end LUs, 66 folders, 305 queries, 324 snapshots, 225 VDGs, 141 virtual disks, 114 resuming async mirror group, 276 async mirror tasks, 283 Import-in-Place, 65 suspended migration tasks, 257 suspended snapclone tasks, 247 sync mirror groups, 294 running queries, 324 S SAN API (CLI) virtual disks, 362 saving event logs, 352 selection of events, 353 security options, configuring, 325 Security tab back-end LU information, 62 domain information, 47 DPM information, 177 folder information, 304 HBA
storage pools changing free capacity alert threshold, 96 creating, 91 deleting, 96 expanding, 93 shrinking, 94 viewing list, 85 stripe set back-end LU tab fields, 73 stripe set information Disabled Operations tab, 76 Security tab, 76 Storage Pool tab, 73 Stripe Set Segment tab, 75 viewing, 71 Virtual Disk tab, 74 stripe set properties, 71 Stripe Set Segment tab, 75 stripe sets adding back-end LUs, 78 adding to storage pools, 82 creating, 77 deleting, 83 removing back-end LUs, 80 removing from storage pools,
User Quota tab user information, 329 virtual disk information, 107 users configuring, 331 creating, 329 deleting, 333 reassigning quotas, 334 viewing list, 327 Users tab, 336 V VDG information Data Path Module tab, 130 Disabled Operations tab, 132 Hierarchy tab, 131 Host Presentation tab, 129 Members tab, 127 PiT tab, 127 Security tab, 131 VDG snapshot information Data Path Module /VSM tab, 217 Disabled Operations tab, 219 Hierarchy tab, 218 Host Presentation tab, 216 Members tab, 213 PiT tab, 214 Security
virtual disks changing LUN, 120 creating, 109 defining as clustered, 121 deleting, 123 expanding, 115 managing permissions, 115 properties, 101 renaming, 114 rolling back, 228 setting application types, 122 synchronous mirroring, 297 VSM client configuring appearance, 35 launching, 25 using interface, 27 VSM properties fields, 39 VSM server backing up configuration, 360 deleting, 54 erasing configuration, 359 importing event logs, 354 managing IP addresses, 38 manual elections, 363 manual failovers, 363 pro
