Hp расширяет возможности виртуального хранилища

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.

•A virtualized SAN configuration, including VSM entities that are defined and configured by users through VSM client sessions and by the active VSM server. These entities can only be managed by the active VSM server of the domain to which they belong. For example:

•Storage pools are created per domain, only using the back-end LUs that the VSM server(s) of that domain manage.

•Virtual disks are created per domain, with storage capacity allocated only from the storage pools of the domain.

•Snapshots are created per domain from only virtual disks of the domain.

•Virtual Disk Groups (VDGs) are created per domain, consisting only of virtual disks and snapshots of the domain.

VSM saves the virtual configuration in a database. The database setup file is saved in a dedicated VSM virtual disk (the setup virtual disk) that resides on SAN back-end LUs managed in the domain and is synchronously mirrored to at least two additional copies, preferably configured to reside on different storage pools.

Hosts may be exposed to more than one domain and non-virtualized storage.

You can interconnect domains to enable data transfer between them using VSM services, such as remote mirror or Continuous Access. When an SVSP domain is connected to another SVSP domain, the active VSM server creates a domain entity for the remote domain, which is displayed by the VSM client. For information about how to interconnect two domains, see the HP StorageWorks SAN Virtualization Services Platform administrator guide.

An enterprise often has one domain per site or per SAN.

You can:

•View the domains list

•View domain information

•Delete domains

Viewing the SVSP domains list

The SVSP domains list includes your local SVSP domain and all SVSP domains exposed to your local SVSP domain:

In the navigation tree, click the SVSP domains node. The SVSP domains list appears in the list area.

2 Operations

Power down the server

WARNING!

To reduce the risk of personal injury, electric shock, or damage to the equipment, remove the power cord to remove power from the server. The front panel Power On/Standby button does not completely shut off system power. Portions of the power supply and some internal circuitry remain active until AC power is removed.

IMPORTANT:

If installing a hot-plug device, it is not necessary to power down the server.

1.Back up the server data.

2.Shut down the operating system as directed by the operating system documentation.

3.If the server is installed in a rack, press the UID LED button on the front panel. Blue LEDs illuminate on the front and rear panels of the server.

4.Press the Power On/Standby button to place the server in standby mode. When the server activates standby power mode, the system power LED changes to amber.

5.If the server is installed in a rack, locate the server by identifying the illuminated rear UID LED button.

6.Disconnect the power cords.

The system is now without power.

1 Overview

The VSM application programming interface (API) and command line interface (CLI) allows storage arrays to perform sophisticated virtualization tasks by calling functions from a VSM library loaded in every client server. This VSM library communicates with the VSM device driver and with the VSM itself.

Use the SVSP CLI to run individual commands and script files for virtualization tasks. Except where noted, the CLI commands are OS-independent. The commands are passed through the Fibre Channel SAN (not the LAN) to the VSM, which enhances the reliability of the operations by taking advantage of the SAN’s redundant components.

The VSM CLI is a separate software package that can be installed on a host connected to SVSP. To install the VSM CLI:

1.Insert the SVSP software CD into the host.

2.From the main menu, select Browse to VSM CLI Packages.

3.Right-click the applicable package and select Save As.

The VSM CLI is best suited for whenever automation or integration into an application is needed. Predefined scripts, typically linked with host-based scripts, run on a scheduled basis to relieve an administrator from having to perform daily tasks at specific times. The combination of VSM CLI commands and hosts scripts interact with the application to ensure the best possible consistency of data.

The most common uses for the VSM CLI are:

•Automated creation and deletion of PiTs—The PiT mechanism is a key functionality of SVSP and is used within many features.

•Integrating with applications to create transaction-consistent PiTs—Backup processes can be improved by providing the backup server with access to production data through the SAN. A snapshot created on a PiT can be mapped to the backup server directly. This provides full access to the snapshot for server-free and LAN-free backups.

•Reporting—Use snapshots or copies to refresh the data of reporting servers. Reporting servers do not necessarily need live access to the data kept databases, for example. Because PiTs taken at consistent states are like freezing the source data, the reports run on this data are based on data in an optimal state.

Use the VSM CLI to perform:

•Basic operations available through the GUI except creating stripe sets and pools, and adding presentations to virtual disks.

•Snapshots

•Snapclones

•Migrations

•Mirrors

Продукты IBM для виртуализации СХД

На рынке корпоративных систем хранения с технологией виртуализации не так много крупных игроков. Остановимся подробнее на том, что предлагает компания IBM.

IBM Storwize V5030

Это инновационная система хранения, которая способна упростить масштабирование уже существующей инфраструктуры. Ее кластерные системы поддерживают растущие потребности бизнеса и упрощают контроль над затратами на каждом этапе внедрения. Благодаря технологии шифрования она обеспечивает защиту и внутренней, и виртуальной среды хранения. Еще один плюс – графический интерфейс, который делает управление системой более простым и понятным.

В распоряжении IBM Storwize V5030два контроллера с кэш-памятью на 32/64 ГБ, два шестиядерных процессора и широкий перечень средств коммуникации: 10 ГБ iSCSI, 1ГБ iSCSI, 16Г ГБ FC, 12 ГБ SAS, 10 ГБ iSCSI/FCoE. Система поддерживает до 504 накопителей с 20 модулями расширения, максимальный объем – 7,74 ПБ (при внешней виртуализации – до 32 ПБ).

IBM Storwize V5030 F

Система отличается повышенной гибкостью управления флеш-массивами AFA. Она увеличивает производительность и эффективность, обеспечивает безопасность и масштабируемость на более продвинутом уровне, чем стандартные (HDD) и гибридные накопители. Возможности флеш-массивов способны удовлетворить потребность в надежном хранилище с высокой скоростью доступа к данным. Увеличится пропускная способность системы, одновременно снизится потребление энергии и уменьшится стоимость владения.

В распоряжении IBM Storwize V5030Fдва контроллера с кеш-памятью на 32 ГБ, два шестиядерных процессора и широкий спектр средств коммуникации: 10 ГБ iSCSI, 1ГБ iSCSI, 16Г ГБ FC, 12 ГБ SAS, 10 ГБ iSCSI/FCoE. Система поддерживает до 504 накопителей с 20 модулями расширения, максимальный объем – 7,74 ПБ (при внешней виртуализации – до 32 ПБ). В качестве 2,5-дюймовых флеш-накопителей используются высокопроизводительные SSDs (400 ГБ, 800 ГБ, 1,6 ТБ и 3,2 ТБ SAS) и оптимизированные SSDs (1,92 ТБ, 3,84 ТБ, 7,68 ТБ и 15,36 ТБ SAS).

IBM Storwize V7000

Эта виртуализированная модульная система хранения поддерживает флеш-накопители, обеспечивает аппаратную компрессию и полностью автоматизированное многоуровневое хранение данных. Она позволяет избежать лишних расходов и эффективно консолидировать рабочие задачи благодаря интегрированной поддержке файлового и блочного хранения.

В распоряжении IBM Storwize V7000 два контроллера с кэш-памятью на 32 ГБ и поддержка стандартов 1 ГБ iSCSI, 10 ГБ iSCSI, FCoE, 8/16 ГБ FC. Одна система работает с накопителями общим объемом 7,74 ПБ (при внешней виртуализации – до 32 ПБ) и масштабируется до 504 дисков с 20 модулями расширения при наличии двух контроллеров и 1 056 дисков – при четырех контроллерах.

В IBM Storwize V7000 доступны модули расширения LFF и SFF для 12 ГБ SAS, где в первом случае поддерживается 12 дисков формата 3,5 дюйма, а во втором – 24 диска формата 2,5 дюйма. Система работает с твердотельными накопителями и дисками повышенной емкости.

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.Launch the VSM client, logging into the SVSP domain you want to manage. See “Launching the VSM client” on page 25

2.Enter a valid license key, if necessary. For information about license keys, see the HP StorageWorks SAN Virtualization Services Platform administrator guide.

3.Familiarize yourself with the VSM client interface. See “Using the VSM client interface” on page 27.

If you want to customize the interface, see “Customizing the user interface” on page 34.

If you want to manage the IP addresses of the VSM servers that manage an SVSP domain, see “Managing VSM server IP addresses” on page 38.

Launching the VSM client

You can run the VSM client from any PC connected to the Internet that has Java 1.5 or later. The VSM client is launched from an Internet browser and does not require any software installation. Alternatively, you can use a remote connection client to access the VSM server. For more information on establishing a remote connection, contact your system administrator.

To use the VSM client to manage an SVSP domain, you need the IP address of the active VSM server of the domain, the TCP port number through which the VSM server is exposed to the IP network, and a user name and password for logging into the VSM server. The VSM client has a default user account, with the user name admin and password of admin. The administrative password should have been changed during the initial installation. This user account has full user privileges. The TCP port number is configured at the VSM server installation stage. The default port number is 8004.

The first time you connect to an SVSP domain, you must use the IP address of the VSM server that is currently active. After you are connected, the active VSM server informs the VSM client of the management IP address of the passive VSM server, if there is one. If there is a failover between VSM servers during your session, the VSM client will switch to the newly active VSM server. To connect to the SVSP domain for subsequent sessions, you can use the IP address of either VSM server. You do not need to know which VSM server is active.

To launch the VSM client:

1.Point your Internet browser to <IP address>:<Port_Number>, where <IP address> is the IP address of the VSM server, and <Port_Number> is the TCP port number through which the VSM server is exposed to the IP network.

2.Click Start VSM client. The login screen appears.

3.In the User Name field, enter your user name.

2 Installing the HP VSM Demo Mode program

The install process includes three easy steps:

•Downloading or copying the Demo Mode installer program to the local hard disk of the target computer

•Running the installation program

•Verifying the configuration

NOTE:

•The target computer is the computer on which you install VSM in Demo Mode.

•The VSM Demo Mode program is certified for use on computers that run Windows XP or Windows Vista, or servers running Windows 2008. Installing the software requires 400 MB of free disk space. If you do not keep the compressed and uncompressed archive files on your computer, only 130 MB is required after installation.

Installing the VSM Demo Mode program

1.Download or copy the Demo Mode installer program to the local hard disk on the target computer. The archive files are normally compressed as a .zip file.

NOTE:

A copy of the Demo Mode program and this guide are contained on the SVSP Documentation CD that is part of the SVSP media kit.

Пример внедрения виртуальной инфраструктуры в проектном институте

Клиенты компании «Ителон» уже оценили эффект от виртуализации СХД на практике. В проектном научно-исследовательском институте они внедрили данную технологию в рамках создания унифицированной виртуальной инфраструктуры. Задача заключалась в том, чтобы организовать конструкторам доступ к программным ресурсам и СХД с виртуальных рабочих мест. Это бы решило вопрос с построением единой высокопроизводительной платформы, повысило производительность и исключило риск утечки конфиденциальной информации.

На первом этапе закупили и установили дополнительные СХД и управляющие серверы. Применив технологию виртуализации, «Ителон» организовали работу инженеров таким образом, чтобы их компьютеры обращались к централизованному высокопроизводительному серверу, который занимается обработкой данных. При этом на рабочие места конструкторов выводилось только изображение программной среды, а обратно на сервер отправлялись команды – движения мыши и нажатия на клавиатуру.

Виртуализация помогла клиентам «Ителон» реорганизовать работу предприятия, оптимизировать доступ к данным и снизить требования к оснащению отдельных рабочих мест (теперь они минимальны). Кроме того, они решили несколько сопутствующих задач: повысили информационную безопасность и предусмотрели дальнейшее масштабирование с минимальными затратами.

Андрей Семенов
22/01.2018

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.

To view the VSM servers that comprise a domain:

1.In the navigation tree, expand the SVSP Domains node.

2.Select a domain in the navigation tree. The VSM servers that comprise the domain are listed in the list area. The following properties are displayed for each VSM server.

Table 14 VSM server properties

1 Storage Virtualizer Profile

Profile introduction

The VSM server supports the Storage Virtualizer Profile version 1.4 which models the VSM server as a system capable of exposing virtual devices aggregated from back-end arrays present on the SAN. In this profile, only the Fabric Agent Architecture is considered.

The following profiles are related to this one:

•Server

•Profile Registration

•FC Target and Initiator Ports

•Masking and Mapping Profile

•Indications

•Block Services/Thin Provisioning

•Extent Composition

•Cascading

•Physical Package

•Multiple Computer System

•Storage Server Asymmetry

•Job Control

•Copy Services

•Replication Services with Migration vendor extension

•Device Credentials

Functional description

The Storage Virtualizer Profile models the fundamental devices of the virtualizer. Additional profiles implement specific model details and manipulation of elements managed by the virtualizer. Below is a list of related profiles and their model enhancement capabilities (henceforth referred to as component profiles):

•Block Services Package: Provides a service for organizing back-end arrays modeled by the Storage Virtualizer profile into storage pools and virtual disks. In VSM terms, this profile manages stripe sets, storage pools, and virtual disks in an SVSP domain.

•Thin Provisioning Profile: Provides for management of thinly provisioned virtual disks. In this implementation, the profile documentation is integrated with the Block Services profile.

•Physical Package: Models the physical stripe set and product information. In VSM terms, the VSM server hardware and products are surfaced.

•Extent Composition: Models details of storage components’ mappings. In VSM terms, the segments of virtual disks and pools are mapped as ranges of primordial and composite extents.

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.Launch the VSM client, logging into the SVSP domain you want to manage. See “Launching the VSM client” on page 21

2.Enter a valid license key, if necessary. For information about license keys, see the HP StorageWorks SAN Virtualization Services Platform administrator guide.

3.Familiarize yourself with the VSM client interface. See “Using the VSM client interface” on page 23.

If you want to customize the interface, see “Customizing the user interface” on page 30.

If you want to manage the IP addresses of the VSM servers that manage an SVSP domain, see “Managing VSM server IP addresses” on page 33.

Launching the VSM client

To launch the VSM client:

2.Click Start VSM client. The login screen appears.

3.In the User Name field, enter your user name.

2 Using the VSM command line interface

A command line interface (CLI) was created for the Virtualization Services Manager (VSM) application to make the management of some tasks easier. This CLI utility allows you to create and run script files to perform virtualization tasks.

Any SAN Virtualization Services Platform (SVSP) domain requires a login operation. Due to security issues, you want to define who can run CLI commands. Users can be defined with the VSM GUI. A user name and its password is used in any CLI operation as the first operation before running the command.

Syntax

The syntax of a command (where means optional) is:

vsm_cli

vsm_cli -SD VSMDomainName UserName Password

vsm_cli -SD VSMDomainName UserName Password -C CliCommand

vsm_cli ~

Options

-SD	This option specifies the destination SVSP domain that follows the CLI
	commands, and is valid when the server is attached to multiple SVSP domains.
	Follow these guidelines:
	1.	To specify the SVSP domain where the CLI commands are to be executed
		when running a single command with the -Coption, the -SDoption must
		come first.
	2.	When running with an input text file (-Ioption), this argument is optional
		for backwards compatibility with old scripts that were created before
		support of the -SD argument. It allows you to run pre-multiple SVSP domain
		scripts (that do not start with the SelectVSMDomain CLI command) in
		multiple SVSP domain environments without the need to update the actual
		input file.
	The username and password arguments are not the operating system users,
	but the SVSP domain-defined users. Each VSM manages the SVSP domain
	and can define users as part of the SVSP-domain configuration. In order to
	run the CLI command, you must have set up or defined a user (using the VSM
	GUI) in order to log into the SVSP domain.
-CCliCommand	This option executes the command specified in the command line. The
	command is specified by a command name and a list of arguments separated
	by commas. For example:

CliCommand -ARG1_NAME arg1_val1, ~ -ARG2_NAME arg2_val1 arg2_val2

where CliCommand is the name of the command,

ARG_NAME is the name of the argument, arg_value is the value of the argument.

2 Using the VSM command line interface

Syntax

The syntax of a command (where means optional) is:

vsm_cli

vsm_cli -SD VSMDomainName UserName Password

vsm_cli -SD VSMDomainName UserName Password -C CliCommand

vsm_cli ~

Options

-SD	This option specifies the destination SVSP domain that follows the CLI
	commands, and is valid when the server is attached to multiple SVSP
	domains. Follow these guidelines:
	1. To specify the SVSP domain where the CLI commands are to be ex-
	ecuted when running a single command with the -Coption, the -SD
	option must come first.
	2. When running with an input text file (-Ioption), this argument is
	optional for backwards compatibility with old scripts that were created
	before support of the -SD argument. It allows you to run pre-multiple
	SVSP domain scripts (that do not start with the SelectVSMDomain
	CLI command) in multiple SVSP domain environments without the
	need to update the actual input file.
	The username and password arguments are not the operating system
	users, but the SVSP domain-defined users. Each VSM manages the SVSP
	domain and can define users as part of the SVSP-domain configuration.
	In order to run the CLI command, you must have set up or defined a user
	(using the VSM GUI) in order to log into the SVSP domain.

HP StorageWorks SAN Virtualization Services Platform Manager command line interface user guide 17

4 To modify or create the setup database (optional)

The Demo Mode program comes with a default setup database that represents a typical HP storage environment. It is also possible to modify the setup database or build a new one from scratch.

The setup database is created or modified by using the dbinit.exe command line utility. This utility accepts commands that create or delete components (back-end LU, HBA, hosts, VSM, and DPM). Instead of typing one command line for each component, there is an option to have a text file with all the commands. Run dbinit.exe and accept the text file with all the commands listed inside. For a detailed description on using the dbinit.exe command, see “How to use DBINIT” on page 27.

1 Introduction

The HP StorageWorks SAN Virtualization Services Platform (SVSP) Virtualization Service Manager (VSM) Demo Mode is a simulation application of the HP VSM GUI interface that can be used for product demonstrations. The Demo Mode program can run on laptops or desktops with Windows XP or Windows Vista, or on servers running the Windows 2008 operating system. The Demo Mode allows you to imitate most of the HP VSM GUI functions: storage pool and virtual disk creation, assignment of virtual disks to a host, creating a PIT, creating a snapshot, and more. The Demo Mode software comes with a default setup database that presents a typical user with an HP storage environment, allowing a quick demonstration with zero setup time.