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 Select Databases dialog box opens.
2. Select one or more of the databases listed in the top panel. Click Next.
The Restore Database dialog box opens.
3. Select from the following options:
● Apply Logs—Enables you to perform custom restore operations without recovery such as manually applying the database
transaction logs to the restored database.
● Fully Recover—Completely restores the database to the contents represented by the Smart Copy set. You can fully
recover a database regardless of the Backup Type used when the Smart Copy set was created.
4. Click Restore.
If the SQL Server is clustered, the cluster physical disk resource for the volume containing the database to be restored is
placed in maintenance mode until the restore operation completes.
When the operation completes, ASM/ME displays the following message:
Restore completed successfully.
Restore All Databases
If a Smart Copy Set contains copies of several databases, you can restore all databases in a single operation.
1. Under the Smart Copies node, right-click the relevant Smart Copy and select Restore All.
ASM/ME displays its progress for steps such as setting volumes offline and later, back online. If the SQL Server is clustered,
the cluster physical disk resources for the volumes are placed in maintenance mode until the restore completes.
2. Wait until ASM/ME displays the following message:
Database restored. Refresh the database management GUI to see the restored database.
Restore a Database as New
Before you begin, make sure the ASM agent is configured to run as a user who has permissions to perform this operation in
SQL.
For detailed information about the various options for this procedure, see the information in the following table.
To perform Restore as New operations on alternate SQL Server hosts, see Importing a Smart Copy.
Table 28. Data Required for Restore As New
Item Description
Smart Copy Type
Restore as New Select option for a snapshot or clone Smart Copy set.
Clone and Restore as New Select option for a replica Smart Copy set.
Volume Mapping
Drive Letter Drive letter, NTFS folder mount point or ReFS folder mount point for the new
volume.
Restore as New Database
New Database Name If required, modify the new database name. ASM/ME appends the string _new to
the original database name to ensure that it is not confused with the original.
Database Server to use
Specify the name of an SQL Server instance that serves the new database, if
different from the instance serving the original database.
On a cluster, this name is the network name of the clustered SQL Server. The
current node must be the owner of the SQL Server Resource Group.
If you are restoring to a new SQL instance, then the SQL Server instance should be
the same SQL version as the original instance.
82 Using ASM/ME with SQL Server