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
● Create Global Verification Task — This option displays only if the Global Verification task does not exist. If it does exist, a
node called Global_Verification_Task displays in the ASM/ME tree panel under the Schedules node.
● Modify Global Verification Task — This option displays only if the Global Verification task exists. If it does not exist, the
Global_Verification_Task node does not appear in the tree panel under the Schedules node.
If you want to support failover of the Global Verification task processing in a cluster configuration, you must create a Global
Verification task on each node that is a potential owner node for an Exchange Server Cluster Group.
Additionally, you need to manually propagate any changes to the Global Verification task to the possible owner nodes if you want
them to be synchronized. This requirement is different from other scheduled tasks.
ASM/ME creates a Global Verification task automatically the first time you either create an Exchange Smart Copy or create a
schedule of Smart Copies, providing the following conditions apply:
● No preceding version of a Global Verification task exists under the Schedules node.
● When creating the Smart Copy, select the local Global Verification window as the scheduled verification time.
Constraints for Global Verification Task
The Global Verification task attempts to verify all Smart Copies, subject to the following constraints:
● Smart Copies are verified serially. You can specify whether to begin processing with the newest copies, or the oldest copies
(chronological sequence).
● If running a verification operation takes longer than the time allotted in the schedule (that is, it exceeds the specified end
time), the operation is not terminated. The operation runs to completion but no new operations are started.
● If a common file share is used by several hosts running Global Verification tasks during the same or overlapping window
(either in a non-cluster configuration, or DAG), configure a different backup document location folder for each of the hosts
to avoid any issues in accessing backup documents.
● Any operations that cannot run in the time available are postponed to the next start time. These operations run first.
● If the host is rebooted before the Global Verification completes, the verification starts again when the host is back up.
Creating a schedule does not guarantee that all backup documents are always verified. You must make sure that operations are
completed successfully and that adequate time is available. If the host running the Global Verification task fails, the Global
Verification task on the inheriting host might not process all of the existing unverified Smart Copies until the next time that it is
scheduled to run.
NOTE: You can force the Global Verification task to restart on the inheriting host using ASM/ME.
Manually Create a Global Verification Schedule
1. In the tree panel, right-click the Schedules node and select Create Global Verification Task.
2. Select from the options described in the following table, then click Next.
The Provide User Account Information dialog box opens.
3. Select whether to run the task as a system user or as a specified user. These options are described in the following table.
4. Click Create to begin creating the Global Verification task. In the tree panel, the Global Verification task node should appear
under the Schedules node.
Table 20. Global Verification Task Schedule Options
Option Description
Process Smart Copies created by this
host
Processes only Smart Copies created on the local computer.
Process Smart Copies created by
another host
Processes Smart Copies created on a remote computer. (See Run Checksum
Verification and Soft Recovery on a Remote Host.)
Start Time The start time of the local Global Verification window. Typically, you specify a
time of low computer usage to make best use of computer resources. The start
time must precede the end time by 3 hours or more. If the start time and end
time are the same, the window is 24 consecutive hours (full time verification).
End Time The end time of the local Global Verification window. This time must be at least 3
hours later than the start time.
Using ASM/ME with Exchange 67