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
The non-clustered host can manage each cluster. The following figure illustrates this HIT Group configuration.
Figure 6. Two-Cluster HIT Group Managed from a Remote Host
In this figure, assume you use the Add Hosts option from the ASM/ME instance on the non-clustered host to add all six cluster
nodes from the two clusters.
ASM/ME automatically sets up the trust relationships, indicated by the different arrows.
On the non-clustered host, nodes 1, 2, 3, 4, 5, and 6 are added at the same time to the non-clustered host. The non-clustered
host can manage all nodes on each cluster.
On Cluster A, every node in Cluster A can manage all other nodes in the cluster. Cluster A’s nodes cannot access or manage
Cluster B’s nodes.
● Nodes 2 and 3 are added to the ASM/ME instance on Node 1.
● Nodes 1 and 3 are added to the ASM/ME instance on Node 2.
● Nodes 1 and 2 are added to the ASM/ME instance on Node 3.
On Cluster B, every node in Cluster B can manage all other nodes in the cluster. Cluster B’s nodes cannot access or manage
Cluster A’s nodes.
● Nodes 5 and 6 are added to the ASM/ME instance on Node 4.
● Nodes 4 and 6 are added to the ASM/ME instance on Node 5.
● Nodes 4 and 5 are added to the ASM/ME instance on Node 6.
Multiple Cluster Management — Two-Cluster Example
Non-clustered hosts are not required to manage multiple clusters; you can manage one cluster from another cluster. For
example, assume that you have two three-node clusters (Cluster A and Cluster B, in the following figure), and that you want to
manage Cluster B from Cluster A. You can run ASM/ME from any node on cluster A, add a node from Cluster B to it, and then
manage Cluster B from that node. The following figure illustrates this scenario.
HIT Groups
41