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 28. Data Required for Restore As New (continued)
Item Description
Make database READ-ONLY after attach
● Choose whether to make the new database read-only.
● Use this option if you do not want users to accidentally make changes to the
new database.
For example, if you plan to make side-by-side restorations to the original
database.
TSQL Command for attaching the
database
This field shows the SQL Server commands that execute to create the new
database. Optionally, you can add custom actions to the command.
On a cluster, ASM/ME does not execute this command. You must perform several
manual steps before attaching to the database. You can then use this command to
attach to the database.
1. Expand the Smart Copies node. Right-click the relevant Smart Copy and select Restore As New. If the Smart Copy is a
replica, the option to select is Clone and Restore as New.
The Select Databases dialog box opens.
2. Make sure that any volume you want to use is not already mounted. If it is, unmount it before proceeding.
3. Select one or more of databases that you want to restore as new. Click Next.
The Select Volume Label dialog box opens.
4. Select a drive letter or mount point for the volume and click Next.
You can specify a mount point with either a relative path, which is combined with the value in the mount root field, or a full
path, which is used exactly as specified.
The mount point is validated as you enter the data. Invalid mount points are shown in red text, and a tooltip in the volume
row displays the problem with the specified mount point.
The Restore As New Database dialog box opens. All the fields are described in the preceding table.
5. Enter the required information. If you selected more than one database, the dialog box is repeated for every database you
selected. Click Restore.
ASM/ME displays the following message when the procedure is complete:
New database created successfully. Refresh database management GUI to see the restored
database.
6. Click Close.
If you are restoring to a clustered SQL instance, the following message is displayed:
Successfully mounted the Smart Copy on all cluster nodes.
ASM/ME lists three manual steps you must perform to complete the restore operation. ASM/ME mounts the volumes
containing the databases to be restored and performs the iSCSI logon for the current node and any possible owner nodes
that are configured to access the PS Series group.
Click OK and perform the following cluster and SQL management operations to complete the restore operation:
● Use the appropriate cluster utility to add the volumes or mount points for the restored databases as physical resources to
the SQL Server cluster group.
● Add the physical disk resources to the dependencies for the SQL Server resource.
● Attach the databases using the SQL Server Management Studio or the TSQL commands shown on the Restore as New
wizard page.
Using ASM/ME with SQL Server
83