EVault for Data Protection Manager. Course 301 Server Protection with DPM File and System State

(1)

Course 301

Server Protection with DPM

File and System State

Server Protection with DPM

(2)

2

3 Objectives

In this course, you will learn how to protect standard file servers with DPM. This includes backing up and restoring individual files along with

instructions on how to restore system state in the event of a system failure.

Scenario

The course is composed of a Windows 2003 file server that we’ll protect. It does require that a VSS patch is installed prior to protecting any data. These instructions are included in the lab. Note that Server 2008 has different requirements for installation and recovery.

Estimated Time to

Complete This Lab

90 Minutes

Requirements for

This Lab

• http://support.microsoft.com/kb/940349/ - IMPORTANT – This needs to be installed in order to protect Windows 2003 Servers

• File Server is joined to our domain • Our File Server is running Windows 2003

• On your productions machines, we recommend that all Windows Updates have been applied

(4)

4 Exercise 1 – Installing Required Windows Update for Windows 2003

Normally you would install the following update on your File Server

http://support.microsoft.com/kb/940349/, but I’ve disabled internet access on the File Server. I’ve already downloaded it, and you’ll find the executable on the desktop of the FS01 machine

(WindowsServer2003-KB940349-v3-x86.ENU.exe). This will require a reboot of your Windows 2003 SQL machine.

Tasks Detailed Steps

1. Initial Logon

FS01

a. Once the lab starts, within Surgient, click on the FS01 server and choose RDP.

b. On the desktop, launch WindowsServer2003-KB940349-v3-x86.ENU.exe. c. When asked “Do you want to run this file?” click Run.

d. In the Software Update Installation Wizard, click Next >.

e. On the License Agreement screen, click “I Agree” and select Next >.

f. Once the installer completes, click Finish. This will reboot your FS01 server. g. Wait at least 3 minutes before continuing to the next exercise as we need to

wait for the File server to finish rebooting.

h. To validate that the File server has completed rebooting, try clicking Connect in Surgient. If it pulls up FS01’s desktop, it has rebooted.

Exercise 2 – Installing DPM Agent on File Server

In this step, we will push the DPM Agent to the File server that we wish to protect. This will allow us to further configure the protection of our File server through DPM.

1. Switch Machines

EDPM

a. Using the Server drop-down at the top of the Surgient window, choose EDPM_Server to connect to the EDPM server.

b. The system should automatically log you in, but if you are prompted for login, below are the credentials.

• Username TrainingLab\Administrator • Password I365password.

c. If Server Manager opens, close it. 2. DPM 2010

Administrator Console

a. On the Desktop, open Microsoft System Center Data Protection Manager 2010.

b. Within the DPM 2010 Administrator Console, click the Management tab. c. On this tab, click the Agents tab.

d. Under Selected Items, click Install… 3. Agent

Installation Wizard

(5)

5

c. Select FS01, and click Add >. d. Click Next >.

e. We need to specify a user with Administrator privileges. This is because the user the backup uses this user to perform backups.

• User name: Administrator • Password: I365password • Domain: TrainingLab.com f. Click Next >.

g. On the Choose Restart Method screen, we’ll choose “No. I will restart the selected computer later.” This way, you can restart the server during off hours.

h. Click Next >.

i. On the Summary screen, click Install.

j. DPM will now push the DPM Agent to the File Server. You’ll notice that the installation fails, but if you look at the details, the File server needs to be rebooted. Click Close.

4. Reboot File Server

FS01

a. Using the Server drop-down at the top of the Surgient window, choose FS01_Server.

c. To reboot FS01, click the Start Menu, and choose Shut Down. d. Choose Restart and click OK.

e. It will take about 3 minutes for the File server to reboot.

f. Using the Server drop-down at the top of the Surgient window, choose FS01_Server and see if you are able to connect. This validates that the server has been rebooted.

g. Using the Server drop-down at the top of the Surgient window, choose EDPM_Server to connect back to the EDPM appliance.

h. Back in the DPM 2010 Administrator Console, you’ll need to refresh the status of the SQL01 server since it’s been rebooted.

(6)

6 Exercise 3 – For this Lab Only – Create sample data

In the next steps, we’ll create some sample data to protect. In your production environment you would not normally follow these steps as you’ll already have some a server with your own proprietary data.

1. Switch Machines

FS01

a. Using the Server drop-down at the top of the Surgient window, choose FS01_Server to connect back to the File server.

c. Right-click the Start menu and choose Explore. d. Navigate to the root of the C:.

e. In Windows Explorer, click File \ New \ Folder.

f. Name the folder Temp. You should now have a folder C:\Temp. g. Double click the folder Temp to navigate there.

2. Create a Sample File that can be Restored Later

a. In Windows Explorer, right-click the right-hand pane and choose New \ Text Document.

b. For the New Text Document type Test.txt for the name of the file. c. Double-click the Test.txt file to open it.

d. For the content of the Test file, type “Testing DPM”. e. Click File \ Save.

(7)

7 Exercise 4 – Creating an File Data and System State Protection Group

In this section, you’ll learn how to protect standard File data and System State data with DPM. Note that there is another course that focuses on Bare Metal Recovery, and this topic will not be discussed in this course. Bare Metal Recovery is only available on Server 2008 and above.

1. Switch Machines

EDPM

a. Using the Server drop-down at the top of the Surgient window, choose EDPM_Server to connect back to the EDPM server.

c. If Server Manager opens, close it. 2. DPM 2010

Administrator Console

a. Within the DPM 2010 Administrator Console, click the Protection tab. b. This is where we’ll be creating a Protection Group.

c. Under Selected Items, click Create Protection Group… 3. Protection

group wizard

a. On the Welcome to the New Protection Group Wizard choose Next >. b. On the Select Protection Group Type screen, select Servers and choose Next

>.

c. On the Select Group Members screen, expand FS01. This will take a minute for DPM to collect FS01’s information.

d. Check All Volumes. You’ll notice that if you expand this field, you’ll see the Server Agents – Includes server class operating systems such as

Windows 2003 and 2008 along with application specific integration. File Data – Allows for protection of file level data such as entire volumes on a system, individual files and folders, shares presented or even system state backups. Server 2008 also allows for possible additional recoverability by providing options to do Bare Metal Recovery.

Application Data – Allows for protection of application data such as SQL, Exchange, SharePoint, and Hyper-V data. Integration allows for seamless hot backups of these applications.

Client Agents – Allows for protection of workstation operating systems such as Windows XP, Vista, and Windows 7

(8)

8

e. You will receive a warning that you should add System State.

f. Click System Protection. You’ll notice that if you expand this item, it has included System State. On your production machine, you might notice that it selects Bare Metal Recovery as well. This is only if you’re running Server 2008 or above. BMR is not available for Server 2003.

g. Click Next >.

h. On the Select Data Protection Method screen, we need to name our Protection Group. In this case name it, File Servers.

• For short-term protection, we’ll use Disk.

• Notice that long-term protection options is greyed out. This is because we do not have a tape library attached for long-term protection.

• Click Next >.

i. We’re now on the Specify Short-Term Goals screen. This is where we setup retentions and backup frequency.

• For the Retention range, we’ll set it to 30 days. This allows us to restore from the last 30 days. The maximum value is 64 days. The more days of retentions, the more storage you’ll need.

• For the Synchronization frequency, we’ll leave the defaults of Every Retention Range – This defines how many days back you can

restore your data.

Synchronization Frequency – During the synchronization process, the DPM Agent sends over the incremental changes since the last backup. Synchronizations allow for the a decrease in the amount of total data sent during this next Recovery Point and Express Full creation.

Initial Replica – With application data, this will send over the entire dataset to the DPM server. With SQL, it will send over the mdf and ldf files. For Exchange, it will send over the .edb, .stm, and .logs. Express Full Backup – With server data on the first Express Full Backup, it will send over the changed blocks since the last Initial Replica. On subsequent Express Full Backups, the Agent will send over the changed blocks since the last Express Full Backup. Each Express Full also generates a Recovery Point. As opposed to just sending over transaction logs, Express Fulls send over changes in the database itself.

(9)

9

EVault for Data Protection Manager - ©2010 i365, A Seagate Company 15 minutes. Incremental changes are sent on 15 minute intervals, but recovery points are not created for each Synchronization. This decreases the total amount of data that needs to be sent during the next Recovery Point.

• For the File Recovery Points setting, we’ll leave the default to backup 8:00 AM, 12:00 PM, 6:00 PM Everyday. However, you could Modify this. These will generate points in time you can recovery from.

• For the Express Full Backup settings, leave the default of 8:00 PM Everyday.

j. We’re now on the Review Disk Allocation screen.

• In the Disk space allocation of new members section, you’ll notice that the Total data size and Disk space allocated in DPM values might seem large. DPM performs some calculations and factors in the most possible change that can occur on your system. You can change these values so that DPM will not dedicate so much space. • We’ll click on Modify later, but first I want to explain the following:

i. Automatically grow the volumes – DPM will automatically

grow your volumes if they are nearing capacity. It will grow them by 25% or 10 GBs whichever is bigger. By choosing this, you can size your volumes smaller and let DPM grow the volumes on its own. DPM can only auto grow a volume once per every 15 minute window.

• Click Modify so that we can see where we could resize the volume allocation.

i. Replica Volume – is where DPM stores the current state of

the server. The smallest size is 1 GB. If your server was 10 GBs, you can set this to 10 GB. Another example is when you’re protecting a folder on the C: that’s 5 GBs but you’re actually using 100 GBs on the C: amongst all of its folders, DPM will display the Replica Volume as 100 GBs because DPM considers that you might want to protect other data on that volume.

ii. Recovery Point Volume – Is where DPM stores the

incremental changes between backups. The Recovery Points are played back against the Replica Volume. The more recovery points made, the larger the Recovery Point Volume. The smallest value for this is 1.56 GB. iii. In this example, we will not change the values here. iv. Click OK.

k. On the Choose Replication Creation Method screen, we’ll leave the Defaults which means we’ll send the Replica Now. However, normally, we

(10)

10

l. On the Consistency check options screen, we’ll choose to “Run a

consistency check if a replica becomes inconsistent.” You can schedule this, but consistency checks can take time as they do a block for block

comparison of the Replica that exists on the DPM server to the production data on the Agent machine. Click Next >.

m. On the Summary screen, click Create Group.

n. On the Status screen, wait for all the results to state Success and click Close. 4. Protection

Status

a. Back in the DPM 2010 Administrator Console, notice that the Protection Group Protection Status changes from Replica creation in progress to OK. b. Once all of the items selected in the Protection Group have an OK Protection

Status, the items you have been successfully backed up. In this lab, it typically takes about 25-30 minutes for this process to complete. c. If you wanted to check on their progress, you can always switch to the

(11)

11 Exercise 5 – For this Lab Only – Delete Sample Data

In the next steps, we’ll simply delete the text file we had created earlier.

1. Switch Machines

FS01

a. Using the Server drop-down at the top of the Surgient window, choose FS01_Server to connect back to the FS01 server.

2. Delete a Text File

a. Right-click the Start menu and choose Explore. b. Within Windows Explorer, navigate to C:\Temp\ c. Delete the Test.txt file that we had created earlier.

Exercise 6 – Recovering a File Data with DPM

For this exercise, we’ll restore the sample file we had created earlier.

1. Switch Machines

EDPM

a. Using the Server drop-down at the top of the Surgient window, choose EDPM_Server to connect back to the EDPM server.

c. If Server Manager opens, close it. 2. Recovering

File data within DPM

a. Within the DPM 2010 Administrator Console, click the Recovery tab. b. Expand Recoverable data\TrainingLab.com\FS01\All Protected

Volumes\C:\. Here you’ll see the various files and folders that we can recover from.

c. In the middle pane, we see a calendar of dates that we can choose from. Any calendar date that is in bold means that at least one Recovery Point exists on that day.

d. For the Recovery Time field, use the drop-down and choose the most recent time.

e. In the middle-pane under Recoverable item, scroll down and double-click the Temp folder.

f. Highlight the Temp.txt file.

g. On the right hand pane under Selected Items, choose Recover. This will spawn the Recovery Wizard.

3. Recovery Wizard

a. On the Review Recovery Selection screen, click Next >.

b. On the Select recovery type screen, select “Recover to the original location” c. On the Specify recovery options screen, click Next >.

d. On the Summary screen, click Recover.

(12)

12 Exercise 7 – Verify that the Data has been Restored

From the restore that we just completed, we want to check that our file has indeed been restored.

1. Switch Machines

FS01

c. Windows Explorer should still be open, but if it’s not, reopen it and navigate to C:\temp\.

d. You should see that the Temp.txt file is back. You can open it to check that it’s the same.

Exercise 8 – Recovering System State with DPM

For this exercise, we’ll restore System State back to our FS01 Server. When recovering System State, DPM allows you recover to a folder or network share. You then need to use either ntbackup or Windows Server Backup on the Agent machine to get the data rolled into your File server.

1. Switch Machines

EDPM

c. Using the Server drop-down at the top of the Surgient window, choose EDPM_Server to connect back to the EDPM server.

d. The system should automatically log you in, but if you are prompted for login, below are the credentials.

d. If Server Manager opens, close it. 2. Recovering

File data within DPM

a. Within the DPM 2010 Administrator Console, click the Recovery tab. b. Expand Recoverable data\TrainingLab.com\FS01\All DPM Protected

Data\System Protection.

c. In the middle pane, we see a calendar of dates that we can choose from. Any calendar date that is in bold means that at least one Recovery Point exists on that day.

d. For the Recovery Time field, use the drop-down and choose the most recent time.

e. In the middle-pane under Recoverable item, select System State. f. On the right hand pane under Selected Items, choose Recover. This will

spawn the Recovery Wizard. 3. Recovery

Wizard

a. On the Review Recovery Selection screen, click Next >.

(13)

13

c. On the Specify destination screen, click Browse.

a. Expand FS01\Volumes\C:\ and select the Temp folder.

b. On the Specify Alternate Recovery Destination screen, click OK. c. Click Next >.

d. On the Specify recovery options screen, click Next >. e. On the Summary screen, click Recover.

f. On the Recovery Status screen, wait for the Recovery Status to read Successful.

g. Click Close.

Exercise 9 – Using ntbackup / Windows Server Backup to replay System State

In this lab, we had been using a Windows 2003 server as an example, and therefore, we’ll need to use ntbackup to recover our System State. If you were using Server 2008, ntbackup has been replaced with Windows Server Backup.

1. Switch Machines

FS01

c. Click Start and then Run.

d. In the Run window, type ntbackup and click OK. 2. Using

Ntbackup to Restore System State

a. In the Backup or Restore Wizard window, click Next >.

b. In the Backup or Restore section, click Restore files and settings and click Next >.

c. In the What to Restore section, click Browse.

• On the Open Backup File screen, click Browse. i. Navigate to C:\Temp\DPM_<Date of

Recovery>\DPM_Recovered_At_<Date of Recovery>\DPM_System_State

ii. Click FS01.bkf and click Open. • On the Open Backup File screen, click OK.

d. Under Items to restore, check System State and click Next >. e. Click Finish.

f. Wait for Restore Progress window to complete and click Close. g. When prompted to Restart your computer, click Yes.

(14)

14 Conclusion

Hopefully you have a better understanding of how to protect File and System State data using DPM. Please feel free to do further testing in your training lab. For further information about DPM, you can always access their Technet site at http://technet.microsoft.com/en-us/library/ff399192.aspx. If this link is broken, goto http://technet.microsoft.com , navigate to Library, System Center, and choose System Center Data Protection Manager 2010.

You can always send comments and suggestions for this training module to [email protected] or for support related issues you can contact us at [email protected].

Server 2008 and Windows Server Backup

When restoring System State on a Server 2008 machine, you must use Windows Server Backup in command line mode.

Restores must be directed to C:\WindowsImageBackup and therefore selecting a source location will not be necessary. To access Windows Server Backup, you must open Command Prompt window.

We must get the version of the System State Backup you want to restore. Type the following command in a Command Prompt window.

Wbadmin get versions

You’ll see the various backups available. Note the Version identifier.

The syntax to run the restore is

Wbadmin start systemstaterecovery –version:[version identifier]

For example:

EVault for Data Protection Manager. Course 301 Server Protection with DPM File and System State

Course 301

Server Protection with DPM

File and System State

Server Protection with DPM

2

Table of Contents

3

Objectives

Scenario

Estimated Time to

Complete This Lab

Requirements for

This Lab

4

Exercise 1 – Installing Required Windows Update for Windows 2003

Exercise 2 – Installing DPM Agent on File Server

5

6

Exercise 3 – For this Lab Only – Create sample data

7

Exercise 4 – Creating an File Data and System State Protection Group

8

9

10

11

Exercise 5 – For this Lab Only – Delete Sample Data

Exercise 6 – Recovering a File Data with DPM

12

Exercise 7 – Verify that the Data has been Restored

Exercise 8 – Recovering System State with DPM

13

Exercise 9 – Using ntbackup / Windows Server Backup to replay System State

14

Conclusion