Users Guide
Table Of Contents
- About This Guide
- Dell EqualLogic Auto-Snapshot Manager/Microsoft Edition Version 5.4 User's Guide
- Introduction to ASM/ME
- Functions Provided By ASM/ME
- Supported Applications
- HIT Groups and Multiple Machine Management
- ASM/ME Smart Copies
- Smart Copy Types
- Smart Copy Operations for Template and Thin Clone Volumes
- Robust Data Recovery
- Thin-Provisioning a Volume
- SAN Data Copy Offload
- Scripts and Command Generation
- Alerts and Event Notification
- Remote Installations
- Failover Cluster Support
- ASM/ME and the Virtual Snapshot Service
- Functions Provided By ASM/ME
- Configure ASM/ME
- PS Series Group Requirements
- Windows Computer Requirements
- Required Access Controls
- VSS/VDS Service Access to the Group
- Access to Volumes and Snapshots
- iSCSI Target Connections
- Volume Mount Point and Drive Letter Assignments
- Mount Point Constraints in Cluster Environments
- ASM/ME Settings
- ASM/ME Graphical User Interface
- Start the ASM/ME GUI
- Tree Panel
- Tree Panel Behavior in Failover Cluster Environments
- Tree Panel Nodes
- Tree Panel Icons
- Group SharePoint Farm Nodes, Clusters, or Host Nodes
- About Aliases
- Customize Color Themes
- HIT Groups
- General ASM/ME Operations
- About Volumes
- Operations on Failover Clusters
- About Collections
- About Schedules
- About Smart Copies
- Restoring Data
- View Multipath Information
- View I/O Details
- Using ASM/ME with Exchange
- View Exchange Applications in ASM/ME
- Exchange Operations
- Overview of Exchange Smart Copies
- Exchange eseutil.exe Utility
- Recovery Considerations for Exchange
- Checksum Verification and Soft Recovery
- Run Checksum Verification and Soft Recovery Immediately
- Run Checksum Verification and Soft Recovery After Smart Copy Creation
- Schedule a Global Verification Task for Checksum Verification and Soft Recovery
- Run Checksum Verification and Soft Recovery on a Remote Host
- View Checksum Verification and Soft Recovery Status
- Checksum Verification and Soft Recovery Logging and Notification
- Create Exchange Smart Copies
- Schedule Smart Copies for Exchange Components
- Recover Exchange Data
- Using ASM/ME with SQL Server
- Using ASM/ME with Hyper-V
- Using ASM/ME with SharePoint
- SharePoint Installation Considerations
- Plan to Install on a SharePoint Farm
- Example of ASM/ME Installed on a SharePoint Farm
- Example of a SharePoint Farm with a SQL Cluster
- Install ASM/ME on a SharePoint Farm
- About Changes to an Existing SharePoint Farm
- Remove a HIT Group Host From a SharePoint Farm
- Add a Writer Host to a SharePoint Farm
- Change a Writer Host in a SharePoint Farm
- Change the Writer Host and Disable the VSS Writer in a SharePoint Farm
- Respond to Changes in a SharePoint Farm
- View SharePoint Farm Components in ASM/ME
- SharePoint Smart Copies
- Restore Options for SharePoint Smart Copies
- Availability of SharePoint Data Restoration Operations
- Mount a SharePoint Smart Copy
- Restore Selected Databases from a SharePoint Smart Copy
- Restore a Database In-Place From a SharePoint Smart Copy
- Restore a Database From a SharePoint Smart Copy as a New Database
- Restore an SSA From a SharePoint Smart Copy
- Using the Command Line Interface
- Introduction to ASMCLI
- How to Use ASMCLI Commands
- General Command Syntax
- ASMCLI Command Summary
- Command Parameters
- ASMCLI Commands and Their Syntax
- ASMCLI -alert
- ASMCLI -breaksmartcopy
- ASMCLI -cloneReplica
- ASMCLI -configureASM
- ASMCLI -configureCHAP
- ASMCLI -createCollection
- ASMCLI -delete
- ASMCLI -deleteCollection
- ASMCLI -enumerateiSCSIPortals
- ASMCLI -enumerateSmartCopies
- ASMCLI -help
- ASMCLI -list
- ASMCLI -modifyCollection
- ASMCLI -mount
- ASMCLI -Properties
- ASMCLI -restore
- ASMCLI -selectiveRestore
- ASMCLI -shutdownsystray
- ASMCLI -shutdownverifier
- ASMCLI -smart
- ASMCLI -unmount
- ASMCLI -verify
- ASMCLI -version
- Use a Script to Create Smart Copies
- Recover a Clustered Volume From a Clone
- Index
Specify the ‑useEarliest parameter to use the chronologically earliest Smart Copy. The ‑useLatest parameter is the
default. You can use the ‑useEarliest parameter only if you specified the ‑volume= parameter, the ‑component=
parameter, or the ‑collection= parameter.
useLatest
Used with: verify, mount, properties, unmount, delete, restore subcommands
Specify the ‑useLatest parameter to use the chronologically latest Smart Copy. The ‑useLatest parameter is the default.
You can use the ‑useLatest parameter only if you specified the ‑volume= parameter, the ‑component= parameter, or the
‑collection= parameter.
volume=
● Used with: smart, verify, mount, properties, unmount, restore, selectiveRestore, createcollection,
and modifycollection subcommands
● Specify the ‑volume= parameter with the path for a mount point or a drive letter of a volume as an alternative to specifying
an ‑objectID=. Typical drive letter values are G:\ and Z:\. You can obtain the drive letter from the ASM/ME GUI
Volumes node by browsing an individual volume’s properties. Alternatively, use the following command to display all
supported drive letters:
ASMCLI ‑list ‑volumes ‑showobjectid
● The ‑volume= parameter and the ‑objectID= parameter are mutually exclusive and the command parser processes the
first valid parameter, ignoring any subsequent parameters.
● The ‑volume= parameter is an alternative to using the ‑document= parameter. If you redundantly specify either a path, or
a collection name, the command parser ignores the redundant parameter.
● For the mount command, the ‑useEarliest or ‑useLatest parameter determines which specific backup document is
mounted. The ‑useLatest parameter is the default, and is assumed if you do not specify either ‑useLatest or
‑useEarliest.
● When used with the createcollection or modifycollection subcommands, the ‑volume parameter identifies a
semicolon‑delimited list of volumes specified as drive letters or mount points. If this parameter is used, the ‑component=
parameter cannot be used.
volumeBased=
● Used with: createcollection and modifycollection subcommands. The options are yes or no.
● Setting this parameter to yes specifies that the operation will not fail even if a database, VM, or Exchange store associated
with a volume in the collection cannot be found. For example, assume a collection that contains a volume named vol1,
associated with an SQL database called DB1. If you delete DB1 and then create a Smart Copy of the collection, the operation
will succeed even though DB1 is no longer associated with vol1.
volumes
● Used with: list subcommand
● Specify the ‑volumes parameter to display all supported volumes. If you do not specify the ‑volumes parameter, the
‑collections parameter, or the ‑components= parameter, the command parser assumes a value of ‑volumes as the
default.
vssvds
● Used with: configureCHAP subcommand
● Indicates that the credentials apply to management access.
writer
Used with: smart, mount, unmount, restore, properties, delete, selectiveRestore, enumerateSmartCopies,
and breakSmartCopy subcommands.
● Applies to SharePoint farms only.
● Specify -writer to restrict the operation to a particular SharePoint VSS writer on a host (writer host).
writers
Using the Command Line Interface
115