LSI - 36100-00, Rev. A, August 2009 - SVM CLI User Guide

LSI Storage Virtualization Manager Command Line Interface
User Guide
36100-00, Rev. A
Proprietary Rights Notice

This document contains proprietary information of LSI Corporation. The information contained herein is not to be used by or disclosed to third parties without the express written permission of an officer of LSI Corporation.
Document Description
36100-00, Rev. A, August 2009. This document will remain the official reference source for all revisions and releases of this product until rescinded by an update.
Disclaimer
It is the policy of LSI Corporation to improve products as new technology, components, software, and firmware become available. LSI reserves the right to make changes to any products herein at any time without notice. All features, functions, and operations described herein may not be marketed by LSI in all parts of the world. In some instances, photographs and figures are of equipment prototypes. Therefore, before using this document, consult your LSI representative for information that is applicable and current. LSI DOES NOT ASSUME ANY RESPONSIBILITY OR LIABILITY FOR THE USE OF ANY PRODUCTS DESCRIBED HEREIN EXCEPT AS EXPRESSLY AGREED TO IN WRITING BY LSI. LSI products are not intended for use in life-support appliances, devices, or systems. Use of any LSI product in such applications without written consent of the appropriate LSI officer is prohibited.
License Restriction
The purchase or use of an LSI Corporation product does not convey a license under any patent, copyright, trademark, or other intellectual property right of LSI or third parties.
Copyright Notice
2009 LSI Corporation. All rights reserved.
Trademark Acknowledgments
Engenio, the Engenio design, HotScale, SANtricity, SANshare, Storage Virtualization Manager, SVM, Data Path Module, and DPM are trademarks or registered trademarks of LSI Corporation. All other brand and product names may be trademarks of their respective companies.
Contents
Chapter 1: GETTING STARTED
Installation and Configuration.....................................................................................................................1-1 Obtain the Appropriate Package for the Host Operating System............................................1-1 Creating the SANAPI Volume.................................................................................................................1-2 SVM CLI Command Syntax............................................................................................................................1-3 Syntax Options............................................................................................................................................1-4 Syntax Rules .................................................................................................................................................1-5 Special Symbols Used in SVM CLI.........................................................................................................1-6 Constraints on the Values of the CLI Parameters ...........................................................................1-7 Template Names ........................................................................................................................................1-7 Using Templates to Run the Same Script ...................................................................................1-7 Using Templates to Delete Old Objects .....................................................................................1-8 Security ................................................................................................................................................................1-8 Synchronous and Asynchronous Modes .................................................................................................1-8 Asynchronous Mode.................................................................................................................................1-8 Synchronous Mode ...................................................................................................................................1-9 Basic Interactive Help (Console Mode)............................................................................................ 1-10 Returned Execution Status .................................................................................................................. 1-10 General CLI Control Commands .............................................................................................................. 1-11 Pause ........................................................................................................................................................... 1-11 Error Control OnErrorGoTo .............................................................................................................. 1-11 GoTo............................................................................................................................................................. 1-12 Quit............................................................................................................................................................... 1-13 AllowExecErrors and DisallowExecErrors ....................................................................................... 1-13
Chapter 2: SVM CLI COMMANDS

Login to the SVM Domain .............................................................................................................................2-1 Show a List of Domains and SVMs .............................................................................................................2-1 Get a List of All Domains..........................................................................................................................2-1 Get a List of All SVMs (and Their Domain Names) ..........................................................................2-1
LSI Storage Virtualization Manager CLI User Guide
iii
Volume Manager Commands......................................................................................................................2-2 Create Volume ............................................................................................................................................2-2 Assign Volume to One or More Hosts ................................................................................................2-2 Create a Volume and Immediately Assign to a Host.....................................................................2-2 Get Volume Properties.............................................................................................................................2-2 Delete Volume ............................................................................................................................................2-2 Expand the Capacity of an Existing SVM Volume ..........................................................................2-3 Expand an SVM Volume and its Corresponding Window Partition (NTFS File System)...2-3 List Pools .......................................................................................................................................................2-4 List Volumes.................................................................................................................................................2-4 List Hosts .......................................................................................................................................................2-4 Back Up the Current SVM Setup into a Local File (on the SVM) ................................................2-4 multiView Commands....................................................................................................................................2-4 Create a Point-in-Time on a Volume or a View ...............................................................................2-4 Create View ..................................................................................................................................................2-5 Create a View and Immediately Assign to a Host...........................................................................2-5 Wait for a Newly Created SVM Object to Become Ready for Use .............................................2-5 List All Views and PiTs ..............................................................................................................................2-6 Delete Point-in-Time or View ................................................................................................................2-6 Get View or PiT Properties ......................................................................................................................2-6 List All PiTs for a Volume or a View......................................................................................................2-6 List All Views for a PiT ...............................................................................................................................2-6 Purge (Delete) Old PiTs or Views ..........................................................................................................2-7 Rollback PiT ..................................................................................................................................................2-7 Rollback Consistency Group PiT ...........................................................................................................2-7 Restore a View.............................................................................................................................................2-8 multiCopy Commands ...................................................................................................................................2-8 List multiCopy Groups .............................................................................................................................2-8 List multiCopy Jobs per Group..............................................................................................................2-8 Get multiCopy Group Information ......................................................................................................2-8 Get multiCopy Job Information............................................................................................................2-8 Create multiCopy Group .........................................................................................................................2-8
iv
Add a multiCopy Job To a Group .........................................................................................................2-9 Add a multiCopy Job to a Group That Is Built Over a Consistency Group.............................2-9 Consistency Group Commands ..................................................................................................................2-9 Create a New Consistency Group.........................................................................................................2-9 Delete a Consistency Group................................................................................................................ 2-10 Add a Volume to a Consistency Group ........................................................................................... 2-10 Remove Volumes from a Consistency Group ............................................................................... 2-10 Get the Information of a Consistency Group ................................................................................ 2-10 Create Point-in-Time of Consistency Group Volumes or Views ............................................. 2-10 Create a View on a Consistency Group PiT .................................................................................... 2-11 Create a View on a Consistency Groups Most Recently Created PiT................................... 2-11 Delete a Consistency Groups Point-in-Time ............................................................................... 2-12 Delete a Consistency Groups Views ................................................................................................ 2-12 Asynchronous multiMirror Commands................................................................................................. 2-12 Create an Asynchronous multiMirror Group ................................................................................ 2-12 Create an Asynchronous multiMirror Group over a Consistency Group ........................... 2-12 Create User PiTs for Asynchronous multiMirror Groups .......................................................... 2-13 Pause Local Asynchronous multiMirror Groups .......................................................................... 2-13 Resume Local Asynchronous multiMirror Groups ..................................................................... 2-14 Break Local Asynchronous multiMirror Groups ........................................................................... 2-14 Break Remote Asynchronous multiMirror Groups...................................................................... 2-14 Delete Remote Asynchronous multiMirror Groups ................................................................... 2-14 Delete Local Asynchronous multiMirror Groups ......................................................................... 2-15 Pause All Local Asynchronous multiMirror Groups .................................................................... 2-15 Resume All Local Asynchronous multiMirror Groups................................................................ 2-15 Break All Local Asynchronous multiMirror Groups..................................................................... 2-15 Break All Remote Asynchronous multiMirror Groups................................................................ 2-15 Pause the Jobs of a Local Asynchronous multiMirror Group .................................................. 2-16 Resume the Jobs of a Local Asynchronous multiMirror Group.............................................. 2-16 Break the Jobs of a Local Asynchronous multiMirror Group................................................... 2-16 Break the Jobs of a Remote Asynchronous multiMirror Group ............................................. 2-16 Pause All Jobs of a Local Asynchronous multiMirror Group ................................................... 2-17 Resume All Jobs of a Local Asynchronous multiMirror Group ............................................... 2-17
Break All Jobs of a Local Asynchronous multiMirror Group.................................................... 2-17 Break All Jobs of a Remote Asynchronous multiMirror Group............................................... 2-18 Synchronous multiMirror Commands ................................................................................................... 2-18 Create a Synchronous multiMirror Group ..................................................................................... 2-18 Add a Synchronous multiMirror Job to Synchronous multiMirror Group ......................... 2-19 Create PiT on a Synchronous multiMirror Group ....................................................................... 2-19 Delete a PiT on a Synchronous multiMirror Group .................................................................... 2-19 Change the Mode of Operation of a Synchronous multiMirror Group ............................... 2-19 Resume Synchronous multiMirror Group ...................................................................................... 2-19 Delete-sync a (Previously Failed) Synchronous multiMirror Group ..................................... 2-19 Re-sync a (Previously Failed) Synchronous multiMirror Group.............................................. 2-19 Break Synchronous multiMirror Jobs .............................................................................................. 2-20 multiMigrate Commands ........................................................................................................................... 2-20 Migrate a Volume ................................................................................................................................... 2-20 Manage Migration .................................................................................................................................. 2-20 DPM-Related Commands........................................................................................................................... 2-20 Set or Change the Volume LUN Configuration............................................................................ 2-20 Change Active DPM (Switch) .............................................................................................................. 2-21 Operating System-Related Commands ................................................................................................ 2-21 Run an Operating System Command from Within the SVM CLI............................................ 2-21 Mount a Volume or View to the Windows Operating System................................................ 2-21 Unmount a Volume or View from the Windows Operating System .................................... 2-22 Flush I/O into Volume or View ........................................................................................................... 2-22
Chapter 3: USING THE SVM CLI SERVER-FREE BACKUP

Typical Server-Free Backup Process ..........................................................................................................3-1 Server-Free Backup in SVM Environment for a Non-Windows Operating System...................3-1 Automating a Server-Free Backup for a Non Windows Operating System ..........................3-2 Scheduling the Scripts .............................................................................................................................3-2 Server-Free Backup in the SVM Environment for the Windows Operating System.................3-3
Chapter 4: CREATING A PIT AND A VIEW WITH MICROSOFT VSS

LSI VSS Hardware Provider............................................................................................................................4-2 Using the Microsoft VSS to Create a Persistent PiT and View ..........................................................4-2
vi
Using Microsoft VSS to Create a PiT and View.................................................................................4-2 Using Microsoft VSS to create a User PiT for Async Mirror..........................................................4-3
Chapter 5: UPGRADING FROM SVM 4 TO SVM 5

Updating the SANAPI CLI Packages...........................................................................................................5-1 SANAPI Application Pack and Microsoft VSS ...................................................................................5-1 Updated SANAPI CLI Commands .........................................................................................................5-1
TRADEMARKS
vii
viii
List of Figures
CHAPTER 4: CREATING A PIT AND A VIEW WITH MICROSOFT VSS
Figure 4-1. VSS Components ..................................................................................................................... 4-1
ix
List of Tables
CHAPTER 1: GETTING STARTED
Table 11. Standard SVM Script and Command Line Symbols ..................................................... 1-6
CHAPTER 4: CREATING A PIT AND A VIEW WITH MICROSOFT VSS

Table 4-1. VSS Component Functions .................................................................................................... 4-1
xi
xii
.............................................................................
Document Conventions
Definitions of Safety Notices
DANGER Indicates an imminently hazardous situation that will result in death or severe personal injury.
WARNING Indicates a potentially hazardous situation that could result in death or severe personal injury.
CAUTION
Indicates a potentially hazardous situation that could result in moderate or minor personal injury.
Definitions of Informational Notices

ATTENTION Indicates a potentially hazardous situation that could result in data loss (or other interruption) or equipment damage.
IMPORTANT Indicates information or criteria that is necessary to perform a procedure correctly.
NOTE: Indicates a clarification of a concept or presents a maintenance tip.
Typographic Conventions
Italic indicates the title of documents, emphasized words, and new terms. Bold indicates choices in procedures and other emphasized text. Bold also indicates menu selections and user-interface controls, such as buttons and key names. Monospace indicates arguments, code examples, code phrases, command-line text, directories, error messages, file names, folders, on-screen text, parameters, Universal Resource Locators (URLs), and user input. Monospace italic indicates placeholders and variables in code. Monospace bold indicates commands and options in running text.
xiii
..............................................................................
xiv
.............................................................................
About This Document

This document describes how to utilize the command line interface (CLI) to use the feature and functions in LSI Storage Virtualization Manager (SVM). LSI has developed a scripting utility with which users can create and run scripts to automate storage virtualization tasks. For a description of installing and configuring SVM in any environment, refer to the Storage Virtualization Manager Installation and Configuration Guide. For a description of how to use SVM, refer to the LSI Storage Virtualization Manager User Guide.
Chapter 1, Getting Started, contains general information that applies to using CLI
commands in SVM.
Chapter 2, SVM CLI Commands, contains specific information that explains how to
use CLI commands in SVM.
Chapter 3, Using the SVM CLI Server-Free Backup, provides an example that
shows how to use the SVM CLI for Server Free Backup.
Chapter 4, Creating a PiT and a View with Microsoft VSS, describes Microsoft VSS in
the SVM and DPM environment and how to use VSS to create a PiT and a view.
Chapter 5, Upgrading From SVM 4 to SVM 5, explains how to upgrade from SVM 4
to SVM 5.
Intended Readers
This document is intended for storage system administrators, system administrators, and service personnel who are responsible for installing, using, maintaining, performing diagnostics and troubleshooting, and servicing the Storage Virtualization Manager and the SAN. Users must be familiar with the following:
Command-line concepts and technologies Scripting languages The following storage concepts and technologies:
Storage area network (SAN) Redundant Array of Independent Disks (RAID) SVM storage virtualization
xv
..............................................................................
Related Publications
The following publications provide additional information that help you operate and maintain a storage system that is managed by the SVM.
Storage Virtualization Manager Installation and Configuration Guide LSI Storage Virtualization Manager User Guide
Web Addresses
For information related to the products mentioned in this document, go to these websites:
The LSI web site at http://www.lsi.com. To obtain the most current LSI Storage Virtualization Manager and Data Path
Module documentation, go to https://partner.lsil.com/gm/cabinet1.25.149.
xvi
Chapter
Getting Started
The Storage Virtualization Manager (SVM) command line interface (CLI) provides scripting capabilities that users can use to automate creation and modification of SVM objects or entities. This document describes how to use the CLI, the CLI syntax, and provides some examples. The package that contains the SVM CLI set of commands is called SANAPI. The SANAPI CLI package is separate from the SVM software and the DPM image. You must install the SANAPI CLI package on every host for which an SVM object (such as a volume, a PiT or a view/snapshot) needs to be created or modified. Each operating system has a specific, unique version of the SANAPI CLI package. For a list of supported operating systems on which you can installed the SANAPI CLI package, refer to the current version of the SVM release notes.
Installation and Configuration

Before you can use the CLI commands, you must first install the appropriate CLI package and then create a SANAPI volume assigned to the host were the CLI package was installed.
Obtain the Appropriate Package for the Host Operating System

After obtaining the appropriate package, follow these instructions. The actual version number of the package might be different than the version numbers shown here.
Windows operating system Run this executable: SVM App-Pack for LA - 5.1.28.1.exe
Solaris operating system Run this package: pkg add -d SVM.App-Pack.Solaris.LA.5.1.28.1.pkg.Z
1-1
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux operating system Unzip and untar this file: SVM-AppPack-V5.R1.28.1-Linux-2.6-i386.tar.gz Run this shell script: SVM-AppPack-V5.R1.28.1-Linux-2.6-i386.sh
AIX operating system Run this package: installp -acd SanApi.AIX.5.1.28.4.LA.bff
The installation programs will install the CLI set of commands in the following locations:
Windows 2008 and Windows 2003 operating systems On all Windows platforms, the path to the set of the SVM CLI commands is set in the system path.
Solaris operating system The set of the SVM CLI commands is in the /usr/sbin/svm/sanapi/ directory.
Linux operating system The set of the SVM CLI commands is in the /usr/local/sanapi directory.
AIX operating system The set of the SVM CLI commands is in the /usr/lpp/svmdd.obj/ directory.
Creating the SANAPI Volume

1 Start the SVM GUI. 2 From the menu bar, select Tools >> Maintenance. 3 Click Create SANAPI Volume.
The Create SANAPI Wizard appears. The Enter volume parameters dialog appears.
4 In the Volume name text box, type a unique name for the volume. 5 In the Comment text box, type optional information 6 Click Next.
The Select pool dialog appears.
7 In the Pools table, select the pool, and click Add.
1-2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SVM CLI Command Syntax
The pool appears in the Selected Pools table.
8 Click Next.
The Select host dialog appears.
9 Choose the host from the Hosts table to which you want to assign permission to
access the SANAPI volume and from which the CLI will run.
10 Click Add.
The host appears in the Selected Hosts table.
11 Click Next.
The Select LUN dialog appears.
12 In the Select LUN dialog, select one of the LUN options:
Next free LUN (recommended) SVM assigns the next available free LUN. Specified LUN Select the LUN from the Specified LUN drop-down list.
13 Click Next.
A confirmation dialog appears.
14 Click Finish.
The SAN API volume is created and assigned to the appropriate host.
SVM CLI Command Syntax

The syntax of the command starts with SanApiExec.
Alternative parameters are separated by a pipe symbol ...|...|....

[-host <HostName1> R|RW|OFF,] [-host <HostName2> R|RW|OFF,]
Variable input is enclosed in angle brackets <...>.

SanApiExec -SD <DomainName> <UserName> <Password>
Optional CLI input is enclosed in square brackets [...].

SanApiExec [-SD <DomainName> <UserName> <Password>] [-I <input_file>] [-O <output_file>]
1-3
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax Options
The following syntax options are available in SVM CLI commands:
-SD
This option specifies the destination SVM domain for following CLI commands. This option is valid for multiple SVM domains. The -SD option serves three purposes:
When running a single command with the C option, the SD option must always come first to specify the SVM domain where the CLI commands are to be executed. When running with an input text file with the -I option, SD is an optional parameter that is used for backwards compatibility. The SD option allows the user to run multiple script files that do not start with the SelectSVMDomain CLI command in multiple domains environment without having to update the input file. The UserName and Password parameters apply to the users for the SVM domain, not to the users of the operating system. See Security on page 1-8 for more details.
-C CliCommand ...
This option executes only a single command specified in the command line. The command consists of a command name and a list of arguments separated by commas, as in the following example:
CliCommand -ARG1_NAME arg1_val1, -ARG2_NAME arg2_val1 arg2_val2
CliCommand The name of the command ARG_NAME The name of the argument arg_value The value of the argument
-I input_file
This option specifies that input commands are to be read from the input file. The format of the commands is the same as the format of commands for the -C option, as in the following example:
command -ARG_NAME1 arg1_value1, -ARG_NAME2 arg2_value1 arg2_value2
-O output_file
This option redirects output to the specified file. When the file exists, the old file is overwritten; that is, the old file is deleted, and a new file is created. When neither the -O output_file option nor the -OX option is specified, the standard output command stdout is used.
1-4
-OX output_file
This option is the same as the -O option; it redirects the output to the specified file. However, if the file already exists, it appends the output to it, rather than overwriting it. When neither the -OX option nor the -O option is specified, the standard output command stdout is used.
Syntax Rules
The following syntax rules apply to SVM CLI commands:
The C and I options are mutually exclusive, and they cannot be used together. When neither C nor I is used, the standard input command stdin is used for interactive input. Command names, argument names, and special keywords are case-insensitive. Names of SVM objects, such as volumes, views, and pools, are case-sensitive. The following example shows the general syntax of a command:
-ARG1_NAME arg1_val1, -ARG2_NAME arg2_val1 arg2_val2
A minus sign (-) immediately precedes an argument name. Arguments are separated by commas. IMPORTANT Missing commas will generate a bad parameter error.
An argument can receive multiple values. Multiple values are separated by one or more spaces, as seen in the example ARG2_NAME. In some instances, each value in a multiple value string is preceded by a special keyword. The special keyword always begins with an _ (underscore), as in the following example:
command -ARG1_NAME _Key1 arg1_val1 _Key2 arg1_val2 _Key3 ~ arg1_val3
EXAMPLE Multiple value string:

AddMCJob group <Group1>, ~ -Job <Job1> Priority 1 _pool <Pool1> _host <MyHost> ~ _permission RW, -timeout 900
Arguments can be entered in any order. Within an argument, the order of the values and keywords must be the same as shown in the commands documentation. When an input file is specified, the # (pound sign) followed by a white space separator at the beginning of a line in the file marks the line as a comment that the CLI does not process.
1-5
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
When a command extends over several lines, a ~ (tilde) must immediately precede each hard return in the command. To avoid problems in parsing the command line, names containing white spaces or symbols must be enclosed in quotation marks. See Table 11 for a list of valid CLI symbols that must be enclosed in quotation marks. A comma normally separates arguments. However, in some countries, a comma is used instead of the decimal point in numbers, as in 4.24 and 4,24. Therefore, enclose numbers that contain a decimal point between quotation marks, such as "4.24" to distinguish it from 4,24. NOTE When you use the -C option, type \" (backslash and quotation mark) instead of " (quotation mark), before the string name and after the string name. The \ is the literal escape character, which causes the next character to be treated literally, as in the following two examples.
EXAMPLE
In a script file:
CreatePiT -volume "<my volume>", -freeze "<my PiT>", ~ -timeout 900
In a command line:
SanApiExec -c CreatePiT -volume \"<my vol>\", -freeze ~ \"<my PiT>\", -timeout 900
Special Symbols Used in SVM CLI

Table 11 shows the standard symbols used in all SVM command lines, the purpose of each symbol, and where each symbol is positioned in SVM command lines.
Table 11 Standard SVM Script and Command Line Symbols Symbol Purpose Where used
# A comment line. (pound sign, or hash) ~ (tilde) Indicates that the line continues on the next line and allows the command to continue on the next input line. Separates command arguments.
At the beginning of a line in an input file.
Before the end-of-line mark (carriage return and line feed).
, (comma)
1-6
Table 11 Standard SVM Script and Command Line Symbols (continued) Symbol Purpose Where used
? (question mark) (minus)
CLI command names search and listing symbol. Marks argument names.
Used as wildcard when listing CLI command names in console mode. Immediately precedes argument names. Immediately precedes value names where value names are used. Enclose names that contain white spaces in them, or numbers with a decimal symbol.
Identifies value names in case of _ (underscore) some predefined arguments that have a multiple number of values. "" (straight quotation marks) Identifies strings containing white spaces as one entity, or numbers with a decimal symbol (which is locale dependent).
Constraints on the Values of the CLI Parameters

The values of the CLI parameters must comply with the following constraints:
They are limited to 31 characters. The names of SVM objects are case sensitive. They can contain only printable characters. They cannot contain the following characters: " : ' ; , * % { } [ ] ~ / \ ? < > |
Template Names
Names of created SVM objects, such as PiTs and views, may be fully provided by the user explicitly, or may be provided as a template, to which the CLI concatenates a unique suffix to create a complete unique name. Template names are limited to 16 characters.
Using Templates to Run the Same Script

Using a template, rather than assigning an absolute name, is useful when running the same script every day to create a new SVM object. When the user assigns an absolute name to an object the first time, then the second time the script runs, it ends with an error, because the object already exists with that absolute name. However, when the user provides a template for the object, every run of the script creates an object with a different name.
1-7
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
For example, when you create a PiT on a volume with the template name pit_on_vol_1, every run of the script creates a PiT with a name like pit_on_vol_1_SA_1 23456789, where the number following the _SA string is different for every run.
Using Templates to Delete Old Objects

Template names are also useful for object cleanups. When a script is run multiple times and creates a new object each time, it is possible to delete old objects. You can run the purge operation to delete the old objects. You can specify the number of most-recently created objects to retain. The purge operation uses the template name to delete old objects whose name starts with the template name followed by the _SA string and retain the specified created objects. IMPORTANT To prevent errors, assign a unique template name for every type of created object from every source object so that the purge operation deletes only objects originating from the same source.
Security
By default, only the system default administrator can run CLI commands. However, other users can also run CLI commands. Before a user can use the CLI, administrators must first define the user under specific SVM domains. To define users, go to the SVM GUI, and configure user names and passwords.
Synchronous and Asynchronous Modes

In the asynchronous mode, the timeout value is set to 0 (zero). In the synchronous mode, the caller or user provides a timeout parameter.
Asynchronous Mode
The asynchronous mode of operation for CLI commands is appropriate for creating SVM objects, such as a volume, a PiT, a view, a PiT on a consistency group, and a view on a consistency group. The user uses the same CLI but sets the timeout value to 0. The CLI starts the operation but does not wait for it to complete. If the CLI returns without an error, the operation started successfully but has not necessarily been completed yet.
1-8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous and Asynchronous Modes
In the asynchronous mode, the (Svm)WaitForObjectCreation parameter is used to wait for the completion of the following operations:
CreateVolume CreatePiT CreateView Operations CreateCGroupPiT CreateCGroupView CreatemultiMirrorUserPiT CreateMCGroup
For example, when you need to create n PiTs, instead of waiting for each PiT successful creation, one after the other (which may take N * time per PiT), you can create all PiTs at the same time, and then call N times the WaitForObjectCreation parameter, once for every PiT. But because the creation of all PiTs has already started, you need to wait only for as long as it takes for the longest PiT to be created.
Synchronous Mode
The synchronous mode timeout parameter specifies the maximum time that the CLI waits for the completion of the operation. The recommended timeout value for most operations is 900 seconds. However, for some operations, such as create a PiT, create a view, delete a PiT, and restore a view, the time to complete the operation depends on how much data the objects need to handle, so higher timeout values may be required.
When the operation is completed before the timeout period expires, the CLI returns a Success status. If the command does not complete before the timeout period expires, the CLI returns an SVM_SYNC_TIMEOUT error after the timeout period expires. The following CLI commands are blocked until the operation of that specific command is completed. The completion of a CLI command returns the following results:
When the CLI creates an SVM object, the created object is ready for immediate use. When the CLI deletes one or more SVM objects, all objects are deleted, and you can immediately create new objects with the same names as of those just deleted.
1-9
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Interactive Help (Console Mode)

When using SVM CLI commands in console mode, you can use ? (question mark) as a wildcard for searching through the commands repository and through the list of all available commands. Search terms are not case sensitive. For example, type list? in console mode to print out the following commands that begin with the token list.
. . . ListPools ListSVMs ListSyncmultiMirrorGroups ListSyncmultiMirrorPiTs ListViews ListViewsChain ListVolumes ** End of listing **
Use the ? wildcard to perform more complex searches. For example, type get ? info to list all of the commands that start with the token get and have the token info somewhere after it, such as the following commands.
. . . GetMCJobInfo GetmultiMirrorGroupInfo GetmultiMirrorJobInfo GetMigrationInfo Get<MyHost>Info GetSwitchInfo GetSyncmultiMirrorGroupInfo ** End of listing **
Returned Execution Status

When you invoke the SanApiExec command from a batch file, the command returns an execution status to the caller.
When no error occurred, the returned status is 0 (zero). If an error occurred, the returned status is a positive number that represents the error code. The CLI command output file for the batch file provides a detailed error description.
1-10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General CLI Control Commands
General CLI Control Commands

Pause
To pause execution of CLI commands from within an input file, use the Pause command. # Pause for <N> seconds Pause -delay <10>
Error Control OnErrorGoTo

The OnErrorGoTo CLI command changes the sequence of executed CLI commands when one of the commands returns with an error. The command can be used only in script files; that is, only when the -I argument is used. The CLI syntax is as follows: # 'On Error Go To' command OnErrorGoTo <LABEL> OnErrorGoTo
OnErrorGoTo <LABEL>
The OnErrorGoTo <LABEL> command instructs the CLI executor to go to LABEL if the execution of a subsequent CLI command returns an error. The OnErrorGoTo command does the following:
It instructs the CLI executor to deactivate the error-trapping mechanism. If an error occurs while the error trapping mechanism is active, the CLI executor searches for the first occurrence of the label and ignores all commands, including other OnErrorGoTo commands, up to the label, or to the end of file if the label is not found.
LABEL LABEL must appear at the beginning of a line immediately followed by a : (colon).
The line with the label in the script file must always come after the line of the OnErrorGoTo command. The LABEL is case insensitive and cannot contain white spaces. Consecutive calls to OnErrorGoTo with different labels change the label after each call, so the label of the most recent call is always in effect.
To exit the script file in case of an error, do either of the following actions:
Place the label as the last line at the end of the script file. Omit the label, although this might confuse the reader about the original intention of the scripts writer.
1-11
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXAMPLES OnErrorGoTo <firstLabel> # now firstLabel is in effect ... OnErrorGoTo <MyLabel> # now MyLabel is in effect ... <firstLabel>: # label is ignored during normal processing (when no error occurs) ... <mylabel>: # label is case insensitive
GoTo
The GoTo CLI command changes the sequence of executed CLI commands. The command can be used only in script files; that is, only when the -I argument is used. The CLI syntax is as follows: # 'Go To' command GoTo LABEL
GoTo LABEL
This command instructs the CLI executor to go to LABEL. The line with the label in the script file must always come after the line of the GoTo command.
GoTo
An empty GoTo command has no label, and a GoTo command without a label is ignored. The GoTo command clears any previous label set by an OnErrorGoTo command. After the GoTo command is executed, no previous OnErrorGoTo command is in effect.
LABEL
LABEL must appear at the beginning of a line, and a : (colon) must immediately follow the label. LABEL is case insensitive and cannot contain white spaces.
1-12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General CLI Control Commands
To exit the script file, perform either of the following actions:
Place the label at the end of the script file. Omit the label in the script file. However, this might confuse the reader about the original intention of the scripts writer.
Quit
The Quit command exits the current CLI session. The Quit command syntax is as follows:
Quit Some message to be printed in the output
When the Quit command is run from an input command file, all of the following commands are ignored, and the CLI application is terminated. When a text string follows the Quit command run from an input command file, the string is printed in the output file or the console. The string can be up to 120 characters in length. When the Quit command is run from the command line, control returns to the command line. When a string follows the Quit command run from the command line, the string is ignored.
AllowExecErrors and DisallowExecErrors

The AllowExecErrors command and the DisallowExecErrord command allow execution errors or ignore execution errors during the execution of CLI commands.
The DisallowExecErrors command terminates the script and immediately exits if a CLI command after it returns an error. This behavior is the default of the SVM CLI. The AllowExecErrors command forces the script to continue even if any of the CLI commands after it returns an error. The AllowExecErrors command and the DisallowExecErrors command can be used only in script files; that is, only when the -I argument is used. The CLI syntax is as in the following example: AllowExecErrors Set for CLI commands DisallowExecErrors
1-13
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-14
Chapter
SVM CLI Commands

This chapter provides lists of CLI commands that cover all of the SVM features and provides some examples that can help you automate your SVM environment.
Login to the SVM Domain

To run the CLI commands, you must first select the current SVM domain for all subsequent CLI operations. The command to select the SVM domain must be the first command in every script or CLI execution. If the command to select the SVM domain is not the first command, you will not be connected to a valid domain, and all subsequent CLI commands will fail. To select the SVM domain, run this command:
SelectSVMDomain -Domain <DomainName>, -User <UserName>, ~ -Password <Password>
The UserName parameter and the Password parameter are for users defined by the SVM domain, not for the operating system users. To run CLI commands, you must use the SVM GUI to define the SVM user to log onto the SVM.
Show a List of Domains and SVMs

Get a List of All Domains
ListDomains
Get a List of All SVMs (and Their Domain Names)

ListSVMs
2-1
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Volume Manager Commands

Create Volume
CreateVolume -volume <VolumeName>, -pool <PoolName1> <MBfromPool1> ~ [-pool <PoolName2> <MBfromPool2>,] ~ [-pool <PoolName3> <MBfromPool3>,] ~ -bootable 0, -cluster 0, [-Thin MBVirtualCapacity] ~ -timeout 900
Assign Volume to One or More Hosts

ChangePermission -volume <VolumeName>, ~ -host <HostName1> R|RW|OFF, ~ [-host <HostName2> R|RW|OFF,] -timeout 900
Create a Volume and Immediately Assign to a Host

CreateVolumeWithLun -volume <VolumeName>, -pool <PoolName1> <MBfromPool1>, ~ [-pool PoolName2 MBfromPool2,] ~ [-pool PoolName3 MBfromPool3,] ~ -host HostName1 R|RW|OFF LunNumber, ~ [-host HostName2 R|RW|OFF, LunNumber] ~ [-thin 0|1] ~ -timeout 900
You can assign a specific LUN number. You can let SVM automatically assign a LUN number by using -1 as the value for the LUN number parameter.
Get Volume Properties

This command returns the status of the volume, capacity of the volume, the CG to which the volume belongs (if any), the time the volume was created, thin volume, the pools to which the volume belongs, the hosts that have permission to access the volume, and other information.
GetVolumeData -volume <VolumeName>
Delete Volume
DeleteVolume -volume <VolumeName>
2-2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Manager Commands
Expand the Capacity of an Existing SVM Volume

NOTE You cannot expand a volume that has PiTs or that is in a Synch multiMirror Group.
ExpandVolume -volume <VolumeName>, -pool <PoolName1> <MBfromPool1>, ~ [-pool <PoolName2> <MBfromPool2>,] [-pool <PoolName3> <MBfromPool3>,] -timeout 900
Expand an SVM Volume and its Corresponding Window Partition (NTFS File System)
ExpandPartitionEx -Drive H:, -By <ExtendByMB>, -Pool <PoolName> ExpandPartition -Drive H:, -Size <CurrentSizeInMB>, ~ -Extend <ExtendByPercent>, -Pool <PoolName>
The drive letter must be followed by either a colon (:) or a $ symbol. Use the By parameter to directly define the expansion size of a partition.
Do not use an expansion size less than 100 MB. Use the Size parameter to define the expansion of a partition as a percentage of the current partition size.
The current partition size is defined in megabytes (MB). You must use the Extend parameter with the Size parameter. The Extend parameter defines the percentage by which you are expanding the partition. In this case, the expansion size is determined by the multiplication of the Size parameter and the Extend parameter.
EXAMPLES: Using the By parameter to expand a partition by 500 MB:

ExpandPartition -Drive Q:, -By 500, -Pool pool
Using the Size parameter to expand a 5000-MB partition by 20 percent:

ExpandPartition -Drive Q:, -Size 5000, -Extend 20, ~ -Pool pool
2-3
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List Pools
ListPools [-Template <Name>]
The default command, without parameters, lists all pools. Adding the -Template parameter returns only objects whose names start with specified Name. The -Template parameter is optional.
List Volumes
ListVolumes [-Template <Name>]
The default command, without parameters, lists all volumes. Adding the -Template parameter returns only objects whose names start with specified Name. The -Template parameter is optional.
List Hosts
ListHosts [-Template <Name>]
The default command, without parameters, lists all hosts. Adding the -Template parameter returns only objects whose names start with specified Name. The -Template parameter is optional.
Back Up the Current SVM Setup into a Local File (on the SVM)
BackupSetup -Destination <destinationPath>
The destinationPath parameter must be a folder on the SVM.
multiView Commands
Create a Point-in-Time on a Volume or a View
CreatePiT -volume <VolumeName>, -freeze <PiTName> [TEMPLATE], ~ -timeout 900
The maximum number of PiTs on a volume is limited. Refer to the release notes for the supported maximum number of PiTs on a volume.
2-4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . multiView Commands
Create View
CreateView ~ -freeze <PiTName> ~ -view <ViewName> [TEMPLATE], ~ -host <HostName1> RW|OFF, [-host <HostName2> RW|OFF,] ~ -pool <PoolName>, ~ -cluster 0, -timeout 900
Create a View and Immediately Assign to a Host

CreateViewWithLun ~ -freeze <PITName> [LastInstance | LastAsyncMM | LastSyncMM],~ -view <ViewName> [TEMPLATE], ~ -host <HostName1> RW|OFF <LunNumber>, ~ [-host <HostName2> RW|OFF <LunNumber>, ] ~ -pool <PoolName>, ~ -timeout 900
You can assign a specific LUN number. You can let SVM automatically assign a LUN number by using -1 as the value for the LUN number parameter.
Wait for a Newly Created SVM Object to Become Ready for Use
WaitForObjectCreation -Name <Name> [LastInstance], ~ -Volume | -Freeze | -View | -CGroupPit | -CGroupView | -UserPit | -SyncPiT | -MCVolume | -Migration , ~ [ -job <JobName1>, [-job <JobName2>, ] ] ~ -timeout 900
Use this command after creating a bulk of the same objects and before moving to the next action. For example, creating 10 volumes with same size, one after the other without waiting for each one of the volumes to be created. Then, in the end, wait for the 10 volumes to be created before continuing.
The LastInstance flag indicates that the most recently created PiT/view (with a Template name) is the name to be used.
2-5
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXAMPLES:
WaitForObjectCreation -Name <MyVolume>, -Volume, -timeout 900 WaitForObjectCreation -Name <MyPiT LastInstance>, -Freeze, ~ -timeout 900 WaitForObjectCreation -Name <myMigrationGroup>, -Migration, ~ -timeout 900 WaitForObjectCreation -Name <MyMCGroup>, -MCVolume, ~ -job <Job1>, -job <Job2>, -timeout 900
List All Views and PiTs

ListViews [-Template <RootName>] [,] [-freeze | -view]
Running the command without parameters lists all PiTs and views. Adding -freeze to the command line lists PiTs only. Adding -view to the command line lists views only.
EXAMPLES:
ListViews ListViews ListViews ListViews -freeze -view -Template <RootName>, -freeze -view , -Template <RootName>
Delete Point-in-Time or View

DeletePiTOrView -name <ViewOrPiTName>, -timeout 900
Get View or PiT Properties

GetViewData -name <ViewOrPiTName>
List All PiTs for a Volume or a View

Provide a list of all PiTs defined on specified volume or view.
ListPiTsChain -view <ViewOrVolumeName>
List All Views for a PiT

Provide a list of all views defined on specified PiTs.
ListViewsChain -freeze <PITName>
2-6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . multiView Commands
Purge (Delete) Old PiTs or Views

PurgePiTsOrViews -View | -Freeze | -SyncPiT, ~ -Template <RootName> [ANYSUFFIX], ~ [-Group <SyncmirrorGroupName>,] -Keep <NumberToKeep>
PiTs with views on them are not purged. If the -Keep parameter NumberToKeep value is 0, the command deletes all PITs or views with the specified template name. If the SyncPit option is used, you must provide the name of the Sync Mirror group for which the Sync Mirror PiTs were created.
EXAMPLES:
PurgePiTsOrViews -Freeze, -Template <MyPiT>, -Keep 3 PurgePiTsOrViews -SyncPiT, -Template sMM_PIT AnySuffix, ~ -Group <sMMGroupName>, -Keep 1
Rollback PiT
Roll back a view or volume to how it was just before the specified PiT was taken (the specified PiT is deleted). The operation is allowed only if there are no views created on any of the deleted PiTs.
RollBack -freeze <PITName>, -timeout 900
Rollback Consistency Group PiT

Roll back the volumes or views in a CG to how it was just before the specified PiT template name (the specified and subsequent PiTs are deleted). The operation is allowed only if there are no views created on any of the deleted PiTs.
RollbackCGroupPiT -Group <CGroupName>, -Freeze <PiTName>, -timeout 900
2-7
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore a View
RestoreView -view <ViewName>
The data of the designated view is collapsed (copied) into the source volume or view, the updated volume or view is renamed to the view name, and all PiTs are deleted. The source volume or source view name does not exist after this operation is completed. The restore view operation is permitted only when these conditions are met:
The designated view is defined on the last (and currently, the only) PIT of the source volume or view. There are no other views/PiTs defined on the source volume or view. There are no views or PiTs defined on the designated view.
multiCopy Commands
List multiCopy Groups
ListMCGroups
List multiCopy Jobs per Group

ListMCJobs -Group <GroupName>
Get multiCopy Group Information

GetMCGroupInfo -Group <GroupName>
Get multiCopy Job Information

GetMCJobInfo -job <JobName>
Create multiCopy Group

CreateMCGroup-Group <GroupName>, -volume <SourceName>, ~ -job <JobName1> _priority ~ -pool <PoolName1> _host <HostName1> ~ -permission RW|OFF [_thin 0|1], ~ [ -job <JobName2> _priority ~ -pool <PoolName2> _host <HostName2> ~ -permission RW|OFF [_thin 0|1] ,] ~ -timeout 900
If there is no host to receive permission for a job, enter a dummy (existing or non-existing) host name with permission set to OFF.
2-8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consistency Group Commands
Add a multiCopy Job To a Group

AddMCJobEx -MCGroup <MCGroupName>, -Job <MCJobName>, ~ -Domain <DestinationDomainName>, -Priority ~ -Volume <SourceVolumeName>, ~ -Destination <DestinationVolume>, ~ -Pool <PoolName>, ~ [-Thin 0|1,] [-host <HostName1> RW|OFF,] ~ -timeout 300
Add a multiCopy Job to a Group That Is Built Over a Consistency Group

AddCGMCJobEx -MCGroup <MCGroupName>,-Job <MCJobName>, ~ -CGroup <destinationCGroupName>, ~ -Domain <DestinationDomainName>, ~ -Priority 1|2|3, ~ [-host <HostName1> RW|OFF,] ~ -Volume <SourceVolume> _Destination <DestinationVolume> ~ -pool <PoolName> _thin [0|1] , ~ [-Volume <SourceVolume> _Destination <DestinationVolume> ~ -pool <PoolName> _thin [0|1] ,] -timeout 900
The CGroup parameter value is used as the name for the created consistency group (CG) on the destination. For any volume included in the source CG, you need to create a destination volume and indicate the pool from which the destination volume will be created. The number of the source volume identified in the -Volume parameter must be the same as the number of volumes in the source CG. It is also important to keep the same order as the volumes appear in the CG volume list.
Consistency Group Commands

Create a New Consistency Group
CreateCGroup -Group <CGroupName>, ~ -<DestinationVolume> <Volume_1_Name> [, -Volume <Volume_2_Name, ...>]
All of the volumes of the CG must have read-write permissions to exactly the same host or hosts.
2-9
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete a Consistency Group

DeleteCGroup -Group <CGroupName>
This command does not delete the any of the volume members in a consistency group.
Add a Volume to a Consistency Group

AddVolumeToCGroup -Group <CGroupName>, ~ -Volume <VolumeName>
This command cannot be used for a CG with Async multiMirror defined on it. All of the volumes of the CG must have read/write permissions to exactly the same host or hosts.
Remove Volumes from a Consistency Group

RemoveVolumesFromCGroup -Group <CGroupName>, ~ -Volume <Volume_1_Name> [, -Volume <Volume_2_Name,...> ]
This command does not delete any of the volume members.
Get the Information of a Consistency Group

GetCGroupInfo -Group <GroupName>
Create Point-in-Time of Consistency Group Volumes or Views

CreateCGroupPiT -Group <CGroupName>, -Freeze <PiTName> [TEMPLATE], ~ -timeout 900
2-10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consistency Group Commands
Create a View on a Consistency Group PiT

CreateCGroupView -Group <CGroupName>, -view <ViewName> , ~ -freeze <FreezeName> [LastInstance | LastAsyncMM], ~ -host <HostName1> RW|OFF, [-host <HostName2> RW|OFF, ...] ~ -pool <PoolName>, -cluster 0|1, -timeout 900
The name of the created individual views is built from the volume name and the consistency group view name. For example, for a volume named vol01 and a consistency group view named BK_view, the name of the created view is vol01BK_view. However, pay attention to the following restrictions:
Do not use the TEMPLATE flag for the view name. The total length of volume name and the view name cannot exceed 31 characters. The view name must be unique. When you delete a previously created consistency group view with same name just before invoking this command again to create another view with the same name. The command fails because the previously views with the same name had not been completely deleted yet. In such cases, a small delay (60 seconds) should be added (with the Pause command) before invoking this CLI command.
Create a View on a Consistency Groups Most Recently Created PiT

CreateCGroupViewOnLastPiT -Group <CGroupName>, ~ [ -Type Any | MV | UserPit ,] ~ -view <ViewName> [TEMPLATE], ~ -host <HostName1> RW|OFF, [-host <HostName2> RW|OFF, ...] ~ -pool <PoolName>, -cluster, -timeout 900
The PiT name is not specified, but the PiT type can be specified. The Type parameter specifies the type of the last PiT to use:
Any Any Pit or multiView (MV) PiT. UserPit An asynchronous multiMirror (Async MM) user PiT. SyncPiT is not allowed with the CG.
If you do not specify a type, the last PiT is used. Not specifying a type has the same effect as using the Any type.
2-11
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete a Consistency Groups Point-in-Time

DeleteCGroupPiT -Group <CGroupName>, -Freeze <PiTName> -timeout 900 ~
Delete a Consistency Groups Views

DeleteCGroupView -Group <CGroupName>, ~ -View <ViewName>, ~ -timeout 900
Asynchronous multiMirror Commands

Create an Asynchronous multiMirror Group
CreateMMGroupEx -Group <MMGroupName>, -Volume <SourceVolumeName>, ~ [-Interval <numberOfMinutes>,] ~ [-Keep <NumberOfPitsToKeep>,][, -UserPitOnly 0|1,] ~ , -Job <MMJobName>, -Domain <DestinationDomainName>, -Priority, -Destination <DestinationVolume>, -Pool <PoolName>, -Thin 0|1, -timeout 300
The -Interval parameter is optional and represents the time between creation of PiTs in minutes, the default value is 30 minutes. The -Keep parameter is optional and represents the number of PiTs to be tracked. The default value keeps one last PiT. The -UserPitOnly parameter determines if the mode of the application for this group will be a user PiT only. By default, it is set to 0.
Create an Asynchronous multiMirror Group over a Consistency Group

CreateCGMMGroupExMMGroup <MMGroupName>, ~ [-Interval <numberOfMinutes>,] ~ [-Keep <NumberOfPitsToKeep>,] ~ [, -UserPitOnly 0|1,] ~ , -Job <MMJobName>,-SourceCG <SourceCGroupName>, ~ , -DestinationCG <destinationCGroupName>,, -Domain <DestinationDomainName>, ~ -Priority, ~ -Volume <SourceVolume> _Destination <DestinationVolume> ~ _pool <PoolName> ~ [_thin 0|1], [-Volume <SourceVolume> _Destination <DestinationVolume> ~ _pool <PoolName> [_thin 0|1,] ] -timeout 900
2-12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous multiMirror Commands
The -SourceCG parameter is used as the name of the source consistency group. The -DestinationCG parameter is used as the name for the created consistency group on the destination. For any volume included in the source consistency group, the user must create a destination volume and indicate the pool from which the destination volume will be created. The -Interval parameter is optional and represents the time between creation of PiTs in minutes. The default value is 30 minutes. The -Keep parameter is optional and represents the number of PiTs to be tracked, the default value keeps one last PiT. The -UserPitOnly parameter determines if the mode of the application for this group is only user PiT. By default, it is set to 0. The number of the source volume identified in the -Volume parameter must be the same as the number of volumes in the source CG. Keep the same order as the volumes appear in the CG volume list.
Create User PiTs for Asynchronous multiMirror Groups

CreateMMUserPiTEx -Group <MMGroup_1_Name PiTRootName_1>, ~ [-Group <MMGroup_2_Name PiTRootName_2>, . . . ] ~ -timeout 900
If a failure occurs for any of the group on the list, the command stops running and does not process the rest of the list.
Pause Local Asynchronous multiMirror Groups

PauseLocalMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
Local means that the source volume is in the current domain. If a failure occurs for any group on the list, the command stops running and does not process the rest of the list.
2-13
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resume Local Asynchronous multiMirror Groups

ResumeLocalMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
Local means that the source volume is in the current domain. If a failure occurs for any group on the list, the command stops running and does not process the rest of the list.
Break Local Asynchronous multiMirror Groups

BreakLocalMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
All jobs of each group are broken, but the groups remain active. This command pauses all of the jobs of a group before breaking the jobs. Local means that the source volume is in the current domain. If a failure occurs for any group on the list, the command stops running and does not process the rest of the list.
Break Remote Asynchronous multiMirror Groups

BreakRemoteMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
All jobs of each group are broken, and the remote groups are deleted. Remote means that the source volume is in a remote domain. If a failure occurs for any group on the list, the command stops running and does not process the rest of the list.
Delete Remote Asynchronous multiMirror Groups

DeleteRemoteMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
Remote means that the source volume is in a remote domain. If a failure occurs for any group on the list, the command stops running and does not process the rest of the list.
2-14
Delete Local Asynchronous multiMirror Groups

DeleteLocalMMGroup -Group <MMGroupName_1>, ~ [-Group <MMGroupName_2, . . . > ,] ~ -timeout 900
Local means that the source volume is in the current domain.
Pause All Local Asynchronous multiMirror Groups

PauseAllLocalMMGroups -timeout 900
Local means that the source volume is in the current domain. This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
Resume All Local Asynchronous multiMirror Groups

ResumeAllLocalMMGroups -timeout 900
This command resumes all local asynchronous multiMirror groups that were previously paused. Local means that the source volume is in the current domain. This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
Break All Local Asynchronous multiMirror Groups

BreakAllLocalMMGroups -timeout 900
This command pauses group jobs before breaking the group jobs. All of the jobs of each group are broken, but the groups remain active. Local means that the source volume is in the current domain. This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
Break All Remote Asynchronous multiMirror Groups

BreakAllRemoteMMGroups -timeout 900
All of the jobs of each group are broken, and the groups are deleted. Remote means that the source volume is in a remote domain. This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
2-15
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pause the Jobs of a Local Asynchronous multiMirror Group

PauseLocalMMJob -Group <MMGroupName>, -Job <MMJobName_1>, ~ [-Job <MMJobName_2, . . .>,] ~ -timeout 900
Local means that the source volume is in the current domain. If a failure occurs for any job on the list, the command stops running and does not process the rest of the list.
Resume the Jobs of a Local Asynchronous multiMirror Group

ResumeLocalMMJob -Group <MMGroupName>, -Job <MMJobName_1>, ~ [-Job <MMJobName_2, . . .>,] ~ -timeout 900
This command resumes the jobs of a local asynchronous multiMirror group that was previously paused. Local means that the source volume is in the current domain. If a failure occurs for any job on the list, the command stops running and does not process the rest of the list.
Break the Jobs of a Local Asynchronous multiMirror Group

BreakLocalMMJob -Group <MMGroupName>, -Job <MMJobName_1>, ~ [-Job <MMJobName_2, . . .>,] ~ -timeout 900
This command pauses all jobs before breaking them. Local means that the source volume is in the current domain. If a failure occurs for any job on the list, the command stops running and does not process the rest of the list.
Break the Jobs of a Remote Asynchronous multiMirror Group

BreakRemoteMMJob -Group <MMGroupName>, -Job <MMJobName_1>, ~ [-Job <MMJobName_2, . . .>,] ~ -timeout 900
Remote means that the source volume is in a remote domain. This command tries to process all of the qualified groups, and ignores failures in the groups, if any failure exists.
2-16
Pause All Jobs of a Local Asynchronous multiMirror Group

PauseAllLocalMMJobs -Group <MMGroupName>, -Destination L|R, ~ -timeout 900
Local means that the source volume is in the current domain. The jobs Destination parameter can be one of these options:
L Local destination, which is the current domain. R Remote destination, which is one of the remote domains.
This command tries to process all of the qualified groups, and ignores failures in the groups, if any failure exists.
Resume All Jobs of a Local Asynchronous multiMirror Group

ResumeAllLocalMMJobs -Group <MMGroupName>, -Destination L|R, ~ -timeout 900
Local means that the source volume is in the current domain. The jobs Destination parameter can be one of these options:
This command tries to process all of the qualified groups, and ignores failures in the groups, if any failure exists.
Break All Jobs of a Local Asynchronous multiMirror Group

BreakAllLocalMMJobs -Group <MMGroupName>, -Destination L|R, ~ -timeout 900
This command pauses all jobs before breaking them. Local means that the source volume is in the current domain. The jobs Destination parameter can be one of these options:
This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
2-17
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Break All Jobs of a Remote Asynchronous multiMirror Group

BreakAllRemoteMMJobs -Group <MMGroupName>, -timeout 900
This command deletes the remote group. Remote means that the source volume is in a remote domain. This command tries to process all of the qualified groups and ignores failures in the groups, if any failure exists.
Synchronous multiMirror Commands

Create a Synchronous multiMirror Group
CreateSyncMMGroup -Name <SyncMMGroupName>, ~ -Volume <SourceVolumeName>, ~ [-QuickRestore 1|2 ,] [-Mode 1|2 ,] -timeout 900
The QuickRestore parameter identifies the dirty mode behavior and can be one of these options:
1 No QuickRestore 2 QuickRestore regions
The Mode parameter can be one of these options:
1 Always synchronous 2 Automatic failover
EXAMPLES:
CreateSyncMMGroup -Name SyncName, -Volume "test", -timeout 900 CreateSyncMMGroup -Name SyncGrpName , ~ -Volume testDyn,-QuickRestore 2, -Mode 2,-timeout 900 CreateSyncMMGroup -Name SyncGrpName , -Volume SourceName, ~ -Mode 2,-timeout 900
2-18
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous multiMirror Commands
Add a Synchronous multiMirror Job to Synchronous multiMirror Group

AddSyncMMJobToGroup -Group <SyncMMGroupName>, ~ -Domain <DestinationDomainName>, ~ -Volume <DestinationVolume>, ~ -Pool <PoolName>, [-WaitForSync 0|1] , ~ -timeout 900
By default, this command will complete only after the job was created and synchronized (WaitForSync = 1). To immediately return after the job creation and not to wait for the job to be fully synchronized, set the WaitForSync parameter to reset (WaitForSync = 0).
Create PiT on a Synchronous multiMirror Group

CreateSyncMMPiT -Group <sMMGroupName>, ~ -Freeze <PiTName> [TEMPLATE], -timeout 900
Delete a PiT on a Synchronous multiMirror Group

DeleteSyncMMPiT -Group <sMMGroupName>, -Freeze <PiTName>, -timeout 900
Change the Mode of Operation of a Synchronous multiMirror Group

ChangeSyncMMGroupMode -Group <sMMGroupName>, -Mode 1|2
The Mode parameter can be one of these options:
1 Always synchronous 2 Automatic failover
Resume Synchronous multiMirror Group

ResumeSyncMMGroup -Group <sMMGroupName>
Delete-sync a (Previously Failed) Synchronous multiMirror Group

DeleteSyncMMGroup -Group <sMMGroupName>
Re-sync a (Previously Failed) Synchronous multiMirror Group

ReSyncMMGroup -Group <sMMGroupName>
2-19
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Break Synchronous multiMirror Jobs

BreakSyncMMJob -Group <sMMGroupName>, ~ -Job Job_1_Name [, -Job Job_2_Name, . . . ]
multiMigrate Commands
Migrate a Volume
MigrateVolume -Group <GroupName>, -Volume <SourceVolume>, ~ -AuxVol <auxilaryVolumeName>, ~ -Pool <PoolName>, -Priority1, [-Thin 0|1 ,] ~ -timeout 200
Manage Migration
NOTE Allow up to 120 seconds for this command to fully take effect.
ManageMigration -Group <GroupName> 1|2|3|4
Optional values for an operation or an action are: 1 Pause migration task 2 Resume migration task 3 Abort migration task 4 Delete migration task group
DPM-Related Commands
Set or Change the Volume LUN Configuration
SetUDHVolumeLun -Volume "<volumeOrViewName>", ~ -Host "<UDH_Name>",~ -Lun "<LunNumber>"
Parameters:
-Volume The volume or view name. -Host The host (UDH) name that has read/write permission for this volume. -Lun The LUN number attched to this volume. The LUN number must be a decimal value from 0 to 254.
EXAMPLE:
SetUDHVolumeLun -Volume "vol1", -Host "host1", -Lun "2"
2-20
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System-Related Commands
Change Active DPM (Switch)

ChangeActiveSwitch -CGroup | -Volume | -View | -SyncGroup ~ <objectName>
For each object, like volume, consistency group, views, or sync mirror group, a pair of primary and secondary DPMs are defined. At any time, one of the DPMs is the active DPM for I/O traffic from the host to the object. This command allows changing the active DPM for a particular object by failing over between the primary DPM and the secondary DPM.
Operating System-Related Commands

Run an Operating System Command from Within the SVM CLI
Run -Command <OneCommandLine>
This command takes the operating system command and sends it to the operating system for execution. When running an operating system command from the SVM CLI, follow these rules:
The command line must be in the correct format for the operating system. The input line cannot be broken. Continuation lines are not allowed.
Mount a Volume or View to the Windows Operating System

MountVolume -MountPoint H:\, -Volume <VolumeName> ~ [, -Override]
The volume or view must have at least one file system (partition) on it. The mount point must always end with a \ . For example, "Q:\", "H:\MP\"
If the mount point points to a folder, the target folder must meet these conditions:
The target folder must be empty or non-existent. The target folder must be under an NTFS file system.
2-21
SVM CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If the mount point is already used by an SVM volume or view, the command behavior is determined by the Override argument.
If the Override argument is specified, then the existing SVM volume or view mount point is unmounted before mounting the new volume or view. If the Override argument is not specified and the mount point is not free, the command fails.
Unmount a Volume or View from the Windows Operating System

UnmountVolume -Volume <VolumeName> [, -Partition <Partition>] UnmountVolume -Volume <VolumeName>, -MountPoint H:\
Flush I/O into Volume or View

FlushCache -volume <MountedVolumeOrViewName>
This command is valid only for the Windows operating systems. This command flushes to the disk the operating system memory cache associated with an SVM volume or view.
2-22
Chapter
Using the SVM CLI Server-Free Backup

One of the most common tasks is running backups. When running backups, a requirement is to minimize, or in some cases completely eliminate, the impact of the backup on the disk and the host performance. To achieve this goal, a snapshot of the disk is taken and mounted to the backup server. The backup process is running from the backup host and not the application, hence server-free backup, against the snapshot and not against the production disk. This method requires coordination between the storage side (SVM) and the backup system because each side needs to perform several steps. This chapter describes how to use the SVM CLI scripting capabilities to automate this process in a non-Windows operating system environment and a Windows operating system environment.
Typical Server-Free Backup Process

A typical server-free backup has four major steps: 1 2 3 4 Creating a snapshot. Mount the snapshot to the backup server. Run the backups. Unmount the snapshot from the backup server and delete the snapshot.
Server-Free Backup in SVM Environment for a Non-Windows Operating System

The following steps are required to implement server-free backup in the SVM environment: 1 2 3 4 5 6 7 Create a PIT on the volume you want to back up. Create a view for that PIT. Assign the view to the backup host. Mount the view to the backup server. Run the backup. Unmount the view from the backup server. Remove the view permission to the backup host.
3-1
Using the SVM CLI Server-Free Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 9
Delete the view. Delete the PIT (optional).
Automating a Server-Free Backup for a Non Windows Operating System

The following sections describe how to automate these steps using SVM CLI scripts 1 Create the PiT by using a script that runs the following command:
CreatePiT -volume <VolumeName>, -freeze <PiTName> [TEMPLATE], ~ -timeout 900
Create the view and assign the view to the backup server by using a script that runs the following command:
CreateView -freeze <PiTRootName> Lastinstance, -View <ViewName>, host~ BackupServerName RW, -pool <PoolName>, -cluster 0, ~ -timeout 900 Mountvolume -MountPoint H:\, -volume <ViewName>, -Override
Unassign the view from the backup server, and delete the view by using a script that runs the following command:
Unmountvolume -volume <ViewName> -MountPoint H:\ -timeout 900 DeletePiTOrView -name <ViewName>, -timeout 900
If you want to delete the PIT, add the following command to this same script:
DeletePiTOrView -name <PiTName>, -timeout 900
Scheduling the Scripts

The last step for implementing the server-free backup in the SVM environment for non-Windows operating systems and automating the process is to schedule the scripts.
On the application host: Use the operating system scheduler to schedule the script that creates the PIT to run a couple of minutes before the scheduled backup job starts.
On the backup host Most backup applications provide the option to run the script before the actual backup job starts to run (pre-backup) and to run another script after the backup job is completed (post-backup).
3-2
. . . . . . . . . . . . . Server-Free Backup in the SVM Environment for the Windows Operating System
Place the script that creates the view and assigns the view to the backup server as the pre-backup script and the script that unmounts the view from the backup server. Delete the view and, optionally, delete the PIT as the post-backup script.
Server-Free Backup in the SVM Environment for the Windows Operating System
On the Windows operating system (Windows 2003 SP1 and later), the server-free backup is easier to implement. The Windows operating system includes the Microsoft VSS, which performs these tasks:
Coordinates and manages the creation of the snapshot (PiT and view). Assigns the view to the backup server and the cleaning processes after the backup is finished. Automatically initiated by the backup software.
You do not need an SVM CLI script when using Microsoft VSS. For more details on Microsoft VSS, refer to Microsoft online documentation. For more details on how to install LSI VSS hardware provider on the Windows hosts, refer to the SVM5 Installation and Configuration User Guide.
3-3
Using the SVM CLI Server-Free Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4
Chapter
Creating a PiT and a View with Microsoft VSS

Microsoft VSS (Virtual Snapshot Service), also known as Virtual Shadow Copy, is a unified storage management interfaces for Microsoft Windows Server 2003 SP1 and later. Microsoft VSS is intendeds primarily for backup solution. Figure 4-1 shows the Microsoft VSS components and their functions.
Figure 4-1 VSS Components
Table 4-1 Component
VSS Component Functions Description
Volume Shadow Copy Service Requestor Writer
A service that coordinates various components to create consistent shadow copies of one or more volumes. An application that requests that a volume shadow copy be taken. A backup application is an example. A component of an application that stores persistent information on one or more volumes that participate in shadow copy synchronization. Typically, this database application is like SQL Server or Exchange Server or a system service like Active Directory.
4-1
Creating a PiT and a View with Microsoft VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-1 Component
VSS Component Functions (continued) Description
Provider
A component that creates and maintains the shadow copies. Examples are the hardware providers included with storage arrays. LSI also provides a VSS hardware provider for SVM. The volume that contains the data to be shadow copied.
Source volume
The major benefit of using Microsoft VSS for backups or creating snapshots is the capability of VSS to commit/flash (also known as Quiescing) all I/O to the disks before taking the snapshots receiving persistent data. There is no need to use the SANAPI CLI because the LSI VSS hardware provider is replacing the SANAPI CLI.
LSI VSS Hardware Provider

The LSI VSS Hardware Provider installs as a service on a Windows host and receives requests from the VSS service on the host to create or delete snapshots. The LSI VSS hardware then communicates with the DPM and SVM to create or delete the snapshots by issuing request to create PiT and then a view, or delete the view and then the PiT. After they are created, the views are also automatically assigned to the server from which the VSS request came. For more information about how to install and configure the LSI VSS Hardware Provider, refer to the SVM 5 Installation and Configuration User Guide.
Using the Microsoft VSS to Create a Persistent PiT and View

While the purpose of Microsoft VSS is to create persistent snapshots for backups, Microsoft VSS can also be used to create persistent snapshots (views) for other usage, or to create a persistent user PiT for a source volume in an Async multiMirror Group. To do so, a VSS requestor needs to initiate the request for the PiT and view from a specific server. Microsoft has developed a requestor called VSHADOW, which is a command line utility that can be downloaded from the VSS SDK on the MSDN website. The following sections describe how to use the VSHADOW as a requestor to create a PiT and view within batch script files.
Using Microsoft VSS to Create a PiT and View

Create a Windows batch file that contains the command that does the following: 1 2 Create the PiT and the view. Assign the view back to the host from which this batch file is running.
4-2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Microsoft VSS to Create a Persistent PiT and View
For example, to take a snapshot of disk F: and assign it back to the same server with read-only permissions, enter this command:
vshadow -p -script=c:\scripts\vss\env.cmd F:
In this example, the batch file includes the VSHADOW command to create the snapshot from the F: disk. 3 Run VSHADOW again to mount the snapshot to the host.
call script=c:\scripts\vss\env.cmd vshadow - el=%SHADOW_ID_1%,c:\mnt\2008Jul22152910\device_1
The VSHADOW pickups the value of the =%SHADOW_ID_1% from the env.cmd file created by the first run of the VSHADOW command, and then mounts it to a mount point, which in this example is c:\mnt\2008Jul22152910\device_1.
Using Microsoft VSS to create a User PiT for Async Mirror

Create a Windows batch file that contains a command that does the following: 1 Create the user PiT without a view. For example, to take a user PiT of disk F: , enter this command:
vshadow -script=c:\scripts\vss\env.cmd F:
In this example, the batch file includes the VSHADOW command to create the user PiT from the F: disk. The command runs without the -p operator, which causes the view and its PiT to be deleted at the end of the operation, except when the volume is marked as an async mirror source. In this case, only the view is deleted.
4-3
Creating a PiT and a View with Microsoft VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
Chapter
Upgrading From SVM 4 to SVM 5

Customers that were working with SAN API CLI scripts on SVM 4 and are planning to upgrade their environment to SVM 5 need to be aware of the constraints described in this chapter.
Updating the SANAPI CLI Packages

The SAN API CLI package that previously worked with SVM 4 is not supported and needs to be removed from the hosts and replaced by the latest supported SAN API CLI package version for SVM 5. Refer to the current SVM 5 version release notes for the currently supported SAN API package version for the appropriate operating system. All SAN API CLI scripts must be reviewed and updated according the information in the following sections.
SANAPI Application Pack and Microsoft VSS

The SAN API AppPacks for specific applications that were provided for SVM 4 environments are no longer supported for SVM 5 environments. Replace these scripts with Microsoft VSS. For more details on using Microsoft VSS, see Chapter 4, Creating a PiT and a View with Microsoft VSS.
Updated SANAPI CLI Commands

The SAN API CLI packages introduce updated commands that are adjusted to work with the SVM 5 environment. Review your scripts, and replace these commands so that your scripts will work with SVM 5. These are the updated commands:
CreateMMUserPiTEx AddMCJobEx AddCGMCJobEx CreateMMGroupEx CreateCGMMGroupExMMGroup ExpandPartitionEx
See Chapter 2, SVM CLI Commands, for details about these commands.
5-1
Upgrading From SVM 4 to SVM 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
Trademarks
This Product includes software under the following terms:
Copyright and Licensing Information for ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM)
ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM) (henceforth referred to as "DOC software") are copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright 1993-2008, all rights reserved. Since DOC software is open-source, freely available software, you are free to use, modify, copy, and distribute-perpetually and irrevocably--the DOC software source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with any code built using DOC software that you release. No copyright statement needs to be provided if you just ship binary executables of your software products. You can use DOC software in commercial and/or binary software releases and are under no obligation to redistribute any of your source code that is built using DOC software. Note, however, that you may not do anything to the DOC software code, such as copyrighting it yourself or claiming authorship of the DOC software code, that will prevent DOC software from being distributed freely using an open-source development model. You needn't inform anyone that you're using DOC software in your software, though we encourage you to let us know so we can promote your project in the DOC software success stories. The ACE, TAO, CIAO, and CoSMIC web sites are maintained by the DOC Group at the Institute for Software Integrated Systems (ISIS) and the Center for Distributed Object Computing of Washington University, St. Louis for the development of open-source software as part of the open-source software community. Submissions are provided by the submitter ``as is'' with no warranties whatsoever, including any warranty of merchantability, noninfringement of third party intellectual property, or fitness for any particular purpose. In no event shall the submitter be liable for any direct, indirect, special, exemplary, punitive, or consequential damages, including without limitation, lost profits, even if advised of the possibility of such damages. Likewise, DOC software is provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage or trade practice. Washington University, UC Irvine, Vanderbilt University, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by DOC software or any part thereof. Moreover, in no event will Washington University, UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages. DOC software is provided with no support and without any obligation on the part of Washington University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use, correction, modification, or enhancement. A number of companies around the world provide commercial support for DOC software, however. DOC software is Y2K-compliant, as long as the underlying OS platform is Y2K-compliant. Likewise, DOC software is compliant with the new US daylight savings rule passed by Congress as "The Energy Policy Act of 2005," which established new daylight savings times (DST) rules for the United States that expand DST as of March 2007. Since DOC software obtains time/date and calendaring information from
Trademarks-1
..............................................................................
operating systems users will not be affected by the new DST rules as long as they upgrade their operating systems accordingly. The names ACE(TM), TAO(TM), CIAO(TM), CoSMIC(TM), Washington University, UC Irvine, and Vanderbilt University, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University, UC Irvine, or Vanderbilt University. This license grants no permission to call products or services derived from this source ACE(TM), TAO(TM), CIAO(TM), or CoSMIC(TM), nor does it grant permission for the name Washington University, UC Irvine, or Vanderbilt University to appear in their names.
Fast DB Distribution terms

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHOR OF THIS SOFTWARE BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.2, October 3rd, 2004
Copyright 1995-2004 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. This notice may not be removed or altered from any source distribution.
2. 3.
Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu
Trademarks-2
.............................................................................
PostgreSQL Data Base Management System

Portions Copyright (c) 1996-2008, PostgreSQL Global Development Group Portions Copyright (c) 19941996 Regents of the University of California Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
Java Service Launcher (for Windows) JSL 0.99i - August 20th 2008
License: There is no license required for version 0.9xx of the JSL executable. The software is FREE. Free means you may use or reuse any part of it the software. You may package it with commercial software and use it in commercial and business environments. You may NOT claim copyright for the JSL software and its source code or any parts of the software and source. Any derived work may retain a copyright or be commercialized as long as the JSL parts of it are not covered by this copyright. You may distribute derived work in executable form and not contain the JSL source code if JSL constitues only a minor part of the intellectual work (in other words, you can take the code and embed it in a Java application you distribute commercially), but you may not charge in particular for or discriminate against or for the use of the parts derived from JSL. In short words: Keep the spirit of free software up. Use it for your project but do not try to commercialize my work. Some pieces of the JSL srouce code come from MSDN and SUN Java launcher examples. As far as I can see Microsoft and SUN have granted developers acknowledging their copyright the permission to create redistributable binaries from those sources If you want to extend the JSL source code I recommend you acknowledge the MSDN and SUN license conditions. You probably have done so anyway by downloading Java and using VC++. This software is supplied AS IS. Sources are supplied for informational purposes for the experienced developer. Please note that this means: I will not take any liability for any direct or indirect consequences of running JSL on your computer.
Trademarks-3
..............................................................................
Please do not use this software in critical environments where human life depends on it. I did NOT run a thorough quality assurance for this software. I cannot guarantee any support or response times. I can offer advice and even consulting if I happen to have time. If you need extensive customizations or extensive QA you will either need to do it yourself or pay me to do it.
OpenSSH 5.1/5.1p1 released July 21, 2008

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on. Users of telnet, rlogin, and ftp may not realize that their password is transmitted across the Internet unencrypted, but it is. OpenSSH encrypts all traffic (including passwords) to effectively eliminate eavesdropping, connection hijacking, and other attacks. Additionally, OpenSSH provides secure tunneling capabilities and several authentication methods, and supports all SSH protocol versions. The OpenSSH suite replaces rlogin and telnet with the ssh program, rcp with scp, and ftp with sftp. Also included is sshd (the server side of the package), and the other utilities like ssh-add, ssh-agent, sshkeysign, ssh-keyscan, ssh-keygen and sftp-server. OpenSSH is developed by the OpenBSD Project. The software is developed in countries that permit cryptography export and is freely useable and re-useable by everyone under a BSD license. However, development has costs, so if you find OpenSSH useful (particularly if you use it in a commercial system that is distributed) please consider donating to help fund the project. OpenSSH is developed by two teams. One team does strictly OpenBSD-based development, aiming to produce code that is as clean, simple, and secure as possible. We believe that simplicity without the portability "goop" allows for better code quality control and easier review. The other team then takes the clean version and makes it portable (adding the "goop") to make it run on many operating systems -- the so-called -p releases, ie "OpenSSH 5.1p1". We sell OpenSSH T-shirts and posters. Sales of these items also help to fund development.
Apache License Version 2.0, January 2004

Copyright 2008 LSI Corporation Modified by LSI Corporation to support IPv6. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/ LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Trademarks-4
.............................................................................
Copyright (c) 2005 Envoi Solutions LLC

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copyright (c) 1990-2007 Info-ZIP. All rights reserved.

For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals: Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ed Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda, Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White. This software is provided "as is," without warranty of any kind, express or implied. In no event shall InfoZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the above disclaimer and the following restrictions: Redistributions of source code (in whole or in part) must retain the above copyright notice, definition, disclaimer, and this list of conditions. Redistributions in binary form (compiled executables and libraries) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, versions with modified or added functionality, and dynamic, shared, or static library versions not from Info-ZIP--must be plainly marked as such and must not be misrepresented as being the original source or, if binaries, compiled from the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip"
Trademarks-5
..............................................................................
without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or the Info-ZIP URL(s), such as to imply Info-ZIP will provide support for the altered versions. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases.
STLport 5.0
LEGALESE This software is being distributed under the following terms: Copyright (c) 1994 Hewlett-Packard Company Copyright (c) 1996-1999 Silicon Graphics Computer Systems, Inc. Copyright (c) 1997 Moscow Center for SPARC Technology Copyright (c) 1999-2003 Boris Fomitchev
This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.
The following copyright and license is applicable to the entire OpenSLP project (libslp, slpd, and related documentation):
Copyright 2000 Caldera Systems, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Caldera Systems nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CALDERA SYSTEMS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
Trademarks-6
.............................................................................
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Trademarks-7

LSI - 36100-00, Rev. A, August 2009 - SVM CLI User Guide

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

LSI - 36100-00, Rev. A, August 2009 - SVM CLI User Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

LSI Storage Virtualization Manager Command Line Interface

Proprietary Rights Notice

Chapter 2: SVM CLI COMMANDS

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

Chapter 3: USING THE SVM CLI SERVER-FREE BACKUP

Chapter 4: CREATING A PIT AND A VIEW WITH MICROSOFT VSS

LSI Storage Virtualization Manager CLI User Guide

Chapter 5: UPGRADING FROM SVM 4 TO SVM 5

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

CHAPTER 4: CREATING A PIT AND A VIEW WITH MICROSOFT VSS

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

Definitions of Informational Notices

IMPORTANT Indicates information or criteria that is necessary to perform a procedure correctly.

NOTE: Indicates a clarification of a concept or presents a maintenance tip.

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

About This Document

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

Installation and Configuration

Obtain the Appropriate Package for the Host Operating System

Solaris operating system Run this package: pkg add -d SVM.App-Pack.Solaris.LA.5.1.28.1.pkg.Z

LSI Storage Virtualization Manager CLI User Guide

AIX operating system Run this package: installp -acd SanApi.AIX.5.1.28.4.LA.bff

Creating the SANAPI Volume

7 In the Pools table, select the pool, and click Add.

LSI Storage Virtualization Manager CLI User Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SVM CLI Command Syntax

The pool appears in the Selected Pools table.

12 In the Select LUN dialog, select one of the LUN options:

SVM CLI Command Syntax

Alternative parameters are separated by a pipe symbol ...|...|....

Variable input is enclosed in angle brackets <...>.

Optional CLI input is enclosed in square brackets [...].

LSI Storage Virtualization Manager CLI User Guide

LSI Storage Virtualization Manager CLI User Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SVM CLI Command Syntax

EXAMPLE Multiple value string:

LSI Storage Virtualization Manager CLI User Guide

Special Symbols Used in SVM CLI

At the beginning of a line in an input file.

Before the end-of-line mark (carriage return and line feed).

LSI Storage Virtualization Manager CLI User Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SVM CLI Command Syntax

? (question mark) (minus)

Constraints on the Values of the CLI Parameters

Using Templates to Run the Same Script

LSI Storage Virtualization Manager CLI User Guide

Using Templates to Delete Old Objects

Synchronous and Asynchronous Modes

LSI Storage Virtualization Manager CLI User Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous and Asynchronous Modes

CreateVolume CreatePiT CreateView Operations CreateCGroupPiT CreateCGroupView CreatemultiMirrorUserPiT CreateMCGroup

LSI Storage Virtualization Manager CLI User Guide

Basic Interactive Help (Console Mode)

Returned Execution Status