Demo Lab Guide Compellent - Amazon S3 · Demo Lab Guide – Compellent Replay Manager SQL Server...

Demo Lab Guide – Compellent

Replay Manager SQL Server

Product Domain: Storage

Author: Joseph Correia

Version: 1.01 Date: 28/01/2016

Table of Contents 1 Product Overview ............................................................................................................................................ 3

1.1 Lab Preparation Considerations and Caveats ................................................................................. 4

2 Introduction ...................................................................................................................................................... 5

What we will be doing: ................................................................................................................................... 5

2.1 Lab Topology and Essential Information ......................................................................................... 6

3 Replay Manager ............................................................................................................................................... 7

3.1.1 Getting Started ...................................................................................................................................... 7

3.1.2 Create a backup set ............................................................................................................................. 9

3.1.3 Run a backup set ................................................................................................................................. 17

3.1.4 Recover a database using Restore ................................................................................................... 18

3.1.5 Recover a database using Expose ................................................................................................... 22

3.1.6 Lab Cleanup (Important) .................................................................................................................. 32

3.1.7 Lab Complete! .................................................................................................................................... 32

3 Dell Demo Center – https://demos.dell.com | Dell Inc., 2016

1 Product Overview

Replay Manager integrates with Data Instant Replay to ensure data remains consistent even if Microsoft

Exchange or Microsoft SQL Server is running as a snapshot or Replay is captured. With Replay Manager

you have the ability to take Replays of Windows Server volumes without having to take Windows Server

applications offline.

- Seamless Integration. Provides an integrated solution for creating Replays of all Microsoft

Exchange and Microsoft SQL Server volumes.

- Ensures Data Consistency. Prevents files from being corrupted or skipped during the backup

process.

- Simplifies the Backup Process. Avoid the difficulties commonly associated with the legacy

backup process, such as processing interruptions due to applications shutting down.

https://demos.dell.com/


1.1 Lab Preparation Considerations and Caveats

It is in your best interests to ensure the demo environment you will be demonstrating is clean & tidy

before you begin. For this reason we would recommend, where possible, you log in to your demo at

least 15 minutes prior to delivery and check the following;

1. Familiarize yourself with the environment during this time and check any specific features you are

expecting to demo.

2. Most importantly, be crystal clear with yourself on what it is you plan to show. A full demo of every

feature described below (with questions) can take several hours. If you only have a short time slot

be sure to focus on the key points that address the customer’s pain points and will drive value

home to them.

3. Ensure that you have scheduled the demo for sufficient time so as not to have the demo end

before you are finished with the customer.

Any other guidance on how the user should prepare for the lab can be added here. If there are limitation

or something the user should be aware of call out also.



2 Introduction

The audience for this document is technical professionals who wish to learn more about protecting

Microsoft SQL Server databases using Replay Manager.

Reminder: This is a virtualized lab environment running pre-release builds of Storage Center 6.7

firmware and Enterprise Manager Software, so expect performance to be slower - please be patient.

Some of the steps you will be asked to perform in the lab may take longer to execute than it would in

a typical production environment. ALSO any references to CPL-HOL-SQL refer to LOCALHOST in

this Lab

What we will be doing:

This lab will show you how to use Replay Manager to backup and recover Microsoft SQL server

databases.

In this lab you will:

1) Create a backup set

2) Run a backup set

3) Recover a SQL Server database using Restore

4) Recover a SQL Server database using Expose



5)

2.1 Lab Topology and Essential Information



3 Replay Manager

3.1.1 Getting Started

Before beginning any of the exercises in this manual, there are a couple steps required to get the

environment ready. First, you’ll need to close any open applications. Then you’ll need to start the two

applications that will be used in this lab: Replay Manager Explorer and SQL Server Management Studio.

Close any open applications.

1. Double-click on the SQL Server 2014 Management Studio icon on the desktop.

Note: The credentials have already been entered and saved, so they do not need to be entered again.

2. Click on the Connect button in the Connect to Server dialog box.



3. Minimize the SQL Server Management Studio. Double-click on the Replay Manager Explorer icon

on the desktop.

4. In the Server Connections pane in the upper left hand corner of the screen, click on CPL-HOL-

SQL.

5. The credentials have already been entered and saved, so they do not need to be entered again.

Click on the OK button in the Login dialog box.



3.1.2 Create a backup set

The first step in protecting SQL Server databases with Replay Manager is to create a backup set for the

databases you want to protect. Each backup set can have a retention policy which tells Replay Manager

how many restore points to keep. A schedule can also be defined for each backup set, telling Replay

Manager how often the backup set should run. In this exercise, you will create a backup set to protect

the databases on an instance of SQL Server. After selecting the databases you want to protect, you will

give the backup set a name, define a retention policy and create a schedule.

1. Select the SQL Server backup extension by clicking on the SQL Databases icon in the Backup

Extensions pane in the lower left-hand corner of the screen.



2. Select the AdventureWorks2014, AdventureWorksDW2014 and AdventureWorksLT2014

databases in the component list in the middle of the screen.

3. Click on Create Backup Set in the Backup pane on the right-hand side of the screen.



4. The Create Backup Set dialog box will be displayed on the screen. Give the new backup set a

name.

5. In the Backup Set pane, enter “HOL Backup Set” in the User Defined Name text box, replacing the

default backup set name.

6. Define the retention policy for the backup set. By default, the backup set will retain three restore

points. Set the retention policy to keep restore points for five days.

7. Underneath Delete Old Restore Points in the Options pane, select Older than (Day) and change

the number of days from 3 to 5.



8. Define a schedule for the backup set. In the Backup Type pane at the bottom of the dialog box,

select Schedule for later and click on the Modify button.



9. The Backup Schedule dialog box will be displayed on the screen.

10. Set the schedule to run the backup set every day at 10pm. Select Recurring in the Schedule Type

pane.

11. In the Daily Frequency pane, Occurs once at will already be selected. Change the time from

12:00:00 AM to 10:00:00 PM.



Note: A backup set schedule can be configured to retry the backup set after a failure. By default,

Replay Manager will not retry the backup set.

12. Configure the schedule to retry two times, waiting five minutes between retry attempts.

13. In the Retry After Failure pane, select Retry Failed Backup Sets. Change the Retry After setting

from 1 minute to 5 minutes. Change the Number of Retries setting from 1 to 2.



14. Click on the OK button to save the schedule.

15. Click on the Submit button to create the backup set.



Note: A new backup set called HOL Backup Set has been created. This backup set will be used in

the next exercise.



3.1.3 Run a backup set

Any backup set, regardless of whether or not it has a schedule, can be run on demand. In this exercise,

you will run the backup set that was created in the previous exercise.

1. Select the backup set HOL Backup Set, by clicking on it in the Backup Set pane.

2. In the Backup Set pane, click on Run Now.



3. A dialog box will appear to confirm you want to run the backup set outside of its normal schedule.

Click on the Yes button.

Note: The backup set HOL Backup Set has been run, creating a restore point that can be used to

recover SQL Server databases. This restore point will be used in the next two exercises.

3.1.4 Recover a database using Restore

There are two methods in Replay Manager that can be used to recover SQL Server databases: Restore

and Expose. In this exercise, you will delete a SQL Server database. Using the Restore method in Replay

Manager, you will then recover the database using the restore point created in the previous exercise.

1. Switch to the SQL Server Management Studio by clicking on its icon in the taskbar.

2. Expand the Databases folder and select the AdventureWorksLT2012 database.

3.

4. Right click and select Delete.



5. The Delete Object dialog box will be displayed.

6. In the Delete Object dialog box, click on the OK button.



7. The AdventureWorksLT2012 database has been deleted. Next, we will recover the database using

the restore method in Replay Manager.

8. Switch to the Replay Manager Explorer by clicking on its icon in the taskbar.

9. Select the restore point that was created using the backup set HOL Backup Set.

10.

11. Click on Restore in the Restore Points pane.

12.

13. The Restore Snapshot dialog box will be displayed.

14. Click on the Unselect All button.



15. Select the AdventureWorksLT2012 database in the list of components.



16. Click on the Restore button.

17.

Note: The deleted database has been recovered using the restore point created by the HOL Backup

Set restore point.

3.1.5 Recover a database using Expose

In this exercise, you will use the Expose method to recover a database. You will first expose a restore

point in Replay Manager, presenting the exposed volumes as the K: and L: drive. You will then attach a

database in SQL Server using database files on the exposed volumes.

1. Select the restore point that was created by running the backup set HOL Backup Set. (The restore

point should already be selected.)



Click on Expose in the Restore Points pane.

The SQL Database Expose dialog box will be displayed.

At the end of the row for the E:\ drive, click underneath Expose Path.



2. Select Assign the following drive letter, chose the K:\ drive from the drop down list box and click

on the Submit button.



3. At the end of the row for the F:\ drive, click underneath Expose Path.

4. Select Assign the following drive letter, chose the L:\ drive from the drop down list box and click

on the Submit button.



5. Select Make exposed volumes writable in the upper right hand corner of the dialog box. Exposed

volumes must be made writable in order to attach databases from the exposed volumes.

6. Click on the Expose button.



Notes: The restore point has been exposed. The volumes from the point in time of the restore point

have been presented to Windows as the K: and L: drives.

7. Switch to the SQL Server Management Studio by clicking on its icon in the taskbar.

8. Select Databases.

9. Right-click and select Attach

.

10. The Attach Databases dialog box will be displayed.



11. Click on the Add button in the Attach Databases dialog box.

12. The Locate Database Files dialog box will be displayed.

13. In the directory tree on the left hand side of the dialog box, drill into the

K:\MSSQL12.MSSQLSERVER\MSSQL directory and select the Data directory.



14. On the right hand side of the dialog box, select the AdventureWorks2014_Data.mdf file and click

on the OK button.



15. SQL Server remembers the old location for the log file. Under Current File Path, change the drive

letter for the log file from F:\ to L:\.

16. Change the name of the attached database. At the top of the screen, click in the Attach As cell

and add “-Expose” to the existing database name. This will attach the database using the name

“AdventureWorks2014-Expose”.



17. Click on the OK button.

Note: A copy of the AdventureWorks2014 database named AdventureWorks2014-Expose has been

recovered from the exposed restore point. You will see the recovered database in the list of

databases in the SQL Server Management Studio.



3.1.6 Lab Cleanup (Important)

The cleanup script is run from a SQL Agent job in the SQL Server Management Studio (SSMS). If SSMS

is not already the current application, switch to SSMS by clicking on its icon in the taskbar,

1. Expand the SQL Server Agent folder.

2. Expand the Jobs folder.

3. Select the Cleanup Lab job.

4. Right-click and select Start Job at Step…

5. After the job is complete, close the Start Jobs dialog box.

6. Close any open applications.

3.1.7 Lab Complete!

You have successfully created a backup set and used it to recover SQL Server databases.


Date post:	30-Aug-2018
Category:	Documents
Upload:	phamdat
View:	227 times
Download:	0 times

Demo Lab Guide Compellent - Amazon S3 · Demo Lab Guide – Compellent Replay Manager SQL Server...

Documents