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
Figure 7. Two-Cluster HIT Group Managed From a Cluster
In the previous figure, assume further that you use the Add Hosts option from the ASM/ME instance on Node 1 to add Node 4
to it. If ASM/ME is not installed on nodes 4, 5, and 6, ASM first sets up the appropriate trust relationships between nodes 4, 5,
and 6. This process is indicated by the bidirectional arrows. After you add Node 4 to Node 1, you can then manage all of Cluster
B’s nodes from Node 1. However, you cannot manage any of Cluster A’s nodes from Cluster B until you add a node from Cluster
A to Cluster B.
Create a HIT Group — Overview
Use the Add Hosts wizard to create a HIT Group. With this wizard, ASM/ME automatically detects whether a clean installation
or update is required on the host that you are adding. ASM/ME automatically installs (or updates) on that host. The host is
added to the HIT Group.
If the installation or update fails, perform a manual installation on the host that you are adding. To add the other host to the HIT
Group, use the Add Hosts wizard.
Prerequisites for HIT Groups
For new installations to run successfully on remote hosts, allow incoming ping requests through the remote host’s firewall to the
remote host. Use Windows Server Manager to create new inbound rules for your firewall. Select ICMPv4 or ICMPv6 protocol
types for IPv4 and IPv6 pings, respectively. If both the local and remote hosts are in the same domain, allow the connections
over the domain profile type.
If you do not want to edit firewall rules, perform a manual installation on the host that you are adding. Use the Add Hosts
wizard on the local host to add the host to the HIT Group.
Enter username and password credentials to install Host Integration Tools on remote hosts added to the HIT Group. These
credentials are never stored and are only used for the installation. The following requirements must be met:
● If installing on a cluster, you must provide the appropriate credentials (domain user with local administrator rights) across all
of the cluster nodes.
● If adding or installing on multiple hosts:
○ Single Domain—For multiple machines that belong to a single domain, you must provide the appropriate user credentials
(domain users with local admin rights) so that ASM/ME can successfully access the machines to perform the required
installations.
○ Single Workgroup—For multiple machines that belong to a single workgroup, each machine must have the same local
admin account credentials.
○ Multiple Domains—For machines across multiple domains, add or install on all the machines from one domain at a time.
The Remote Procedure Call (RPC) service must be running. This service should start by default on Windows systems. If it is not
running, or if the firewall is blocking it, the installation will not work.
If you use the Browse Network option to add hosts to the HIT Group, verify that the network browser is working in
Windows.
NOTE:
If you cannot add hosts by browsing the network; add them manually by using the Manual Entry option in the Add
Hosts wizard.
42 HIT Groups