Compellent Storage Center

(1)

Compellent Storage Center

SAN-Based Backup and Recovery with Microsoft

Data Protection Manager (2007/2010) and

Compellent Storage Center

Compellent Corporate Office Compellent Technologies 7625 Smetana Lane

Eden Prairie, Minnesota 55344

(2)

Introduction

Audience

The target audience for this white paper is Exchange administrators, system

administrators, storage administrators, DPM administrators, and architects who analyze, design, and maintain robust storage systems. Readers should be familiar with Microsoft Exchange Server, Microsoft Windows Server 2003, Microsoft Data Protection Manager, and Compellent Storage Center.

Customer Support

Compellent provides live support 1-866-EZSTORE (866.397.8673), 24 hours a day, 7 days a week, and 365 days a year. For additional support, email Compellent at

[email protected]. Compellent responds to emails during normal business hours.

Disclaimers

Information in this document is subject to change without notice.

© 2010 Compellent Technologies. All rights reserved. Reproduction in any manner without the express written permission of Compellent Technologies is strictly prohibited. Trademarks used in this text are property of Compellent Technologies, or their respective owners.

General Syntax

Item Convention

Menu items, dialog box titles, field names, keys Bold

Mouse click required Click:

User Input Monospace Font

User typing required Type:

Website addresses http://www.compellent.com

Email addresses [email protected]

Document Revision

Date Revision Description

1/21/2009 1.0 Release

(4)

Overview of Microsoft Data Protection Manager

Data Protection Manager (DPM) is a key member of the Microsoft System Center family of management products, designed to help IT professionals manage their Windows environment. DPM is the new standard for Windows backup and recovery—delivering continuous data protection for Microsoft application and file servers using seamlessly integrated disk and tape media. DPM enables rapid and reliable recovery through advanced technology for enterprises of all sizes.

Today’s business climate is more challenging than ever and businesses are under constant pressure to lower costs while improving overall operational efficiency. In short, businesses are being asked to ―do more for less.‖ One way that enterprises of all sizes can reduce costs and improve business agility is by changing the way data protection is managed. DPM provides the following additional benefits:

Continuous Data Protection – DPM captures data changes as they occur in real-time and synchronizes every 15 minutes to ensure Windows data and user productivity are

protected—unlike other legacy methods that backup data only once a day—so that business critical data can be protected at all times.

Lossless Restores for Applications – By seamlessly integrating a point-in-time database restore with the existing application logs, DPM delivers lossless recovery of Microsoft Exchange, SQL, and SharePoint servers without the need for constant replication or synchronization.

Superior Application Integration for Exchange Server, SQL Server, and SharePoint – DPM offers integrated support for Exchange Servers 2003 and 2007 with advanced cluster configurations, shorter SQL Server backup windows without the need for compression, and integrated restores for SharePoint. DPM also provides one touch application restores with zero data loss.

Rapid Recovery – Backing up data to disk provides the fastest way to recover data that’s been lost due to user error or software and hardware corruption. With DPM, recovering information is as simple as browsing a share and copying directly from the DPM platform to the production server within seconds. By restoring data from disk, DPM enables customers to recover data in minutes, versus the hours it takes to recover from tape.

Reliable Recovery – DPM leverages disk-based backup to provide the highest level of reliability versus traditional—and often unpredictable—tape backup methods. All of the various failure points for tape backup, including corrupt indexes, broken media,

misplaced cartridges, and human error are all avoided by relying on disk storage as the primary restoration medium, while still leveraging tape for long-term archival storage. Seamless Disk and Tape Integration – DPM transparently leverages both disk and tape mediums to enable fast, multiple points-in-time-per-day restores from disk, while ensuring long term retention and off site portability with disk.

Unified Protection Policies Across Data Types – DPM allows protection to be configured across heterogeneous applications and file-sharing platforms with a single policy. This allows you to manage logical groupings of data from a single UI—delivering Exchange, SQL, SharePoint and File data mixed, within a single policy, to any

(5)

SLA-driven Backup Process – Protection policies are based on intent and SLAs, creating a layer of abstraction that insulates the user from the often confusing process of scheduling individual backup jobs in order to meet an overall SLA.

Block Filter – With an efficient disk infrastructure and reduced network traffic, DPM’s volume filter changes how backups are achieved and maintained:

 The volume of full backups is reduced by as much as 90 percent, saving disk space and reducing backup time from hours to minutes.

 Express full backups and an enhanced network throttling mechanism allows for more granular management of bandwidth.

Overview of the Compellent Storage Center

Compellent’s Storage Center is an enterprise class storage area network (SAN) that significantly lowers capital expenditures, reduces storage management and

administration time, provides continuous data availability and enables storage

virtualization. Storage Center’s industry-standard hardware and sophisticated software manage data at the block-level, maximizing utilization, automating tiered storage, simplifying replication and speeding data recovery.

A Modular Hardware Design – The hardware design consists of industry standard-based clustered controllers providing automatic failover. Compellent can seamlessly connect to any open-systems server without the need for server side agents.

Organizations can mix and match Fibre Channel and iSCSI server connectivity, and disk enclosures support any external interface and disks based on Fibre Channel, Mid-Tier Fibre Channel, or Serial ATA.

Powerful Suite of Software – Storage Center offers a powerful suite of enterprise capabilities to manage data differently. Building on Compellent’s Dynamic Block

Architecture, Storage Center software intelligently optimizes data movement and access at the block-level to maximize utilization, automate tiered storage, simplify replication and speed data recovery.

Intuitive, Unified Interface – A centralized management interface streamlines

administration and speeds common storage management tasks. The interface features a point-and-click wizard-based setup and management, comprehensive Phone Home capabilities, automatic notification when user-defined capacity thresholds are reached, and advanced storage consumption and chargeback reporting.

(6)

DPM 2007

DPM Process Overview

Data Protection Manager (DPM) helps you manage the process of protecting and recovering data on the file and application servers in your network. This topic describes the high-level steps you need to perform to successfully protect and recover data in the DPM environment.

Protecting data – As illustrated in Figure 1, the high-level process used to protect data involves the following steps:

1. You select data sources on a server that you want to protect whether it is an application server or a file server.

2. To start protecting data, DPM creates a full copy (referred to as a replica) of the selected data sources on the DPM server.

3. To continue protecting data, DPM synchronizes each replica with the data sources on a recurring schedule. When a replica is updated, it replaces the previous replica.

4. To support data recovery, DPM creates point-in-time copies (referred to as recovery points) of the replica on a recurring schedule. DPM maintains up to 64 recovery points for each replica.

DPM Server

File Server

Replica Created

Updates

Current Replica

Shadow Copy Created

Figure 1 - Protection

Recovering data – As illustrated in Figure 2, the high-level process for recovering data involves the following steps:

1. You select the version of the data that you want to recover from the recovery points on the DPM server.

(7)

DPM Server

File Server

Shadow Copies

Figure 2 – Recovery

DPM Initial Replication and Recovery Process Utilizing Compellent Storage

In this scenario, a single dynamic volume (sized accordingly) is presented from the Compellent Storage Center to the DPM Server which uses the volume for the recovery points (shadow copies).

It is important to note that the transfer of backup data from the protected server to the DPM Server occurs over the local area network (LAN).

Agent Configuration

1. If you have not done so already, install a DPM Server. This server must be a member of a domain as do the other servers in which it will protect.

2. Open the Microsoft DPM Server console and install the DPM agent on the server that you want to protect. (Management > Install…) The server will then reboot. Storage Pool Configuration

1. Using the Compellent Storage Center web administration interface, create a new volume to be used in the storage pool and will contain the recovery points for DPM and its protected servers. Map this new volume up to the DPM server. NOTE: This volume should be at least two times the size of the total amount of data in which you plan to protect.

(8)

3. Back in the DPM console, at the top of console, click on Management, Disks tab, and then Add.

4. Select the new disk under ―Available Disks‖, click ―Add‖, then OK.

5. DPM will inform you that it is going to convert the selected disks to dynamic. Click ―Yes.

(9)

Protection Group Configuration

The protection group contains the server(s) that will be backed up. You can have multiple protection groups containing different types of servers and applications.

1. In the DPM console, at the top, click on ―Protection‖, then ―Create Protection Group‖.

2. Select the server(s) and the objects that you want to be included in the protection group. Click Next.

3. Name the protection group something that describes what it is protecting. Accept the default for the protection method. Click Next.

(10)

5. Review the storage pool disk space allocated for the protection group. No changes should be necessary here. Click Next.

(11)

7. Review the settings summary, and then click ―Create Group‖. This will create and configure the new protection group based on the settings you have selected. NOTE: The DPM server will configure the necessary partitions on the dynamic disk and then start to replicate across the network. This process will attempt to use all available network bandwidth of the DPM and protected server(s). This initial process should be completed only during non-peak hours to reduce the impact on the production environment.

Recovery

The recovery process can be network intensive as data is copied from the DPM server back to the protected server. During this time, the DPM server will attempt to utilize as much of the NIC resources as possible on both the DPM server and protected server as indicated below. DPM does also offer bandwidth throttling capabilities.

(12)

1. In the DPM Server console, at the top, click on ―Recovery‖. Expand the tree and in the left pane, select the object that contains the data you want to recover. 2. Next, from the lower right panel, select the recoverable item you want to recover. 3. From the ―Recovery Time‖ dropdown, select the recovery point you wish to

restore.

4. On the right side, Click ―Recover‖.

5. Follow the Recovery Wizard and choose the appropriate settings for your recovery.

DPM Process Utilizing SAN-Based Backup & Recovery

In this scenario, snapshots or replays of the volumes from the protected server are used as recovery points on the DPM server. This process leverages Compellent Storage Center Data Instant Replay and eliminates the amount of network traffic and utilization otherwise normally required.

For this scenario, we will be using a Windows Server running SQL Server 2005. Agent Configuration

1. If you have not done so already, install a DPM Server. This server must be a member of a domain as do the other servers in which it will protect.

2. Open the Microsoft DPM Server console and install the DPM agent on the server that you want to protect. (Management > Install…) The server will then reboot. Recovery Point Volume Configuration

(13)

DPM and the protected server that will use the SAN-based backup. Map this new volume up to the DPM server.

NOTE: This volume should be at least two times the size of the total amount of data in which you plan to protect.

2. Open the Disk Management MMC on the DPM server and rescan disks. When the newly created disk appears and the dialog appears, initialize the disk, format, and assign a drive letter.

Protected Server Volume Setup

This section describes the overall process of taking a replay of the protected volumes and assigning them to the DPM server.

1. In the Compellent Storage Center web interface, take a replay of the volume(s) that will be protected. (right-click on the volume, click Create Replay)

(14)

3. On the DPM server, assign a drive letter or mount point to the local recovery volumes (replays) that have been mapped.

8. Open the DPM Administrator Console. At the top, click on ―Protection‖, then ―Create Protection Group‖.

(15)

5. Name the protection group something that describes what it is protecting. Accept the default for the protection method. Click Next.

6. Specify your short-term recovery goals. Click Next.

7. Review the storage pool disk space allocated for the protection group. For DPM 2010, uncheck both checkboxes, and then click the Modify button in the disk space allocation dialog.

DPM 2007 DPM 2010

(16)

DPM 2007 DPM 2010

9. Once you have configured the disk allocation, click OK.

10. Click Next; leave the default replica creation method as ―Manual‖ which is the only option available. Then click ―Create Group‖.

11. Open Windows Explorer and browse to: DPM 2007: C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\computer_name\SQLServerWriter\ database_name DPM 2010: C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\computer_name\SQLServerWriter\ VOL_GUID

(17)

13. In the DPM Administrator Console, under the Protection tab, select the protection group and the object you just moved the files for, right-click and select ―Perform Consistency Check…‖

Recovery

The recovery process when configured will use a SAN-based recovery which relies on the availability of VSS hardware snapshots.

To recover data, follow these steps:

1. Run the ―CreateShadowCopy.ps1‖ script which is included with the installation of Data Protection Manager and is available at C:\Program Files\Microsoft

DPM\DPM\bin\. (If you are unable to locate the script, you can copy its contents from the appendix of this document.)

2. From the Compellent Storage Center web interface, take replays of the replica volumes and the recovery point volume mapped to the DPM server.

(18)

4. On the protected server, start Disk Management and rescan for disks and then assign a drive letter or mount point to each new disk from the replays that were mapped to the server.

5. From the DPM Administrator Console, select the ―Recovery‖ tab.

6. Drill down through the tree to find the database that you want to recover and select it.

7. Follow the Recovery wizard to select your options including the recovery type, what state the database should be left in.

(19)

(20)

DPM 2007 Requirements

The Microsoft System Center Data Protection Manager server must be a dedicated, single-purpose server, and cannot be either a domain controller or an application server. To install DPM successfully, you must install the software listed in Table 1.1 before installing the DPM application. DPM Setup will then install the additional required prerequisite software.

If you want to install the required prerequisite software manually, you must follow the steps detailed in Manually Installing Prerequisite Software in the Data Protection Manager Help.

Table 1.1 lists the DPM server prerequisite software that DPM Setup does not install. You must install the following software before you can install DPM.

Software Install from

Microsoft Management Console 3.0 http://go.microsoft.com/fwlink/?LinkId=55423

Hotfix 891957: This hotfix resolves an issue with Windows-based systems which may cause them to deplete their paged pool if the Volume Shadow Copy Service is placed under heavy load.

32-Bit x86 operating systems:

http://go.microsoft.com/fwlink/?LinkId=48584 x64-Bit operating systems:

http://go.microsoft.com/fwlink/?LinkId=75131

Windows PowerShell 1.0 32-Bit x86 operating systems:

http://go.microsoft.com/fwlink/?LinkId=658 x64-Bit operating systems:

http://go.microsoft.com/fwlink/?LinkId=65814

Table 1.1 Prerequisite Software that DPM Installs

Following is the DPM server prerequisite software that DPM Setup installs before installing the DPM application.

 Microsoft .NET Framework 2.0

 Microsoft Software Quality Metrics (SQM)  Single Instance Storage (SIS)

(21)

Protected Computers

Each server Microsoft System Center Data Protection protects must meet the requirements in Table 1.2.

Protected Computers Computer Requirements

File servers You can protect file servers on any of the following operating systems:

 Windows Server 2003 with Service Pack 1 (SP1) or later (Standard and Enterprise Editions).

 Windows Advanced Server 2003 with SP1 or later.  Windows Server 2003 R2 (Standard and Enterprise

Editions).

 Windows Storage Server 2003 with SP1 or later (Standard, Enterprise and Express Editions).

Note

To obtain SP1 for Windows Storage Server 2003, contact your original equipment manufacturer.

 Windows Small Business Server 2003 (Standard and Premium Editions).

 Windows Small Business Server 2003 R2 (Standard and Premium Editions).

 Windows Server 2008 (Core, Standard, and Enterprise Editions).

Computers running SQL Server

 Microsoft SQL Server 2000 with Service Pack 4 (SP4)

 - OR -

 Microsoft SQL Server 2008 - OR -

(22)

Note

DPM supports Standard, Enterprise, Workgroup, and Express Editions of SQL Server.

Important

You must start the SQL Server VSS Writer Service on computers running SQL Server 2005 SP1 before you can start protecting SQL Server data. The SQL Server VSS Writer Service is turned on by default on computers running SQL Server 2005. To start the SQL Server VSS Writer service, in the Services console, right-click SQL Server VSS writer, and then click Start.

Computers running Exchange Server

 Exchange Server 2003 with SP2 - OR -

 Exchange Server 2007

Note

DPM supports Standard and Enterprise Editions of Exchange Server.

 Before you can protect Exchange Server 2007 data, you must install hotfix 940006. For more details, see Knowledge Base article 940006, "Description of Update Rollup 4 for Exchange 2007"

(http://go.microsoft.com/fwlink/?LinkId=99291).

Computers running Virtual Server / Hyper-V

 Hyper-V (Required DPM SP1)  Microsoft Virtual Server 2005 R2 SP1

Note

(23)

Machine Additions

Windows SharePoint Services

 Windows SharePoint Services 3.0  Microsoft Office SharePoint Server 2007

Before you can protect Windows SharePoint Services (WSS) data, you must do the following:

 Install Knowledge Base article 941422, "Update for Windows SharePoint Services 3.0"

(http://go.microsoft.com/fwlink/?LinkId=100392).  Start the WSS Writer service on the WSS Server and

then provide the protection agent with credentials for the WSS farm. For more information, see "Starting and Configuring the WSS VSS Writer Service" in Configuring DPM 2007

(http://go.microsoft.com/fwlink/?LinkId=91852).  Update the instance of SQL Server 2005 to SQL

Server 2005 SP2.

Shared disk clusters  File servers

 SQL Server 2000 with SP4  SQL Server 2005 with SP1  Exchange Server 2003 with SP2  Exchange Server 2007

Non-shared disk clusters

 Exchange Server 2007

Workstations  Windows XP Professional SP2

 Windows Vista (must be a member of a domain)

(24)

DPM 2007 Protectable and Recoverable Data

Product Protectable Data Recoverable Data

Microsoft Exchange Server 2003 with Service Pack 2 (SP2)

Exchange Server 2007

Storage group Storage group Database Mailbox

Microsoft SQL Server 2000 with Service Pack 4 (SP4)

SQL Server 2005 with Service Pack 1 (SP1) or later

Microsoft SQL Server 2008

Database Database

Microsoft Office SharePoint Server 2007 Microsoft Windows SharePoint

Services 3.0

Farm Farm

Database Site File or list

Windows Server 2003 with SP1

Windows Storage Server 2003 with SP1 Windows Server 2008 Volume Share Folder Volume Share Folder File data

Microsoft Virtual Server 2005 R2 SP1 Microsoft Hyper-V

Virtual server host configuration Virtual machines Data for applications running in virtual machines

All computers that can be protected by DPM 2007 except computers running

(25)

Windows Vista or Windows Server 2008

Workstations running Windows XP Professional SP2

Windows Vista operating systems, except the Windows Vista Home Premium

operating system (the computer running Windows Vista must be a member of a domain)

Note

DPM does not support file protection on portable computers running Windows XP Professional SP2 and Windows Vista operating systems.

(26)

DPM 2010

DPM 2010 Overview

Microsoft System Center Data Protection Manager 2010 provides continuous data protection of Windows applications and file servers including Windows Server 2003 through 2008 R2, SQL Server 2000 through 2008 R2, Exchange Server 2003 through 2010, SharePoint Server 2003 through 2010, Dynamics AX 2009, SAP running on SQL Server, Microsoft Virtual Server 2005 R2, and Hyper-V (including Cluster Shared Volumes).

A single DPM server can protect up to 100 servers, 1000 laptops, or 2000 databases.

Compellent VSS Hardware Provider Support

With the introduction of DPM 2010, Microsoft has added support for third-party VSS hardware providers. It is important to note that third-party VSS hardware provider support is ONLY available when used with Hyper-V workloads on Cluster Shared Volumes. In addition, Compellent’s VSS hardware provider is only available with the purchase of Compellent Replay Manager for Microsoft Servers. Microsoft strongly recommends the use of hardware snapshots via a VSS hardware provider for CSV clusters.

Tested VSS Hardware Providers:

http://blogs.technet.com/b/dpm/archive/2010/02/05/tested-hardware-vss-provider-table.aspx

CSV Backups via Hardware Snapshot with DPM 2010

Cluster Shared Volumes provide the ability for all nodes of a Hyper-V cluster to have simultaneous access to a specific volume while each virtual machine has direct I/O access to its specific VHD on the CSV regardless of its location within the cluster. When a backup takes place via a software snapshot or using VOLSNAP (as DPM does), the CSV on which the VHD is contained has to be moved local to the node where the virtual machine is currently homed. During the backup, the CSV remains active on the specific node for the duration of the snapshot and the actual backup process. This results in a performance impact since Direct I/O will be minimized, which in turn results in limiting the number of VM backups that can take place since these backups take place in a serial fashion.

(27)

Hyper-V Protection Prerequisites

Virtual Machine Item-Level Recovery

To enable virtual machine item-level recovery, the Hyper-V role must be installed on the DPM Server. If the DPM Server hardware does not support the installation of the Hyper-V role, DPM will still continue to protect the virtual machine, but item-level recovery will not be available.

Integration Components

The Hyper-V Integration Components must be installed on all guest virtual machines. (http://go.microsoft.com/fwlink/?LinkId=165041)

Windows Server 2008 SP2

On the Hyper-V server, install Microsoft Windows Server 2008 SP2 or install the Hyper-V prerequisites. (http://go.microsoft.com/fwlink/?LinkID=133781)

Windows Server 2008 R2

Install these hotfixes: KB975354 (http://support.microsoft.com/kb/975354), and KB975921 (http://support.microsoft.com/kb/975921).

Compellent VSS Hardware Provider (for CSV Clusters only)

For a CSV deployment, install the Compellent Replay Manager for Microsoft Servers, which contains the Compellent VSS hardware provider on each Hyper-V node in the cluster.

Compellent VSS Hardware Provider Configuration

The Compellent VSS hardware provider is configured via the Replay Manager Configuration wizard. The

configuration of this wizard allows you to setup the connection to the Compellent Storage Center which contains the CSV volumes that are part of the Hyper-V cluster. Once the host, user name, password, and server object are specified and saved, VSS uses this configuration information to perform the hardware-based snapshots (replays).

(28)

Hyper-V CSV Backup Process with Compellent VSS Hardware Provider

Data Protection Manager 2010 initiates

a Hyper-V virtual machine backup contained on a cluster shared volume (CSV).

The Compellent VSS Hardware Provider receives the call from DPM 2010 to take a snapshot of the CSV. The snapshot is completed on the Storage Center and the new replay is visible in the Storage Center Manager.

(29)

The data from the ―view‖ (replay) that was mapped up to the Hyper-V cluster node is copied over the network to the DPM Server storage pool.

Once the backup is complete, the ―view‖ (replay) is unmapped from the Hyper-V cluster node and deleted from the Storage Center (including the original replay that was taken as part of the backup process.

The DPM backup is successfully completed as indicated in the dialog.

Protecting Non-Virtualization Workloads with SAN-Based Backup

As stated above, DPM 2010 can leverage Compellent’s VSS hardware provider for snapshots of Hyper-V with CSV cluster workloads. However, at this time, only CSV cluster workloads are supported when using the VSS hardware provider.

(30)

Hardware Requirements

Component Minimum requirement Recommended requirement

Processor 1 GHz, dual-core CPU or faster

2.33 GHz quad-core CPU

RAM 4 GB

For more information about how DPM manages memory, see DPM and Memory.

8 GB

Pagefile 0.2 percent of the combined size of all recovery point volumes, in addition to the recommended size (generally, 1.5 times the amount of RAM on the computer).

For more information about configuring the DPM pagefile size, in the DPM Operations Guide, see Managing

Performance.

1.5 times the amount of RAM on the computer

Disk space for DPM installation

DPM installation location: 3 GB

Database files drive: 900 MB System drive: 1 GB

Note

The system drive disk space requirement is necessary if you choose to install the dedicated instance of SQL Server from DPM Setup. If you use a remote instance of SQL Server, this disk

Note

(31)

space requirement is considerably less.

Disk space for storage pool

Note

The storage pool does not support Universal Serial Bus (USB)/1394 disks.

1.5 times the size of the protected data

For more information about calculating capacity

requirements and planning the configuration of the disks, in Planning a

DPM 2010 Deployment, see

Planning the Storage Pool.

2.5–3 times the size of the protected data

Logical unit number (LUN)

N/A Maximum of 17 TB for GUID

partition table (GPT) dynamic disks

2 TB for master boot record (MBR) disks

Note

These requirements are based on the maximum size of the disk as it appears to the Windows Server operating system.

The following table lists the data source limits that a DPM server can protect (if it meets the minimum hardware requirements) and the recommended disk space required for the DPM server.

Platform Data source limit Recommended disk space

64-bit computers

600 volumes, of which 300 are replica volumes and 300 are recovery point volumes

Data sources are typically spread

(32)

across approximately 75 servers and 150 client computers.

Protected Computer Requirements

Protected

computers Computer requirements

File servers You can protect file servers on any of the following operating systems:

Windows Server 2003 Service Pack 2 (SP2), Core, Standard, Enterprise, and Datacenter Editions

Before you can protect a file server running Windows Server 2003 SP2, you must apply the following updates: Knowledge Base article 940349: Update for Windows Server 2003

The hotfix described in Knowledge Base article 975759: An application or service that uses a file system filter driver may experience function failure on a computer that is running Windows Vista, Windows Server 2003, or Windows Server 2008

Windows Server 2008, Core, Standard, Enterprise, and Datacenter Editions

Before you can protect a file server running Windows Server 2008, you must apply the following updates:

The hotfix described in Knowledge Base article 977381: The DFS Replication service may stop responding when it initializes the replication process for the replicated folders on a computer that is running Windows Server 2008 or Windows Server 2008 R2

The hotfix described Knowledge Base article 975759: An application or service that uses a file system filter driver may experience function failure on a computer that is running Windows Vista, Windows Server 2003, or Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=185943). Windows Server 2008 R2, Core, Standard, Enterprise, and

Datacenter Editions

Before you can protect a file server running Windows

Server 2008 R2, you must apply the hotfix described in Knowledge Base article 977381: The DFS Replication service may stop responding when it initializes the replication process for the replicated folders on a computer that is running Windows Server 2008 or Windows Server 2008 R2

(33)

Computers running SQL Server

Microsoft SQL Server 2000 with Service Pack (SP4), Standard, Enterprise, Workgroup, Compact, and Express Editions

Before you can protect a computer running SQL Server 2000 on Windows Server 2003 SP2, you must apply Knowledge Base article 940349: Update for Windows Server 2003

Microsoft SQL Server 2005 with SP1, SP2, or SP3, Standard, Enterprise, Workgroup, Compact, and Express Editions

Before you can protect a computer running SQL Server 2005 on Windows Server 2003 SP2, you must apply Knowledge Base article 940349: Update for Windows Server 2003

Microsoft SQL Server 2008, Standard, Enterprise, Workgroup, and Compact, Express Editions

Important

Before you can start protecting computers running SQL Server 2005 SP1, you must start the SQL Server VSS Writer service. By default, the SQL Server VSS Writer service is turned on for computers running SQL Server 2005. To start the SQL Server VSS Writer service, in the Services console, right-click SQL Server VSS writer, and then click Start.

Computers running Exchange Server

Exchange Server 2003 with Service Pack 2 (SP2), Standard and Enterprise Editions

Before you can protect a computer running Exchange Server 2003 on Windows Server 2003 SP2, you must apply Knowledge Base

article 940349: Update for Windows Server 2003

Exchange Server 2007, Standard and Enterprise Editions

Before you can protect Exchange Server 2007 data in a Clustered Continuous Replication (CCR) configuration, you must apply Knowledge Base article 940006: Description of Update Rollup 4 for Exchange 2007 (http://go.microsoft.com/fwlink/?LinkId=99291). Exchange Server 2010

(34)

The eseutil.exe and ese.dll versions that are installed on the most recent release of Exchange Server must be the same versions that are installed on the DPM server.

In addition, you must update eseutil.exe and ese.dll on the DPM server if they are updated on a computer running Exchange Server after applying an upgrade or an update.

For more information about updating eseutil.exe and ese.dll, see

Eseutil.exe and Ese.dll.

Computers running Virtual Server

Microsoft Virtual Server 2005 R2 SP1

Microsoft Virtual Server 2008 (non-clustered and clustered)

Note

To protect virtual machines for online backups, we recommend that you install Microsoft Virtual Server 2005 Updated Additions

Hyper-V Windows Server 2008 with Hyper-V

Before you can protect a computer running Windows Server 2008 with Hyper-V, you must apply the following updates:

Knowledge Base article 948465: Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2 - Five Language Standalone

The hotfix described in Knowledge Base article 971394: A backup of virtual machines fails when you use the Hyper-V VSS writer to back up virtual machines concurrently on a computer that is running Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=186554). Windows Server 2008 R2 with Hyper-V

Before you can protect a computer running Windows Server 2008 R2 with Hyper-V, you must apply the following updates:

For a clustered or non-clustered computer running Windows Server 2008 R2 with Hyper-V, apply the hotfix described in Knowledge Base article 975354: A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2

(35)

article 975921: You may be unable to perform certain disk-related operations after an exception when a hardware provider tries to create a snapshot in Windows Server 2008 R2 or in Windows 7

Windows SharePoint Services

Windows SharePoint Services 3.0

Before you can protect a computer running Windows SharePoint Services 3.0, you must apply the update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 with Service Pack 1 (SP1) Before you can protect Windows SharePoint Services 3.0 data, you must do the following:

Start the Windows SharePoint Services VSS Writer service on the Windows SharePoint Services server and then provide the protection agent with credentials for the Windows SharePoint Services farm. Install the SQL Server Client components on the front-end Web server of the Windows SharePoint Services farm that DPM is going to protect. For information about installing SQL Server 2008

components, see How to: Install SQL Server 2008

If you use the Office SharePoint Server Search service, before you can protect Windows SharePoint Services 3.0 data, you must apply the following updates:

The update in Knowledge Base article 951695: Infrastructure Update for Windows SharePoint Services 3.0

The update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0

(http://go.microsoft.com/fwlink/?LinkId=100392). Windows SharePoint Services 4.0

Microsoft Office SharePoint Server 2007

Before you can protect a computer running Office SharePoint Server 2007, you must apply the update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0

(36)

The update in Knowledge Base article 951695: Infrastructure Update for Windows SharePoint

Services 3.0(http://go.microsoft.com/fwlink/?LinkId=186530). The update in Knowledge Base article 941422: Update for Windows SharePoint Services 3.0

(http://go.microsoft.com/fwlink/?LinkId=100392). Office SharePoint Server 2010

Important

Before you can protect a computer running any version of SharePoint Services or SharePoint Server on Windows

Server 2003 SP2, you must apply the update in Knowledge Base article 940349: Update for Windows Server 2003

Shared disk clusters

File servers

SQL Server 2005 with Service Pack 1 (SP1) SQL Server 2008

Exchange Server 2003 with Service Pack 2 (SP2) Exchange Server 2007 Exchange Server 2010 Hyper-V Non-shared disk clusters Exchange Server 2007 Exchange Server 2010

Workstations Windows XP Service Pack 2 (SP2) or later

Note

(37)

Windows Vista or Windows Vista Service Pack 1 (SP1) Windows 7 Client

DPM 2007/2010 Configuration Best Practices

Database File Copy

During the database file move portion of the ―SAN-Based backup and Recovery‖, you will only move the .mdb (database) file to the DPM ―FULL‖ folder. When the Consistency Check has completed, you will see that DPM moves the .ldb (log) file to that location as well.

In addition, you will only see one of the volumes in the ―Modify Disk‖ section. You will not see either the Log or Database volumes. Therefore, you protect only the Database volume and DPM handles the log file(s).

Automation

You may wish to use the Compellent PowerShell Command Set in addition to the built-in DPM PowerShell cmdlets to automate portions of this. By utilizing PowerShell, you can streamline this process to avoid user error during the backup and recovery of your data. Recovery Points and Snapshot Deltas

In order to recover from a specific point in time, all volumes attached to the DPM server for that protection group must have a snapshot (replay) taken and assigned to the protected server. However, if those copies already reside on the protected server you do not need to re-perform this action.

Mount Points

For larger environments that maintain a large number of volumes, it will be necessary to utilize mount points instead of individual drive letters for each protected server volume replica that is being mapped up to the DPM Server. The overall process doesn’t change, however, when configuring the protection group and specifying disk allocations, the custom volume (particularly the replica volume) dropdown box will show all volumes that contain either a drive letter or mount point.

Automount

Automount, the process that enables Windows to automatically mount new basic

volumes that are added to the system and to assign them drive letters, must be enabled for DPM 2010 backup and recovery to work.

The following PowerShell script will enable Automount on a Windows server. Invoke-command -computername <ServerName> -scriptblock {"automount enable" | diskpart.exe}

Conversely, the following PowerShell script will disable Automount on a Windows server. Invoke-command -computername <ServerName> -scriptblock

(38)

Performance Benefits of SAN-Based Recovery

Data Instant Replay

With Compellent Storage Center Data Instant Replay, you can recover any size volume to any server quickly, without any of the traditional snapshot restraints. Using a simple point-and-click interface in concert with Microsoft Data Protection Manager,

administrators of all levels can immediately recover in the event of disruption.

Data Instant Replay supports unlimited number of Replays per volume, mapped to any server. There are no requirements to have pre-allocated disk storage for your replays; replays are created without an initial mirror saving capacity.

Data Progression

Hardware snapshots (replays) can participate in another feature of the Compellent Storage Center: tiered storage, also known as Data Progression.

Storage Center's Data Progression is a complete hardware and software architecture that delivers fully automated tiered storage. This patented technology cuts administrative time and reduces overall storage costs by dynamically classifying and moving data at the block-level between tiers of storage based on frequency of access. This complete Automated Tiered Storage solution does not require time consuming data classification and the repetitive manual transfer of data between tiers. That means that data that isn’t regularly access is migrated to lower cost storage, which in turn means that your Tier 1 storage is reserved for only data that is access regularly like your mission critical application and file data.

Thin Provisioning

(39)

Network Bandwidth

(40)

Appendix

PowerShell Script: CreateShadowCopy.ps1

This script can be used for taking snapshots in a SAN recovery on a DPM 2007/2010 implementation. Copy and paste the script contents below into a file and name it CreateShadowCopy.ps1. This file should be saved to the BIN directory of your Microsoft DPM installation. (ex. C:\Program

Files\Microsoft DPM\DPM\bin\)

param([string] $DSName, [string] $PGName) if(!$args[0])

{

if(!$DSName) {

$DSName = read-host "DatasourceName:"

} } else {

if(("-?","-help") -contains $args[0])

{

write-host Usage::

write-host CreateShadowCopy.ps1 DatasourceName ProtectionGroupName

write-host Help::

write-host Creates a shadow copy for the given Datasource

write-host

exit 0 }

else {

write-host "Usage -? for Help"

exit 1 }

}

if(!$PGName) {

$PGName = read-host "ProtectionGroupName:"

}

$dpmname = &"hostname"

connect-dpmserver $dpmname

$pg = get-protectiongroup -dpmservername $dpmname

if (!$pg) {

write-error "Cannot get the protectionGroup"

disconnect-dpmserver $dpmname

exit 1 }

(41)

write-error "Cannot get the requested protectionGroup"

exit 1 }

$ds = get-datasource -protectiongroup $mypg

if (!$ds) {

write-error "Cannot get the datasources for the PG"

exit 1 }

$myds = $ds | where {$_.Name -eq $DSName} if (!$myds)

{

write-error "Cannot get the required Datasource"

exit 1 }

$j = new-recoverypoint -datasource $myds -DiskRecoveryPointOption

WithoutSynchronize -Disk if (!$j)

{

write-error "Cannot get the required Datasource"

disconnect-dpmserver $dpmname exit 1 } $jobtype = $j.jobtype while (! $j.hascompleted ) {

write-host "Waiting for $jobtype job to complete..."; start-sleep 5

}

if($j.Status -ne "Succeeded") {

write-error "Job $jobtype failed..."

}

Write-host "$jobtype job completed..."

Compellent Storage Center

Compellent Storage Center

SAN-Based Backup and Recovery with Microsoft

Data Protection Manager (2007/2010) and

Compellent Storage Center

Contents

Introduction

Audience

Customer Support

Disclaimers

General Syntax

Document Revision

Overview of Microsoft Data Protection Manager

Overview of the Compellent Storage Center

DPM 2007

DPM Process Overview

DPM Initial Replication and Recovery Process Utilizing Compellent Storage

DPM Process Utilizing SAN-Based Backup & Recovery

DPM 2007 Requirements

Protected Computers

DPM 2007 Protectable and Recoverable Data

DPM 2010

DPM 2010 Overview

Compellent VSS Hardware Provider Support

CSV Backups via Hardware Snapshot with DPM 2010

Hyper-V Protection Prerequisites

Compellent VSS Hardware Provider Configuration

Hyper-V CSV Backup Process with Compellent VSS Hardware Provider

Protecting Non-Virtualization Workloads with SAN-Based Backup

Hardware Requirements

Protected Computer Requirements

DPM 2007/2010 Configuration Best Practices

Performance Benefits of SAN-Based Recovery

Appendix

PowerShell Script: CreateShadowCopy.ps1