Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
PRESENTED TO:
VSNL, Chennai
PRESENTED BY:
Page 1 of 16
1. DOCUMENT REVISION HISTORY 2. NETBACKUP CONFIGURATION AT VSNL 2.1 New Features in NetBackup 6.0 2.2 Block Diagram Chennai
3 4 4 5
2.9.1. Backup Selection for Chennai Servers................................................................................10 2.9.2. Backup Selection for Singapore Servers.............................................................................10
2.10 NetBackup policies at VSNL 11
2.10.1. Policy Detail for Chennai..................................................................................................11 2.10.2. Policy Details for Singapore..............................................................................................12
3. CATALOG AND MEDIA SIZING 3.1 Calculating NetBackup Catalog Size 3.2 Calculate media requirement 4. NETBACKUP OPERATIONS MANAGER (NOM) 12 12 13 14
Page 2 of 16
Page 3 of 16
2.1
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
Page 4 of 16
2.2
2.2.1.
Page 5 of 16
2.2.2.
Chennai Rack - II
<
>
Page 6 of 16
2.4
Sr No
1 2 3 4 5 6 7 8 9 10 11 12 13
CHNVSNSMBK001 CHNVSNSMNM001 CHNVSNRSMT001 CHNVSNRSMT002 CHNVSNTSMT001 CHNVSNPMMT001 CHNVSNPMMT002 CHNVSNDVMT001 CHNVSNDVMT002 CHNVSNCMMT001 CHNVSNRTMT001 CHNVSNTSMT002 CHNVSNTSMT003
Veritas NetBackup Master server #1 Veritas NOM server RSM / CCM / RT RSM / CCM / RT (Redundant) Cold / Test server BMC Performance Manager suite BMC Performance Manager suite (Redundant) BMC DashBoard suit & Visualis BMC DashBoard suit & Visualis (Redundant) BMC Configuration Manager for servers (Bundle) + AlarmPoint BMC Patrol and Performance Manager Reporting + Reporting Studio Cold / Test server Cold / Test server
10.32.128.10 10.32.128.11 10.72.217.25 10.72.217.26 10.72.217.27 10.72.217.30 (28,29) 10.72.217.33 (31,32) 10.72.217.36 (34,35) 10.72.217.39 (37,38) 10.72.221.13 5 10.72.221.13 8 (136,137) 10.72.221.14 1 (139,140) 10.72.221.14 4 (142,143)
10.32.130. 31 10.32.130. 32 10.32.128.12 10.32.128.13 10.32.128.14 10.32.128.15 10.32.128.16 10.32.128.17 10.32.128.18 10.32.128.19 10.32.128.20 10.32.128.21 10.32.128.22
2.5
Sr.No
1 2 3 4 5 6 7
Veritas NetBackup Master server #1 Cold / Test server Cold / Test server RSM / CCM / RT RSM / CCM / RT Cold /Test Server Cold /Test Server
Page 7 of 16
2.6
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 1 2 3 Schedule Name Daily Weekly Monthly Backup Type Incremental Full Full Retention Period 2 Week 1 Month 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 Chennai Policy name Description CHNVSN_SYS Backup of Shadow_Copy_Components for "server" CHNVSN_FS Backup of All_Local_Drives for "server" CHNVSN_SQL_DB Backup of SQL db's for "server" CHNVSN_Linux_App Backup of Linux for "server" CHNVSN_Sun_App Backup of Sun for "server"
S/N 1 2 3 4 5
S/N 1 2 3 4 5
Naming convention for NetBackup Policies AT Singapore Policy name Description SGPVSN_SYS Backup of Shadow_Copy_Components for "server" SGPVSN_FS Backup of All_Local_Drives for "server" SGPVSN_SQL_DB Backup of SQL db's for "server" SGPVSN_Linux_App Backup of Linux for "server" SGPVSN_Sun_App Backup of Sun for "server"
Page 8 of 16
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 Volume Description Pool Day of run Daily backup of the "Backup Selection" Daily Mon to Sat Weekly backup of the "Backup Selection" Weekly Sunday First Sunday of Monthly backup of the "Backup Selection" Monthly the month
S/N 1 2 3
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.
Sr No
Server Name
1 2 3 4 5 6 7 8 9 10 11 12 13
Chennai CHNVSNSMBK001 CHNVSNSMNM001 CHNVSNRSMT001 CHNVSNRSMT002 CHNVSNTSMT001 CHNVSNPMMT001 CHNVSNPMMT002 CHNVSNDVMT001 CHNVSNDVMT002 CHNVSNCMMT001 CHNVSNRTMT001 CHNVSNTSMT002 CHNVSNTSMT003 2.8.2.
Veritas NetBackup Master server #1 Veritas NOM server RSM / CCM / RT RSM / CCM / RT (Redundant) Cold / Test server BMC Performance Manager suite BMC Performance Manager suite (Redundant) BMC DashBoard suit & Visualis BMC DashBoard suit & Visualis (Redundant) BMC Configuration Manager for servers (Bundle) + AlarmPoint BMC Patrol and Performance Manager Reporting + Reporting Studio Cold / Test server Cold / Test server
W2003 SP1 W2003 SP1 W2003 SP1 W2003 SP1 W2003 SP1 Solaris 10 Solaris 10 Solaris 9 Solaris 9 W2003 SP1 Solaris 10 Solaris 10 Solaris 10
LAN LAN LAN LAN LAN LAN LAN LAN LAN LAN LAN LAN
Sr.No
Server Name
Description
W2003
SUN Solaris
1 2 3
Veritas NetBackup Master server #1 Cold / Test server Cold / Test server
Page 9 of 16
4 5 6 7
RSM / CCM / RT RSM / CCM / RT Cold /Test Server Cold /Test Server
2.9
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. S/N Backup Selection for Chennai Servers Hostname AT Chennai NetBackup Role Master/Media server Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) NetBackup Version Backup Selections SYS (Daily, Weekly, Monthly), C:\, D:\, E:\, (Weekly), NBU_Catalog (Daily) SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES < > < > < > SYS < > < > < >
1 2 3 4 5 6 7 8 9 10 11 12 13 2.9.2. S/N
CHNVSNSMBK001 CHNVSNSMNM001 CHNVSNRSMT001 CHNVSNRSMT002 CHNVSNTSMT001 CHNVSNPMMT001 CHNVSNPMMT002 CHNVSNDVMT001 CHNVSNDVMT002 CHNVSNCMMT001 CHNVSNRTMT001 CHNVSNTSMT002 CHNVSNTSMT003
6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4
Backup Selection for Singapore Servers Hostname At Singapore NetBackup Role Master/Media server Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) Client (LAN) NetBackup Version Backup Selections
1 2 3 5 6 7 8
6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4 6.0 MP4
Full Root backup (Weekly), NBU_Catalog (Daily) SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES SYS, ALL_LOCAL_DRIVES < > < >
Legend : ALD - ALL_LOCAL_DRIVES SYS - SHADOW_COPY_COMPONENTS (Daily, Weekly and Monthly) Root - < >
Page 10 of 16
1 2 3 4 5 6 7 8 9 10 11 12 13
CHNVSNSMBK001 CHNVSNSMNM001 CHNVSNRSMT001 CHNVSNRSMT002 CHNVSNTSMT001 CHNVSNCMMT001 CHNVSNPMMT001 CHNVSNPMMT002 CHNVSNDVMT001 CHNVSNDVMT002 CHNVSNRTMT001 CHNVSNTSMT002 CHNVSNTSMT003
CHNVSNMBK001_CAT CHNVSN_SYS CHNVSN_FS CHNVSN_SYS CHNVSN_FS CHNVSN_SYS CHNVSN_FS CHNVSN_SYS CHNVSN_FS CHNVSN_SYS CHNVSN_FS CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr CHNVSN_SUN_Full CHNVSN_SUN_Incr
<
Root
<
Root
<
Root
<
Root
<
Root
<
Root
<
Page 11 of 16
2.10.2.
S/N
Hostname
1 2 3 4 5 6 7
SGPVSNMBK001_CAT SGPVSN_SYS SGPVSN_FS SGPVSN_SYS SGPVSN_FS SGPVSN_SYS SGPVSN_FS SGPVSN_SYS SGPVSN_FS SGPVSN_SYS SGPVSN_FS SGPVSN_SUN_Full SGPVSN_SUN_Incr
Page 12 of 16
Size of full backups = 100 gigabytes * 4 * 6 months = 2.4 terabytes Size of incremental backups = (20% of 100 gigabytes) * 30 * 1 month = 600 gigabytes Total data tracked = 2.4 terabytes + 600 gigabytes = 3 terabytes NetBackup catalog size = 2% of 3 terabytes= 60 gigabytes
3.2
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 above Formula can be expanded to Number 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 terabytes Size of incremental backups = (20% of 500 gigabytes) * 30 * 1 month = 3 terabytes Total data tracked = 12 terabytes + 3 terabytes = 15 terabytes Solution : Tape drive type = LTO gen 3 Tape capacity without compression = 400 gigabytes Tape capacity with compression = 800 gigabytes Without compression: Tapes needed for full backups = 12 terabytes/400 gigabytes = 30 Tapes needed for incremental backups = 3 terabytes/400 gigabytes = 7.5 ~= 8 Total tapes needed = 30 + 8 = 38 tapes With 2:1 compression: Tapes needed for full backups = 12 terabytes/800 gigabytes = 15 Tapes needed for incremental backups = 3 terabytes/800 gigabytes = 3.75 ~= 4 Total tapes needed = 15 + 4 = 19 tapes
Page 13 of 16
Page 14 of 16
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 CPUs 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 SP4 o Microsoft Windows 2003 SP1 o Solaris 8 o 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.
Page 15 of 16
Page 16 of 16