Command-line arguments
-
PDF of this doc site
-
Administration for Linux
- Role-based access control in SnapDrive for UNIX
-
Installation and Administration for Solaris
- Role-based access control in SnapDrive for UNIX
- Creating and using Snapshot copies in SnapDrive for UNIX
-
Installation and Administration for IBM AIX
- Role-based access control in SnapDrive for UNIX
-
Administration for Linux
Collection of separate PDF docs
Creating your file...
The SnapDrive for UNIX takes arguments in a specific format.
The following table describes the arguments you can specify with the keywords.
Use the format snapdrive type_name operation_name [<keyword/option> <arguments>]
; for example, if you wanted to create a Snapshot copy called snap_hr
from the host file system /mnt/dir
, you would enter the following command line:
snapdrive snap create -fs/mnt/dir -snapnamesnap_hr
.
Argument | Description | ||
---|---|---|---|
dest_fspec |
The name by which the target entity will be accessible after its disk groups or LUNs are connected. |
||
dgname |
The name of a disk group or volume group. |
||
d_lun_name |
Allows you to specify a destination name that SnapDrive for UNIX uses to make the LUN available in the newly-connected copy of the Snapshot copy. |
||
filername |
The name of a storage system. |
||
filer_path |
A path name to a storage system object. This name can contain the storage system name and volume, but it does not have to if SnapDrive for UNIX can use default values for the missing components based on values supplied in the previous arguments. The following are examples of path names:
|
||
file_spec |
The name of a storage entity, such as a host volume, LUN, disk or volume group, file system, or NFS directory tree. In general, you use the file_spec argument as one of the following:
The objects do not have to be all of the same type. If you supply multiple host volumes, they must all belong to the same volume manager. If you supply values for this argument that resolve to redundant disk groups or host volumes, the command fails. Example of incorrect usage: This example assumes dg1 has host volumes hv1 and hv2, with file systems fs1 and fs2. As a result, the following arguments would fail because they involve redundant disk groups or host volumes.
Example of correct usage: This example shows the correct usage for this argument.
|
||
fspec_set |
Used with the snap connect command to identify:
The argument also lets you specify a set of destination names that SnapDrive for UNIX uses when it makes the entity available in the newly connected copy of the Snapshot copy. The format for fspec_set is: |
||
host_lvm_fspec |
Lets you specify whether you want to create a file system, logical volume, or disk group when you are executing the storage create command. This argument might have any of the three formats as described in the following. The format you use depends on the entity you want to create.
|
||
To create a file system, use this format: You must name the top-level entity that you are creating. You do not need to supply names for any underlying entities. If you do not supply names for the underlying entities, SnapDrive for UNIX creates them with internally generated names. If you specify that SnapDrive for UNIX create a file system, you must specify a type that SnapDrive for UNIX supports with the host LVM. These types include The option |
|||
ig_name |
The name of an initiator group. |
||
long_filer_path |
A path name that includes the storage system name, volume name, and possibly other directory and file elements within that volume. The following are examples of long path names:
|
||
long_lun_name |
A name that includes the storage system name, volume, and LUN name. The following is an example of a long LUN name:
|
||
long_snap_name |
A name that includes the storage system name, volume, and Snapshot copy name. The following is an example of a long Snapshot copy name: With the Example: This example uses wildcards with both the snap show command and the snap delete command: snap show myfiler:/vol/vol2:mysnap*
Limitation for wildcards: You cannot enter a wildcard in the middle of a Snapshot copy name. For example, the following command line produces an error message because the wildcard is in the middle of the Snapshot copy name: banana:``/vol/vol1:my*snap` |
||
lun_name |
The name of a LUN. This name does not include the storage system and volume where the LUN is located. The following is an example of a LUN name: |
||
path |
Any path name. |
||
prefix_string |
prefix used in the volume clone's name generation |
||
s_lun_name |
Indicates a LUN entity that is captured in the Snapshot copy specified by |
Related information