nbu detail design - ver 1

Introducon to T S3500 T ape Li b ar y ..........................................................................................26 r 1.5.1 1.5.2 1.6 2 2.1 Components of the library .................................................................................................. 30 Tape Drives..........................................................................................................................32

Advanced Library Management System .....................................................................................32 Introducing Bare Metal Restore.................................................................................................. 33 BMR Boot Servers ...............................................................................................................34 Protecting clients ................................................................................................................37

BMR Planning...................................................................................................................................... 33 2.1.1 2.1.2

3

Different Backup Methods..................................................................................................................38 3.1 3.2 3.3 3.4 Backups based on LAN ................................................................................................................38 SAN style backups via SAN Client................................................................................................40 SAN Configuration...............................................................................................................42 SAN style backups via SAN Media Server ...................................................................................43 Snapshot Backup.........................................................................................................................44 EMC CLARiiON Software Requirements.............................................................................. 45

3.2.1

3.4.1

5

99

3.4.2 3.5 3.5.1 3.5.2 3.5.3 3.6 3.7 3.8 3.6.1

Instant Recovery .................................................................................................................46 Configuring a backup policy for an Oracle database ..........................................................46 Adding backup selections to an Oracle policy .................................................................... 47 NetBackup for Oracle with Snapshot Client........................................................................ 48 Configuring a backup policy for an SQL Server database ...................................................48

NetBackup for Oracle..................................................................................................................46

NetBackup for SQL Server........................................................................................................... 48 VMware Backup ..........................................................................................................................49 Active Directory Backup.............................................................................................................. 51 Backup Policy for Active Directory ......................................................................................52 Requirement for Active Directory Granular Recovery ........................................................52

3.8.1 3.8.2 4 4.1

MCI Backup Requirements and Fulfillments.......................................................................................53 OS & Application Files .................................................................................................................53 OS & Application Reside On Local Disks.............................................................................. 53 OS & Application Reside On SAN Volumes ......................................................................... 61 SenSage Servers ..................................................................................................................66 Rating and Mediation Servers.............................................................................................69 Other Application Servers ................................................................................................... 71 Oracle Databases ................................................................................................................74 SQL Server Databases ......................................................................................................... 77 MYSQL Databases ...............................................................................................................78 4.1.1 4.1.2 4.2 4.2.1 4.2.2 4.2.3 4.3 4.3.1 4.3.2 4.3.3 4.4

Application Data Files..................................................................................................................64

Databases.................................................................................................................................... 74

Active Directory ..........................................................................................................................78 Licensing Vault ............................................................................................................................81 Vaulting Strategy.........................................................................................................................81 Vault Process...............................................................................................................................82 Vault Reports ..............................................................................................................................85

5

NetBackup Vault ................................................................................................................................. 80 5.1 5.2 5.3 5.4

Page of

6

99

5.4.1 5.4.2 5.4.3 6 6.1 6.2

Reports for media going offsite ..........................................................................................86 Reports for media coming on-site ......................................................................................87 Inventory reports ................................................................................................................87

Configuring storage.............................................................................................................................88 Configuring disk storage ............................................................................................................. 89 Configuring Tape Library............................................................................................................. 90 Media sharing .....................................................................................................................90 Naming Tape Drives ............................................................................................................ 91 Bar Code Label ....................................................................................................................92 Tape Volumes......................................................................................................................93 Volume pools ......................................................................................................................93 Tape Drive Cleaning ............................................................................................................ 95

6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 7 7.1 7.2 7.3

Routine Operation ..............................................................................................................................95 NetBackup Catalog Backup ......................................................................................................... 95 Catalog Archiving ........................................................................................................................96 Monitoring and Reporting .......................................................................................................... 97 Activity Monitor ..................................................................................................................97 Auditing Manager ...............................................................................................................98 Reports utility......................................................................................................................98

7.3.1 7.3.2 7.3.3

Page of

7

99

Table 1: Hardware specicaons o e f ach o the N t B f e ackup ser ver s .........................................................14 Table 2: Client License Tiers........................................................................................................................18 Table 3: Server List with Standard Client License .......................................................................................22 Table 4: Server list with Standard Client + APP & DB Agent ....................................................................... 23 Table 5: Server List with Enterprise Client + APP & DB Agent Tier 2 ..........................................................23 Table 6: Server List with Enterprise Client Tier2.........................................................................................25 Table 7: Server List with Enterprise Client + APP & DB Agent Tier 3 ..........................................................26 Table 8: Server List with Enterprise Client + APP & DB Agent Tier 4 ..........................................................26 Table 9-TS3500 Tape Library Frame Types ................................................................................................. 28 Table 10- TS1040 Tape Drive Specicaon ................................................................................................. 32 Table 11: List of Required BMR Boot Servers .............................................................................................35 Table 12: BMR Boot Servers Specicaon .................................................................................................. 36 Table 13: EMC CLARiiON Snapshot Methods..............................................................................................44 Table 14: EMC Snapshot Sowa r e R equi rem nt ........................................................................................45 e Table 15: Oracle Backup Levels...................................................................................................................47 Table 16: MS-SQL Backup Levels.................................................................................................................49 Table 17: Required NFS Components ......................................................................................................... 53 Table 18: Policy Ar i b es fo O & A B ut r S PP ackup .......................................................................................54 Table 19: Schedule A ributes for OS & APP Backup ..................................................................................55 Table 20: Client List for OS & APP Backup Policies .....................................................................................58 Table 21: Backup Volume Calculaon - File System ....................................................................................59 Table 22: Transfer Rates- Different Network Technologies........................................................................ 59 Table 23: Summary Backup Policy- OS & APP.............................................................................................60 Table 24: O-Site Tape Requirement-OS & APP Backup ............................................................................ 60 Table 25: Disk Storage Requirement- OS & APP Backup ............................................................................ 60 Table 26: Storage Group Denion - OS & APP Backup .............................................................................. 61 Table 27: List of SAN Media Servers ........................................................................................................... 61 Table 28: Backup Policy Summary- File System for Boot ON SAN servers .................................................62 Table 29: Policy Ar i b es - OS & APP Backup-Boot on SAN Servers .........................................................62 ut Table 30: Schedule Ar i b es - OS & APP Backup-Boot on SAN Servers ....................................................62 ut Table 31: Client List- FS Backup for Boot on SAN Servers........................................................................... 63 Table 32: Disk Storage Requirement- OS & APP Boot on SAN.................................................................... 63 Table 33: O-Site Tape Requirement- OS & APP BootOnSAN.................................................................... 63 Table 34: STUG Denion - OS & APP Backup BootOnSAN......................................................................... 64 Table 35: Applicaon D t a F le o S ver s ................................................................................................65 a i s n er

Page of

8

99

Table 36: SenSage Backup Requirement .................................................................................................... 66 Table 37: SenSage Backup Volume Calculaon ..........................................................................................67 Table 38: Backup Volume- SenSage Backup ...............................................................................................67 Table 39: Tape Requirement- SenSage Backup ..........................................................................................67 Table 40: Backup Trac Rate-SenSage Servers..........................................................................................67 Table 41: Tape drive data transfer rate ...................................................................................................... 68 Table 42: Backup Rate- arch-sls Servers ..................................................................................................... 68 Table 43: Policy Denion - SenSage Backup ..............................................................................................68 Table 44: Schedule Denion - SenSage Backup.........................................................................................69 ..................................................................................70 Table 46: Policy Ar i b es - Mediation & Rating Servers ........................................................................... 70 ut Table 47: Schedule Ar i b es - Mediation & Rating Servers ...................................................................... 71 ut Table 48: Storage Requirement Summary.................................................................................................. 71 Table 49: Client List-1.................................................................................................................................. 72 Table 50: Client List-2.................................................................................................................................. 72 Table 51: Policy for other servers ...............................................................................................................72 Table 52: Schedule for other servers .......................................................................................................... 72 Table 53: Policy Summary- Other Servers................................................................................................... 73 Table 54: Disk Space Requirement ............................................................................................................. 73 Table 55: Tape Requirement.......................................................................................................................73 Table 56: Storage Units on Disk ..................................................................................................................73 Table 57: Oracle Databases.........................................................................................................................74 Table 58: Esm t ed si ze o O acl e D t abases ............................................................................................75 a f r a Table 59: Oracle Backup Summary-Large Size Database............................................................................ 76 Table 60: Oracle Backup Summary- Normal Size Database........................................................................ 76 Table 61: Storage Requirement- Large Size Oracle DB ...............................................................................77 Table 62: Storage Requirement- Normal Size Oracle DB............................................................................ 77 Table 63: MS-SQL Server Database............................................................................................................. 77 Table 64: Policy Ar i b es - MSSQL Server ................................................................................................. 77 ut Table 65: Schedule Ar i b es - MSSQL Server............................................................................................78 ut Table 66: MYSQL Database List...................................................................................................................78 ...............................................................................................79 Table 68: Acv e D rector y S i chedul e A i bu es .........................................................................................79 r t Table 69: Osite Volume Pools...................................................................................................................83 Table 70: Vault Catalog Backup ..................................................................................................................83 Table 71: Picking List for Robot report ....................................................................................................... 86 Table 72: Disk Storage Conguraon .......................................................................................................... 90 Table 73: Disk Storage Space Allocaon ..................................................................................................... 90

Page of

9

99

Table 74: Tape Drives Naming ....................................................................................................................92 Table 75: Media ID Generaon R e ........................................................................................................... 93 ul Table 76: Default Volume Pools..................................................................................................................94 Table 77: Volume Pools to be dened........................................................................................................ 94

Figure 1: NetBackup storage domain.......................................................................................................... 13 Figure 2- TS3500 Tape Library Frame Posion ...........................................................................................29 Figure 3: Components of the IBM System Storage TS3500 ........................................................................ 31 Figure 4: Sample BMR Network .................................................................................................................34 Figure 5: BMR Networking Topology .......................................................................................................... 35 Figure 6: Backup Trac Flow- LAN Backup................................................................................................. 39 Figure 7: Restore Trac Flow through LAN................................................................................................40 Figure 8: Backup Trac Flow- SAN Client................................................................................................... 41 Figure 9: Restore Trac Flow- SAN Clients ................................................................................................42 Figure 10: Backup Trac Flow-SAN Media Server .....................................................................................43 Figure 11: Snapshot Process .......................................................................................................................45 Figure 12: Backup Trac Flow- VMware backup .......................................................................................50 Figure 13: VMware Restore Trac Flow .................................................................................................... 51 Figure 14: Relaons hi p o V t a o her N t B s f aul nd t e ackup com onent s ........................................................80 p Figure 15: Vault Eject Interface...................................................................................................................84

Page of

10

99

Having sustainable operation environment is vital of importance for every business. In an environment like MCI Datacenter which hosts huge amount of valuable information and data; every minutes of downtime or service interrupt means losing business values which are harmful to the entire operation of the operator. To guarantee sustainable operation in such kind of environments a wide variety of technologies and techniques are used to ensure the high availability and data protection. The architecture of MCI Datacenter includes redundancy in different layers from entire I/O system to servers and applications by means of clustering or using Mirrors and RAIDs. These are building blocks for highly available data access, but not for the entire data protection solution. Mirrored and RAID arrays store blocks of binary data reliably, regardless of its meaning. It must be noted that a RAID array stores incorrect data just as reliably as it stores correct data. Mirroring and RAID do not protect against data corruption due to human errors or application faults. A regular backup with an enterprise backup and recovery application offers the only realistic protection against these causes of data loss. So the primary goals of the backup are to be able to do the following: Enable normal services to resume as quickly as is physically possible after any system component failure or application error. Enable data to be delivered to where it is needed, when it is needed. Meet the regulatory and business data retention requirements. Meet recovery goals, and in the event of a disaster, return the business to the required operational level. To achieve these goals, the backup and recovery solution must be able to do the following: Make copies of all the data, regardless of the type or structure or platform upon which it is stored, or application from which it is born. Manage the media that contain these copies, and in the case of tape, track the media regardless of the number or location. Provide the ability to make additional copies of the data. Scale as the enterprise scales, so that the technology can remain cost effective.Page of

11

99

In the rest of this document well try to explain the backup and recovery architecture for MCI Tohid Datacenter which is designed to achieve mentioned goals as above. There are different types of Data and Data Stores available at MCI Tohid Datacenter which should be backed up and protected by centralized backup and recovery solution. According to the high level design these Data types can be categorized into two parts: 1. Data and files which belong to OS systems. OS systems which are used in this DC include: Solaris 10, RedHat Enterprise Linux 5, Windows 2008 and Windows 2003. 2. Application Data. This type of Data includes: a. Data belong to fundamental and management services like DNS, Active Directory, NMS and etc. b. Data belong to business applications like Billing, Automation System and Financial Systems which are business critical data. OS system files are stored on DAS (Direct Attached Storage) for entry-level and mid-range servers, for High-End servers these Data are stored on SAN (Storage Area Network). Application Data which include fundamental, management and security services are stored on DAS; in this case Data files dont occupy too much space and they are mostly reside on EntryLevel servers. The Data which belong to Web Applications and Application Software are also stored on DAS. These types of Data dont need high capacity and can be stored on local disks. The most important Data which are business critical Data are those which are related to MCI business. These kinds of Data are stored on Clustered Databases and SAN technology is used as the storage system. Besides the Data that mentioned above, there is another kind of Data; which has passed the first phase of their life cycle and they are stored using NAS technology; CDRs and event logs are the most important of this type. So the backup and recovery solution should cover all mentioned types of Data which are stored on different locations including SAN, NAS and DAS. Also it should be able to backup different OS types and Databases without interrupting the system operation.

Page

of

12

99

As virtualization is used inside MCI Datacenter to lower the CAPEX for Hardware and minimize the OPEX for the servers which require less resources; the backup solution should be able to take backup of Virtual Machines as well as the capability to take backup of different OS types. This document will describe the methods, topologies and techniques that are used by the backup solution to cover any part of the requirements as mentioned on the above. The first chapter which is the introduction will give us an overview of backup solution and specific features and functions of NetBackup. Well also have an introduction about the IBM tape library as the main storage system of our backup and recovery solution. Chapter 2 will explain one of the most important features of NetBackup as BMR. Chapter 3 will explain different backup methods that will be used to create backup images for different types of data. In chapter 4, well check the backup requirements specified by relevant MCI system administrators; and we plan to meet their requirements. Chapter 5 is about another option of NetBackup named Vault which is mostly used for off-site backup management. Chapter 6 is about the configuration of storage systems that will be used as target for backup images including the CX4-240 as disk storage and IBM TS3500 as tape storage. The last chapter will explain some major routine jobs for the operation of backup system.

NetBackup provides a complete, flexible data protection solution for a variety of platforms. The platforms include Microsoft Windows, UNIX, Linux, and NetWare systems. NetBackup administrators can set up periodic or calendar-based schedules to perform automatic, unattended backups for clients across a network. An administrator can carefully schedule backups to achieve systematic and complete backups over a period of time, and optimize network traffic during off-peak hours. NetBackup includes both the server and the client software as follows: Server software resides on the computer that manages the storage devices. Client software resides on computers that contain data to back up. (Servers also contain client software and can be backed up.) Figure 1 shows an example of a NetBackup storage domain.

Page

of

13

99

NetBackup accommodates multiple servers that work together under the administrative control of one NetBackup master server in the following ways: The master server manages backups, archives, and restores. The master server is responsible for media and device selection for NetBackup. Typically, the master server contains the NetBackup catalog. The catalog contains the internal databases that contain information about NetBackup backups and configuration. Media servers provide additional storage by allowing NetBackup to use the storage devices that are attached to them. Media servers can also increase performance by distributing the network load. During a backup or archive, the client sends backup data across the network to a NetBackup server. The NetBackup server manages the type of storage that is specified in the backup policy. During a restore, users can browse, and then select the files and directories to recover. NetBackup finds the selected files and directories and restores them to the disk on the client.

Page

of

14

99

For MCI Tohid Datacenter, NetBackup Enterprise solution will be deployed, which is composed of three main parts: Master Server, Media Server and client. Beside these three main roles well have another 3 servers as BMR boot servers which are used for the implementation of BMR, an important option of NetBackup solution. The installation of these BMR boot servers and their functionality will be covered later under BMR planning section. The following table lists the hardware specifications of each of the NetBackup servers.

1 2 3 4 5 6 7 8

mstr-nbkp-srv1 mstr-nbkp-srv2 media-nbkp-srv1 media-nbkp-srv2 linux-bmr-srv win-bmr-srv solaris-bmr-srv vm-bkphost-srv

VERITAS NetBackup Master Server Backup Management Server VERITAS NetBackup Master Server Backup Management Server Veritas NetBackup Media Server LAN Backup Management Server Veritas NetBackup Media ServerSAN Backup Management Server Veritas NetBackup Linux BMR Boot Server Veritas NetBackup Windows BMR Boot Server Veritas NetBackup Solaris BMR Boot Server VM Backup Host

DL380 DL380 DL380 DL380 DL380 DL380 T5140 DL380

2 2 2 2 2 2 1 2

Xeon x5570 Xeon x5570 Xeon x5570 Xeon x5570 Xeon x5570 Xeon x5570 Ultra Sparc T2 Plus Xeon x5570

4 4 4 4 4 4 4 4

4 4 8 8 4 4 8 8

2*146GB 2*146GB 2*146GB 2*146GB 2*146GB 2*146GB 2*146GB 2*72GB

1 1 1 1 1 1 1 1

1.5 1.5 18 31 2 2 2 2

1+0 1+0 5 5 5 5 5 5

1.5 1.5

4 4 4 4 4 4 4 4

2 2 2 2 2 2 2 2

2 2 2 2 2 2 2 2

CX4-960 CX4-960 CX4-240 CX4-240 CX4-240 CX4-240 CX4-240 CX4-240

Increase efficiencies by managing all data protection technologies and multiple NetBackup servers and domains from one location. Quickly restore files, emails and other granular items from Microsoft Exchange, SharePoint, and Active Directory and for hypervisors such as VMware and Hyper-V. Benefit from a flexible, three-tiered architecture that scales with the needs of todays growing data centerPage of

15

99

Fully automated and integrated system recovery with NetBackup Bare Metal Restore, built-in replication, and offsite tape management. Flexible encryption technologies for maximum data security while in transit or in media. For the protection of business-critical applications and databases, NetBackup provides application-aware agents that enable hot/online backup, wizard-based configuration, and support for application-specific tools such as Oracle Recovery Manager (RMAN). NetBackup provides a variety of technologies that ensure data can be recovered quickly, even instantly, from anywhere, and with minimal data loss.

Enable quick client restore from a single backup image for decreased application host impact and less network bandwidth Facilitates faster backups and restores since there is no tape device latency, and non-multiplexed backup images can be used for faster recovery Allows a failed backup or recovery job to be resumed from the last checkpoint Writes multiple data streams from one or more clients/servers to a single tape drive for optimum performance Enables the creation of multiple concurrent backup images, each with unique retention attributes, run either simultaneously with or after completion of the primary backup Reduce tape drive configuration time with the automatic generation of drive names and configuration of swapped tape drives Allows multiple NetBackup media servers to actively share a given tape media for write purposes

Page

of

16

99

NetBackup for Microsoft SQL Server delivers comprehensive data protection for SQL Server and SQL Server databases. Features and Benefits: Verify-only restores can be used to verify the SQL contents of a backup image without actually restoring the data Recovers SQL databases to the exact point in time or transaction log mark by rolling forward only the transactions that occurred prior to a user-specified date and time Display of database object properties provides backup and recovery flexibility

The NetBackup Oracle Agent is tightly integrated with the Oracle Recovery Manager (RMAN) to deliver high performance backup and recovery solutions. Features and Benefits: Keep the database online and increase reliability by eliminating manual processes and scripts Tightly integrated with the Oracle Recovery Manager (RMAN) wizard to deliver high performance backup and recovery NetBackup options enhance data protection environments with features listed as below:

Provides all the files and services necessary to perform system recovery, including the ability to perform diskless network booting, temporary OS installation, and disk configuration.

Designed for customers who would prefer to utilize their storage area network (SAN) for backup operations instead of their local area network (LAN). This feature enables LAN-free data protection with high-performance access to shared resources.Page of

17

99

Offloads backup traffic from the LAN and allows for fast backups over the SAN at approximately 150 MB/sec. The SAN client can send data to a variety of NetBackup disk opons a a lo nd l ws us to back up and restore to disk over the SAN. Data is sent to media servers via SCSI commands over the SAN rather than TCP/IP over the LAN to optimize performance.

NetBackup can provide both client and virtual machine (VM) level protection using the vStorage API. This integration enables a single backup of VMware images to deliver granular file-level or full image-level recovery, reducing both the time and cost of VMware data protection.

Share tape drives across NetBackup media servers and a SAN for enhanced performance and deliver a higher return on investment for tape drive and library hardware. Some key benefits include: Minimized backup costsIncrease tape drive utilization and lower the total number of drives required Rapid deploymentGraphical wizards quickly discover and configure shared tape drives Increased fault toleranceAccess additional tape resources in the event of a drive or network failure; includes support for multiple paths to tape drives

Help ensure that tapes being transported offsite cannot be read in the event they are lost, mishandled, or stolen. MSEO provides maximum flexibility and performance by providing parallelized and selectable encryption and compression as well as "set it and forget it" key management. Some key benefits include: : Encrypt within the NetBackup policy, eliminating a separate process or an extra dedicated device to manage Choose what data you want to encrypt and then choose the appropriate compression and encrypon strengt h (A 1 -bit or AES 256-bit) ES 28 Includes support for disk staging to tape, the creation of tape copies for offsite purposes.

Page

of

18

99

There are two different licenses for the clients in NetBackup Enterprise solution. We have to choose the right license type for each host, so the backup operation can run properly. The following is a brief description about each of the license types and relevant license for each host among MCI Tohid Datacenter.

The NetBackup Standard Client contains key features such as bare metal restore, and client encryption. It resides on the same server as the application, database, or files that are being protected and sends data to a NetBackup server for protection or receives data during a recovery.

The NetBackup Enterprise Client contains the functionality of the Standard Client plus many more advanced features that maximize backup performance while potentially reducing impact of backups such as Snapshot client, SAN Client, SAN Media Server, and integrated protection for VMware and Hyper-V environments. NetBackup Enterprise Client is licensed per system (on a tier basis) and is ideal for systems requiring high performance, low impact protection. The tier of the required license is determined by the number of populated processor sockets on the machine as the following table:

Tier 1 Tier 2 Tier 3 Tier 4

1 to 2 processor sockets 3 to 4 processor sockets 5 to 12 processor sockets 13 or more processor sockets

1 processor socket 2 to 3 processor sockets 4 to 7 processor sockets 8 or more processor sockets

According to the above the type of client license on each of the servers will be as following table:

Page

of

19

99

1 2

chrgcrd-web-srv1 chrgcrd-web-srv2

Charge Card Web/Application Server Charge Card Web/Application Server VAS Box Web/Application Server (Pardis) VAS Box Web/Application Server (Pardis)

DL380 DL380

RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 Solaris 10 Solaris 10

2 2

Xeon x5570 Xeon x5570

3 4

vas-app-srv1 vas-app-srv2

T5440 T5440

2 2

UltraSparc T2 Plus UltraSparc T2 Plus

5 6

vas-app-srv3 vas-app-srv4

VAS Box Web/Application Server (Pardis) VAS Box Web/Application Server (Pardis)

T5440 T5440

Solaris 10 Solaris 10

2 2


7 8

portal-web-srv1 portal-web-srv2

Portal Web/Application Server Portal Web/Application Server

T5440 T5440


4 4


9 10

reg-web-srv1 reg-web-srv2

Registration Web/Application Server Registration Web/Application Server

T5440 T5440


4 4


11 12

otp-app-srv1 otp-app-srv2

OTP Application Server OTP Application Server

T5440 T5440


2 2


13 14

otp-rep-srv lms-netmgt-srv

OTP Report Server CiscoWorks LMS Network Management Server

DL380 T5140

Windows 2003 Solaris 10

2 1

Xeon x5570 UltraSparc T2 Plus

15 16

dcnm-netmgt-srv nfc-trfmon-srv

Cisco Data Center Manager Network Management Server Cisco NetFlow Collector Server

DL380 T5140


2 1


17

bluct-trfmon-srv

BlueCoat Traffic Management Server

DL380

Windows 2003

2

Xeon x5570

18

hpic-srvmgt-srv

HP System Insight Manager Servers Management Server

DL380

Windows 2003

1

Xeon x5570

19 20

smc-srvmgt-srv vc-vmmgt-srv1

Sun Management Center Servers Management Server VMware vCenter Virtual Machines Mangement Server

T5140 DL380

Solaris 10 Windows 2003

1 2

UltraSparc T2 Plus Xeon x5570

21 22

vc-vmmgt-srv2 cfm-sanmgt-srv

VMware vCenter Virtual Machines Mangement Server Cisco Fabric Manager SAN Management Server

DL380 DL380

Windows 2003 Windows 2003

2 1


Page

of

20

99

23 24

emc-strgmgt-srv linux-bmr-srv

EMC Storage Systems Management Server Veritas NetBackup Linux BMR Boot Server

DL380 DL380

Windows 2003 RedHat Enterprise Linux 5 Windows 2003 Solaris 10

2 2


25 26

win-bmr-srv solaris-bmr-srv

Veritas NetBackup Windows BMR Boot Server Veritas NetBackup Solaris BMR Boot Server

DL380 T5140

2 1


27 28

vm-bkphost-srv csm-secmgt-srv

VMware vStorage API Backup Host Server Cisco CSM Security Devices Mangement Server

DL380 DL380

Windows 2003 Windows 2003 RedHat Enterprise Linux 5 windows 2008

2 2


29 30

nsm-secmgt-srv msad-dir-srv1

Juniper NSM Security Devices Management Server MicroSoft Active Directory Server

DL380 DL380

2 2


31 32

msad-dir-srv2 ms-ca-srv1

MicroSoft Active Directory Server MicroSoft CA Server

DL380 DL380

windows 2008 windows 2008

2 1


33 34

ms-ca-srv2 ilm-auth-srv1

MicroSoft CA Server MicroSoft ILM Authentication Integration Server

DL380 DL380

windows 2008 Windows 2003

1 2


35 36

ilm-auth-srv2 bigfix-patch-srv

MicroSoft ILM Authentication Integration Server BigFix Patch Management Server

DL380 DL380


2 1


37 38

kasper-av-srv fprot-av-srv

Kaspersky Anti-Virus Management Server FPROT Anti-Virus Management Server

DL380 T5140


1 1


39 40

csa-hipsmgt-srv trpw-chngmgt-srv

Cisco Security Agent HIPS Management Server Tripwire Change Management Server

DL380 DL380

Windows 2003 RedHat Enterprise Linux 5 Windows 2003 Windows 2003

1 1


41 42

sec-scan-srv prtus-isms-srv

Security Scanning and Analysis Server ISMS Implementation Tools Server

DL380 DL380

1 1


43 44

tvl-netview-srv tvl-mon-srv

IBM Tivoli NetView Total Network Management Server IBM Tivoli Monitoring Total Servers and Systems Management Server

DL380 DL380


2 2


45

tvl-ccmdb-srv

IBM Tivoli CCMDB Total Configuration Management Database Server

DL380

Windows 2003

2

Xeon x5570

Page

of

21

99

46

tvl-srm-srv

IBM Tivoli Service Request Management Server IBM Tivoli Application Dependency Discovery Manager Server IBM Tivoli Netcool/OMNIbus Server

DL380

Windows 2003

2

Xeon x5570

47 48

tvl-addm-srv tvl-omnibus-srv

T5140 T5440

Solaris 10 Solaris 10 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 Windows 2003 RedHat Enterprise Linux 5

1 4


49 50

archv-colct-srv1 archv-colct-srv2

SenSage CDR Archiving Collector Server SenSage CDR Archiving Collector Server

DL380 DL380

2 2

X5670 X5670

51 52 53 54 55 56

archv-anlz-srv1 archv-anlz-srv2 snsg-colct-srv1 snsg-anlz-srv1 svn10-bkp-srv ext-dns-srv1 rslv-dns-srv1

SenSage CDR Archiving Analyzer Server SenSage CDR Archiving Analyzer Server SenSage Security Event Warehouse Collector Server SenSage Security Event Warehouse Analyzer Seven 10 Server External DNS Server DNS Resolver Server

DL381 DL382 DL380 DL380 DL380 DL380

2 2 2 2 2 2

X5670 X5670 X5670 X5670 E5620 X5670

57

ext-dns-srv2 rslv-dns-srv2

External DNS Server DNS Resolver Server

DL380

RedHat Enterprise Linux 5

2

X5670

58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74

int-mlgt-srv 1 int-mlgt-srv 2 int-mlst-srv-1 int-mlst-srv-2 emlrt-app-srv1 emlrt-app-srv2 rbt-app-srv1 rbt-app-srv2 rbt-app-srv3 rbt-app-srv4 smsbx-web-srv-1 smsbx-web-srv-2 smsbx-web-srv-3 smsbx-web-srv-4 sms-web-srv mmsbx-app-srv1 mmsbx-app-srv2

Internal Mail GatewayServer Internal Mail GatewayServer Internal Mail Store Server Internal Mail Store Server Send SMS When Receive E-mail Send SMS When Receive E-mail RingBack Tone Server RingBack Tone Server RingBack Tone Server RingBack Tone Server Web Service SMS Box Server 1 (URL Sender) Web Service SMS Box Server 2 (URL Sender) Web Service SMS Box Server 3 (URL Sender) Web Service SMS Box Server 4 (URL Sender) Web SMS Server (SMS Bulk) MMS BOX Applicaon S ver 1 er MMS BOX Applicaon S ver 2 er

DL380 DL380 DL380 DL380 DL380 DL380 T5440 T5440 T5440 T5440 DL380 DL380 DL380 DL380 DL380 T5440 T5440

RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 Solaris 10 Solaris 10

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4

X5670 X5670 X5670 X5670 X5670 X5670 UltraSparc T2 Plus UltraSparc T2 Plus UltraSparc T2 Plus UltraSparc T2 Plus X5670 X5670 X5670 X5670 E5620 UltraSparc T2 Plus UltraSparc T2 Plus

Page

of

22

99

75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95

mmsbx-app-srv3 mmsbx-app-srv4 prvs-app-Srv1 prvs-app-Srv2 prvs-app-Srv3 prvs-app-Srv4 prvs-app-Srv5 prvs-app-Srv6 prvs-Test Bed-Srv prvsrep-App-srv prvsLeg-db-srv cmptel-tst-srv intbill-tst-srv agrt-web-srv3 agrt-web-srv4 BMSP-Vahdat-srv BMSP-Emam-srv BMSP-Yeganehsrv BMSP-Ray-srv BMSP-Resalat-srv BMSP-Ghods-srv bcc-file-srv1 incc-file-srv1 sim-file-srv1 vch-file-srv1 bcc-file-srv2 incc-file-srv2 sim-file-srv2 vch-file-srv2 bcc-mdlwr-srv1 cc-mdlwr-srv1 incc-insvc-srv1 bcc-mdlwr-srv2 cc-mdlwr-srv2 incc-insvc-srv2 bill-web-srv1 intbill-web-srv1 bill-web-srv2 intbill-web-srv2 bill-xlate-srv1 sa-app-srv1 bill-xlate-srv2 sa-app-srv2

MMS BOX Applicaon S ver 3 er MMS BOX Applicaon S ver 4 er Comptel Service Provisioning Primary Server Balancing the Load-1 Comptel Service Provisioning Primary Server Balancing the Load-2 Comptel Service Provisioning Primary Server Balancing the Load-3 Comptel Service Provisioning Primary Server Balancing the Load (Hot Backup)-1 Comptel Service Provisioning Primary Server Balancing the Load (Hot Backup)-2 Comptel Service Provisioning Primary Server Balancing the Load (Hot Backup)-3 Comptel Service Provisioning Test Bed Comptel Service Provisioning Reporting Tool Application Comptel Service Provisioning Legacy Database Server Test Server for Comptel Test Server for Interconnect Aggregate Web Service Server 3 Aggregate Web Service Server 4 Failover Servers, Tehran BMSP Servers Failover Servers, Tehran BMSP Servers Failover Servers, Tehran BMSP Servers Failover Servers, Tehran BMSP Servers Failover Servers, Tehran BMSP Servers Failover Servers, Tehran BMSP Servers BehPardaz BCC File Server BehPardaz IN CC File Server BehPardaz SIM Bank Application (File) Server BehPardaz Voucher Bank Application (File) Server BehPardaz BCC File Server BehPardaz IN CC File Server BehPardaz SIM Bank Application (File) Server BehPardaz Voucher Bank Application (File) Server BehPardaz BCC (BMSP) Middleware Server BehPardaz Customer Care Middleware Application Server BehPardaz IN Service Application Server BehPardaz BCC (BMSP) Middleware Server BehPardaz Customer Care Middleware Application Server BehPardaz IN Service Application Server BehPardaz Billing Web/Application Server Intec Interconnect Billing Web/Application Server BehPardaz Billing Web/Application Server Intec Interconnect Billing Web/Application Server BehPardaz Billing Translator Application Server BehPardaz Service Provisioning Application Server BehPardaz Billing Translator Application Server BehPardaz Service Provisioning Application Server

T5440 T5440 DL580 DL580 DL580 DL580 DL580 DL580 DL580 DL580 DL380 T5140 T5440 DL580 DL580 DL380 DL380 DL380 DL380 DL380 DL380

Solaris 10 Solaris 10 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 Solaris 10 Solaris 10 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 windows 2003 windows 2003 windows 2003 windows 2003 windows 2003 windows 2003

4 4 4 4 2 4 4 2 2 4 1 2 2

UltraSparc T2 Plus UltraSparc T2 Plus X7560 X7560 X7560 X7560 X7560 X7560 X7560 X7560 X5670 ULTRA SPARC T2 Plus ULTRA SPARC T2 Plus

96

DL380

windows 2003

2

X5670

97

DL380

windows 2003

2

X5670

98

DL580

windows 2003

4

X7560

99 100 101 102 103

DL580 T5440 T5440 DL580 DL580

windows 2003 Solaris 10 Solaris 10 Windows 2003 Windows 2003

4 4 4 4 4

X7560 UltraSparc T2 Plus UltraSparc T2 Plus X7560 X7560

Page

of

23

99

1 2

bank-gw-srv1 Rep-Portal-srv1 bank-gw-srv2 Rep-Portal-srv2 tap-in-srv1 tap-out-srv1 int-tap-srv1

Banks Vosooli Gateway Application Server 10.0.0.177 Banks Vosooli Gateway Application Server 10.0.0.177 Tap-In Application/Database Server (Roaming) Tap-Out Application/Database Server (Roaming) Kish & Esfehan Roaming (10.100.0.233)

VM-DL380-1 VM-DL380-2

DL380 DL380


2 2


3

VM-DL580-1

DL580

Windows 2003

2

Xeon x7460

4

tap-in-srv2 tap-out-srv2 int-tap-srv2 sms-bill-srv1 ecare-web-srv1 sms-bill-srv2 ecare-web-srv2

Tap-In Application/Database Server (Roaming) Tap-Out Application/Database Server (Roaming) Kish & Esfehan Roaming (10.100.0.233) SMS Billing Application/Database Server e-care Internet Billing Web/Application SMS Billing Application/Database Server e-care Internet Billing Web/Application

VM-DL580-2

DL580

Windows 2003

2

Xeon x7460

5 6

VM-DL580-1 VM-DL580-2

DL580 DL580


2 2


1 2 3 4

chrgcrd-db-srv1 chrgcrd-db-srv2 otp-db-srv1 otp-db-srv2

Charge Card Database Server Charge Card Database Server OTP Database Server OTP Database Server

chrgcrd-db-DL380-1 chrgcrd-db-DL380-2 otp-db-T5440-1 otp-db-T5440-2

DL380 DL380 T5440 T5440

RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 Solaris 10 Solaris 10

2 2 2 2

Xeon x5570 Xeon x5570 UltraSparc T2 Plus UltraSparc T2 Plus

Page

of

24

99

1

edch-ftp-srv1 EDCH FTP Server int-ftp-srv1 Internal FTP Server edch-ftp-srv2 EDCH FTP Server int-ftp-srv2 Internal FTP Server SenSage Data Center Events Data Warehouse SLS Server SenSage Data Center Events Data Warehouse SLS Server SenSage Data Center Events Data Warehouse SLS Server SenSage Data Center Events Data Warehouse SLS Server SenSage Data Center Events Data Warehouse SLS Server

LDOM-T5440-1

T5440

Solaris 10

3

UltraSparc T2 Plus

2

LDOM-T5440-2

T5440

Solaris 10 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise Linux 5 RedHat Enterprise

3

UltraSparc T2 Plus

3 snsg-log-srv1

snsg-log-rx2660-1

rx2660

2 Intel Itanium 9140M

4 snsg-log-srv2

snsg-log-rx2660-2

rx2660


5 snsg-log-srv3

snsg-log-rx2660-3

rx2660


6 snsg-log-srv4

snsg-log-rx2660-4

rx2660


7 snsg-log-srv5

snsg-log-rx2660-5

rx2660


8 archv-sls-srv1 SenSage CDR Archiving SLS Server

archv-sls-rx2660-1

rx2660



archv-sls-rx2660-2

rx2660



archv-sls-rx2660-3

rx2660



archv-sls-rx2660-4

rx2660



archv-sls-rx2660-5

rx2660



archv-sls-rx2660-6

rx2661



archv-sls-rx2660-7

rx2662


15 archv-sls-srv8 SenSage CDR Archiving SLS Server 16 archv-sls-srv9 SenSage CDR Archiving SLS Server

archv-sls-rx2660-8 archv-sls-rx2660-9

rx2663 rx2664

2 Intel Itanium 9140M 2 Intel Itanium 9140M

Page

of

25

99

Linux 5 17 archv-sls-srv10 SenSage CDR Archiving SLS Server 18 rating-srv1 19 rating-srv2 Rating Server Rating Server archv-sls-rx2660-10 rating-app-T5440-1 rating-app-T5440-2 rx2665 T5440 T5440 RedHat Enterprise Linux 5 Solaris 10 Solaris 10 2 Intel Itanium 9140M 2 2 UltraSparc T2 Plus UltraSparc T2 Plus

1 2 3 4 5 6 7 8 9 10 11 12 13

bcc-db-srv1 bcc-db-srv2 incc-db-srv1 incc-db-srv2 cmptel-medsrv1 cmptel-medsrv2 intbill-db-srv1 intbill-db-srv2 vas-db-srv1 vas-db-srv2 portal-db-srv1 portal-db-srv2 reg-db-srv1

BehPardaz Post-paid Customer Care Database Server BehPardaz Post-paid Customer Care Database Server BehPardaz Pre-paid Customer Care Database BehPardaz Pre-paid Customer Care Database Comptel Mediation Server Comptel Mediation Server Intec Interconnect Billing Database Server Intec Interconnect Billing Database Server VAS Box Database Server VAS Box Database Server Portal Database Server Portal Database Server Registration Database Server

M9000-1 M9000-2 M9000-1 M9000-2 med-T5440-1 med-T5440-2 M9000-1 M9000-2 vas-db-T5440-1 vas-db-T5440-2 LDOM-T5440-1 LDOM-T5440-2 LDOM-T5440-1

M9000 M9000 M9000 M9000 T5440 T5440 M9000 M9000 T5440 T5440 T5440 T5440 T5440

Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10

4 4 4 4 4 4 4 4 4 4 4 4 4

Sparc64 VII Sparc64 VII Sparc64 VII Sparc64 VII UltraSparc T2 Plus UltraSparc T2 Plus Sparc64 VII Sparc64 VII UltraSparc T2 Plus UltraSparc T2 Plus UltraSparc T2 Plus UltraSparc T2 Plus UltraSparc T2 Plus

Page

of

26

99

14

reg-db-srv2

Registration Database Server BehPardaz Voucher Bank Database Server BehPardaz Voucher Bank Database Server BehPardaz Service Provisioning Database Server BehPardaz Service Provisioning Database Server

LDOM-T5440-2

T5440

Solaris 10

4

UltraSparc T2 Plus Sparc64 VII Sparc64 VII

15 16

vchbnk-db-srv1 vchbnk-db-srv2

vchbnk-db-T5440-1 vchbnk-db-T5440-2

T5440 T5440


4 4

17 18

sa-db-srv1 sa-db-srv2

sa-db-T5440-1 sa-db-T5440-2

T5440 T5440


4 4

Sparc64 VII Sparc64 VII

19 20

1 2 3 4

bill-db-srv1 bill-db-srv2 prvs-db- srv1 prvs-db- srv2

BehPardaz Billing Database Server BehPardaz Billing Database Server Comptel Service Provisioning Database Server-1 Comptel Service Provisioning Database Server-2

M9000-1 M9000-2 M9000-1 M9000-2

M9000 M9000 M9000 M9000

Solaris 10 Solaris 10 Solaris 10 Solaris 10

8 8 8 8

Sparc64 VII Sparc64 VII Sparc64 VII Sparc64 VII

Note: Those servers which are listed in one single row will be installed on VM; therefore we consider one license per ESX server.

The IBM TS3500 Tape library is chosen as the tape library soluon fo M I Tohi d D t a C er . r C a ent The IBM System Storage TS3500 Tape Library is designed to provide a highly scalable, automated tape library for open systems backup and archive in midrange to enterprisePage of

27

99

environments. The TS3500 tape library is also ordered with a dual accessor model opon to help increase the mount performance and overall system reliability. The TS3500 tape library is designed to provide the flexibility required to help address the system capacity and performance requirements of the most demanding applications by accommodang u to 1 d i v in u to si x p 92 r es p teen T S3500 tape lib ar y fram s . T T r e he S3500 tape library is designed with a variety of advanced features. The TS3500 Tape Library offers the following enhancements: Enhanced data accessibility through dual accessors that increase speed and provide failover protection Enhanced data security through support for tape drive encryption and write-once-readmany (WORM) cartridges Increased storage capacity with high-density frames that greatly increase capacity without requiring more floor space Some additional features of the TS3500 Tape Library are listed below: Ability to attach multiple simultaneous heterogeneous servers Remote management using a web browser or the TS3500 Command Line Interface Remote monitoring using Simple Network Management Protocol (SNMP) Multipath architecture Drive/media exception reporting In-depth reporting using the Tape System Reporter Host-based path failover An individual library consists of one base frame and up to 15 expansion frames and can include up to 192 tape drives and more than 20 000 tape cartridges. When the second accessor of the tape library is installed, the TS3500 Tape Library features enhanced availability by utilizing an additional accessor. The additional accessor enables the library to operate without disruption if any component of the working accessor fails. As another advantage, cartridge mount performance is also optimized. (A mount occurs when the accessor removes a cartridge from a drive, returns it to its storage slot, collects another cartridge from a random storage slot, moves it, and loads it into the drive.)

Page

of

28

99

When dual accessors are installed and master server issues a command for cartridge movement, the library automatically determines which accessor can perform the mount in the most timely manner. If the library's primary accessor fails, the second accessor assumes control and eliminates system outage or the need for operator intervention. The tape library for MCI Tohid Data Center includes four Frame Models as listed in Table 9TS3500 Tape Library Frame Types in below:

HA1

Service Bay A

N/A

N/A

This is required for second accessor. Contains slots for diagnostic cartridges only. Equipped with the enhanced frame control assembly Equipped with the enhanced frame control assembly. Configured as service bay B. Contains gripper test slots for diagnostic cartridges, and also contains unusable storage slots.

L53

Base Frame

LTO Ultrium

Up to 12 drives and up to 287 cartridges Up to 12 drives and up to 440 cartridges

D53

Expansion frame

LTO Ultrium

D53

Service Bay B

N/A

N/A

After the installation as you view the library from the front, service bay A (the HA1 frame) is on the far left and service bay B is on the far right. The following figure - TS3500 Tape Library Frame Position -shows the location of service bays in the TS3500 Tape Library.

Page

of

29

99

TS3500 Tape Library Frame Posion

Page

of

30

99

The following describes the major parts of the TS3500 Tape Library. 1. Library frames The base frame is named L53 and the expansion frame is D53. Each frame contains a rail system, cartridge storage slots, and 12 tape drives. There are another two frames as Service Bay A & Service Bay B which are needed to deploy dual accessor configuration. 2. Rail system The assembly on which the cartridge accessor moves through the library. The system includes the top and bottom rails. 3. Cartridge accessor The assembly that moves tape cartridges between storage slots, tape drives, and the I/O stations. 4. Accessor controller A circuit board that facilitates all accessor motion requests (such as calibrations, moves, and inventory updates). The second accessor also has a second accessor controller. 5. Cartridge storage slots Cells that are mounted in the TS3500 Tape Library and used to store tape cartridges. 6. IBM LTO Ultrium tape drives Mounted in the TS3500 Tape Library, 12 units that read and write data that is stored on tape cartridges. 7. Front door The front door of any frame. 8. Door safety switch A device in each frame that shuts down the motion power to the cartridge accessor whenever the front door is opened.

Page 30 of 99

31

99

9. I/O stations A cartridge compartment on the front door of the base frame of the TS3500 Tape Library that allows us to insert or remove tape cartridges without the library performing a reinventory of the frame. 10. Operator panel Located on the front of the base frame, the operator panel is the set of indicators and controls that lets us perform operations and determine the status of the library. 11. Enhanced frame control assembly An assembly of components that facilitate RS-422 communicaon bet w en the dr i v i n a e es frame and the accessor controller and operator panel controller. It includes two power supplies, both of which can provide power to the library and all drives in a frame. 12. Patch panel A panel that houses the cable connections from the Fibre Channel interfaces on each LTO Drive.

Figure 3: Components of the IBM System Storage TS3500

Page 31 of 99

32

99

The IBM tape library for MCI Tohid Data Center is congured to have 24 LTO Ultrium-4 tape drives. The LTO Ultrium-4 tape drives are high-performance, high-capacity data-storage units that are installed in the TS3500 Tape Library. There are 12 drives installed in each base and expansion frame of the library. The following Table 10 lists the specifications of Ultrium-4 Tape Drives:Type of Drive IBM System Storage LTO Ultrium-4 Tape Drive Speed of Connectivity 4 Gbps Fibre Native Data Rate 120 MB/s Native Capacity 800 GB (745.06 GB) Other Information Also known as the TS1040 tape drive

Table 10- TS1040 Tape Drive Specicaon

The most highlighted features for Ultrium 4 tape drives: Speed Matching Speed matching dynamically adjusts the drive's native (uncompressed) data rate to the slower data rate of a server. Channel Calibration Channel calibration customizes each read/write data channel for optimum performance. The customization enables compensation for variations in the recording channel transfer function, media characteristics, and read/write head characteristics. Power Management Power management reduces the drive's power consumption during idle power periods. ALMS is an extension of IBM's patented Multi-Path Architecture. With ALMS, the TS3500 Tape can virtualize the locations of cartridges (called SCSI element addresses) while maintaining native SAN attachment for the tape drives. ALMS enables logical libraries to consist of unique drives and ranges of volume serial (VOLSER) numbers, instead of fixed locations. ALMS offers dynamic management of cartridges, cartridge storage slots, tape drives, and logical libraries. For MCI Data Center as we are using NetBackup to control the operation and

Page 32 of 99

33

99

functionality of the Tape Library, we just use the ALMS for some special configuration and hardware troubleshooting.

NetBackup Bare Metal Restore (BMR) is one of the most valuable options of NetBackup. BMR is the server recovery option of NetBackup that can be used in situation of disaster recovery or any other time that we need to restore the whole system with its operation system, Hardware drivers, installed applications and others. BMR automates and streamlines the server recovery process, making it unnecessary to reinstall operating systems or configure hardware manually. Administrators can restore servers in a fraction of the time without extensive training or tedious administration, using NetBackup BMR option. BMR restores the operating system, the system configuration, and all the system files and the data files with the following steps: Run one command from the NetBackup master server. Reboot the client. Separate system backups or reinstallations are not required. The components of a BMR protection domain are as following: BMR master server The NetBackup BMR master server manages backups and restores of the protected client systems and the operation of BMR. NetBackup media servers NetBackup media servers control storage devices on which the client files are stored. BMR boot servers Boot servers provide the environment that is required to rebuild a protected client, including resources such as shared resource trees (SRTs). Shared resource trees contain the software that is used to rebuild the protected system so that NetBackup can restore the original files. The software includes the operating system software and the NetBackup client software.

Page 33 of 99

34

99

Clients Clients are the systems backed up by NetBackup and protected by BMR. A client may also be a server for other applications or data, a NetBackup media server, or a BMR boot server. The figure in below depicts the general topology of BMR backup:

Figure 4: Sample BMR Network

For each type of client that we want to protect the relevant boot server need to be installed. For example, a Solaris client requires a Solaris boot server, a Windows client requires a Windows boot server, and so on. For UNIX, Linux, and legacy Windows restores, a boot server at a particular operating system version can only host SRTs of the same operating system version or lower. For example, a Solaris 9 boot server can host Solaris 8 and Solaris 9 SRTs, but not Solaris 10 SRTs. The servers inside MCI Tohid Data Center are running four different types of OS: RedHat Enterprise Linux 5, Windows 2003, Windows 2008 and Solaris 10. Based on the above facts we need three boot servers as the following:

Page 34 of 99

35

99

Row 1 2 3

Server Name linux-bmr-srv win-bmr-srv solaris-bmr-srv

Server Type DL380 DL380 T5140

Operating System RedHat Enterprise Linux 5 Windows 2008 Solaris 10

Application Veritas NetBackup Linux BMR Boot Server Veritas NetBackup Windows BMR Boot Server Veritas NetBackup Solaris BMR Boot Server

Table 11: List of Required BMR Boot Servers

Each network segment of clients must have a BMR boot server that can support the clients; so the network interfaces of these boot servers should be configured in a way that Boot Servers have a physical IP presence on multiple networks. Figure 5 in the following shows the networking topology for BMR Boot Servers connection:

Figure 5: BMR Networking Topology

The following tables show the specifications of each of the Boot Servers:Server Name Win-bmr-srv

Page 35 of 99

36

99

Server Name

Win-bmr-srv

Server Name

Linux-bmr-srv

Server Name

Solaris-bmr-srv

Table 12: BMR Boot Servers Specification

Page 36 of 99

37

99

A client is protected after a NetBackup backup policy that is configured for BMR protection backs it up. Backups must occur before a client fails and requires a Bare Metal Restore. Each protected client must be backed up regularly by at least one policy that performs a full backup. The policy also can perform cumulative incremental or differential incremental backups, but a full backup must occur. The backup saves the files of the computer on a storage device that NetBackup manages. The backup saves the configuration of the client on the BMR master server. After a client is backed up by a policy that is configured for BMR protection, the client is registered with BMR as a protected client. It then appears in the Bare Metal Restore Clients view in the NetBackup Administration Console. We can use one policy or multiple policies to protect a single client. The following are the requirements for protecting BMR clients: A policy must be either type MS-Windows (for Windows clients) or Standard (for UNIX and Linux clients). A policy must have the Collect disaster recovery information for Bare Metal Restore attribute set. To integrate all backup policies and schedules we defined the policies to back up all the servers to be protected by BMR in Section 4 along with other types of backups. Please refer to section 4 to check out the defined policies and schedules. As mentioned before shared resource tree (SRT) is a collection of the following: Operating system files NetBackup client software Other programs to format drives, create partitions, rebuild file systems, and restore the original files using the NetBackup client software.

Page 37 of 99

38

99

A shared resource tree must be created on a local file system of the boot server. BMR sets permissions for the SRT directory to allow read access to all and read and write access to the root or Administrator user. To create an SRT, the installation software or images for the following items are needed: Operating system (UNIX and Linux only). For Linux SRTs, the Bare Metal Restore third-party products CD. This CD contains the open source products that may not be included in the vendor Linux distribution. Optional: Other applications or packages. Optional: Patches, maintenance levels, Maintenance Packs, service packs, or the drivers that the operating system requires or other software that is installed in the SRT. You must install into the SRT any operating system patches that the NetBackup client software requires. If they are not installed, NetBackup does not function correctly in the temporary restore environment, and the restore may fail.

NetBackup provides different options and agents to back up different objects; even for the same object there are different methods to be selected as backup approach. In this section well explain about different methods that will be used in MCI Tohid Datacenter as our approaches to back up different types of Data. The next section, when the backup requirement is mentioned, we just name the backup method that will be used to fulfill the specific requirements; and the detail explanation about each method can be found in this section. LAN backup is the most common method used. This is the simplest and cheapest method. Backup LAN involves setting up an additional LAN and setting another set of IP addresses on relevant clients; the detail of IP addressing and network segmentation is not in the scope of the current document and needs to be referred to Network Planning Document. The disadvantage of this method is the low speed of LAN if the amount of Data to be backed up is huge. Also it may affect the performance of LAN network negatively. In this method the backup traffic will pass through the LAN network between NetBackup client and LAN media server (media-nbkp-srv1).Page 38 of 99

39

99

This method no need any special license to be activated. By installing NetBackup client and entering the NetBackup Standard Client license, we can back up the data over LAN. Figure 6 in the following depicts the backup traffic flow between different components.

Figure 6: Backup Traffic Flow- LAN Backup

As it is shown on the above figure, the communication between NetBackup Master Server and NetBackup clients will go through LAN, also the backup traffic will pass through different clients to the NetBackup Media server (media-nbkp-srv1) and then writes to the target storage units. In the restore process the direction of traffic flow would be reversed. It means the image of data will be read by media-nbkp-srv1 from tape or CX-240 and then it will be transferred to the target server via LAN. The following figure depicts the restore traffic flow:

Page 39 of 99

40

99

Figure 7: Restore Traffic Flow through LAN

SAN Client is a NetBackup optional feature that provides high speed backups and restores of NetBackup clients. In this method the backup and restore traffic occurs over a SAN, and NetBackup server and client administration traffic occurs over the LAN. This method is useful when we are going to back up huge amount of data in a short time. By using SAN as the transport network for backup traffic we can lower the required time for backup and also we eliminate the negative effect of backup traffic on limited LAN network. Figure 8, in below is showing the backup traffic flow between different components of NetBackup system.

Page 40 of 99

41

99

Figure 8: Backup Traffic Flow- SAN Client

Fibre Transport connections between NetBackup clients and NetBackup FT Media Server (media-nbkp-srv2) are referred to as FT pipes. The SAN client can be in a cluster and can host clustered applications. The FT client service and the Symantec PBX service must run on all failover nodes. The backup policy references to client computers can be to aliases or dynamic application cluster names. In this scenario well use either disk or tape as a storage destination for the SAN Client backup. With tape as a destination we can use multi streaming, which divides automatic backups for a client into multiple jobs. Because the jobs are in separate data streams, they can occur concurrently. The data streams can be sent over one or more FT pipes to the FT media server. The media server multiplexes them together onto one or more tape media volumes. In the restore process, the backup image will be read by media-nbkp-srv2 from tape or CX-240. Then the image will be transferred to the target host through FT pipe (SAN) and finally will be written to the central storage system by the server which owns the data.Page 41 of 99

42

99

The following picture shows the traffic flow for restore process:

Figure 9: Restore Traffic Flow- SAN Clients

The configuration and zoning of SAN is not in the scope of this document and it is explained in SAN Design document, anyway the following are important considerations about the HBA configuration on NetBackup media server and preferred SAN zoning configuration. Two 4Gb FC ports on NetBackup media server (media-nbkp-srv2) will be used for the connections to the SAN clients. The HBA must be configured to use the NetBackup target mode driver. The HBA ports on the SAN clients must operate in the default initiator mode. Another two 4Gb FC ports will be connected to storages. The HBA ports that connect to the storage must remain in the default initiator mode. About the zoning of SAN, Symantec recommends the following zones:

Page 42 of 99

43

99

An FT traffic zone that includes only the SAN clients and the NetBackup FT media servers HBA ports that connect to the SAN clients. The backup storage zone should include the storage and the FT media server HBA ports that connect to the storage. These zones prevent SAN Client traffic from using the bandwidth that may be required for other SAN activity. SAN media servers are NetBackup media servers that back up their own data. SAN media servers cannot back up data that resides on other clients. SAN media servers are useful for certain situations. SAN media servers will use SAN as their transport network for backup traffic, the same as SAN clients, but they have another main advantage that they can share tape resources with NetBackup Master and Media Servers. The Shared Storage Option of NetBackup (SSO) needs to be licensed to enable sharing the tape drives between different SAN media servers and NetBackup media servers (media-nbkp-srv1, 2). Figure 10, in the following shows the backup traffic flow between different components of NetBackup system. As we can see the backup traffic is directly send from SAN Media Servers to IBM tape library of disk storages.

Figure 10: Backup Traffic Flow-SAN Media Server

Page 43 of 99

44

99

This solution is mainly used in case we have large size database on the server (NetBackup Client) that needs to be backed up frequently. So well need to do the licensing for relevant Application and Database Agent as well as licensing for SAN Media Server. To define a backup policy for a SAN media server, the SAN media server is added only as the client. A snapshot is a point-in-time, read-only, disk-based copy of a client volume. NetBackup can back up the original volume or the snapshot that is created from original volume. The contents of the snapshot volume are cataloged as if the backup was produced directly from the primary volume. After the backup is complete, the snapshot-based backup image on storage media is indistinguishable from a backup image produced by a traditional, non-snapshot backup. Users and client operations can access the primary data without interruption while data on the snapshot volume is being backed up NetBackup includes a set of software libraries that are called "snapshot providers." The providers enable Snapshot Client to access the snapshot technology in the storage subsystem. The EMC CLARiiON disk array enables NetBackup to create hardware snapshots in the CLARiiON array. There are two main methods provide by EMC CLARiiON to create snapshots as listed in the following table:Snapshot method EMC_CLARiiON_Snapview_Clone EMC_CLARiiON_SnapView_Snapshot Description and notes For full-volume mirror snapshots with EMC CLARiiON disk arrays. For space-optimized, copy-on-write snapshots with EMC CLARiiON disk arrays.

Table 13: EMC CLARiiON Snapshot Methods

If the snapshot method is specified in the definition of the backup policy, NetBackup will use the snapshot of the Data to be backed up. When the policy runs, the snapshot method calls the EMC CLARiiON provider library. The provider then accesses the commands of Unisphere Secure CLI in the CX4-960 storage subsystem to create the snapshot.

Page 44 of 99

45

99

The following table includes software requirements to make Snapshots using EMC CLARiiON arrays.

Table 14: EMC Snapshot Software Requirement

The figure in below shows the software components on the NetBackup clients and the CLARiiON array, and indicates the contro5l function of each.

Figure 11: Snapshot Process

At the moment there are some uncertainties about using snapshots for the backup creation. 1- The amount of free space on CX4-960 is not nalized yet, so we cant decide about allocated space for snapshot purpose.

Page 45 of 99

46

99

2- The CX4-960 will use FLARE OS 30 according to the latest design and the Navisphere will be replaced by Unisphere. As currently there are not so much stuff about the compabi lity o N t B f e ackup 7 1 a U i spher e, it is n 1 . nd n ot 00% sur e that snaps hot s c an be created by the current version. This feature makes backups available for quick recovery from disk. Instant Recovery combines snapshot technology with the ability to do rapid snapshot-based restores. The snapshot is retained on disk as a full backup image. The snapshot can also be the source for an additional backup copy to tape or other disk based storage. Because snapshots require disk space, they cannot be retained forever. To balance the space consumed against the convenience of having multiple snapshots available for instant recovery, we have to limit the number of snapshots to retain. NetBackup integrates the database backup and recovery capabilities of the Oracle Recovery Manager (RMAN) with the backup and recovery management capabilities of NetBackup. In this case NetBackup for Oracle supplies the Veritas I/O Library (ibobk) and Oracle Database software will supply RMAN + OCI. Using this combination, NetBackup can automate and centralize the backup operation of Oracle databases. A backup policy for Oracle database defines the backup criteria for the backup job. These criteria include the following: Storage unit and media to use Policy attributes Backup schedules Clients to be backed up Backup templates or script files to be run on the clients The first four criteria are common for different types of backup, and the last one is particularly defined for Oracle database backups. With a few exceptions, NetBackup manages a database backup like a file system backup. One major difference is that backup levels that are defined

Page 46 of 99

47

99

will be based on the Oracle backup levels. Table 15 in the following lists specific levels used for Oracle backup.

Full backup

A full backup copies all blocks into the backup set, skipping only data file blocks that have never been used. Note that a full backup is not the same as a whole database backup; "full" is an indicator that the backup is not incremental. A full backup has no effect on subsequent incremental backups, which is why it is not considered part of the incremental strategy. An incremental backup is a backup of only those blocks that have changed since a previous backup. RMAN lets you so on. A level 0 incremental backup, which is the base of subsequent incremental backups, copies all blocks containing data. When you generate a level n incremental backup in which n is greater than 0, you back up the following: All blocks that have been modified since the most recent backup at a level n or lower. This condition is the default type of incremental backup. It is called a differential incremental backup. All blocks that have been modified since the most recent backup at level n-1 or lower. This condition is called a cumulative incremental backup. In a differential level n incremental backup, you back up all blocks that have changed since the most recent backup at level n or lower. For example, in a dierenal le 2 b vel ackup, y b ou ack u a l b o ks that a e m di si n e the la p l l c r o ed c st level 2, level 1, or level 0 backup. In a cumulative level n incremental backup, you back up all blocks that have changed since the most recent backup at level n-1 or lower. For example, in a cumulav e le 2 b vel ackup, y b ou ack u a l b o ks that a e changed si n e the m s t p l l c r c o recent level 1 or level 0 backup.Table 15: Oracle Backup Levels

Incremental backup

Multilevel incremental backup

Differential incremental backup

Cumulative incremental backup

The backup selections list in a database policy has a different meaning than that for nondatabase policies. For example, in a Standard or MS-Windows policy, the list contains files and directories to be backed up. In a database policy, we specify templates or scripts to be run. The script needs to be provided by DB administrator for each particular system.

Page 47 of 99

48

99

NetBackup for Oracle can be used in conjunction with NetBackup Snapshot Client. In this way NetBackup for Oracle can back up Oracle objects by taking snapshot images of the component files. Later, it backs up the snapshot version to the storage unit. Snapshot backup captures the data at a particular instant without causing significant client downtime. Client operations and user access continue without interruption during the backup. The resulting capture or snapshot can be backed up without affecting the performance or availability of the database. Using Snapshot backup makes backups available for instant recovery from disk. Optionally, the image is retained on disk as well as backed up to storage. To use NetBackup for Oracle with Snapshot Client, we must have both NetBackup Snapshot Client and NetBackup for Oracle installed and licensed.

NetBackup for SQL Server extends the capabilities of NetBackup for Windows to include backing up and restoring SQL Server databases. NetBackup for SQL Server includes a client-based graphical user interface (GUI) program to perform various activities on SQL Server. These activities include the following: Configuration of options for NetBackup for SQL Server operations. Backups and restores of databases and database components, which include transaction logs, differentials, files, and file groups. Monitoring NetBackup for SQL Server operations. To use the SQL Server Agent to back up the database, we must set the policy type as MS-SQLServer type. These criteria related to this policy type include the following: Storage unit and media to use Policy attributes Backup schedules Clients to be backed up The batch files to run on the clients

Page 48 of 99

49

99

From the listed criteria on above all of them are common for different policy types and the last one is the one specifically defined for SQL Server Backup. The same as Backup for Oracle Databases, MS-SQL backup has its own definition for different backup levels. Table 16 in the following lists different types of backup that can be performed on MS-SQL databases:Term Full MS-SQL Backup Levels Definition The database, including all of its component files are backed up as a single image. The log file is included in a full database backup. All of the changes since the last full are backed up to a single image.

Differential

Transaction Log

Transaction log backups are only available for the full and bulk-load recovery options. In this operation, the inactive portion of the transaction log is backed up.Table 16: MS-SQL Backup Levels

To protect the data on virtual machines there are two basic procedures. Each of these methods offer performance advantages as well as limitations. 1. Local backup: This involves installing a standard NetBackup client inside each virtual machine and backing up the virtual machine the same way that would be used if it was a physical system. This backup methodology is popular because the implementation process is essentially the same as with physical machine backups. 2. Off-host backups: This method takes advantage of the vStorage API for Data Protection. Introduced with vSphere 4, this method o-loads backup processing from the ESX server to a separate backup server referred as the VMware Backup Host. The first architecture essentially gives us a backup solution that closely resembles that of physical servers, is simple to configure, and provides the same file level restore capabilities of traditional backups. The advantages of local backup for virtual machines can be listed as below:

Page 49 of 99

50

99

Simple and familiar implementation. Backup administrators are more familiar with this method and they can easily manage the virtual machine backups using this method. Single file or folder backups and restores for all supported Guest OSs. Single file restores directly into the Guest OS are supported. Application and database backups (e.g. Microsoft SQL Server and Oracle) are supported. The configuration process is exactly the same as configuring the same type of backup within a physical system. The disadvantages of local backup method are: Full virtual machine images (vmdk files) are not backed up making entire virtual machine restores (e.g. disaster recovery) more complex. The backup processing load on one virtual machine may negatively impact ESX resources available to other virtual machines hosted on the same physical server. Well need one standard client license on each guest operating system. According to the suggestion from the project consultant, well use the second method to back up the VMs. In this case we need less standard client licenses, as we just use one license per ESX server. The following picture shows the backup traffic flow using VMware Backup Host:

Figure 12: Backup Traffic Flow- VMware backup

Page 50 of 99

51

99

For the restore process the same components will be involved, but the direction of the data flow would be reversed as the following picture:

Figure 13: VMware Restore Traffic Flow

NetBackup uses MS-Windows policy type to back up systems running on Windows. It also has a special feature to back up the systems with Active Directory installed. A NetBackup policy that backs up the Active Directory can be configured to allow the restore of the objects and attributes in the Active Directory. The objects and attributes can be restored locally or remotely without the interruption of restarting the domain controllers where the restore is performed. Any Active Directory backup is always a NetBackup full backup, whether it is a granular backup or not. Whenever Active Directory is in a policys Backup Selections list, the Active Directory

Page 51 of 99

52

99

portion is always fully backed up, even when the backup type is incremental, d

nbu detail design - ver 1

Documents

backup policy

snapshot backup

active directory backup

backup selections

vmware backup

oracle policy

application servers

oracle databases