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
● Used with: smart, mount subcommands
● Specify the -locationroot= parameter with a drive letter or mount point. The locationroot represents a tree of all
the mount points needed to mount every volume in the Smart Copy.
● If any path variables contain embedded spaces, you must enclose the variable in quotation marks ("").
newname=
● Used with: modifycollection subcommand
● Specifies a new collection name. This name must be valid and not be identical to another existing collection name. If a
collection is renamed, and Smart Copies and Schedules of the collection will be updated to refer to the renamed collection.
Schedule names will not be automatically modified, but can be changed by selecting the Modify Schedule option for the
affected schedule.
NoEmail
● Used with: smart, verify, delete, restore, selectiverestore, unmount, and mount subcommands
● Specifying this parameter will ensure that you do not receive an email notification when alerts are triggered. This parameter
is set by default for delete, restore, selectiverestore, unmount, and mount subcommands. To receive an email
notification for these subcommands, specify the email parameter.
nosignatureupdate
● Used with: breaksmartcopy subcommand
● Specifying this parameter will only reset the volume attributes (HIDDEN, READONLY, SHADOWCOPY, and
NO_DEFAULT_DRIVE_LETTER), and not the disk signature.
NOTE: If you do not specify this parameter, both the disk signature and the volume attributes will be reset.
objectID=
● Used with: smart, mount, unmount, restore, properties, delete, and selectiveRestore subcommands
● Specify the ‑objectID= parameter with an object identifier for an existing object. Use the ‑list command to display
object identifiers.
For example:
ASMCLI ‑list ‑volumes ‑collections ‑components ‑showObjectID
● Depending on the operation that you want to perform, specify one of the following parameter values:
○ Volume Operations — Specify a PS Series volume identifier (Ps Vol ID). A volume identifier has the following format:
Psv{hex‑string} For example:
Psv{18a09060‑3be0‑3fa8‑0a7a‑e4120000e045;32256}
You can obtain the Ps Vol ID from the ASM/ME GUI Volumes node by browsing an individual volume’s properties.
Alternatively, use the following command to display the Ps Vol ID for all supported volumes:
ASMCLI ‑list ‑volumes ‑showobjectid
○ Application Component Operations — Specify a component name. A component name has the following format:
Component{hex‑string }. For example:
Component{38951b83‑4249‑4a16‑8962‑563d8de79c92}
You can obtain the component name from the ASM/ME GUI Applications node by browsing an individual component’s
properties.
Alternatively, use the following command to display all component names:
ASMCLI ‑list ‑components ‑showobjectid
○ Collection Operations — Specify a collection name. A collection name has the following format:
Collection {ascii_string} For example:
Using the Command Line Interface
111