SnapManager
SnapManager empowers storage administrators with the tools necessary to do these tasks:
•Perform policy-driven data management
•Schedule and create regular database and application backups with minimal impact
•Restore data from these backups in the event of data loss or disaster
•Create clones for non-disruptive testing
With SnapManager, you can create backups on primary storage and create protected backups on secondary storage.
In this chapter, we describe several of the environments supported by SnapManager. As an installation example, we pay special attention to the installation on Microsoft Hyper-V.
The following topics are covered:
The following topics are covered:
31.1 Introduction to SnapManager
SnapManager uses N series technologies while integrating with the latest database and application releases. SnapManager is integrated with the following N series applications and technologies:
•Protection Manager uses resource pools, datasets, and protection policies to provide policy-based automation for SnapVault and SnapMirror capabilities.
•Operations Manager provides role-based access control of storage features for enhanced security.
•SnapDrive automates storage provisioning tasks and simplifies the process of creating error-free, host-consistent Snapshot copies of the storage.
•Snapshot (a feature of Data ONTAP) creates point-in-time copies of the database.
•SnapVault (a licensed feature of Data ONTAP) uses disk-based backups for reliable, low-overhead backup and recovery of databases.
•SnapMirror (a licensed feature of Data ONTAP) replicates database data across a global network at high speeds in a simple, reliable, and cost-effective manner.
•SnapRestore (a licensed feature of Data ONTAP) recovers an entire database in seconds, regardless of capacity or number of files.
•FlexClone (a licensed feature of Data ONTAP) helps to create fast, space-efficient clones
•of databases from the Snapshot backups.
31.2 Supported databases and applications
SnapManager is compatible with the following database and applications:
•Microsoft Hyper-V
•Microsoft Exchange Server
•Microsoft Exchange Server 2000
•Microsoft Office SharePoint Server
•Microsoft SQL Server
•Oracle
•SAP
31.3 SnapManager for Hyper-V
SnapManager for Hyper-V provides a solution for data protection and recovery for Microsoft Hyper-V virtual machines (VMs) running on Data ONTAP on cluster shared volumes and Windows shared and dedicated volumes.
You can perform application-consistent and crash-consistent dataset backups according to protection policies set by your backup administrator. You can also restore VMs from these backups. Reporting features enable you to monitor the status of and get detailed information about your backup and restore jobs.
31.3.1 What you can do with SnapManager for Hyper-V
SnapManager for Hyper-V enables you to back up and restore multiple virtual machines across multiple hosts. You can create datasets and apply policies to them to automate backup tasks such as scheduling, retention, and replication.
You can perform the following tasks with SnapManager for Hyper-V:
•Group virtual machines into datasets that have the same protection requirements and apply policies to those datasets
•Back up and restore dedicated and clustered virtual machines on storage systems running Data ONTAP software
•Back up and restore virtual machines running on cluster shared volumes and using Windows Failover clustering
•Automate dataset backups using scheduling policies
•Perform on-demand backups of datasets
•Retain dataset backups for as long as you need them, using retention policies
•Update the SnapMirror destination location after a backup successfully finishes
•Specify custom scripts to run before or after a backup
•Restore virtual machines from backups
•Monitor the status of all scheduled and running jobs
•Manage hosts remotely from a management console
•Provide consolidated reports for dataset backup, restore, and configuration operations
•Perform a combination of crash-consistent and application-consistent backups
•Perform disaster recovery operations using PowerShell cmdlet
31.3.2 Installing and uninstalling SnapManager for Hyper-V
Before you install the SnapManager for Hyper-V software, be aware of the following requirements:
•Data ONTAP requirements
•Hyper-V parent host requirements
•Hotfix requirements
•License requirements
Hyper-V parent host requirements
Hyper-V parent hosts are physical servers on which the Hyper-V role is enabled. Hosts that contain virtual machines are added to SnapManager for Hyper-V for protection and recovery. To install and run all of the SnapManager for Hyper-V software components, the Hyper-V parent hosts must meet certain technical requirements. All Hyper-V parent hosts must meet minimum operating system and Hyper-V requirements.
SnapManager for Hyper-V runs on any of the following operating system versions:
•Windows Server 2008 R2 x64 or later
•Windows Server 2008 R2 SP1 x64
Management consoles must be running one of the following operating systems:
•Windows Server 2003, SP2
•Windows XP Professional, SP3
•Windows Server 2008
•Windows Vista Business and Ultimate, SP1
•Windows Server 2008 R2
•Windows Server 2008 R2, SP1
•Windows 7
Installing or upgrading SnapManager for Hyper-V
You can install or upgrade SnapManager for Hyper-V so that you are able to back up and restore your data:
1. Download SnapManager for Hyper-V from the N series support site.
2. Launch the SnapManager for Hyper-V executable file.
3. Complete the steps in the SnapManager for Hyper-V InstallShield wizard.
Installation order
You need to install SnapDrive for Windows on all hosts before installing SnapManager for Hyper-V. If the hosts are members of a cluster, all nodes in the cluster require the installation of SnapDrive for Windows.
When SnapManager for Hyper-V starts it communicates with SnapDrive for Windows to get the list of all virtual machines running on a host. If SnapDrive for Windows is not installed on the host, this API fails and the SnapManager for Hyper-V internal cache does not update with the virtual machine information.
31.3.3 Configuring SnapManager for Hyper-V
You can configure and manage your hosts and virtual machine resources with policies to protect and restore your data.
Dashboard
The dashboard displays an overview of resources that are currently being protected, as well as those that are not protected. You can select different segments of either the VM Protection Status pie chart or the Job History bar graph to view general information about the status of your jobs, resources, and history.
The dashboard (Figure 31-1) displays an overview of resources.
Figure 31-1 SnapManager for Hyper-V Windows console
When you select a segment in the VM Protection Status pie chart, you can view information about the protection status of the virtual machines in the Details pane.
Adding a Hyper-V parent host or host cluster
You can add a Hyper-V parent host or host cluster to back up and restore your virtual machines.
1. From the navigation pane, click Protection.
2. From the Actions pane, click Add host.
3. Either type the name of the host or click Browse to select, and click Add.
|
Tip: When you add a host to a cluster, the information about the new host is not automatically displayed in the GUI. Manually add the host information to the xml file in the installation directory.
|
Exporting the VM from a non-Data ONTAP host
You must first export a virtual machine (VM) from a non-Data ONTAP host before you can import it to a Data ONTAP host.
The VM that you want to migrate must be powered off.
1. Open the application Server Manager.
2. In the left pane, click Role → Hyper-V → Hyper-V Manager.
3. Select the name of the non-Data ONTAP host on which the VM that you want to migrate currently resides.
4. From the Virtual Machines pane, right-click the name of the VM that you want to migrate.
5. Click Export.
6. Click Browse.
7. A window displaying available hard disk drives opens.
8. Click the Data ONTAP host destination for the VM.
9. Click Select Folder.
10. The VM is exported to the Data ONTAP destination that you chose in Step 7.
31.3.4 Managing backup jobs
You can manage scheduled backups using the Jobs Management window and you can also create and monitor on-demand backups in SnapManager for Hyper-V.
You can create scheduled backup jobs using policies attached to datasets. You can create, modify, view, and delete the policies that make up scheduled backup jobs.
You can create on-demand backup jobs when you want them. An on-demand backup job can include retention and replication policies as well as scripts to run before and after the backup has taken place.
Types of backup jobs that SnapManager for Hyper-V can perform
SnapManager for Hyper-V enables you to use two types of backup jobs: application consistent and crash consistent. A combination of the two provides an ideal backup strategy.
Application-consistent backup
These backups are thorough, reliable, and resource intensive. Application-consistent backups are made in coordination with Microsoft Volume Shadow Copy Service (VSS) to ensure that each application running on the VM is quiesced before making a Snapshot copy. This backup method guarantees application data consistency. It can be used to restore VMs and the applications running on them. However, application-consistent backups are time consuming and can be complex.
Crash-consistent backup
These backups are quick Snapshot copies of all the LUNs used by VMs involved in a dataset. The resulting backup copy is similar to the data capture of a VM that crashes or is otherwise abruptly powered off. Crash-consistent backups are a quick way to capture data, but the VMs must be present in order to be restored from a crash consistent backup.Crash-consistent backups are not intended to replace application-consistent backups.
Crash-consistent backups take only one Snapshot copy, always. They do not provide VSS integration.
Multiple crash-consistent backups can execute in parallel. A crash-consistent backup can run in parallel with an application-consistent backup.
Manually backing up a dataset
You can create an on-demand backup of a dataset. You must have the following information available:
•Backup name and description
•Policy name, if necessary
•Policy override information
(if you plan to change any of the previously specified policy options)
(if you plan to change any of the previously specified policy options)
•Backup type
•Backup options information
Follow these steps:
1. From the navigation pane, click Protection → Datasets.
2. Select the dataset for which you want to create a manual backup and click Backup.The Backup wizard appears.
3. Complete the steps in the wizard to create your on-demand backup. Closing the wizard does not cancel the on-demand backup.
Monitoring backup jobs
You can view the scheduled backup jobs for a particular dataset by using the Jobs Management window Scheduled tab. You can also view the backup and restore jobs that are currently running by using the Jobs Management window Running tab.
1. From the navigation pane, click Jobs.
2. Click either the Scheduled tab or the Running tab.
3. Select the scheduled or running backup job, or the restore job, that you want to monitor. Information about the job appears in the Details pane.
4. Use the Running Job report in Reports view, if you want to view a live report of a running job.
|
Tip: You can also monitor backup jobs with Microsoft's SCOM console. See the Microsoft web site for more information.
|
31.3.5 Restoring a virtual machine
You can restore a virtual machine (VM) from a backup by using SnapManager for Hyper-V. You can also restore a VM that is part of a cluster. SnapManager for Hyper-V determines the appropriate node in the cluster to restore the VM.
To restore a VM, SnapManager for Hyper-V uses the file-level restore feature in SnapDrive for Windows. You can spread the associated files of a VM, including the configuration file, Snapshot copies, and any VHDs, across multiple Data ONTAP LUNs. A LUN can contain files belonging to multiple VMs.
If a LUN contains only files associated with the VM that you want to restore, SnapManager for Hyper-V restores the LUN by using LCSR (LUN clone split restore). If a LUN contains additional files not associated with the virtual machine that you want to restore, SnapManager for Hyper-V restores the virtual machine by using the file copy restore operation. You can follow these steps:
1. From the navigation pane, click Recovery.
2. Select the virtual machine that you want to restore.
3. In the Backups pane, select the backup name that you want to restore and click Restore. The Restore wizard appears.
If you start a restore operation of a Hyper-V virtual machine, and another backup or restoration of the same virtual machine is in process, it fails.
4. Complete the steps in the wizard to restore the virtual machine backup. Closing the wizard does not cancel the restore operation. SnapManager for Hyper-V validates the virtual machine configuration before beginning the restore operation. If there have been any changes in the virtual machine configuration, a warning appears and you can choose to continue or cancel the operation.
31.4 SnapManager for Microsoft Exchange
SnapManager provides you with an integrated data management solution for Microsoft Exchange that enhances the availability, scalability, and reliability of Exchange databases. SnapManager provides rapid online backup and restoration of databases, along with local or remote backup set mirroring for disaster recovery.
31.4.1 What SnapManager for Microsoft Exchange does
SnapManager uses online Snapshot technology that is part of Data ONTAP and integrates Exchange backup and restore APIs and Volume Shadow Copy Service (VSS). SnapManager uses SnapMirror to support disaster recovery.
SnapManager provides the following data management capabilities:
•Migrating Exchange databases and transaction logs to LUNs on storage systems
•Backing up Exchange databases and transaction logs from LUNs on storage systems
•Verifying the backed-up Exchange databases and transaction logs
•Managing backup sets
•Archiving backup sets
•Restoring Exchange databases and transaction logs from previously created backup sets
You can use SnapManager with configurations having multiple servers. You can perform local administration, remote administration, and remote verification.
SnapManager provides the following capabilities:
•Local administration:
You install SnapManager on the same Windows host system as your Exchange server.
•Remote administration:
If you install SnapManager on a remote computer, you can run SnapManager remotely to perform any task that you can perform on a locally installed SnapManager system.
•Remote verification:
You can also perform remote database verification from a remote administration server that is configured with SnapDrive and Exchange server. Remote verification offloads the CPU-intensive database verification operations that can affect the performance of your production Exchange server.
31.4.2 Installation on a stand-alone Windows host system
You can install SnapManager on a stand-alone Windows host system that is used for a production Exchange server, a remote administration server, or a remote verification server.
You can run the software installation utility for SnapManager in either the interactive mode or the unattended mode. SnapManager guides you through the interactive mode; the unattended mode requires that you type certain commands and then installation takes place on its own.
31.4.3 Installing SnapManager in interactive mode
You can install SnapManager using the software installation utility in the interactive mode. The InstallShield wizard guides you through the installation.
The SnapManager Server Identity account must meet the following requirements:
•The account must have administrator privileges on the Exchange server.
•The account must also have system administrator server privileges.
The CD-ROM installation is the same as the network installation. The only difference is the name of the installation executable and the distribution media.
Do not use Terminal Services for any type of SnapManager administration, because you might miss critical information that is displayed only in pop-up boxes at the system console.
You do not need to stop Exchange services while you install SnapManager. Exchange can continue to run while you install SnapManager and afterward.
The SnapManager software installation program does not allow you to continue with the installation process if Microsoft .NET 3.5 is not installed. If .NET is not installed on a 32-bit system, the installation setup automatically installs it; on a 64-bit system, SnapManager prompts you to install it.
Follow these steps:
1. Network:
Download the SnapManager package from the network, save it on the Windows host system, and then launch the SnapManager installation package by double-clicking it in your Windows Explorer.
CD-ROM:
Browse to the SnapManager installation package and double-click setup.exe.
2. In the License Agreement window, accept the license agreement.
3. In the Customer Information window, specify the user name, the organization name, and the SnapManager license type.
4. Note the full path of the folder in which you want to install SnapManager.
You can change this default directory by clicking Change.
You can change this default directory by clicking Change.
5. In the SnapManager Server Identity window, specify the user account you want to use to run SnapManager.
6. Type and confirm the password.
7. Click Install.
8. Wait until the InstallShield Wizard Completed window appears; then click Finish to exit the software installation utility.
31.5 SnapManager for Oracle on UNIX
SnapManager for Oracle simplifies and automates database backup, recovery, and cloning by using the Snapshot, SnapRestore, and FlexClone technologies.
31.5.1 What SnapManager for Oracle on UNIX does
SnapManager for Oracle on UNIX provides the following capabilities:
•Create space-efficient backups to primary or secondary storage and schedule backups to occur on a regular basis.
•Restore full or partial databases using file-based or volume-based restore operations and preview restore operations before they occur from primary or secondary storage.
•Automatic restore and recovery of database backups.
•Prune archive log files from the archive log destinations while creating the archivelog-only backups.
•Automatically retain minimum number of archive log backups by retaining only the backups with unique archive log files.
•Track operation details and produce reports by host, profile, backup, or clone.
•Verify backup status.
•Maintain history of the SnapManager operations associated with a profile.
•Create space-efficient clones of backups on primary or secondary storage.
31.5.2 Installing or upgrading SnapManager on a UNIX host
You can install or upgrade SnapManager software on any approved UNIX host. Install only one SnapManager server instance per host.
For HP-UX PA-RISC platform, ensure that you installed the 32-bit Oracle client software.
The software is installed in the following paths:
•Solaris/opt/NTAPsmo
•For all other platforms: /opt/Nseries/smo
Follow these steps:
1. Log in as root.
2. On the UNIX database host, change to the directory where you saved the software.
3. If the file is not an executable file, use the following command to change permissions on the downloaded file so it is executable:
chmod 544 Nseries.smo*
4. For upgrades, stop the server:
smo_server stop
5. Use the appropriate command to start the installation of the software on the host:
Solaris (SPARC-x86_64)
# ./Nseries.smo.sunos-sparc64-3.2.bin
Solaris (*x86_64)
# ./Nseries.smo.sunos-x64-3.2.bin
AIX
# ./Nseries.smo.aix-ppc-3.2.bin
AIX (ppc64)
# ./Nseries.smo.aix-ppc64-3.2.bin
HP-UX (Itanium)
# ./Nseries.smo.hpux-ia64-3.2.bin
HP-UX (PA-RISC)
# ./Nseries.smo.hpux-hppa-3.2.bin
Linux
# ./Nseries.smo.linux-x86-3.2.bin
# ./Nseries.smo.linux-x64-3.2.bin
# ./Nseries.smo.sunos-sparc64-3.2.bin
Solaris (*x86_64)
# ./Nseries.smo.sunos-x64-3.2.bin
AIX
# ./Nseries.smo.aix-ppc-3.2.bin
AIX (ppc64)
# ./Nseries.smo.aix-ppc64-3.2.bin
HP-UX (Itanium)
# ./Nseries.smo.hpux-ia64-3.2.bin
HP-UX (PA-RISC)
# ./Nseries.smo.hpux-hppa-3.2.bin
Linux
# ./Nseries.smo.linux-x86-3.2.bin
# ./Nseries.smo.linux-x64-3.2.bin
6. After the Introduction text, complete the following steps:
a. Press Enter to continue.
b. If it is an upgrade, press Enter when you receive the following message:
Existing SnapManager For Oracle Detected.
Existing SnapManager For Oracle Detected.
7. For SnapManager for Oracle, at the prompt for the operating system user, press Enter to accept the default value. For a new installation, the default value for the user is oracle.
8. At the prompt for operating system group, press Enter to accept the default value. For a new installation, the default value is dba.
9. At the prompt for the Server Startup Type, press Enter to accept the default value.
10. At the Configuration Summary page, press Enter to continue.
11. or HP-UX PA-RISC platform that run Oracle 11gR2, you need to set the Oracle client home path in the SnapManager configuration file (smo.config). The Oracle client home path is the location in which you have installed the 32-bit Oracle client software. Enter the path of the 32-bit Oracle client software in the Oracle client home variable of the configuration file (smo.config): oracle.client.home=<>.
12. Start the SnapManager server by entering this command:
smo_server start
SnapManager displays a message stating that the SnapManager server is running.
13. Verify that the SnapManager system is running correctly by entering this command:
smo system verify
SnapManager displays a message stating that the operation succeeded.
14. For upgrades, upgrade each SnapManager repository by entering this command:
smo repository update -repository -dbname repo_service_name -host repo_host -login -username repo_username -port repo_port
SnapManager displays a message stating that the operation succeeded.
31.6 SnapManager for SAP on Windows
SnapManager for SAP simplifies and automates database backup, recovery, and cloning by using the Snapshot, SnapRestore, and FlexClone technologies.
31.6.1 What SnapManager for SAP on Windows does
SnapManager for SAP has several advantages for managing data and databases over other products:
•Create space-efficient backups to primary or secondary storage and schedule backups to occur on a regular basis.
•Restore full or partial databases using file-based or volume-based restore operations and preview restore operations before they occur from primary or secondary storage.
•Perform automatic restore and recovery of database backups.
•Prune archive log files from the archive log destinations while creating the archivelog-only backups.
•Automatically retain minimum number of archive log backups by retaining only the backups with unique archive log files.
•Track operation details and produce reports by host, profile, backup, or clone.
•Verify backup status.
•Maintain history of the SnapManager operations associated with a profile.
•Create space-efficient clones of backups on primary or secondary storage. For example, you can use the clone for testing updates in non-production environments.
31.6.2 Installing SnapManager for SAP on Windows
You can install or upgrade SnapManager software on any approved Windows host. Install only one SnapManager server instance per host.
Follow these steps:
1. For upgrades, stop the server by completing the following actions:
a. In the Windows Services window, select N series SnapManager 3.1 for SAP.
b. In the left panel, click Stop.
2. Double-click the downloaded executable file.
For Windows x86, use Nseries.smsap.windows-x86-3.1.exe. For Windows x64, use Nseries.smsap.windows-x64-3.1.exe.
3. A dialog box might appear with this message:
The publisher could not be verified. Are you sure you want to run this software?
Click OK.
Click OK.
4. In the Introduction window, click Next.
5. If it is an upgrade, a pop-up window appears. To continue, click OK.
6. For new installations (not upgrades) at the next Choose Install Folder window, either click Next to accept the default location for the installation folder, or choose a new location.
7. On the Menu Availability window, click Next.
8. On the Specify Service Properties window, enter the account and password for the Windows service for SnapManager.
9. On the Pre-Installation Summary window, click Install.
10. At the Install Complete window, click Next.
11. At the Important Information window, click Done to exit the installer.
12. Start the SnapManager server by completing the following steps:
a. In the Windows Services window, select N series SnapManager 3.1 for SAP.
b. In the left panel, click Start.
13. Verify that the SnapManager system is running correctly by following these steps:
a. Open the SnapManager Command Line Interface (CLI) command prompt window by selecting Start → Programs → N series → SnapManager for SAP → Start SMSAP Command Line Interface (CLI)
b. In the CLI window, enter the following command:
smsap system verify
SnapManager displays a message stating that the operation succeeded.
14. For upgrades, upgrade each SnapManager repository by following these steps:
a. Open the SnapManager Command Line Interface (CLI) command prompt window by selecting Start → Programs → N series → SnapManager for SAP → Start SMSAP Command Line Interface (CLI)
b. In the CLI window, enter the following command:
smsap repository update -repository -dbname repo_service_name -host
repo_host
-login -username repo_username -port repo_port
repo_host
-login -username repo_username -port repo_port
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.