Disk-to-Disk Backup Solution

(1)

Disk-to-Disk Backup Solution

Introduction: The Data Protection Challenge ...2

The Solution: Disk-to-Disk Backup with Snap Server 4500 ...2

Test Configuration ...3

Configuration Details ...3

1. Application Server Information ...3

2. Snap Server 4500 Information ...3

3. Ethernet Switch Information ...4

4. Application (Software) Information ...4

PART 1: Snap Server 4500 Setup ...4

Connecting to the Snap Server for the First Time ...4

To Connect to a Snap Server Using the Server Name ...4

To Connect to a Snap Server Using Snap Server Manager ...5

Creating the iSCSI Target on Snap Server 4500 for Backup ....5

PART 2: Application Server Setup ...7

Install Microsoft iSCSI Initiator ...7

Connecting to iSCSI Disks ...7

PART 3: Backup/Restore Application Setup ...9

CommVault QiNetix Installation and Configuration ...9

Library and Device Configuration ...16

New Storage Policy Creation ...19

Backup Procedures ...22

Restore Procedures ...25

Solutions Tests ...27

Performance Results ...27

Summary ...27

Using CommVault QiNetix v5.0.0 with Adaptec Snap Server 4500

Storage Array

In this configuration, each application server also has the backup server software installed, enabling it to back up the data from its primary storage (Fibre Channel storage in this example) to the nearline storage (iSCSI storage from Snap Server 4500 in this example). There is no need for a dedicated backup server.

Testing was performed using only one Ethernet port on the Snap Server 4500. However, with both Ethernet ports used, the performance was relatively consistent.

In order to use both Ethernet ports (Eth1 and Eth2) for iSCSI disks, they must have active connections and legal IP addresses configured when the first iSCSI disk is created. If only one Ethernet port was properly configured and connected when the first iSCSI disk is created, then all iSCSI disks will be available only on that port.

Configuration Details

1. Application Server Information (4 identical servers) Mfg: Super Micro

Model: X5DPR-1G2+

Processor: Intel Xeon 1.6 GHz Memory: 1GB

BIOS: Phoenix 4.0 R6.0 X5DPR-1G2+/X5DPR-8G2+ Rev 1.4c OS Version: Windows 2003 Enterprise Server

iSCSI Initiator: Microsoft iSCSI initiator v1.05a 2 embedded gigabit Ethernet ports

2. Snap Server 4500 Information Mfg: Adaptec

Brand and Model: Snap Server 4500 Boot OS Version: GuardianOS 3.1.079 CPU: P4 2.4GHz

Memory RAM: 503MB

RAID: RAID5 of 4 IDE ATA disks

Disk Drive Vendor and Model: WDC-WD2500BB-50 Disk Drive Capacity: 250GB

Number of Disk Drives: 4

APPLICATION SERVER 1

LOCAL STORAGE Gb Ethernet MS iSCSI v1.05a

GigE SWITCH

3COM Super Stack3 3C16468

SNAP SERVER 4500

(4)

Eth1: 1000Mbps / Full duplex: IP address=x.x.x.x Eth2: 1000Mbps / Full duplex (Not used for this test)

4x 100GB iSCSI disks with each server only uses 1x 100GB iSCSI disk 3. Ethernet Switch Information

Vendor/Model: 3Com SuperStack 3 3C16468 Ethernet speed: 6x 100/1000T ports Firmware version: 2.55

4. Backup/Restore Application Information Vendor: CommVault Systems

Product: QiNetix Galaxy v 5.0.0

Part 1: Snap Server 4500 Setup

Connecting to the Snap Server for the First Time

Snap Servers are preset to acquire an IP address from a DHCP server. If no DHCP server is found on the network, the Snap Server defaults to an IP address of 10.10.10.10, and you may not be able to see the server on your network. You can discover a Snap Server using either the default server name or the Snap Server Manager (SSM) utility. Use the server name method if you are installing one Snap Server on the network. Use SSM if you are installing two or more Snap Servers, or if your network does not have a DHCP server.

To Connect to a Snap Server Using the Server Name

This procedure requires that name resolution services (via WINS or an equivalent service) be operational.

1. Find the server name. The default server name is “Snapnnnnnn,” where “nnnnnn” is the server number. For example, the name of a Snap Server with a server number of 610019 is Snap610019. The server number is a unique, numeric string that appears on a label affixed to the inside of your Snap Server. To view the label, remove the front bezel.

2. In a web browser, enter the following URL: http://Snapnnnnnn (where nnnnnn is the server number) 3. Press Enter. The Web View screen opens.

4. Log into the Administration Tool and complete the Initial Setup Wizard. Click the “Administration” link and in the login dialog box, enter “admin” as the user name and “admin” as the password, and then click “OKЃ. Com- plete the setup procedure using the Initial Setup Wizard.

(5)

To Connect to a Snap Server Using Snap Server Manager

Snap Server Manager (SSM) is a Java-based, platform-independent, multi-server administrative application that runs on all major platforms. Administrators can discover, configure, and monitor all local and remote GuardianOS Snap Servers from the SSM interface. You can download and install Snap Server Manager using the “Install.html”

file found on your Snap Server User CD. Be sure to install SSM on a computer residing on the same network segment as your Snap Server(s).

1. Launch SSM. SSM discovers all Snap Servers on its local network segment and displays their server names, IP addresses, and other status information in the main console.

Tip: To distinguish multiple Snap Servers you may need to find their default server names as explained in the previous procedure.

2. Launch a server’s Administration Tool. In the Snap Server Manager console, right-click a server name and select

“Launch Web Administration”.

3. Log into the Administration Tool and complete the Initial Setup Wizard. Click the “Administration” link, and in the login dialog box, enter “admin” as the user name and “admin” as the password, and then click “OK”. The first screen of the Initial Setup Wizard opens.

Please refer to the Snap Server 4500’s Quick Start Guide and User CD if you need more information.

Creating the iSCSI Target on Snap Server 4500 for Backup

1. Enter the Snap Server’s IP address or server name in the browser and press “Enter”. Then enter the appropriate User Name and Password to log into the Snap Server.

(6)

2. Click “Storage” option.

3. Click “iSCSI” option.

4. Click “Create iSCSI Disk” option.

(7)

5. Enter a name and desired capacity for the iSCSI disk. Click “Continue” to create an iSCSI

Note: There is no ACL (Access Control List) for mapping iSCSI disks to their associated initiators on the servers. There- fore, all created iSCSI disks are accessible by ALL initiators.

Repeat the above steps to create additional iSCSI disks for all application servers.

Part 2: Application Server Setup Install Microsoft iSCSI Initiator

Please refer to Readme file of the Microsoft iSCSI Initiator software version 1.05a to install the iSCSI Initiator software on all application servers before performing the following tests.

Documentation and iSCSI software updates can be found at Microsoft’s support site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a-15d6-4585-b385-befd1319f825&Dis- playLang=en

Connecting to iSCSI Disks

1. Launch “Microsoft iSCSI Initiator” by double clicking on the “Microsoft iSCSI Initiator” icon on the desktop.

Then click “Add” in the “Target Portals” window.

(8)

2. Enter the Snap Server’s IP address and click “OK.”

3. Click the “Available Targets” tab. Select the appropriate target(s) you want to connect to and then click the

“Logon” button.

4. Check the “Automatically restore this connection when the system reboots” box and click “OK” to commit changes.

(9)

5. Open the “Computer Management” control panel and click “Disk Management” under the “Storage” option.

Verify that your configured iSCSI disk is detected and accessible by Windows Disk Management. Create a partition and format the iSCSI disk with NTFS file system.

Tip: Since Microsoft iSCSI initiator software v1.05a does not support dynamic disks, the iSCSI disk should be set as a basic disk and not upgraded to a “Dynamic Disk.”

Repeat the above steps on all application servers so they each have their own iSCSI disk connected, partitioned and formatted.

Part 3: Backup/Restore Application Setup CommVault QiNetix Installation and Configuration The following CDs are required to install QiNetix:

1. QiNetix Software Release 5.0.0 CD (Installs the core QiNetix application. Note that the Installation Wizard refers to this CD as the “Galaxy Installation CD.”)

2. QiNetix CommServe Database Release 5.0.0 CD (Installs MS SQL packages. Note that the Installation Wizard refers to this CD as the “Galaxy Database CD.”)

Microsoft SQL Server + Sp3 is required when installing CommVault QiNetix v 5.0.0. This software application CD is shipped with the QiNetix package and is labeled “QiNetix CommServe Database Release 5.0.0”

1. Insert “CommVault QiNetix v5.0.0” CD. The Main Installation menu will auto-launch. Click “Install QiNetix Software on this computer” then click “Next.”

(10)

2. Click “Next” on “Welcome” screen.

3. Click “OK” on virus scanning software warning dialog box.

4. Review the “Licensing Agreement” and click “Next” to continue.

5. Select following platforms from the “Select Platforms” screen:

• CommServe // Basic product

• CommCell Console for Java // Java console for CommVault QiNetix

• Java Runtime Environment 1.4 // Java Runtime engine

• MediaAgent // Media agent for server

• iDataAgent, iDA for Windows Server 2003 // Data Agent for server Click “Next” to continue.

6. Click “Yes” to install Microsoft SQL Server.

7. At the CommVault Installer screen, you will be asked to select the drive and directory from which you want to install the Microsoft SQL Server. Verify that the correct CD-ROM drive letter is selected. The Installation Wizard will prompt you to swap in the correct Installation CD and automatically locate the correct installation directory in the subsequent steps.

(Note: You will need to swap the “QiNetix Software Release 5.0.0 CD” and “QiNetix CommServe Database Release 5.0.0 CD” multiple times during the installation process if only one CD-ROM drive is installed.)

(11)

8. If your system has only one CD-ROM drive installed, you will get the following prompt to insert the “Galaxy Database CD.” Remove the QiNetix Software CD and insert the QiNetix CommServe Database CD. Press “OK” to continue with the installation.

9. Click “Continue.”

10. Enter password for SQL user.

(12)

11. When MSSQL installation is complete, re-insert the Galaxy Installation CD (“QiNetix Software Release 5.0.0 CD”) when dialog box shown appears. Click “OK” to continue.

12. You will then be prompted to select where to install the MSSQL Service Pack3 package from at the next screen.

Verify that the correct CD-ROM drive letter is selected and click “Next” to proceed with installation.

13. You will be prompted to insert the Galaxy Database CD. Insert the “QiNetix CommServe Database Release 5.0.0 CD” and click “OK” to continue.

14. Click “Yes” on “JRE 1.4.1_02” installation screen. Click “Yes” on “License Agreement” screen.

15. Select “Typical” setup at the “InstallShield Wizard” screen.

16. Select CommVault Galaxy Destination Path. Click “Next.”

(13)

17. Select CommVault Database path. (The default “Typical” was used for this test). Click “Next.”

18. Enter the CommServe Name on following screen. (Note: This test was performed on a local system so the client name and server are in same system). Click “Next.”

19. For the “Express Recovery Path” field, select a directory where you want to store the Express recovery backup files. Click “Next” to continue.

(14)

20. Select “No” on “Firewall Configuration” screen. Click “Next.”

21. The CommVault Galaxy installation is required to stop Removable Storage services in order for the Galaxy Media Agent to function correctly. Select “Yes” then click “Next” to continue.

22. Select Galaxy Index Cache path. Click “Next.”

23. Select Galaxy Job Result Path. Click “Next.”

24. The “QiNetix Installation Summary” screen will appear. If you wish to make any changes, click the “Back” button to the appropriate screens to make your changes. When you are satisfied with your installation choices, click

“Next” to proceed.

25. At the “License Path” screen, you must enter the correct location of the License File (on the CommVault floppy disk). Insert the provided “Installation Pilot License Key” floppy disk and click “Next” to continue.

26. The next screen will prompt you to enter a CommCell username and password. The default username is “cvad- min,” but you may choose any name. Enter the desired password for the username you created and click “Next” to continue.

(15)

27. The next screen will prompt you to enter in a “Media Password.” Entering a password will ensure that unau- thorized users will not have access to Galaxy media. Click “Next” to continue.

28. Note: CommCell Plus is a feature that allows you to select a particular CommServe module when you start the Java CommCell Console. To use CommCell Plus, the CommServe module must be installed on a Windows 2000 or Windows Server 2003 computer that is a member of an Active Directory-enabled domain. If your application server is a member of Windows 2000 Active Directory enable domain, you may need to run following command to make it a part of CommCell Plus:

RegEvMgrsWithAD –c “application server name”

When prompted by the “CommVault Installer Warning” dialog box, click “OK” to continue.

(16)

29. The next screen will ask if you want to install the “cvmminst” package, which is intended for the configuration of magnetic libraries. For the time being, click “No” to continue with installation. (Configuration of magnetic libraries will be discussed in the “Library and Device Configuration” section.)

30. Click “Finish” to complete CommVault setup. Repeat the above steps on each Application server to install CommVault QiNetix.

Library and Device Configuration

Before performing backup and restore jobs with an iSCSI disk/target, you must configure the desired iSCSI/target using the QiNetix “Library and Device Configuration” utility.

1. Launch “CommCell Console for Java GUI” from the Start menu а Programs а CommVault QiNetix а Galaxy.

2. Enter user name and password to connect to the “CommCell” server.

(17)

3. Open “Library & Device Configuration” from the “Tools” menu.

(Note: The Media agent must be selected before configuring the library.) 4. Select Media agent and click “Add.” Click “OK.”

5. Click “General” tab, select “Add” from drop-down menu, then select “Magnetic Library.”

(18)

6. Enter the alias name for “Magnetic Library.” Click “OK.”

7. Enter the library mount path (Note: K:\ is iSCSI disk volume from the Snap Server 4500). Click “OK”.

8. The Library configuration is complete. Close “Library and Device Configuration Screen.” Repeat the above steps to configure a magnetic library on each Application server.

(19)

New Storage Policies Creation

1. Right click on “Storage Policies” from “CommCell Browser” and select “New Storage Policy.”

2. When “Galaxy Create Storage Policy Wizard” screen appears, click “Next.”

3. Select the desired Storage Policy Type and click “Next” to continue. In our example, we selected the default

“iDataAgent Backup (Standard)” setting.

(20)

4. Enter storage policy name. Click “Next.”

5. Enter primary copy name. Click “Next.”

6. Select default library to which you wish to associate this primary copy. Click “Next.”

(21)

7. Select Media agent. Click “Next.”

8. Enter number of streams for storage policy (Note: 5 streams used in this test). Click “Next.”

9. Click “Finish” to create storage policy. Repeat the above steps to set the storage policy on each application server.

(22)

Backup Procedures

1. Right click on “iDA File System” from “Client Computers.” Select “New Backup Set” from drop-down menu.

2. Enter the new backup set name. Click “Add.”

3. Enter the subclient name for new backup set from “General” menu.

(23)

4. Enter the backup source in the “Content” menu by clicking “Browse.” (Note: “E:\project data” was used as the backup source in this test).

5. Select storage policy name for new backup set from “Data Storage Policy” menu of “Storage Device” menu.

6. Select software compression on/off from “Software Compression” menu (default is “Off ”).

(24)

7. Note: All subclients must have the storage policy assigned to create a new backup set. Select storage policies for all subclients, including the “default” and “System State” subclients.

8. Click “OK.”

9. Click “Yes” when dialog boxes shown appear.

(25)

10. Set the backup schedule and backup type. Click “OK” to run the backup job.

Restore Procedures

1. Right click on backup set “Daily_Full” from “iDA File System,” then select “Restore” from drop-down menu.

(Note: “Daily_Full” is the backup set used for this test.)

2. Enter the starting path of the data you wish to restore and click “OK.” (Note: “E:\Project data” is starting path for this test.)

3. Select “Destination Computer” and “Destination folder” from “Restore Options” screen. Click “OK” to begin restore job.

(26)

The “Restore Progress” screen below will appear.

(27)

All other trademarks used are owned by their respective owners.

Information supplied by Adaptec Inc., is believed to be accurate and reliable at the time of printing, but Adaptec Inc., assumes no responsibility for any errors that may appear in this document.

Adaptec, Inc., reserves the right, without notice, to make changes in product design or specifications. Information is subject to change without notice.

P/N: 906744-011 Printed in USA 03/05 3692_1.3 Adaptec, Inc.

691 South Milpitas Boulevard Milpitas, California 95035 Tel: (408) 945-8600 Fax: (408) 262-2533

Literature Requests:

US and Canada: 1 (800) 442-7274 or (408) 957-7274 World Wide Web: http://www.adaptec.com

Pre-Sales Support: US and Canada: 1 (800) 442-7274 or (408) 957-7274 Pre-Sales Support: Europe: Tel: (32) 2-352-34-11 or Fax: (32) 2-352-34-00

Solution Tests

1. General Backup/Restore Test

In testing of disk-to-disk backup operations, the combination of the Snap Server 4500 and CommVault QiNetix software proved an easy and effective backup solution with simple, rapid restore capabilities for data recovery.

Conclusion: Using the Snap Server 4500 with CommVault’s QiNetix application is a cost-effective solution for pro- tecting business-critical data.

2. Backup Performance Test

In the performance test, the four application servers all ran the CommVault QiNetix application concurrently to back up data from their associated primary storage to the Snap Server 4500. The following criteria were used in our performance measurement test:

1. Source of the backup test on each application server consists of 20.1GB data of directories of large and small files.

2. Each server was synchronized to the same time.

3. Scheduled backup jobs on all four servers were run concurrently.

4. Three scheduled backup jobs using the same source on each server were run and the average used for the performance result.

To achieve maximum performance, the Verify and Compression options for the backup jobs were set to “Off.”

Performance Results:

Summary

In testing of typical backup/restore operations, the combination of the Adaptec Snap Server 4500 storage array and CommVault QiNetix application provide a practical, cost-effective, and easily deployed solution for handling day- to-day backup/restore tasks. In our tests, the Adaptec Snap Server and CommVault QiNetix configuration proved an effective way for companies to satisfy their data protection strategies of today…and those of tomorrow.

System(s) Throughput GB/hr

Test 1 Test 2 Test 3 Average

S1 5.08 5.08 5.08 5.08

S2 4.98 4.96 4.96 4.97

S3 5.06 5.08 5.08 5.07

S4 4.98 4.98 4.98 4.98

Total 20.10 20.10 20.10 20.10

Disk-to-Disk Backup Solution