VSNL - NetBackup Design and Configuration Document 1 1

VERITAS Consulting Services Page 1 of 16

PRESENTED TO:

VSNL, Chennai

PRESENTED BY:

VERITAS Consulting ServicesVERITAS Software Asia Pacific Trading Pte Ltd

6 Temasek Boulevard#11-01 Suntec Tower 4

Singapore 038988, Singapore

APRIL 7, 2023

Videsh Sanchar Nigam LimitedNetBackup Design and Configuration Document

1. DOCUMENT REVISION HISTORY 3

2. NETBACKUP CONFIGURATION AT VSNL 4

2.1 New Features in NetBackup 6.0 4

2.2 Block Diagram Chennai 5

2.2.1. Chennai Rack - I 52.2.2. Chennai Rack - II 6

2.3 Block Diagram Singapore 6

2.3.1. Singapore Rack – I 62.3.2. Singapore Rack - II 6

2.4 Backup Network details for Chennai 7

2.5 Backup Network details for Singapore 7

2.6 Backup schedules and retention periods 8

2.7 Naming conventions 8

2.8 Clients listing 9

2.8.1. Chennai Client List 92.8.2. Singapore Client List 9

2.9 Backup selections for VSNL servers 10

2.9.1. Backup Selection for Chennai Servers 102.9.2. Backup Selection for Singapore Servers 10

2.10 NetBackup policies at VSNL 11

2.10.1. Policy Detail for Chennai 112.10.2. Policy Details for Singapore 12

3. CATALOG AND MEDIA SIZING 12

3.1 Calculating NetBackup Catalog Size 12

3.2 Calculate media requirement 13

4. NetBackup Operations Manager (NOM) 14


1. DOCUMENT REVISION HISTORY

There has been a consolidated effort to ensure that this document is accurate and up to date. The following people have participated in this documents creation and review.

Version Date Description Contributors

1.0 1st January 2007 Initial Draft Milind Patil1.1 4th January 207


2. NETBACKUP CONFIGURATION AT VSNL

The aim of this document is to provide a glimpse of NetBackup 6.0 setup at VSNL Chennai & Singapore data centre.

2.1 New Features in NetBackup 6.0

VERITAS NetBackupTM 6.0 is strongly recommended for the VSNL environment. NetBackup 6.0 contains many new features and enhancements designed to increase scalability and functionality of NetBackup for large enterprise customers. These features can help to further enhance the backup environment at TM Berhad and make operations smoother and easier.

Some of the prominent new features in NetBackup 6.0 are:

NetBackup Media Manager enhancements with the new Enterprise Media Manager (EMM) database.

NetBackup enhancements to the core functionality : Intelligent Resource Manager (IRM) NetBackup catalog enhancements – Online, Differential and scheduled backups Enhanced disk backup capabilities Respond to the increased market requirement for backing up data to disk Collaborate with Network Appliance to differentiate NetBackup by providing support to back up

data directly to NearStore appliances Meet the VERITAS integration guidelines and enhance NetBackup integration with other

VERITAS products Enable NetBackup to be more easily localized to other languages. In addition, a new management and reporting interface for NetBackup is introduced in this

release. NetBackup Operations Manager (NOM) is a new product feature developed to address NetBackup management needs of enterprise customers.

NetBackup Advanced Client enhancements NetBackup Bare Metal Restore (BMR) integrated into the NetBackup Administration Console and

the Backup Policies BMR master server supported on Windows systems. BMR Windows boot servers Added Linux client support and improved the support for VERITAS Volume manager and file

system NetBackup SAP Database Agent integration with Oracle RMAN NetBackup supports Microsoft SQL Server 2005 and NetBackup SharePoint 2003 Leverage disk storage unit (DSU) groups Enhanced device discovery for ACS and TLM robotics. Improvements to the device configuration

wizard Multi-path Shared Storage Option (SSO) including NDMP support. NDMP WORM tape support. NetBackup supports Sybase ASA components Port reduction for NetBackup components Robust file logging Enhanced PBX infrastructure integration Unified Logging standardization NDMP Enhancements Integrated Snapshot feature NDMP agent enhancements including SSO and Enhanced Tape Alert support NetBackup Operations Manager (NOM) provides NetBackup management and reporting

capabilities NetBackup proliferations New back-level administration capabilities


2.2 Block Diagram Chennai

2.2.1. Chennai Rack - I


2.2.2. Chennai Rack - II

Connectivity diagram for Mgd backup.ppt

2.3 Block Diagram Singapore

2.3.1. Singapore Rack – I

2.3.2. Singapore Rack - II

< >


2.4 Backup Network details for Chennai

Sr No

Server Name Description Production IPBackup LAN

IP

1 CHNVSNSMBK001 Veritas NetBackup Master server #1 10.32.128.1010.32.130.

31

2 CHNVSNSMNM001 Veritas NOM server 10.32.128.1110.32.130.

323 CHNVSNRSMT001 RSM / CCM / RT 10.72.217.25 10.32.128.124 CHNVSNRSMT002 RSM / CCM / RT (Redundant) 10.72.217.26 10.32.128.135 CHNVSNTSMT001 Cold / Test server 10.72.217.27 10.32.128.14

6 CHNVSNPMMT001 BMC Performance Manager suite10.72.217.30

(28,29) 10.32.128.15

7 CHNVSNPMMT002 BMC Performance Manager suite (Redundant)10.72.217.33

(31,32) 10.32.128.16

8 CHNVSNDVMT001 BMC DashBoard suit & Visualis10.72.217.36

(34,35) 10.32.128.17

9 CHNVSNDVMT002 BMC DashBoard suit & Visualis (Redundant)10.72.217.39

(37,38) 10.32.128.18

10 CHNVSNCMMT001BMC Configuration Manager for servers (Bundle) + AlarmPoint

10.72.221.135 10.32.128.19

11 CHNVSNRTMT001BMC Patrol and Performance Manager Reporting + Reporting Studio

10.72.221.138 (136,137) 10.32.128.20

12 CHNVSNTSMT002 Cold / Test server10.72.221.141 (139,140) 10.32.128.21

13 CHNVSNTSMT003 Cold / Test server10.72.221.144 (142,143) 10.32.128.22

2.5 Backup Network details for Singapore

Sr.No Server Name Description Production IPBackup LAN

IP

1 SGPVSNSMBK001 Veritas NetBackup Master server #1 10.72.212.4610.32.112.2

0

2 SGPVSNTSBK001 Cold / Test server 10.32.96.510.32.112.1

6

3 SGPVSNTSBK002 Cold / Test server 10.32.96.7010.32.112.1

74 SGPVSNRSMT001 RSM / CCM / RT 10.32.96.70 10.32.112.105 SGPVSNRSMT002 RSM / CCM / RT 10.72.212.31 10.32.112.116 SGPVSNAVMT001 Cold /Test Server 10.72.212.32 10.32.112.12

7 SGPVSNTSMT002 Cold /Test Server10.72.212.71

(72,73) 10.32.112.13


2.6 Backup schedules and retention periods

VSNL Singapore & Chennai data centre would perform an incremental backup for all servers on a daily basis. Full backups are performed for all servers on a weekly and monthly basis. The configured retention period for Daily backup is 2 week, Weekly backups for 1 month and Monthly backups for 6 Momths.Application backup will be taken every alternate week at the time of weekly backup. The retention period for application backup will be 4 Weeks. This can be further changed based on the business and operational requirements at VSNL.

The following backup schedules and retention periods are implemented for VSNL backups:

Backup schedules and Retention of data

S/N Schedule Name Backup Type Retention Period1 Daily Incremental 2 Week2 Weekly Full 1 Month3 Monthly Full 6 Month

2.7 Naming conventions

The following table shows the current NetBackup policy naming conventions that are implemented for VSNL:

Naming convention for NetBackup Policies AT ChennaiS/N Policy name Description

1 CHNVSN_SYS Backup of Shadow_Copy_Components for "server"2 CHNVSN_FS Backup of All_Local_Drives for "server"3 CHNVSN_SQL_DB Backup of SQL db's for "server"4 CHNVSN_Linux_App Backup of Linux for "server"5 CHNVSN_Sun_App Backup of Sun for "server"

Naming convention for NetBackup Policies AT SingaporeS/N Policy name Description

1 SGPVSN_SYS Backup of Shadow_Copy_Components for "server"2 SGPVSN_FS Backup of All_Local_Drives for "server"3 SGPVSN_SQL_DB Backup of SQL db's for "server"4 SGPVSN_Linux_App Backup of Linux for "server"5 SGPVSN_Sun_App Backup of Sun for "server"


The following table shows the naming convention and properties of various backup schedules that are configured for servers at VSNL:

Naming convention for NetBackup Schedules

S/NSchedule

name DescriptionVolume

Pool Day of run Retention1 Daily Daily backup of the "Backup Selection" Daily Mon to Sat 2 Weeks2 Weekly Weekly backup of the "Backup Selection" Weekly Sunday 1 Months

3 Monthly Monthly backup of the "Backup Selection" MonthlyFirst Sunday of the month 6 Months

2.8 Clients listing

The following table lists the various servers at VSNL environment, along with the application which they run and their current NetBackup role:

2.8.1. Chennai Client List

Sr No Server Name Description W2003 SUN Solaris SAN / LAN

Chennai1 CHNVSNSMBK001 Veritas NetBackup Master server #1 W2003 SP12 CHNVSNSMNM001 Veritas NOM server W2003 SP1 LAN3 CHNVSNRSMT001 RSM / CCM / RT W2003 SP1 LAN4 CHNVSNRSMT002 RSM / CCM / RT (Redundant) W2003 SP1 LAN5 CHNVSNTSMT001 Cold / Test server W2003 SP1 LAN6 CHNVSNPMMT001 BMC Performance Manager suite Solaris 10 LAN7 CHNVSNPMMT002 BMC Performance Manager suite (Redundant) Solaris 10 LAN8 CHNVSNDVMT001 BMC DashBoard suit & Visualis Solaris 9 LAN9 CHNVSNDVMT002 BMC DashBoard suit & Visualis (Redundant) Solaris 9 LAN10

CHNVSNCMMT001BMC Configuration Manager for servers (Bundle) + AlarmPoint W2003 SP1 LAN

11CHNVSNRTMT001

BMC Patrol and Performance Manager Reporting + Reporting Studio Solaris 10 LAN

12 CHNVSNTSMT002 Cold / Test server Solaris 10 LAN13 CHNVSNTSMT003 Cold / Test server Solaris 10 LAN

2.8.2. Singapore Client List

Sr.No Server Name Description W2003 SUN SolarisSAN / LAN

1 SGPVSNSMBK001 Veritas NetBackup Master server #1 Solaris 102 SGPVSNTSBK001 Cold / Test server W2003 SP1 LAN3 SGPVSNTSBK002 Cold / Test server W2003 SP1 LAN4 SGPVSNRSMT001 RSM / CCM / RT W2003 SP1 LAN5 SGPVSNRSMT002 RSM / CCM / RT W2003 SP1 LAN6 SGPVSNTSMT001 Cold /Test Server W2003 SP1 LAN


7 SGPVSNTSMT002 Cold /Test Server Solaris 10 LAN

2.9 Backup selections for VSNL servers

The following table lists the backup selections which have been configured for each of the servers in the current VSNL backup environment:

2.9.1. Backup Selection for Chennai Servers

S/NHostname AT

Chennai NetBackup RoleNetBackup

Version Backup Selections

1 CHNVSNSMBK001Master/Media server 6.0 MP4

SYS (Daily, Weekly, Monthly), C:\, D:\, E:\, (Weekly), NBU_Catalog (Daily)

2 CHNVSNSMNM001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES3 CHNVSNRSMT001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES4 CHNVSNRSMT002 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES5 CHNVSNTSMT001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES6 CHNVSNPMMT001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES7 CHNVSNPMMT002 Client (LAN) 6.0 MP4 < > 8 CHNVSNDVMT001 Client (LAN) 6.0 MP4 < > 9 CHNVSNDVMT002 Client (LAN) 6.0 MP4 < >

10 CHNVSNCMMT001 Client (LAN) 6.0 MP4 SYS11 CHNVSNRTMT001 Client (LAN) 6.0 MP4 < > 12 CHNVSNTSMT002 Client (LAN) 6.0 MP4 < > 13 CHNVSNTSMT003 Client (LAN) 6.0 MP4 < >

2.9.2. Backup Selection for Singapore Servers

S/NHostname At

Singapore NetBackup RoleNetBackup

Version Backup Selections

1 SGPVSNSMBK001Master/Media server 6.0 MP4 Full Root backup (Weekly), NBU_Catalog (Daily)

2 SGPVSNTSBK001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES3 SGPVSNTSBK002 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES5 SGPVSNRSMT001 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES6 SGPVSNRSMT002 Client (LAN) 6.0 MP4 SYS, ALL_LOCAL_DRIVES7 SGPVSNTSMT001 Client (LAN) 6.0 MP4 < > 8 SGPVSNTSMT002 Client (LAN) 6.0 MP4 < >

Legend :ALD - ALL_LOCAL_DRIVESSYS - SHADOW_COPY_COMPONENTS (Daily, Weekly and Monthly)Root - < >


2.10 NetBackup policies at VSNL

The following table lists all the NetBackup policies configured for servers at VSNL, their policy type, backup selection and Schedule information:

2.10.1. Policy Detail for Chennai

S/N Hostname NetBackup Policy Policy Type Backup Selection Schedules

1 CHNVSNSMBK001

CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,

CHNVSN_FS MS-Windows-NT All_Local_Drives Weekly, Monthly

CHNVSNMBK001_CAT NBU-Catalog NetBackup Catalog Daily, Weekly, Monthly

2 CHNVSNSMNM001CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,


3 CHNVSNRSMT001CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,


4 CHNVSNRSMT002CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,


5 CHNVSNTSMT001CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,


6 CHNVSNCMMT001CHNVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily,


7 CHNVSNPMMT001CHNVSN_SUN_Full Standard Root Weekly, Monthly

CHNVSN_SUN_Incr Standard < > Daily

8 CHNVSNPMMT002CHNVSN_SUN_Full Standard Root Weekly, Monthly


9 CHNVSNDVMT001CHNVSN_SUN_Full Standard Root Weekly, Monthly


10 CHNVSNDVMT002CHNVSN_SUN_Full Standard Root Weekly, Monthly


11 CHNVSNRTMT001CHNVSN_SUN_Full Standard Root Weekly, Monthly


12 CHNVSNTSMT002CHNVSN_SUN_Full Standard Root Weekly, Monthly


13 CHNVSNTSMT003CHNVSN_SUN_Full Standard Root Weekly, Monthly



2.10.2. Policy Details for Singapore

S/N Hostname NetBackup Policy Policy Type Backup Selection Schedules

1 SGPVSNSMBK001

SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly

SGPVSN_FS MS-Windows-NT All_Local_Drives Monthly

SGPVSNMBK001_CAT NBU-Catalog NetBackup Catalog Daily, Weekly, Monthly

2 SGPVSNTSBK001SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly


3 SGPVSNTSBK002SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly


4 SGPVSNRSMT001SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly


5 SGPVSNRSMT002SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly


6 SGPVSNTSMT001SGPVSN_SYS MS-Windows-NT Shadow Copy Components:\ Daily, Weekly, Monthly


7 SGPVSNTSMT002SGPVSN_SUN_Full Standard Root Weekly, Monthly

SGPVSN_SUN_Incr Standard Daily

3. CATALOG AND MEDIA SIZING

3.1Calculating NetBackup Catalog Size

Catalog is very important part of NetBackup configuration; it is recommended that at least two copies of catalog to be back up daily. Additional you can keep one copy on local or SAN storage.

An important factor when designing your backup system is to calculate how much disk space you need to store your NetBackup catalog. Catalog keeps track of all the files that have been backed up. The catalog’s size is directly tied in to several variables, including the frequency of your backups, the number of files being backed up, the path length for each file being backed up, and your retention periods. On average, the size of catalog can be between 1% to 2% (or higher) of the total data being tracked.

To calculate NetBackup catalog size, need to know how much data you will be backing up for full and incremental backups, how often these backups will be performed, and for how long they will be retained. Here are two simple formulas to calculate these values:

Data being tracked = (Amount of data to back up) * (Number of backups) * (Retention period)

NetBackup catalog size = 120 * (number of files)

Example: Calculating the size of your NetBackup catalog

Assumptions:

Amount of data to back up = 100 gigabytesIncremental backups = 20% of all dataFull backups per month = 4Retention period for full backups = 6 monthsIncremental backups per month = 30Retention period for incremental backups = 1 month

Solution:

Size of full backups = 100 gigabytes * 4 * 6 months = 2.4 terabytes


Size of incremental backups = (20% of 100 gigabytes) * 30 * 1 month = 600 gigabytesTotal data tracked = 2.4 terabytes + 600 gigabytes = 3 terabytes

NetBackup catalog size = 2% of 3 terabytes= 60 gigabytes

3.2 Calculate media requirement

The number of tapes that you will need depends on:

The amount of data that you are backing up The frequency of your backups The planned retention periods The capacity of the media used to store your backups.

A simple formula for calculating your tape needs is shown here:

Number of tapes = (Amount of data to back up) / (Tape capacity)

To calculate how many tapes will be needed based on all your requirements, the aboveFormula can be expanded toNumber of tapes = ((Amount of data to back up) * (Frequency of backups) *

(Retention period)) / (Tape capacity)

Example: Calculating how many tapes are needed to store all your backups

Preliminary calculations:

Size of full backups = 500 gigabytes * 4 (per month) * 6 months = 12 terabytesSize of incremental backups = (20% of 500 gigabytes) * 30 * 1 month = 3 terabytesTotal data tracked = 12 terabytes + 3 terabytes = 15 terabytes

Solution :

Tape drive type = LTO gen 3Tape capacity without compression = 400 gigabytesTape capacity with compression = 800 gigabytes

Without compression:

Tapes needed for full backups = 12 terabytes/400 gigabytes = 30Tapes needed for incremental backups = 3 terabytes/400 gigabytes = 7.5 ~= 8Total tapes needed = 30 + 8 = 38 tapes

With 2:1 compression:

Tapes needed for full backups = 12 terabytes/800 gigabytes = 15Tapes needed for incremental backups = 3 terabytes/800 gigabytes = 3.75 ~= 4Total tapes needed = 15 + 4 = 19 tapes


4. NETBACKUP OPERATIONS MANAGER (NOM)

NetBackup Operations Manager (NOM) is an advanced, easy-to-use management and monitoring application that works in conjunction with NetBackup master and media servers and clients. It is strongly recommended that VSNL uses NOM for achieving advanced management, reporting and alerting functions that simplify administration of their NetBackup environment.

NetBackup Operations Manager (NOM) replaces earlier VERITAS NetBackup add-on products like Global Data Manager (GDM) and Advanced Reporting Option (ARO).

Features of NOM helpful to the VSNL backup environment

The following salient features of NOM will assist in managing and monitoring NetBackup environment: NOM is web-based and allows viewing the operational status and health of the distributed data

protection environment. NOM is capable of managing and monitoring dozens of NetBackup installations spread across multiple locations from a single point. Using NOM does not require a separate login to each NetBackup master or media server.

NOM provides a consistent backup management interface to simplify the complex tasks involved in protecting and managing the data resources of a large enterprise effectively. NOM offers NetBackup job activity, job policy, media and devices, and service monitoring and management; as well as policy-based alerting and notification.

NOM is an operations monitoring and management tool for NetBackup. Management tasks available with NOM are focused on maintaining your environment once initial configuration is completed.

NOM is not a web-based UI for NetBackup configuration and administrative functions. The NetBackup Administration console and command line interfaces are still used for core administrative functions such as configuration of your media, storage units, policies, and schedules.

NOM is a completely new product based on a new architecture, data modeling, design, and implementation, and is not an incremental update to any existing VERITAS products.

NOM includes new reporting capabilities, such as built-in standard reports that you can use immediately. You also can modify these reports to better meet your needs, or create your own reports using the many database views that are provided.

The following are some key features of NOM in a nut shell:• NOM is bundled with NetBackup 6.0 for no additional cost• Browser based User Interface• Real time monitoring & administration• Server Grouping for advanced management and reporting• Includes built-in reports• Enhanced reporting with custom report building• Provides troubleshooting assistance• Log management and viewing• Alert management and notification• Security features

NOM Components

The NOM console provides a single user interface to the NOM server. All requests from the console are sent to the NOM web client (a component of the NOM server).

The NOM server component is the focal point for centralized monitoring and managing of the NetBackup servers in your environment. It gathers data and information from NetBackup master servers and stores it the NOM database. It also handles any user-requested monitoring and maintenance tasks for the NetBackup master servers. It can be a dedicated server or on a server where NetBackup is installed.


Requirements for NOM server at VSNL

The NOM server generally needs a lot of system resources. It is hence suggested that VSNL to have a dedicated server to act as the NOM server. This would make sure that the monitoring, altering and reporting load is taken off the NetBackup master server. The NOM server is recommended to have the following minimal requirements:

NOM server software does not have to be installed on the same server as NetBackup 6.0 master server software

NOM server must have atleast NetBackup 6.0 client software installed NOM server should have atleast 2 CPU’s and 4 GB of RAM for the Telekom NetBackup

environment NOM server should have a record of stability; this means long uptimes with minimal interruptions NOM server should be able to support a medium or large-scale Sybase database application NOM server must have network connectivity to all managed NetBackup 6.0 servers NOM server should be configured as a fixed host, rather than as a dynamic host (DHCP) VERITAS recommends that you do not install NOM software on a clustered NetBackup master

server NOM supports Microsoft Internet Explorer 6.0 or higher and Netscape 7.1 or higher web Browsers NOM server can be one of the following platforms:

o Microsoft Windows 2000 SP4o Microsoft Windows 2003 SP1o Solaris 8o Solaris 9

As seen from the above figure, a single NOM server can be used to monitor multiple NetBackup master servers and domains. In the longer run, VSNL can even plan to implement NetBackup 6.0 across all its data centers and have a single NOM server. This would help in getting single consolidated backup reports for all regions.

The screenshot below shows a sample NOM overview page.



Documents

VSNL - NetBackup Design and Configuration Document 1 1