Dell EqualLogic PS6210XS EqualLogic Auto-Snapshot Manager/Microsoft Edition Ve - Page 115

ASMCLI -modifyCollection, ASMCLI -mount

Get Dell EqualLogic PS6210XS PDF manuals and user guides View all Dell EqualLogic PS6210XS manuals
Add to My Manuals
Save this manual to your list of manuals

Page 115 highlights

> ASMCLI -list • List all of the configured SharePoint writers: > ASMCLI -list ASMCLI -modifyCollection The ‑modifyCollection command modifies an existing collection by replacing the current definition with a list of volumes or components, if the list constitutes a valid collection. If the modification fails validation, the original definition is unchanged. Command Syntax ASMCLI ‑modifycollection [-collection="collection_name"] [-volume={"drive" | "mount_point"} | -component="component_name"] [-newname] [-volumeBased={"Yes"|"No"}] For a description of these parameters, see Command Parameters. Example Modify the collection Test Collection 1 by changing its definition to volumes e:\ and f:\, and add any components contained on the new volumes. > ASMCLI ‑modifycollection ‑collection="Test Collection 1" ‑volume=e:\;f:\ ASMCLI -mount Specify the ‑mount subcommand to mount an existing Smart Copy. Use optional parameters to mount multiple volumes and control the selection of volumes. NOTE: ASM will only detect drives that were mapped with the same user as ASM is running. This limitation is caused by the user access control behavior on Windows. Explorer runs under the administrator account, so if you used Explorer to map a network folder and your ASM is running as a system account, ASM will not detect that network folder. That network folder will be mounted but you will still see the network folder mapped to the original drive letter you used in Explorer. Command Syntax ASMCLI ‑mount [{-document="path" | -volume={"drive_letter" |"mount_point"}| -component="component_name" | -collection="collection_name"| -writer="writer_name" | -objectID="identifier"}] [{-location="* | drive_letterA;drive_letterB;...| mount_point;;;;... | -locationroot=

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
> ASMCLI -list
•
List all of the configured SharePoint writers:
> ASMCLI -list
ASMCLI -modifyCollection
The
‑
modifyCollection
command modifies an existing collection by replacing the current definition with a list of volumes or
components, if the list constitutes a valid collection. If the modification fails validation, the original definition is unchanged.
Command Syntax
ASMCLI
‑
modifycollection
[-collection="
collection_name
"]
[-volume={"
drive
" | "
mount_point
"} |
-component="
component_name
"]
[-newname] [-volumeBased={"Yes"|"No"}]
For a description of these parameters, see
Command Parameters
.
Example
Modify the collection Test Collection 1 by changing its definition to volumes
e:\
and
f:\
, and add any components contained on the new
volumes.
> ASMCLI
‑
modifycollection
‑
collection="Test
Collection 1"
‑
volume=e:\;f:\
ASMCLI -mount
Specify the
‑
mount
subcommand to mount an existing Smart Copy.
Use optional parameters to mount multiple volumes and control the selection of volumes.
NOTE:
ASM will only detect drives that were mapped with the same user as ASM is running. This limitation is caused by
the user access control behavior on Windows. Explorer runs under the administrator account, so if you used Explorer to
map a network folder and your ASM is running as a system account, ASM will not detect that network folder. That
network folder will be mounted but you will still see the network folder mapped to the original drive letter you used in
Explorer.
Command Syntax
ASMCLI
‑
mount
[{-document="
path
" |
-volume={"
drive_letter
" |"
mount_point
"}|
-component="
component_name
" |
-collection="
collection_name
"|
-writer="
writer_name
" |
-objectID="
identifier
"}]
[{-location="* |
drive_letterA
;
drive_letterB
;...|
mount_point;;
;;... |
-locationroot=<
drive_letter
|
mount_point
}]"
[{-useLatest | -useEarliest}] [-email | -noemail]
-readwrite -retry=
n
For a description of these parameters, see
Command Parameters
.
Examples
•
Mount the Smart Copy backup document named
e2b3
‑
f1a3
‑
234.bcd
on drive
D:/
> \ASMCLI
‑
mount
‑
document="C:\BackupDocs\Shadows\
PSV{18A09060
‑
3BE0
‑
3FA8
‑
0A7A
‑
E4120000E045;32256}\e2b3
‑
f1a3
‑
234.bcd"
‑
location=D:\
Using the Command Line Interface
115