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
For any type of collection, creating a volume-based collection results in scheduled tasks still running successfully, even if the
collection definition is changed. Any collection that contains Cluster Shared Volumes (CSVs) is forced to behave as a
volume-based collection.
● When you do not select the option to create a volume-based collection, the scheduled task fails when any change occurs in
the collection definition. The components included in the collection, however, are based on the state of the collection at the
point in time the Smart Copy was created.
Create a Collection
1. Right-click the Collections node in the ASM/ME tree panel and select Create Collection.
ASM/ME displays the Collection name dialog box.
2. Specify a unique, alphanumeric name for the collection. If you want to create a volume-based collection, select the checkbox
and click Next.
ASM/ME displays the Components dialog box. See Volume-Based Collections for more information.
3. Select the volumes or application components to include in the collection. ASM/ME automatically includes required
components.
4. Click Next.
The Summary dialog box opens. This dialog box lists the default settings that are used when ASM/ME creates Smart
Copies of the collection components.
5. Click Create to create the collection.
The new collection is displayed in the ASM/ME tree panel under Collections.
When you have created a collection, you can create Smart Copies of the collection volumes as described in Create Smart
Copies. Smart Copy sets for collections are located under the collection name under Smart Copies in the ASM/ME tree
panel.
6. Select the collection name to display its details.
More Collection Operations
You can create a Smart Copy schedule for a collection, and generate an ASMCLI command for creating a Smart Copy of the
collection. You can also modify or delete a collection, as follows:
1. Expand Collections in the ASM/ME tree panel and right-click the collection name.
2. Select an operation from the menu. The options include:
● Configure New Schedule
● Create Smart Copy
● Delete Collection
● Generate Create Smart Copy Command
● Modify Collection
When your rename a collection, any Smart Copies and schedules of the collection are updated to refer to the renamed
collection. Schedule names are not automatically modified, however, you can select the Modify Schedule option to change
the schedule name. When you modify a collection, ASM/ME indicates that the originating computer is Unknown. This status
occurs because the originating computer properties change to the name of the host that modified it.
NOTE:
Ideally, modify a collection only from the originating host. (A collection’s originating host can be unknown if the
collection was created on an earlier version of ASM/ME, which did not include the originating host information.)
To change the originating host, you do not need to make any actual changes to the collection. For example, you can deselect
and then immediately reselect a volume in the collection, then click Update. This process is enough to change the collection
properties.
About Schedules
You can create schedules to perform Smart Copy operations at regular intervals. ASM/ME notifies you when scheduled
operations complete or fail.
48
General ASM/ME Operations