Users Guide

● Used with: alert subcommand
● Specify the category name (Critical, Warning, or Informational) or the category abbreviation (C, W, or I) to enable all alerts
of that type.
enableEmails=
● Used with: configureASM subcommand
● Specify whether or not to enable email functionality when configuring ASM/ME. The options are yes and no.
ignorelogoutfail
● Used with: smart, verify, unmount, restore subcommands
NOTE: This parameter is restricted to Windows Server 2012 R2.
● Specify the ‑ignorelogoutfail parameter to change the default command behavior for logout failures. By default, the
unmount operation is aborted if it encounters a logout failure and all retry attempts are exhausted. When you specify
‑ignorelogoutfail, the unmount operation forces the logout.
CAUTION: To avoid a risk of data corruption, make sure that no files are open on the volume that you intend
to unmount.
keepcount= nn
● Used with: smart subcommand
● Specify ‑keepcount=nn where the value of nn is an integer in the range 0‑99. This value indicates the maximum number of
Smart Copy backup documents retained at any one time. If you not specify a value for ‑keepcount, a default value of 8
backup documents is assumed.
● Replication schedules for boot volumes create three Smart Copy replicas on the group for every one displayed in ASM, for
each replication. The keepcount value refers to the number of replicas maintained by ASM, not on the group. When you
delete a Smart Copy from the host, all three replicas created by the scheduled replication are deleted.
● The ‑keepcount queue operates on a chronological first‑in‑first‑out basis. If you create a Smart Copy causing the number
of current Smart Copies to exceed the value of ‑keepcount, the oldest Smart Copy backup document is deleted.
● You must specify the ‑scheduleID= parameter when specifying ‑keepcount=, otherwise the keep count limit is not
maintained and Smart Copies are created until there is insufficient space.
● Specify a unique schedule identifier, using an 8‑4‑4‑4‑12 hexadecimal format. For example:
‑scheduleID="00000000‑1111‑2222‑3333‑000000000000"
location= “[{* | drive_letterA;drive_letterB;... | mount_point;mount_point;...}]”
● Used with: smart, mount, and unmount subcommands
● Specify the ‑location= parameter with the location of one or more volumes or document paths as follows:
○ A wildcard (*) mounts the volumes in the Smart Copy at any available drive letters.
○ An ordered list of drive letters (such as G:\) with each drive letter delimited by a semicolon (;).
○ One or more mount point paths at which the volumes in the Smart Copy backup document should be mounted. Each path
is delimited by a semicolon (;).
● When specifying the ‑location parameter, you can enter either the wildcard, or a semicolon‑delimited list that can contain
both drive letters and path names of mount points. The ‑location parameter is optional for everything but template
volumes.
● To omit a Smart Copy, enter a semicolon at its position in the list. If any path variables contain embedded spaces, you must
enclose the variable in quotation marks ("").
● The list of volumes in an existing collection is sorted into ascending alphabetical order when the Smart Copy is created.
For example, if the Smart Copy set contains volumes originally mounted at E:\, F:\Mount Point A , and G:\ and the
‑location=T:\;S:\;H:\ then the Smart Copies of volumes E:\ will be mounted as T:\, F:\Mount Point A will be
mounted as S:\, and G:\ will be mounted as H:\.
locationroot= "[{drive_letter | mount_point}]"
110
Using the Command Line Interface