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 resulting Smart Copy (containing A2 and B2) contains all of Component1, as indicated by Callout 1. It also contains the
partial data set indicated by Callout 2. This partial data set is referred to as a torn data set because it does not contain all the
files in the source data set.
CAUTION: If you use this torn Smart Copy to restore Component1, you also partially overwrite Component2,
potentially destroying live data on your production computer.
When you have a torn Smart Copy, restore data only from those data sets that you know to be complete in the Smart Copy.
This process can take longer, depending on the size of the files you restore from the Smart Copy. Because of the risk of data
loss, and the more complicated recovery procedure, Dell recommends that you avoid spanning different data sets across
common volumes.
Requirements for Creating Smart Copies
The following requirements must be met before you can create a Smart Copy:
● The computer must meet the requirements described in Windows Computer Requirements.
● The computer must be logged in to each iSCSI volume that comprises the Smart Copy object, as described in iSCSI Target
Connections.
● The iSCSI volumes must have drive letters assigned, as described in Volume Mount Point and Drive Letter Assignments on
page 18.
● If you are creating a snapshot Smart Copy, the PS Series volume must have snapshot space reserved.
● If you are creating a replica Smart Copy, you must configure replication between two PS Series groups and on the volumes.
The primary group must be available and ready to start replication on the volumes. Otherwise, the operation results in an
error. ASM/ME does not require access to the secondary group. For information about using Group Manager, see the Dell
EqualLogic Group Manager Administrator’s Guide.
● If you are creating a clone Smart Copy, the PS Series group must have a minimum of free space equal to the size of the
original volumes.
● If you want to create a Smart Copy of a volume, component, or collection that affects cluster resources, you must perform
the ASM/ME operation from the node that owns the cluster resources.
Constraints for Smart Copy Operations
The following constraints apply to specific Smart Copy procedures:
● If you create or schedule a replica Smart Copies, ASM/ME allows the operation to proceed, but displays a warning that you
cannot use the resulting Smart Copy for a restore operation (specifically, an in-place restore operation).
● In clustered environments:
○ Smart Copy are visible to all nodes even though the node might not be able to use the Smart Copy for recovery. That is,
ownership of resources is not required to see the Smart Copies.
○ Smart Copies appear as unreachable in the tree panel.
● For thin clones, ASM/ME supports the creation of snapshots, clones, and replicas. These objects are displayed under the
Smart Copies folder after they are created.
● For template volumes, ASM/ME supports the creation of thin clones and clones, which appear under the Smart Copies
folder after they are created.
● Replication of a thin clone volume through ASM/ME is possible when its template volume has been replicated through the
Group Manager GUI. Replication for template volumes is not supported in ASM/ME.
● For Smart Copies of SAN boot volumes:
○ To restore data from a Smart Copy of a boot volume, you must mount it and manually copy data from it, or perform a
selective restore from the Smart Copy.
○ You can add a boot volume to a collection with other volumes. However, if you create a Smart Copy of such a collection,
you cannot perform an in-place restore from that Smart Copy. You can only perform a selective restore operation.
○ The Unmount and Logoff operations are disabled.
CAUTION:
If a Smart Copy was created before you made changes to the layout of data in a volume, you
cannot use that Smart Copy to recover data. Attempting to recover the data might cause data loss on the
original volume. For example, assume four databases are stored on a volume, and then you create a Smart
Copy of that volume. Then, you add a fifth database to the volume, and perform a restore operation from the
Smart Copy. The restore operation will complete, but you lose the fifth database.
General ASM/ME Operations 53