HCS Best Practice guide for VMware ESXi 4.x ConfigGuide v3.2 English

8/10/2019 HCS Best Practice guide for VMware ESXi 4.x ConfigGuide v3.2 English

1/79

Best Practices Document VMware ESX 4.0/4.1 Configuration Guide

HCS_BestPracticeDoc_VMware_ConfigGuide_v3.2_English.docx Page 1

Hitachi Command Suite

Best Practices Document

VMware ESX 4.0/4.1Configuration Guide


2/79



All rights reserved. Copyright (c) 2011. Hitachi Ltd

Product and company names mentioned in this document may be the trademarks of their respective owners.Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms bywriting the name with the capitalization used by the manufacturer, or by writing the name with initial

capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this documentshould not be regarded as affecting the validity of the trademark.

Information in this document is subject to change without notice and does not represent a commitment onthe part of Hitachi. The software described in this manual is furnished according to a license agreementwith Hitachi. The license agreement contains all of the terms and conditions governing your use of thesoftware and documentation, including all warranty rights, limitations of liability, and disclaimers ofwarranty.Material contained in this document may describe Hitachi products not available or features not available inyour country.

Edition history:2010/12/20 Edition 1, Software Division, Hitachi2010/12/29 Edition 2, Software Division, Hitachi2011/2/3 Edition 3, Software Division, Hitachi


3/79



Table of Contents

1. Introduction ......................................................................................................................................... 4 1.1. Target audience ......................................................................................................................... 4 1.2. Background ............................................................................................................................... 4 1.3. Prerequisite version of HCS ..................................................................................................... 4 1.4. Supported versions of VMware ................................................................................................ 4

2. Resource Management (HDvM, HTSM, and HDvM Agent) ........................................................... 5 2.1. Managing ESX servers in HDvM ............................................................................................. 5 2.2. Allocating volumes to an ESX server ....................................................................................... 5 2.3. Allocating volumes to a virtual machine (raw device mapping ............................................ 6

2.3.1. Non-NPIV environments ................................................................................................... 6 2.3.2. NPIV environments ............................................................................................................ 6

2.4. Managing volume pairs on virtual machines ............................................................................ 17 2.5. Performing disk migration in units of datastores (HTSM) ....................................................... 17 2.6. Environment settings for managing ESX servers ..................................................................... 19

2.6.1. Setting up vMA monitoring environment Common Physical Environment ................... 21 2.6.2. Setting up vMA monitoring environments Mixed Physical Environment ...................... 24

2.6.3. Setting up a system in which vMA monitors VMware vCenter Server ............................. 27 2.7. Environment settings for installing the HDvM agent on a virtual machine that uses NPIV..... 31

2.7.1. Configuration ..................................................................................................................... 31 2.7.2. Setting procedure for the HDvM server ............................................................................. 31 2.7.3. Setting procedure for the HDvM agent .............................................................................. 32

3. Performance Management (HTnM and HTnM Agent) ................................................................... 34 3.1. Prerequisite version of Device Manager ................................................................................... 34 3.2. Notes about monitoring NPIV environments ............................................................................ 34 3.3. Notes about changing the configuration of pair volumes ......................................................... 37 3.4. Notes about migrating LDEVs ................................................................................................. 38 3.5. Notes about setting the command device attribute ................................................................... 41

4. Backup and Restore Management (HPtM and HRpM) ................................................................... 42 4.1. HPtM/HRpM Application Agent (CLI) .................................................................................... 42

4.1.1. HPtM for SQL Server ........................................................................................................ 42 4.1.2. HPtM for Exchange Server ................................................................................................ 57 4.1.3. HPtM for file systems ........................................................................................................ 62

4.2. Hitachi Replication Manager (HRpM) ..................................................................................... 69 4.2.1. Prerequisite version of HDvM ........................................................................................... 69 4.2.2. Specifying command devices for virtual machines ............................................................ 69 4.2.3. Collaborating with applications ......................................................................................... 69

5. Multi-Path Management (HDLM and HGLM) ................................................................................ 76


4/79



1. Introduction

This document describes the best practices for configuring Hitachi Command Suite (HCS) in VMware 4.0and 4.1 environments.

1.1. Target audience

Users of HCS Users who want to use VMware virtualized hosts with HCS for the following purposes:

To manage NPIV virtual WWNs configured on virtualized hosts To configure CCI (or pair management) servers on virtualized hosts To configure backup servers by using the HRpM application agent

1.2. Background

Due to VMware s storage management architecture, there are some configuration prerequisites andoperations that customers need to know in advance to use HCS to manage virtualized hosts. This document

describes best management practices for HCS, product by product.

1.3. Prerequisite version of HCS

This document assumes the following versions of HCS: When using HCS Version 6: V6.4.0-06 or later When using HCS Version 7: V7.0.1 or later

1.4. Supported versions of VMware

This document assumes the following versions of VMware: VMware ESX 4.0 VMware ESX 4.1 VMware ESXi 4.0 VMware ESXi 4.1


5/79



2. Resource Management (HDvM, HTSM, and HDvM Agent)

2.1. Managing ESX servers in HDvM

The following methods can be used to manage ESX servers:

Table 1: Methods used to manage ESX servers

ID Management Target Management Method Procedure

1-1 ESX server Manage as a virtualization server byusing HDvM

Discover the ESX server in HDvM

1-2 Manage as a host in HDvM Manually register a host #1

2-1 Virtual machine (VM)on an ESX server

Manage by using the HDvM agent #2 Install the HDvM agent on the virtualizationserver

2-2 Manage as a host in HDvM Manually register a host #1

#1: Use one of the following methods to manually create a host: Manually create the host by using the GUI or CLI, and then register WWNs Automatically create the host from an existing host group by using the HostScan and MergeHost

functions.#2: In HDvM V7, HDC (Host Data Collector) manages hosts without installing the HDvM agent. HDC,however, does not support guest OSs on virtual machines. Therefore, use the HDvM agent when you useHDC.The numbers 1-1, 1-2, 2-1, and 2-2 in the following tables correspond to the ID numbers in the above table.

Table 2: Features of directly managing ESX servers

1-1 1-2

1 Volumes can be allocated to ESX servers. Yes Yes

2 Volumes allocated to ESX servers can be managed. Yes Yes

3 The relationship between a datastore created on an ESX server and

the LDEVs that make up that datastore can be displayed.

Yes No

4 Information about virtual machines running on ESX servers can bedisplayed.

Yes No

5 Volumes can be managed from the viewpoint of virtual machines. Yes No

6 The HDvM agent must be installed. No No

Table 3: Features of managing virtual machines on ESX servers

2-1 2-2

7 Volumes can be allocated to virtual machines. Yes Yes

8 Volumes allocated to virtual machines can be managed. Yes Yes

9 Information about guest OS file systems can be displayed. Yes No

10 Pair operations can be performed. Yes # No

11 The HDvM agent must be installed. Yes, on eachvirtualmachine

No

#11: You can install the HDvM agent on only one virtual machine, make it a CCI server, and then perform pair operations. If you do so, you do not have to install the HDvM agent on other virtual machines. Fordetails, see section 2.4.

2.2. Allocating volumes to an ESX server

New volumes can be allocated to an ESX server for many purposes, such as creating datastores.The same procedures used for allocating volumes to normal hosts can be used to allocate volumes to ESX


6/79



servers. When allocating volumes to an ESX server, specify the ESX server's physical WWN. The allocatedvolumes can then be used by the ESX server. For example, to create a datastore, use VMware tools.

2.3. Allocating volumes to a virtual machine (raw device mapping

When allocating volumes to a virtual machine, the WWN to be specified depends on whether an NPIV

environment is used.2.3.1. Non-NPIV environments

In an environment where a physical WWN is assigned to each virtual machine, volumes can be allocated byusing the same procedures for allocating volumes to normal hosts. When allocating volumes, specify the

physical WWN assigned to the virtual machine.

Figure 1: (Non-NPIV environment) When allocating volumes to virtual machines

2.3.2. NPIV environments

In an NPIV environment, volumes must be allocated to ESX servers and virtual machines. Therefore, inHDvM, specify the WWN of each target ESX server and virtual machine.If multiple virtual machines use the same storage port, all virtual WWNs that are assigned to those virtualmachines must be registered in the same host group. In addition, in a VMotion environment, the physicalWWNs of all ESX servers for VMotion must be registered in the same host group.


7/79



Figure 2: (NPIV environment) When allocating volumes to virtual machine

(1) Allocating new volumes to an existing virtual machineIn HDvM, specify the physical WWN and the virtual WWN of each virtual machine that uses the samestorage port.

Figure 3: (NPIV environment) When allocating new volumes to existing virtual machines

The following describes the procedure for HDvM V6 and HDvM V7.

For HDvM V6Prerequisites: Register the ESX server and all virtual machines as described below.


8/79



Discover the ESX server as a virtualization server or manually register it as a host in HDvM. The figureabove shows an ESX server discovered as a virtualization server, and the following figure shows an ESXserver registered as a host.

Install the HDvM agent on the target virtual machine or manually register the virtual machine as a host inHDvM.To allocate volumes to virtual machines:1. Select volumes (LDEVs) to allocate to virtual machines, and then click the Allocate Storage button.


9/79


10/79



Windows Extension or Windows for a Windows operating system). For USP, USP V/VM, or VSP,specify VMware Extension or VMware for the host mode.

4. Specify LU settings (such as creating a LUSE), map LUs to the port, and specify LUNs the same aswhen allocating volumes to a normal host.


11/79



For HDvM V7To allocate volumes to virtual machines in HDvM V7:1. Create a logical group that includes the ESX server and virtual machines that use the same storage port.

The list of logical groups can then be used as the starting point for allocating volumes to a virtualmachine.

2. Create a logical group that includes the ESX server and virtual machines that use the same storage port.

3. Select the ESX server and all virtual machines, and then start the Allocate Volumes dialog box.4. In the Allocate Volumes dialog box, select volume and storage port settings.


12/79



5. If you selected a storage port that has not been used, create a host group by specifying options in HostGroup and LUN Settings . For AMS, WMS, or SMS, specify the same host mode as the virtualmachine s operating system (for example, specify Windows Extension or Windows for a Windowsoperating system). For USP, USP V/VM, or VSP, specify VMware Extension or VMware for the hostmode.

6. Confirm the plan summary, and then allocate the volumes.


13/79



(2) Allocating new volumes to new virtual machinesIn HDvM, to use the virtual WWNs assigned to new virtual machines, either

a) Install the HDvM agent on the new virtual machines or b) Manually register the new virtual machines as hosts.

Next, if a path is already assigned to existing virtual machines on the storage port used by the new virtualmachines, assign the same path for the new virtual machines. (This operation requires adding the newWWNs for the new virtual machines to the same host group.) Finally, in the HDvM GUI, select thevolumes to be allocated to the new virtual machines. At this time, specify the ESX server's physical WWNsand all virtual WWNs of all virtual machines that use the same storage port.

Figure 4: (NPIV environment) Allocating new volumes to new virtual machines

The following describes the procedure in HDvM V6 and HDvM V7.

For HDvM V6As described in section 2.3.2(1), make sure that the ESX server and virtual machines are registered inHDvM. In addition, create a logical group that includes all volumes already allocated to the existing virtualmachines so that you can use the Modify Security functionality to add WWNs to the host group.

In the Hosts navigation tree, select the virtual machines to which volumes have been allocated, and thencheck the list of volumes already allocated for the corresponding virtual machines. Select the allocatedvolumes, and then click the Move Storage button to add the volumes to the logical group you created.


14/79



Note: Create the logical group for the target of volumes before you click the Move Storage button.

To allocate new volumes to new virtual machines:1. Display the logical group to which you added allocated volumes. In this window, click the Modify

Security button, and then register the virtual WWNs assigned to the new virtual machines in the hostgroup.

2. Allocate new volumes to the target virtual machine by continuing with step 3 in 2.3.2(1).

For HDvM V7To allocate volumes to virtual machines in HDvM V7, first create a logical group that includes the ESXserver and virtual machines that use the same storage port. The list of logical groups can then be used as thestarting point for allocating volumes to a virtual machine.


15/79



1. Select the ESX server and all virtual machines, and then start the Allocate Volumes dialog box.

2. Manually select the volumes to be newly allocated and volumes already allocated to virtual machines,and then allocate the volumes. This operation adds the WWNs of new virtual machines to the hostgroup that the already allocated volumes use. This host group is used to allocate new volumes.


16/79



(3) Allocating allocated volumes to new ESX serversIf you add new ESX servers to a VMotion environment, allocate the existing allocated volumes to the newESX servers.

Figure 5: (NPIV environment) Allocating allocated volumes to new ESX servers

For HDvM V6

Follow the procedure in section 2.3.2(2) step 1 to add the physical WWN of the new ESX server to the hostgroup.


17/79



For HDvM V7Follow the same procedure in section 2.3.2(2). You should first register the new virtual machines to thelogical group. Perform step 1 and then select the volumes that have been already allocated to virtualmachines. This operation adds the WWNs of new virtual machines to the host group that the alreadyallocated volumes use.

2.4. Managing volume pairs on virtual machinesThe following CCI server configuration is recommended for managing volume pairs on virtual machines.To manage volume pairs on virtual machines, install the HDvM agent and RAID Manager on to a virtualmachine (VM1 in Figure 6) . You can also install the HDvM agent on VM2 and VM3, but are not requiredto.

Figure 6: Recommended CCI server configuration for managing volume pairs on virtualmachines

2.5. Performing disk migration in units of datastores (HTSM)

VMware ESX server virtual disks are created on datastores. Therefore, migrating or backing up datastoresis a convenient way to migrate or back up disks.HTSM migrates disks in migration group units. If you register all the LDEVs for a datastore in the samemigration group, you can migrate disks in units of datastores.When you create a migration group in HTSM, first use the HDvM virtualization server window to confirmthe relationship between datastores and LDEVs, and then register all LDEVs for a datastore in the samemigration group.When you migrate this migration group, all LDEVs that make up the datastore will be migratedautomatically.


18/79



For HDvM V61. In the virtualization server window, select the target ESX server.2. Find the ID of the datastore to be migrated in the File System column of the list of LDEVs.3. Check the volumes (LDEVs) allocated to that datastore.

4. In HTSM, create a new migration group that includes the volumes (LDEVs) you identified in step 1.


19/79



5. Run a migration task for the created migration group (set a task).

For HDvM V7Follow the same procedure as for V6.

2.6. Environment settings for managing ESX servers

This section describes the environment settings required if HDvM manages VMware ESX 4.0 or later. Thefollowing three system configurations are supported:

vMA monitors a VMware ESX server in the same physical environment.(See Figure 7) vMA monitors a VMware ESX server in a different physical environment. (See Figure 8) VMA manages vCenter Server. (See Figure 9)

These configurations require that the monitoring targets have not been registered in vMA.

Figure 7: System configuration in which vMA monitors a VMware ESX server in the same physical environment


20/79


21/79



# ID Description password Remarks

2 Virtualization serveruser ID

For the configurations in Figure 7and Figure 8, vMA is used toacquire information from thevirtualization server.

The password is setwhen the user ID iscreated.

The user must have View permissions or higher.Register the user in thevirtualization server before

performing the proceduresdescribed in this document.

3 VMware vCenterServer user ID

For the configuration in Figure 9, vMA is used to acquire informationfrom VMware vCenter Server.

The password is setwhen the user ID iscreated.

The user must have View permissions or higher.Register the user in avirtualization server before

performing the proceduresin this document.

4 HDvM account name Used to log in to HDvM This password is setwhen an account iscreated.

Use either of the followingaccounts:- System (built-in account)- An account that isassigned to the [AllResources] resource groupand that Modify

permissions.

2.6.1. Setting up vMA monitoring environment Common Physical EnvironmentThis section describes how to set up the configuration in Figure 7, in which vMA monitors a VMware ESXserver in the same (common) physical environment.

2.6.1.1 Registering a monitoring target in vMA

For vMA V4.0To register the VMware ESX server to be monitored by vMA V4.0:1. Use an SSH client or other means to log in to the virtualization server vMA (vMA of virtualization

server A in Figure 7) by using the vMA login ID (usually vi-admin ) and password.2. Run the vMA environment setup script.

1. Run the following command:sudo /etc/vmware/vmware-smis-setup.pl

2. At the Password prompt, enter the password of the vMA standard user vi-admin .

Password: password-for-vi-admin

3. In vMA, set the virtualization server information to be registered in HDvM.1. At the Enter username prompt, enter the virtualization server user ID.

Enter username: user-ID-for-the-VMware-ESX-server

2. At the Enter Password prompt, enter the password of the above user.

Enter Password: password-for-the-VMware-ESX-server Note: The password is not displayed.

3. A message asking whether you want to stop Openwsman is displayed. At the prompt, enter yes .Stopping Openwsman before SMI-S setup!Stop Openwsman for setup [yes/no]?yes

4. A message asking whether you want to stop Pegasus is displayed. At the prompt, enter yes .Stopping Pegasus before SMI-S setup!


22/79



Stop Pegasus for setup [yes/no]?yes

Note: This procedure does not need to be performed if the above prompt is not displayed.

5. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS) forHDvM.

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNSname (hostname.domain)vSphere Server: IP-address-of-the-virtualization-server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNSname (hostname.domain)vSphere Server: host-name-of-the-virtualization-server

6. A message asking whether you want to add Pegasus is displayed. At the prompt, enter yes .Add Pegasus service to chkconfig [yes/no]?yes


7. A message asking whether you want to add Openwsman is displayed. At the prompt, enter yes .Add Openwsman service to chkconfig [yes/no]?yes

8. A message asking whether you want to start Pegasus is displayed. At the prompt, enter yes .Start Pegasus [yes/no]?yes


9. A message asking whether you want to start Openwsman is displayed. At the prompt, enter yes .

Start Openwsman [yes/no]?yes

4. Confirm that the virtualization server information for HDvM is registered correctly.1. Open the following file by using a text editor or display it by using the cat command.

/etc/vmware/vmware-cim-config.xml

2. Confirm that the virtualization server IP address or host name for HDvM described above isregistered in the element.

Example:If the virtualization server IP address for HDvM is 172.10.43.53:

https://172.10.43.53/sdk/webServiceIf the virtualization server host name is VMHITACHI:

https://VMHITACHI/sdk/webService

For vMA V4.1To register the VMware ESX server to be monitored by vMA V4.1:1. Use an SSH client or other means to log in to the virtualization server vMA (vMA of virtualization

server A in Figure 7) by using the vMA login ID (usually vi-admin ) and password.2. In vMA, set the information of a virtualization server to be registered in HDvM.

1. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS) forHDvM by using one of the following commands:

vifp addserver IP-address-of-the-virtualization-server


23/79



Or

vifp addserver host-name-of-the-virtualization-server 2. Enter the virtualization server root user password at the following prompt:

root@ IP-address-of-the-virtualization-server 's password: password-for-root Or

root@ host-name-of-the-virtualization-server 's password: password-for-root Note: The password is not displayed.

3. Run the environment setting script of vMA.1. Run the following command:

sudo /etc/vmware/vmware-smis-setup.sh

2. At the Password prompt, enter the password of the vMA standard user vi-admin .



4. A message asking whether you want to stop Pegasus is displayed. At the prompt, enter yes .Stopping Pegasus before SMI-S setup!Stop Pegasus for setup [yes/no]?yes


5. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS)

described in (2).vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: IP-address-of-the-virtualization-server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: host-name-of-the-virtualization-server






9. A message asking whether you want to start Openwsman is displayed. At the prompt, enter yes .Start Openwsman [yes/no]?yes


24/79



4. Confirm that the virtualization server information for HDvM is registered correctly.1. Open the following file by using text editor or display it by using the cat command.


2. Confirm that the virtualization server IP address or host name for HDvM described in (3) 5) isregistered in the element.Example:If the Virtualization server IP address for HDvM is 172.10.43.53:

https://172.10.43.53/sdk/webService

If the virtualization server host name is VMHITACHI:


2.6.1.2 Registering a virtualization server in the HDvM server

To register a virtualization server in HDvM via vMA:1. Log in to HDvM by using either of the following accounts:

1. System (built-in account)2. An account that meets both of the following conditions:

a) The account is assigned to the All Resources resource group. b) The account has Modify permissions.

2. In the Explorer menu, choose Resources , and then Hosts .3. In the application area, click the Add Virtualization Server button.

The Add Virtualization Server dialog box appears.4. Enter the IP address (IPv4) for vMA of virtualization server A in Figure 7. 5. Select Secure . For the Figure 7 configuration, Secure is the default.6. Enter the vMA login ID (usually vi-admin ) as the user ID.7. Enter the password of the login ID specified in step 7.8. Click the OK button.

2.6.2. Setting up vMA monitoring environments Mixed Physical EnvironmentThis section describes how to set up the configuration in Figure 8, in which vMA monitors a VMware ESXserver in a different (mixed) physical environment.


For vMA V4.0

To register the monitored VMware ESX server in vMA V4.0:1. Use an SSH client or other means to log in to the virtualization server vMA (vMA of virtualization

server A in Figure 8) by using the vMA login ID (usually vi-admin ) and password.2. Run the environment vMA setup script.

1. Run the following command:sudo /etc/vmware/vmware-smis-setup.pl

2. At the Password prompt, enter the password of the vMA standard user vi-admin :


3. In vMA, set the virtualization server information to be registered in HDvM.

1. At the Enter username prompt , enter the virtualization server user ID for HDvM.Enter username: user-ID-for-the-VMware-ESX-server


25/79




Enter Password: password-for-the-VMware-ESX-server Note: The password is not displayed.




5. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS) forHDvM.

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNSname (hostname.domain)vSphere Server: IP-address-of-the-virtualization-server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNSname (hostname.domain)vSphere Server: host-name-of-the-virtualization-server







4. Confirm that the virtualization server information for HDvM is registered correctly.1. Open the following file by using a text editor or display it by using the cat command:


2. Confirm that the virtualization server IP address or host name for HDvM described above isregistered in the element.



If the host name of the virtualization server for HDvM is VMHITACHI:


26/79




For vMA V4.1To register the monitored VMware ESX server in vMA V4.1:1. Use an SSH client or other means to log in to the virtualization server (vMA of virtualization server A

in Figure 8) by using the vMA login ID (usually vi-admin ) and password.2. In vMA, set the virtualization server information to be registered in HDvM.

1. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS) forHDvM by using one of the following commands:

vifp addserver IP-address-of-the-virtualization-server Or

vifp addserver host-name-of-the-virtualization-server

2. Enter the virtualization server root user password at the following prompt:

root@ IP-address-of-the-virtualization-server 's password: password-for-root Or

root@ host-name-of-the-virtualization-server 's password: password-for-root Note: The password is not displayed.

3. Run the vMA environment setup script.1. Run the following command:


2. At the Password prompt, enter the password of vMA standard user vi-admin .





5. Enter the virtualization server IP address (IPv4) or host name (that can be resolved by DNS)described above.vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: IP-address-of-VMware-vCenter-Server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: host-name-of-VMware-vCenter-Server

6. A message asking whether you want to add Pegasus is displayed. At the prompt, enter yes .

Add Pegasus service to chkconfig [yes/no]?yes Note: This procedure does not need to be performed if the above prompt is not displayed.


27/79




8. A message asking whether you want to start Pegasus is displayed. At the prompt, enter yes .

Start Pegasus [yes/no]?yes Note: This procedure does not need to be performed if the above prompt is not displayed.


4. Confirm that the virtualization server information for HDvM is registered correctly in vMA.

1. Open the following file by using text editor or display it by using the cat command:/etc/vmware/vmware-cim-config.xml

2. Confirm that the virtualization server IP address or host name for HDvM described in (3) 5) isregistered in the element.



If the host name of the virtualization server for HDvM is VMHITACHI:


2.6.2.2 Registering a virtualization server in the HDvM serverTo register a virtualization server in HDvM via vMA (vMA of virtualization server A in Figure 8) :1. Log in to HDvM by using either of the following accounts:


a) The account is assigned to the All Resources resource group. b) The account has Modify permissions.


The Add Virtualization Server dialog box appears

4. Enter the IP address (IPv4) for vMA of virtualization server A in Figure 8. 5. Select Secure . For the Figure 8 configuration, Secure is the default.6. Enter the vMA login ID (usually vi-admin ) as the user ID.7. Enter the password of the user ID specified in (7).8. Click the OK button.

2.6.3. Setting up a system in which vMA monitors VMware vCenter ServerThis section describes how to set up the configuration in Figure 9, in which vMA monitors VMwarevCenter Server.


28/79




For vMA V4.0To register VMware vCenter Server to be monitored by vMA V4.0:1. Use an SSH client or other means to log in to vMA of the virtualization server (virtualization server A

in Figure 9) by using the vMA login ID (usually vi-admin ) and password.

2. Run the vMA environment setup script:1. Run the following command:

sudo /etc/vmware/vmware-smis-setup.pl

2. At the Password prompt, enter the password of the vMA standard user vi-admin :


3. In vMA, set the information of VMware vCenter Server for HDvM.1. At the Enter username prompt, enter the VMware vCenter Server user ID.

Enter username: user-ID-for-VMware-vCenter-Server


Enter Password: password-for-VMware-vCenter-Server Note: The password is not displayed.




5. Enter the VMware vCenter Server IP address (IPv4) of or host name (that can be resolved by DNS)for HDvM.

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNSname (hostname.domain)vSphere Server: IP-address-of-VMware-vCenter-Server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully Qualified DNS

name (hostname.domain)vSphere Server: host-name-of-VMware-vCenter-Server






29/79





4. Confirm that the virtualization server information is registered correctly in vMA.1. Open the following file by using a text editor or display it by using the cat command:


2. Confirm that the VMware vCenter Server IP address or host name for HDvM described above isset in the element.

Example:If the IP address of VMware vCenter Server for HDvM is 172.10.43.53:


If the host name of VMware vCenter Server for HDvM is VCHITACHI:

https://VCHITACHI/sdk/webService

For vMA V4.1To register VMware vCenter Server to be monitored by in vMA V4.1:

1. Use an SSH client or other means to log in to the vMA virtualization server (vMA of virtualizationserver A in Figure 9) by using the vMA login ID (usually vi-admin ) and password.

2. In vMA, set the VMware vCenter Server information to be registered in HDvM.1. Enter the VMware vCenter Server IP address (IPv4) or host name (that can be resolved by DNS)

for HDvM by using the following commands:

vifp addserver IP-address-of- VMware-vCenter-Server Or

vifp addserver host-name-of- VMware-vCenter-Server

2. Enter the VMware vCenter Server (VMware vCenter Server in Figure 9) root user password at thefollowing prompt:

Enter username for IP-address-of-VMware-vCenter-Server 's password:user-ID-for-VMware-vCenter-Server

Or

Enter username for host-name-of- VMware-vCenter-Server 's password:user-ID-for-VMware-vCenter-Server

3. Enter the password for the VMware vCenter Server user ID described above at the following prompt:

user-ID-for-VMware-vCenter-Server @ IP-address-of- VMware-vCenter-Server 'spassword: password-for-VMware-vCenter-Server

Or

user-ID-for-VMware-vCenter-Server @host-name-of- VMware-vCenter-Server 'spassword: password-for-VMware-vCenter-Server

Note: The password is not displayed.

4. A message asking whether you want to store the user ID and password in a credential store eventhough doing so is a security risk is displayed. At the prompt, enter yes .

This will store username and password in credential store which isa security risk. Do you want to continue?(yes/no): yes


30/79



3. Run the vMA environment setup script:1. Run the following command:


2. At the Password prompt, enter the password of the vMA standard user vi-admin .Password: password-for-vi-admin




5. Enter the VMware vCenter Server (VMware vCenter Server in Figure 9) IP address (IPv4) or hostname (that can be resolved by DNS) described above.

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: IP-address-of-VMware-vCenter-Server

Or

vSphere Server must be an IPv4 address (xx.xx.xx.xx) or Fully QualifiedDNS name (hostname.domain)vSphere Server: host-name-of-VMware-vCenter-Server







4. Confirm that the information of the VMware vCenter Server is registered correctly in vMA.

1. Open the following file by using text editor or display it by using the cat command:/etc/vmware/vmware-cim-config.xml

2. Confirm that the VMware vCenter Server IP address or host name for HDvM described above isregistered in the element.


31/79



Example:If the IP address of VMware vCenter Server for HDvM is 172.10.43.53:


If the host name of VMware vCenter Server for HDvM is VCHITACHI:


2.6.3.2 Registering a virtualization server in the HDvM server

To register a virtualization server in HDvM via vMA (vMA of Virtualization server A in Figure 2-3):1. Login to HDvM by using either of the following accounts:


a) The account is assigned to the All resources resource group. b) The account has Modify permissions.


The Add Virtualization Server dialog box appears.4. Enter the IP address (IPv4) for vMA of virtualization server A in Figure 9. 5. Select Secure . For the Figure 9 configuration, Secure is the default.6. Enter the vMA login ID (usually vi-admin ) as a user ID.7. Enter the password of the user ID specified in (7).8. Click the OK button.

2.7. Environment settings for installing the HDvM agent on a virtual machine thatuses NPIV

This section provides notes and cautions for using the HDvM agent in a virtual environment that usesVMware ESX 4.0 or later.

2.7.1. Configuration

When using the HDvM agent in a VMware ESX 4.0 or later environment, the problems described belowmay occur. If they do, perform the indicated procedure.

In an environment in which virtual WWNs are assigned to virtual machines by using NPIV(N_Port_ID Virtualization), hosts or volumes cannot be managed because a conflict exists between thevirtualization server's physical WWN and the virtual WWNs of the virtual machines. If this problemoccurs, perform the procedures described in sections 2.6.2.2(2) and 2.6.2.2(3).

When manually creating, deleting or changing the status of copy pairs, the copy pair type is sometimes

displayed incorrectly. If this problem occurs, perform only the procedure described in section2.6.2.2(3).

2.7.2. Setting procedure for the HDvM server

(1) Prerequisites

The following conditions need to be met to register virtual WWNs in the HDvM server: The HDvM server must be installed on a Windows host. A virtual machine exists on which the HDvM agent and VMwareTools are installed.

(2) Setting procedure

(a) Generate a virtual WWN definition file npivmapping.properties.Generate a virtual WWN definition file by running the createnpivinfo command for the ESX server (orvCenter Server that manages the ESX server) of the target virtual machine.


32/79


33/79



server.properties .2. Run the following commands to restart the services of the HDvM agent:

installation-folder-of-the-HDvM-agent \bin\hbsasrv.exe stop installation-folder-of-the-HDvM-agent \bin\hbsasrv.exe start

Notes:

Backup servers are not supported in virtualization environments. Therefore, configure the backupserver on a server that is not in a virtualization environment. The above procedures do not update copy pair statuses. To update the statuses, refresh the storage

systems. For VMware ESX 4.0 or later, create command devices before allocating volumes to virtual machines.

If command devices are created after volumes are allocated to a virtual machine, the virtualizationserver needs to be restarted so that the command devices can be recognized.


34/79



3. Performance Management (HTnM and HTnM Agent)

In the following cases, special points must be considered when using Tuning Manager to monitor VMwareESX 4.0 or later:

When monitoring NPIV environments When changing the configuration of pair volumes When migrating LDEVs When setting the command device attribute

The sections below provide details on these cases.

3.1. Prerequisite version of Device Manager

When monitoring VMware ESX 4.0 or later, the following version of Device Manager is required: When using Device Manager Version 6: V6.4.0-06 or later When using Device Manager Version 7: V7.0.1 or later

For details on configuring Device Manager, see 2. Resource Management (HDvM, HTSM, and HDvM Agent) .

3.2. Notes about monitoring NPIV environments

When monitoring an NPIV environment provided by VMware ESX 4.0 or later, note the following.

(1) Physical WWNs are displayed for HBA port WWNs.

(a) Main Console GUI

The physical WWN assigned to an HBA is displayed for the WWN associated with a host.To display the HBA WWN:1. From the Explorer area, select Hosts .

2. Select the guest OS.3. From Device Files , select the target device file.4. In the report area, select the Details tab.The Host Port Node WWN and Host Port WWN fields in the report area indicate the HBA's physicalWWN.


35/79


36/79



The following window shows an example of a virtual WWN of an HBA associated with a host:


37/79



3.3. Notes about changing the configuration of pair volumes

When the pair volume information below provided by Hitachi Tuning Manager Agent for Server Systemis exported, even if the configuration has changed, information from before the change is output. Theinformation is updated when the virtualization server is restarted.

Record File System Configuration (PD_FSC)

Field P/S Volume (P_PAR_S_VOLUME)

The following window shows an example of pair volume information in the Performance Reporter GUI:

To use Device Manager s All Storage view to confirm the current pair volume information withoutrebooting the virtual server:1. From the Explorer area, select All Storage .2. Select the target storage system from the list of storage systems.3. Select Open-Allocated for the target storage system.4. Check Copy Type in the LDEV list.

The following window shows an example of pair volume information:


38/79



3.4. Notes about migrating LDEVs

When the LDEV parity group information below provided by Hitachi Tuning Manager Agent for ServerSystem is exported, even if the configuration has changed, information from before the change is output.The information is updated when the virtualization server is restarted.

Record File System Configuration (PD_FSC)

Field RAID Group Number (RAID_GROUP_NUMBER)

RAID Level (RAID_LEVEL)

The following window shows an example of parity group information in the Performance Reporter GUI:

To confirm the current parity group information without rebooting the virtual server, refer to either of thefollowing:

LDEV list of the LDEV folder in the Main Console GUI Summary information for an LDEV in the Main Console GUI


39/79



The following window shows an example of an LDEV list in the LDEVs folder in the Main Console GUI:


40/79



The following window shows an example of summary information for an LDEV in the Main Console GUI:


41/79



3.5. Notes about setting the command device attribute

If you are running Hitachi Tuning Manager - Agent for RAID on a guest OS on a virtualization server (hostOS), be sure to set the command device attribute to a logical device before setting an LU path to the logicaldevice on the host OS.Agent for RAID will not recognize the attribute change if you set an LU path to a logical device on thevirtualization server before setting the command device attribute to the logical device. For this case, thefollowing will occur:

The command device is not listed in the output of the jpctdlistraid command. If you create an instance of Agent for RAID by specifying the command device, you can start the

services of Agent for RAID, but the jpctdchkinst command will output the following error messageto the standard output: KAVF18852-E The device set by the agent instance parameter is nota command device.

To recover from this error, perform either of the following procedures: Perform the following to delete and then re-set the LU path to the command device:

1. Use Storage Navigator to delete the LU path to the command device on the virtualization server,and then make sure that the command device is no longer available on the virtualization server.

2. Use Storage Navigator to re-set the LU path to the command device, and then make sure that thecommand device is available on the virtualization server again.

3. Make the command device available on the guest OS. Restart the virtualization server.


42/79



4. Backup and Restore Management (HPtM and HRpM)

4.1. HPtM/HRpM Application Agent (CLI)

HPtM/HRpM Application Agent (CLI) is hereafter abbreviated as HPtM.

4.1.1. HPtM for SQL Server

4.1.1.1 Supported versions of VMware

HPtM supports backup and restore operations for Exchange Server database in Windows guest OSs in thefollowing virtual environments.

VMware ESX 4.0 VMware ESX 4.1 VMware ESXi 4.0 VMware ESXi 4.1

Prerequisites for using VMware environments:

HPtM can back up only Raw LUNs to which RAW device mapping has been applied by using the physical compatibility mode.

Do not run live migrations (for example, VMware VMotion) and HPtM commands concurrently, because HPtM commands may fail. If an HPtM command fails, perform the countermeasuresdescribed for the error messages.

HPtM does not support VMware HA (High Availability).

4.1.1.2 Supported configurations

Database servers in virtual environments are supported.The supported backup server configuration depends on the operations to be performed. Table 5 describesthe supported backup server configurations for HPtM. If HPtM is not used on the backup server, see section

4.1.1.2(4).Table 5: Supported backup server configurations for HPtM (SQL Server)

Number ofsecondary volumegenerations

With tape backup operations Without tape backupoperations

Server in a virtualenvironment

Server not in avirtual environment

No backup server

1 Supported #1 See section 4.1.1.2(1)

Supported SupportedSee section 4.1.1.2(3)

2 or more Not supported #2, #3 SupportedSee section4.1.1.2(2)

#1: Secondary volumes do not have to be concealed from the OS on the backup server. Therefore, either donot specify the DEVICE_DETACH parameter in the RAID Manager-linkage definition file ( DEFAULT.dat ) orspecify DISABLE for this parameter. This parameter enables the functionality for concealing secondaryvolumes.#2: HPtM does not support backup servers in these virtual environments because secondary volume must

be concealed from the OS.#3 This operation is supported in configurations in which only the secondary volumes of the firstgeneration are connected to the backup server.

About HPtM functionality for concealing secondary volumesHPtM provides functionality for concealing secondary volumes to avoid disk-signatures from beingchanged.When a primary volume is replicated to multiple secondary volumes, some secondary volumes might havethe same disk-signature as the primary volume.


43/79



When a Windows OS recognizes multiple disks that have the same disk-signature, it automatically changesthe disk-signature so that each disk has a unique value. As a result, the disk-signatures of the primaryvolume and secondary volumes become different, and errors may occur during restore operations.

(1) Configuration with one generation of secondary volumes and tape backup operationsThe backup server can be configured in a virtual environment because secondary volumes do not have to beconcealed.

Figure 10: Configuration with one generation of secondary volumes and tape backupoperations


44/79



(2) Configuration with multiple generations of secondary volumes and tape backup operationsThe backup server cannot be configured in a virtual environment because secondary volumes must beconcealed. In this configuration, HPtM dynamically notifies the operating system of the secondary volumesof only one generation if needed.

Figure 11: Configuration with multiple generations of secondary volumes and tape backupoperations


45/79



(3) Configuration without tape backup operationsHPtM supports the following configuration:

Figure 12: Configuration without tape backup operations

(4) Other cases (HPtM is not used on the backup server) Note the following if HPtM is not installed on a backup server to which secondary volumes are connected:

When performing tape backup, use RAID Manager or Windows commands to mount and unmountsecondary volumes.

Also, note the following points, which are the same as when using HPtM: When running backup, restore, or resync operations, make sure that secondary volumes are not

mounted. Also, disable the OS functionality to automatically mount new volumes by using thediskpart command. If this functionality is not disabled, the OS might automatically mount volumes.For details about how to disable the OS functionality to automatically mount new volumes, see theHPtM documentation.

If multiple generations of secondary volumes are used, the problem described in About HPtM functionality for concealing secondary volumes in section 4.1.1.2 may occur. Therefore, werecommend using a backup server that is not in a virtual environment.


46/79



Figure 13: Other cases (HPtM is not used on the backup server)


47/79



4.1.1.3 System configuration example

The following figure shows an example SQL Server system configuration:


48/79



Figure 14: Software and hardware configuration


49/79



4.1.1.4 Expected operations

The following figure shows the expected backup and restore operations:

Figure 15: Expected SQL Server backup and restore operations

Table 6: Explanation of expected SQL Server backup and restore operations (based on)

Symbol OperationType

Execution server ExecutionTiming

Description Note

B(01) Backup(D2D2T)

Database server Scheduled(0:00)

Backup operation from the P-VOL to the firstgeneration S-VOL and a tape device.

See section4.1.1.5(1)

B(02) Backup(D2D)


Backup operation from the P-VOL to thesecond generation S-VOL.

See section4.1.1.5(2) #1, #2

B(03) Backup(D2D)


Backup operation from the P-VOL to thethird generation S-VOL.

See section4.1.1.5(2) #1, #2

C(11) Data copy(D2D)

Backup server anddevelopment server

On demand Operation to copy backup data (acquired byB(01)) from the first generation S-VOL to a

leaf S-VOL. The leaf S-VOL is used fordevelopment, not restore operations.

See section4.1.1.5(3) #3, #4

R(T) Restore(T2D)

Backup server On demand Operation to copy backup data (acquired byB(01)) from tape device to the first generationS-VOL.


R(01) Restore(D2D)

Database server On demand Operation to restore backup data (acquired byB(01) or restored by R(T)) from the firstgeneration S-VOL to the P-VOL.


R(02) Restore(D2D)

Database server On demand Operation to copy backup data (acquired byB(02)) from the second generation S-VOL tothe P-VOL.

See section4.1.1.5(5) #1

R(03) Restore

(D2D)

Database server On demand Operation to copy backup data (acquired byB(03)) from the third generation S-VOL tothe P-VOL.

See section4.1.1.5(5) #1


50/79



Notes:#1: Use this operation only if multiple generations are configured.#2: B(02) and B(03) are not backed up to a tape device. To avoid disk-signature conflicts with the firstgeneration S-VOL, do not allocate the second or third generation S-VOL to the backup server.#3: Do not perform C(11) while B(01) is running because doing so might cause a backup error in B(01).#4: Do not perform C(11) for S-VOLs that contain system databases. This operation is intended for copyinguser databases for development purposes using SQL Server on the development server.

4.1.1.5 SQL Server backup and restore operations

(1) Backup operation B(01)This section describes how to perform a backup from the P-VOL to the first generation S-VOL (MU#0) andthe tape device.

Server preparations

1) Start Protection Manager Service on the backup server.Before installing HPtM, prepare a user account for starting Protection Manager Service that has thefollowing permissions:

Local Administrator permissions Log on as a service permission Permissions to run tape backup software

2) Create a user script on the database server.Create the HPtM user script for performing D2D2T backup on the database server.Location of the HPtM user script:

Server: Database server

Example file name: C:\work\UserScript.txt

Sample HPtM user script ( UserScript.txt ):

LOCAL_BACKUP=YES# Pre-processing section[PRE_PROC]# Clearing of the secondary volume cache (mounting and unmounting)[CMD]CMDLINE=" C:\Program Files (x86)\HITACHI\DRM\bin\drmmount.exe" -copy_group G01,v01END_CODE=TERMINATE_NZTIMEOUT=0LOCATION=REMOTEPARENT_STAT=NORMAL[CMD]CMDLINE="C:\Program Files (x86)\HITACHI\DRM\bin\drmmount.exe" -copy_group G01,v02END_CODE=TERMINATE_NZTIMEOUT=0LOCATION=REMOTEPARENT_STAT=NORMAL[CMD]CMDLINE="C:\Program Files (x86)\HITACHI\DRM\bin\drmumount.exe" -copy_group G01,v01END_CODE=TERMINATE_NZTIMEOUT=0LOCATION=REMOTEPARENT_STAT=NORMAL[CMD]

CMDLINE="C:\Program Files (x86)\HITACHI\DRM\bin\drmumount.exe" -copy_group G01,v02END_CODE=TERMINATE_NZTIMEOUT=0


51/79



LOCATION=REMOTEPARENT_STAT=NORMAL#Post-processing section[POST_PROC]#Tape backup of the secondary volume[CMD]

# Batch file for tape backupCMDLINE=C:\work\tapebackup.batEND_CODE=TERMINATE_NZTIMEOUT=0LOCATION=REMOTEPARENT_STAT=NORMAL

3) Create a tape backup batch file on the backup server.Create a tape backup batch file to be called by the user script, and store it in the location coded in the userscript.Location of the tape backup batch file:

Server: Backup serverExample file name: C:\work\tapebackup.bat

Sample tape backup batch file ( tapebackup.bat ):

rem [Export Backup Catalog]rem Export and save the backup catalogrem by specifying the Backup ID imported on the backup server."C:\Program Files (x86)\HITACHI\DRM\bin\drmdbexport.exe" %DRMENV_R_BACKUPID% -fC:\BackupCatalog\HPTM_BACKUPCAT.drm

rem [Tape Backup]

rem Environment variable "DRMENV_COMMENT" can be usedrem for referencing the backup comment specified in the HPtM backup command.rem Make sure to include both the S-VOL mount pointrem and the exported backup catalog file in the tape backup target.


52/79



-auto_import Transfer the backup catalog to the backup server.

-auto_mount Mount the secondary volume.

-comment comment Specify the backup comment.

-rc local_0 Specify to use the first generation S-VOL (MU#0). Note: The -svol_check option cannot be used.

Server operations

1) Run the scheduled backup job on the database server.

(2) Backup operations B(02) and B(03)This section describes how to perform a backup from the P-VOL to the second generation S-VOL (MU#1)and third generation S-VOL (MU#2).

Server preparations

1) Create a backup job for the second generation S-VOL (MU#1) on the database server.

Use the following command to create a job, and then schedule it to be run at 8:00.drmsqlbackup instance-name comment comment rc local_1

Description of options:

-rc local_1 Specify to use second generation S-VOL (MU#1). Note: The -svol_check cannot be used.

2) Create a backup job for the third generation S-VOL (MU#2) on the database server.Use the following command to create a job, and then schedule it to be run at 16:00.

drmsqlbackup instance-name comment comment rc local_2

Description of options:

-rc local_2 Specify to perform backup using the third generation S-VOL (MU#2). Note: The -svol_check cannot be used.

Server operations

1) Run the scheduled backup jobs on the database server.

(3) Data copy operation C(11)This section describes how to copy backup data from the first generation S-VOL (MU#0) to a leaf S-VOLfor development purposes.

Server preparations

1) Acquire volume names on the development server.Acquire the volume names to be used for mounting volumes.Before the following procedures, assign a mount point to each volume and acquire the volume names asfollows.

C:\Windows\system32\mountvol- - - - - - (Snip) - - - - - -Current mount point and possible volume names:

\\?\Volume{94cd5098-01dc-11e0-8a88-806e6f6e6963}\F:\

\\?\Volume{94cd5099-01dc-11e0-8a88-806e6f6e6963}\G:\

- - - - - - (Snip) - - - - - -


53/79



2) Disable automatic mounting of new volumes on the development server.Automatic mounting of new volumes must be disabled.To disable the automatic mounting of new volumes:

1. At the command prompt, run diskpart .2. Run automount to display current status.

3. If Automatic mounting of new volumes enabled is displayed, run automount disable to disablethe automatic mounting of new volumes.4. Run exit to exit the diskpart command.

Example:

Server operations

1) Detach SQL Server databases on the development server.If SQL Server databases are in use on the development server, take them offline and detach them.Example:

In a script file (for example, detach_db.sql ), define SQL queries to take SQL Server databases offlineand detach them. To run the script file, use the sqlcmd command as follows.

sqlcmd E i C:\work\detach_db.sql

Sample script file for detaching SQL Server databases ( detach_db.sql ):

use [master]goalter database [DB1] set offline with rollback immediategoalter database [DB2] set offline with rollback immediategosp_detach_db @dbname = N'DB1'gosp_detach_db @dbname = N'DB2'go

2) Unmount leaf S-VOLs from the development server and take them offline.If leaf S-VOLs are mounted on the development server, unmount them and take them offline.


54/79



1. Unmount Leaf S-VOLs.Example:

Unmount leaf S-VOLs mounted to the F G drives by using the Windows MOUNTVOL command.

C:\Windows\system32\mountvol F: /PC:\Windows\system32\mountvol G: /P

2. Take leaf S-VOLs offline.Example:In a script file (for example, offline_disk.txt ), define commands to take leaf S-VOLs disk10 anddisk11 offline. To run the script file, use the diskpart command as follows.

C:\Windows\system32\diskpart /s C:\work\offline_disk.txt

Sample script file for taking disks offline ( offline_disk.txt ):

select disk 10offline diskselect disk 11offline disk

3) Copy the S-VOL to the leaf S-VOL on the backup server.To copy data from the S-VOL to the leaf S-VOL:

1. Make sure that the pair status for the S-VOL is SSUS .2. Resync the pairs.3. Split the pairs.

Example:

In a script file (for example, Copy_Data_for_Develop.bat ) use CCI (RAID Manager) commands to

define the three procedures above, and then run the script file.

Sample script file for copying from a S-VOL to a leaf S-VOL ( Copy_Data_for_Develop.bat ):

echo offsetlocalrem *********************************************echo Processing to copy from an S-VOL to a leaf S-VOL will now start.echo Now checking whether the S-VOL status is "SVOL_PSUS"...C:\HORCM\etc\pairvolchk -ISI1001 -g G01 -ssIF NOT %ERRORLEVEL%==34 goto ERRORecho The status of the S-VOL is "SVOL_PSUS".rem *********************************************echo The copy pair will now be resynchronized...C:\HORCM\etc\pairresync -ISI2000 -g G11IF NOT %ERRORLEVEL%==0 goto ERRORC:\HORCM\etc\pairevtwait -ISI2000 -g G11 -s pair -t 3600IF NOT %ERRORLEVEL%==0 goto ERRORrem *********************************************echo The copy pair will now be split...C:\HORCM\etc\pairsplit -ISI2000 -g G11IF NOT %ERRORLEVEL%==0 goto ERRORC:\HORCM\etc\pairevtwait -ISI2000 -g G11 -s psus -t 3600IF NOT %ERRORLEVEL%==0 goto ERRORrem *********************************************

echo Processing to copy from an S-VOL to a leaf S-VOL finished.exit /B 0:ERROR


55/79



echo Processing to copy from an S-VOL to a leaf S-VOL terminated with an error.exit /B 1

endlocal

4) Bring the leaf S-VOLs online on the development server and mount them.Bring the leaf S-VOLs with copied data online, and then mount them on the development server.1. Bring the leaf S-VOLs online.

Example:

In a script file (for example, online_disk.txt ), define commands to put leaf S-VOLs disk10 anddisk11 online. To run the script file, use the diskpart command as follows.

C:\Windows\system32\diskpart /s C:\work\online_disk.txt

Sample script file for putting disks online ( online_disk.txt ):

select disk 10

online diskattribute disk clear readonlyselect disk 11online diskattribute disk clear readonly

2. Mount the leaf S-VOLsExample:Mount the leaf S-VOLs as the F and G drives by using the Windows MOUNTVOL command.

C:\Windows\system32\mountvol F: \\?\Volume{94cd5098-01dc-11e0-8a88-806e6f6e6963}\C:\Windows\system32\mountvol G: \\?\Volume{94cd5099-01dc-11e0-8a88-806e6f6e6963}\

Note: For the second argument of MOUNTVOL command, specify the volume names acquired in step 1 ofServer preparations .

5) Attach SQL Server databases on the development server.Attach the SQL Server databases on the development server and make them ready to use.Example:

In a script file (for example, at tach_db.sql ), define SQL queries to attach the SQL Server databases. Torun the script file, use the sqlcmd command as follows.

sqlcmd E i C:\work\attach_db.sql

Sample script file for attaching SQL Server databases ( attach_db.sql ):

use [master]gosp_attach_db @dbname = N'DB1',@filename1 = N'F:\MSSQL\DB1.mdf',@filename2 = N'F:\MSSQL\DB1_log.ldf';gosp_attach_db @dbname = N'DB2',@filename1 = N'F:\MSSQL\DB2.mdf',@filename2 = N'F:\MSSQL\DB2_log.ldf';go


56/79



(4) Restore operation R(T)This section describes how to restore backup data from a tape device to an S-VOL.

Server operations

1) Mount the S-VOLs on the backup server.Mount the S-VOLs by using HPtM.Example:

drmmount copy_group G01,v01drmmount copy_group G01,v02

2) Tape restore from the tape device to the S-VOLs on the backup server.Restore the backup data and backup catalog from the tape device by using backup software.

3) Unmount the S-VOLs from the backup server.Unmount the S-VOLs by using HPtM.Example:

drmumount copy_group G01,v01drmumount copy_group G01,v02

4) Transfer the backup catalog from the backup server.Transfer the backup catalog file to the database server by using FTP or another such method.

(5) Restore operations R(01), R(02) and R(03)This section describes how to restore backup data from an S-VOL to a P-VOL.

Server operations

1) Import the backup catalog on the database server.If a backup of the catalog file was transferred from the backup server, import it by using HPtM.Example:

drmdbimport f C:\BackupCatalog\HPTM_BACKUPCAT.drm

2) Select restore targets on the database server.

Identify the backup ID of each restore target by using HPtM.Example:

PROMPT>drmappcat -comment *BACKUP-COMMENT BACKUP-ID BACKUP-MODE BACKUP-OBJECT START-TIME END-TIMEMU0_Backup 0000000411 ONLINE MSSQL 2010/12/11 00:00:00 2010/12/1100:01:00MU1_Backup 0000000409 ONLINE MSSQL 2010/12/10 08:00:00 2010/12/1008:01:00MU2_Backup 0000000410 ONLINE MSSQL 2010/12/10 16:00:00 2010/12/1016:01:00

To identify the backup to be restored, use the backup start time ( START TIME).


57/79


58/79




59/79



(1) Configuration with VSS backup mode, multiple generations of secondary volumes, andtape backup operations

The backup server cannot be configured in a virtual environment because secondary volumes must beconcealed. In this configuration, HPtM dynamically notifies the operating system of the secondary volumesof only one generation if needed.

Figure 16: Configuration with VSS backup mode, multiple generations of secondary volumes,and tape backup operations


60/79


61/79



(3) Configuration with cold backup mode, multiple generations of secondary volumes, andtape backup operations


Figure 18: Configuration with cold backup mode, multiple generations of secondary volumes,and tape backup operations


62/79



(4) Configuration with cold backup mode and no tape backup operationsHPtM supports the following configuration:

Figure 19: Configuration with cold backup mode and no tape backup operations

4.1.3. HPtM for file systems

4.1.3.1 Supported versions of VMware

HPtM supports backup and restore operations for file systems in Windows guest OSs in the followingvirtual environments:

VMware ESX 4.0 VMware ESX 4.1 VMware ESXi 4.0 VMware ESXi 4.1

Prerequisites for using VMware environments: HPtM can back up only Raw LUNs to which RAW device mapping has been applied by using the

physical compatibility mode. Do not run live migrations (for example, VMware VMotion) and HPtM commands concurrently,

because HPtM commands may fail. If an HPtM command fails, perform the countermeasuresdescribed for the error messages.

HPtM does not support VMware HA (High Availability).

4.1.3.2 Supported configurations

Database servers in virtual environments are supported.The supported backup server configuration depends on the operations to be performed. Table 8 describes

the supported backup server configurations for HPtM. If HPtM is not used on the backup server, see section4.1.3.2(5).


63/79


64/79



(1) Configuration with VSS backup mode, multiple generations of secondary volumes, andtape backup operations


Figure 20: Configuration with VSS backup mode, multiple generations of secondary volumes,and tape backup operations


65/79



(2) Configuration with VSS backup mode, multiple generations of secondary volumes, and notape backup operations


Figure 21: Configuration with VSS backup mode, multiple generations of secondary volumes,and no tape backup operations


66/79



(3) Configuration with cold backup mode, one generation of secondary volumes, and tapebackup operations

The backup server can be configured in a virtual environment because secondary volumes do not have to beconcealed.

Figure 22: Configuration with cold backup mode, one generation of secondary volumes, andtape backup operations


67/79



(4) Configuration wit

HCS Best Practice guide for VMware ESXi 4.x ConfigGuide v3.2 English

Documents

Transcript of HCS Best Practice guide for VMware ESXi 4.x ConfigGuide v3.2 English