HP StorageWorks SAN Virtualization Services Platform Manager command line interface user guide (AG781-96016, March 2009)

• When expanding a dynamic volume (file system) with the CLI commands, the command will always
expand the VSM virtual disk associated with the first dynamic disk added to the dynamic volume
(file system).
For example, if the dynamic volume P: was originally created spanning three disks (#7, #8, and
#9), the CLI command will expand the VSM virtual disk associated with disk #7 (which is presum-
ably the first disk to be added to that partition).
Expanding a partition (file system) on Windows 2003/2008
When using the ExpandPartition and the ExpandPartitionEx commands on Windows
2003/2008, make sure that Windows Disk Manager console is closed. Leaving the Disk Manager
console open while the VSM API tries to expand a file system may cause the operation to fail. In case
of a failure because of Disk Manager, close it and rerun the ExpandPartition command, expanding
the partition by a small amount of storage (by no less than 100 MB).
General comments
Template/root names
Names of created VSM objects (such as, point-in-time (PiT), snapshot, and so on) may be fully provided
by the user explicitly, or may be provided as a template (root) name, to which the VSM API
concatenates a unique suffix to create a complete unique name. This is useful when you want to run
the same script every day to create some new VSM object (for example, a PiT on a virtual disk). If
you provide an absolute PiT name, an error occurs the second time the script runs, since there is
already a PiT by that name. However, if you provide a template/root name for the PiT, every execution
of the script will create a PiT with a different name.
For example, if you create a PiT with the template name pit_on_vol_1, then every time the script
is run, a PiT is created with a name similar to pit_on_vol_1_SA_123456789, where the number
following the _SA_ string is different every time the script is run.
Template/root names are limited to under 16 characters. Template names are also useful for cleanups.
If the above script is run periodically, creating a new object every time, old objects need to be cleaned
up. There is a Purge operation for this purpose. The Purge operation uses the template name to delete
old objects whose names start with the template name (followed by the _SA_ string), leaving a
user-defined number of the most recently created objects.
IMPORTANT:
To prevent mistakes or errors, it is essential that you use a unique template name for every type of
created object (PiT, snapshot, and so on) from every source object (for example, virtual disk, virtual
disk group, synchronous/asynchronous mirror group, and so on), so that the Purge operation deletes
only those objects originating from the same source.
Synchronous and asynchronous operations
Many APIs and CLI commands may take some time to complete, so a timeout argument is required.
This argument defines the maximum time that the API or CLI will wait for the completion of the operation.
If the operation completes before the timeout period expires, the API or CLI returns at that time with
a success status. If the command does not complete within the timeout period, the API or CLI returns
after the timeout period expires with a VSM_SYNC_TIMEOUT error.
Overview14