Introduction to Netbackup

Veritas Product Symantec took over veritas 70 to 80% of companies world wide use Versions->5.1 to 6.5.37,7.01 GUI and CLI

4 Tier Architecture of Netbackup

1st tier Netbackup Client(MLAs) 2nd tier Media Server(Cabinet Ministers) 3rd tier Master Server(CM) 4th tier Global Data Manager(PM)

Hardware compatibility list: http://seer.entsupport.symantec.com/docs/33 6875.htm

Netbackup Client
During the backup or archive,the client system generates the backup as a data stream and sends it across the network to the media server. Therefore, our target is the client whose data needs to be backed up or restored MS SQL Agent comes free with Netbackup client

Media Server
To increase performance by providing additional processing ability and better distribution of workload (Load balancing). Note: Tape libraries are always attached to the media server only

Master Server
Master Server is netbackups central brain, providing centralised operations and management to any media server and clients

Global Data Manager

GDM organises the span geographics and provides the ability to perform backup and recovery operations from various locations.

ARCHIVE BIT
The archive bit is a binary bit. As such, it is either 1 or 0, also frequently called set (1) and clear or reset (0). It represents whether the file has (1) or has not (0) changed since the last backup.

Types of Backup
Full (Archive bit is reset) Differential Incremental (Changes since the latest backup, archive bit is reset) [Incremental] Cumulative Incremental(Changes since the last full backup) Archive Backup (Delete data from source after backup leaving behind the metadata ,eg:Oracle archive log backup) User Initiated Backup (Backup window is 24x7)

Vault
Vault job initiates duplicate backup jobs. One for onsite and another for offsite Ejects the filled tapes from the tape library Automatically sends email to Iron mount and backup admins stating the scratch set tape details and tapes which need to be reloaded License is very costly.

NetBackup Catalog
NetBackup catalogs are internal databases that contain information about NetBackup backups and configuration. Backup information includes records of the files that have been backed up and the media on which the files are stored. The catalogs also contain information about the media and storage devices. NetBackup requires the catalog information in order to restore backups so it is extremely important to configure a catalog backup before using NetBackup for regular client backups, and to schedule the catalog backups to occur on a regular basis thereafter. Without regular catalog backups, you risk losing your regular backups if there is a problem with the disk that contains the catalogs.

Parts of the Catalog

The NetBackup catalog resides on the disk of the NetBackup master server. The catalog consists of the following parts: Image Database: The image database contains information about what has been backed up. It is by far the largest part of the catalog. [c:\prog files\veritas\netbackup\db\] NetBackup Relational Database: This includes the media and volume data describing media usage and volume information which is used during the backups. [c:\prog files\veritas\volmgr\database] NetBackup configuration files: Policy, schedule and other flat files used by NetBackup.[ c:\prog files\veritas\netbackup\var\]

Netbackup Management
Host Properties Master Server Media Server Clients ->Double click to check network connectivity

Media and Device Management

Device Monitor -> Lists Tape drives and Robots Media->Robot Type->TLD (In tape lib) or none (Offsite) Media->Volume Pools->Default 4 Pools

NOTE
Media ID:- is a 6 digit alphanumeric & usually a media has a barcode. Media>Robots (RC)>Robot Inventory>Update Volume config->Start

Frozen,Suspend,Import,Duplicate
Frozen tape:-Media Manager will auto freeze a media if the backup cant use it after 3 attempts. Incase of media errors 83,84,86,we freeze the media. Unfreeze later. Suspend:-It means that Netbackup won't write any new data to that tape, until all data on it expires. It will then be available for re-use. Expire:-Data on media will be removed but the image (index) will remain until the tape is overwritten Duplicate:-Medias sent offsite.Backup done using either vault/duplicate backup option. Import:-catalog db(index/image) from tape when server crashes and needs restoration

Volume Pool
Definition:-Volume Pool is a set of volumes from which netbackup can draw or take volumes when performing backup Group of tapes -Volume/Cartridge/media/tape A volume pool identifies a logical set of volumes by type of usage. Associating volumes with a volume pool protects them from access by unauthorized users, groups, or applications. With the exception of the volume pools that are automatically created by NetBackup, you must create a volume pool before you can add volumes to a volume pool. The following volume pools are automatically created (see Volume Pools List): NetBackup, created by Media Manager, for NetBackup use. DataStore, created by NetBackup, for DataStore use. CatalogBackup, created by NetBackup, for NetBackup catalog backups. During initial configuration, it is easiest to create all of your volume pools first. Then as you add volumes, you can assign them to volume pools. It is also possible to configure a scratch pool from which Media Manager can transfer volumes, when a volume pool has no volumes available. If the volume pool will contain WORM media, see Using WORM Volume Pools to Manage WORM Media for more information.

Default Volume Pools

None -> Cleaning Tapes are present Netbackup ->Brand new tapes go to netbackup volume pool after inventory DataStore Catalog Backup Volume Pool which need to be created Scratch Pool :-Needs to be created so that expired tape medias which can be reused come to the scratch pool.

Volume Groups
Volume Groups is a physical location for a media. It manages a group of tapes for purpose of admin actions that allows movement of tapes from slots to drive and vice versa. Rules for Assigning Volume Groups The following are the rules for assigning volume groups: All volumes in a group must be the same media type. However, a media type and its corresponding cleaning media type are allowed in the same volume group (for example, DLT and DLT_CLN). All volumes in a robotic library must belong to a volume group. You cannot add volumes to a robotic library without specifying a group or having Media Manager generate a name for the group. The only way to clear a volume group name is to move the volume to standalone and not specify a volume group. More than one volume group can share the same location. For example, a robotic library can contain volumes from more than one volume group and you can have more than one standalone volume group. All volumes in a group must be in the same robotic library or be standalone. That is, Media Manager will not let you add a group (or part of a group) to a robotic library, if it already exists in another robotic library.