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
Table 7. General Settings (continued)
Option Description
specify another user, you must provide the domain, user-name, and password
credentials.
See also Managing the ASM Services.
About the Backup Document Directory
Every Smart Copy and collection has a corresponding backup document, which can be used to import Smart Copies on different
hosts. You can specify the location for the parent folder, whether that parent folder is a UNC path in the cluster environment or
a regular file path in the normal environment, that stores these documents. If you intend to import Smart Copies on different
hosts, consider specifying a shared file system accessible to all the computers that can import the transported Smart Copy Sets.
A backup document must exist on a computer for ASM/ME to access the Smart Copy. If a Smart Copy consists of multiple
components, the associated backup document describes each component in the Smart Copy. For example, assume you create a
collection of volumes. If you take a snapshot of that collection, the resulting Smart Copy consists of snapshots of different
volumes. The Smart Copy’s associated backup document then describes each snapshot in the Smart Copy.
Backup documents that were not created by or imported to a host displays a warning message on the Smart Copy list node, and
the Smart Copies represented by that backup document is not displayed.
If you change the location of the backup document directory, backup documents that were created on or imported to the host
are moved (copied to the new location and removed from the source location). Collections that were created or modified by the
current host are also moved. Untagged collections (those for which the original host cannot be determined) are copied to the
new location, but also left in the original location.
Backup Document Directories for Standalone (Non-Clustered) Hosts
A host that is not part of a cluster or a SharePoint farm should have its own backup document directory for storing backup
documents. The hosts should use different directories for storing their backup documents. If you use a shared Windows
directory for a standalone host, you must use a subdirectory within the shared directory. If host A and host B (both standalone
hosts) store their backup documents on a shared directory, they should each store them in their own subdirectories.
For example, Host A would store them on \\server\share\subdirectory1, and Host B would store them on \\server
\share\subdirectory2.
Backup Document Directories for Clusters and SharePoint Farms
With the exception of Exchange Data Availability Group (DAG) clusters, cluster nodes and hosts in a SharePoint farm must
always share the same backup document directory path. For example, if Node 1 stores backup documents on \\server
\share\subdirectory1, then Node 2 must also store backup documents on \\server\share\subdirectory1.
In a cluster, you can specify a directory as a non-clustered or clustered resource. You must first use Windows cluster utilities to
create the folder and make it available to the cluster nodes.
If you specify a shared folder located on a clustered iSCSI volume, you can create Smart Copies of that volume, but cannot
restore data from the volume (otherwise the folder might be overwritten).
Set the Backup Document Directory
1. In the navigation area, click Settings.
2. Click the General Settings tab.
If you are managing multiple hosts and want to make the same changes to multiple hosts, multiselect the hosts in the middle
panel. The changes will affect all selected hosts.
3. Specify a directory for backup documents.
a. For a single-system configuration, you can change the location of Auto-Snapshot Manager Document Directory. Do not
change the location of Smart Copy documents if you have configured remote verification.
See Run Checksum Verification and Soft Recovery on a Remote Host.
Configure ASM/ME
21