Veritas NBU 5.

0 Training
Ramesh N - ISDU

2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Netbackup 5.0 Fundamentals

At

the end of this module :

Able to describe the architecture of NBU 5.0 Identify the components of NBU 5.0 Relate with various terminologies of NBU Perform basic installation of NBU

Netbackup is
A

distributed backup application

Designed for enterprise backup and disaster recovery Supports Unix, Windows, PC, MacOS, Novell LAN Server Backs-up File systems, Disk Images, all major database applications live
Has

integrated Robotic and Volume Management

Supports all major tape library devices in the market Enables lights-out operation of backup

Netbackup consists of Two applications: 1. Media manager 2. NetBackup

Netbackup 5.0 Architecture concepts

NBU

Has a 3 tier architecture

NetBackup Master Server NetBackup Global Data Manager

NetBackup Media Servers

NetBackup Clients/ Agents

NetBackup uses a three-tier architecture, consisting of 1) the NetBackup MASTER Server, 2) one or more NetBackup MEDIA Server(s), and 3)NetBackup CLIENTS. NetBackup MASTER Server A NetBackup backup domain contains a single MASTER Server. The MASTER Server can be a UNIX (many OS flavors) or WindowsNT platform. The MASTER Server houses the majority of NetBackup Configuration information. The MASTER Server runs the backup scheduler which is responsible for executing automatic backups. The MASTER Server is responsible for writing backup data to tape (during backups) and reading backup data from tape (during restores), and for maintaining the database(s) which track the location and contents of all backups. NetBackup Media (Slave) Server A NetBackup backup domain includes one or more NetBackup MEDIA Servers. The MEDIA Server(s) can be any mixture of UNIX (many OS flavors) or WindowsNT platforms. A NetBackup MEDIA Server is simply a destination to which a backup can be written. The primary functions of a NetBackup Media Server is to provide the interface to STORAGE DEVICES (magnetic disk drives, magnetic tape drives, or optical disk drives), and to maintain a database of removable storage MEDIA (magnetic tapes or optical disks) NetBackup Clients A NetBackup CLIENT is any system which will be backed by NetBackup software. NetBackup supports a wide range of UNIX, NT, Mac, OS2, Novell client platforms.

Global Data Manager A software product that uses a Java Interface to administer multiple NetBackup domains (Master servers)

Supported Server Platforms

Master Server

Media Server(s)

Auspex Digital UNIX Digital OSF/1 HP-UX IBM AIX NCR UNIX

Pyramid DCOSx, Reliant UNIX Sequent DYNIX/ptx Silicon Graphics IRIX SunOS4 Sun Solaris2 Windows NT (Intel & Alpha) ..and more

Every NBU configuration has at least one server, the MASTER. The platform which is acting as the NetBackup MASTER Server can also be a NetBackup MEDIA Server. The number of additional MEDIA Servers in a backup domain is virtually unlimited. The NetBackup Servers can run on any mixture of supported operating systems. The list of supported NetBackup Server platforms changes (is added to) regularly. Consult the NetBackup supported platform matrix for the most up-todate information. http://deptwebs.veritas.com/prodman/products/

Supported NetBackup client Platforms

Apple Macintosh Auspex Cray UNICOS DG-UX Digital OSF/1, UNIX (alpha) Digital VMS HP-UX IBM AIX IBM OS/2 Warp Motorola SVRx NCR UNIX NCR SVR4MP-RAS Network Appliance (client=server) Novell NetWare Pyramid DCOSX Pyramid Reliant UNIX Red Hat - Linux Sequent DYNIX/ptx SGI IRIX Sun Solaris2 Sun Solaris x86 SunOS4 Windows 2k, 2k3, NT, 95, 98, 3.1 and more being added

The list of platforms that can be backed-up by NetBackup (can run the NetBackup CLIENT software) is substantial. This list is changing (being added to) on a regular basis. Be sure to check the current product support matrix for current information.

Media Manager Architecture

Two

Separate applications

Netbackup Media Manager

Must

be the same version (On all servers) on the same CD-ROM

Clients may be of older version

Distributed

Solaris CD UNIX (non-solaris) Windows CD

The applications dont install separately and dont have a separate executable, it is all built into the NBU application itself. The reason for splitting these two application is due to the fact that other Veritas applications such as VxVM, VxCS,

Netbackup Architecture Explanation

Defines backup details: who, when, what, where NetBackup scheduler initiates automated backups scheduler Accepts/Processes requests -User backups/restores Maintains database(s) which track location/contents of all database(s) backups Writes/Reads tape labels Reads from client/writes to media - during backups Reads from media/writes to client - during restores Provides administrative interfaces/tools Communicates with Media Manager for device/media requests

Media Manager Architecture

Provides interface/control of Storage Devices (tape drives, optical drives) Provides Media (removable) Management tracks location/status of volumes in Volume Database volumes Provides interface to applications which require its services its (NetBackup and Storage Migrator) Migrator) Provides administrative interfaces Receives requests for media from NetBackup, locates media which meets criteria, determines location of media Controls robotic devices

Media Manager Architecture

3

Tiers

Master Server Media server(s) server(s) Clients

Allows

for scalability of the product features GDM

Optional VxSS

Adds a 4th Tier

(Security Services)

For securing the Netbackup Operations

10

Master Server Architecture

Only One Master Server backup domain domain Houses configuration that defines backups Runs Scheduler that initiates automated backup Accepts/Processes requests for user backup/restore Maintains Databases that tracks location/contents of all backups Provides administrative interfaces/information Communicates with Media Servers to initiate backup/restore

NetBackup and Media Manager support both master server and media servers. A master server manages the NetBackup backups, archives, and restores. Media servers typically provide additional storage by allowing NetBackup to use the storage devices that are attached. A master server has Media Manager software installed. The following point applies only to NetBackup Server. NetBackup master and media server software are both installed on the same host. This is the host where NetBackup is installed. In this case, the host acts as both a master and a media server. All related databases are also located on that host. The following point applies only to NetBackup Enterprise Server. You can have multiple master and media servers in your configuration. Typically a master server controls multiple media servers. You should manage your media servers from the master server point of view.

11

Media Server Architecture

Unlimited (virtually) in a backup domain Receive requests for backups/restores from master server Communicates with Media Manager (on the same System) to select Media for backup/restore Communicates with NBU Client during a backup/restore operation
Received backup DataStream from client on backup writes to storage device (backup) Reads restore DataStream from backup device/media - writes to clients (restore)

Monitors status of storage devices Works in conjunction with NBU Security to control user access to the vmd

Media manager Features -Robotic and Standalone Drive Support In Media Manager, a robot is a peripheral device for the automated mounting and dismounting of volumes in tape drives. A standalone drive is a drive that is not associated with a robot. Media Manager supports a wide range of robots and automates the handling of volumes in these devices. Except for initial setup and loading of tapes or an equipment failure, manual intervention is not required. Visit the VERITAS support web site for a list of the platforms and peripherals that Media Manager supports. -Media handling in standalone drives is also automated to the extent that Media Manager automatically uses the tape that is in a drive, if it is required by NetBackup. Capability to perform automated drive cleaning, based on the TapeAlert feature or a frequency-based cleaning schedule. Cleaning tapes that are configured incorrectly are also recognized.

MediaManager running on NetBackupWindows servers does not support optical disk storage devices. -Media Location Tracking MediaManager maintains a volume database that shows the location of all media (for example, the robot and slot). This information permits Media Manager to find media when it is required to satisfy a request. -Media Statistics Tracking MediaManager keeps a record of statistics that are useful in tracking the useful life of media (for example, an expiration date and the number of times that media has been mounted). -Security Media Manager vmd security works in conjunction with NetBackup authentication/authorization security to control user access to vmd (the NetBackup Volume Manager service). The following are the features: The relationship with NetBackup authentication/authorization security. Controlling user access to vmd (the Media Manager volume daemon). Controlling user access to Media Manager robotic daemons and services. Robot Inventory and Update Media Manager can inventory a robot, provide reports, and update the volume database to match the results of the inventory. This simplifies administration, by permitting you to quickly determine the contents of a robot. This also automates the configuration process. MediaManager can also inventory a robotic library that does not support barcodes or that contains volumes that do not have readable barcodes. In these cases, you use the physical inventory utility (vmphyinv). - Automatic Volume Recognition

12

Media Manager Hosts

Media manager is automatically installed during NBU Installation. Has the following hosts:
Master Server Media servers SAN Media servers
Volume Database host Global Device Database Host

Master Servers NetBackup and Media Manager support both master server and media servers. A master server manages the NetBackup backups, archives, and restores. Media servers typically provide additional storage by allowing NetBackup to use the storage devices that are attached. A master server has Media Manager software installed. The following point applies only to NetBackup Server. NetBackup master and media server software are both installed on the same host. This is the host where NetBackup is installed. In this case, the host acts as both a master and a media server. All related databases are also located on that host. The following point applies only to NetBackup Enterprise Server. You can havemultiplemaster andmedia servers in your configuration. Typically a master server controls multiple media servers. You should manage your media servers from the master server point of view. Media Servers A host with Media Manager software installed and devices attached is termed a media server. The use ofMedia servers can increase system performance by distributing network loads. Media servers can also be referred to as device hosts. Regular media servers are licensed by VERITAS, and can back up their own data or data from other network clients. You can have multiple media servers in your configuration. A media server can also just be a host that provides the robotic control for a robot (known as a robot control host). SAN Media Servers This is a NetBackup Enterprise Server topic. VERITAS also licenses SAN media servers that can only back up their own data to shared drivesno backing up of data residing on other clients is allowed. Volume Database Host A volume database host is a Media Manager host where the volume database is located. This database is the repository for all Media Manager volume configuration information about the media in storage devices. The following point applies only to NetBackup Server. TheMedia Manager volume database is located on the host where NetBackup is installed. The following points apply only to NetBackup Enterprise Server.

13

Clients Architecture

Unlimited number (virtually) in a backup domain domain May (if allowed) request backups/restores (user) user request is directed to the MASTER server Scheduled backups initiated by MASTER server Communicates with MEDIA server during backups and restores Validates connection requests from NetBackup servers Supports compression of backup stream Supports Include/Exclude lists Provides User Interfaces (backup/restore/browse)

14

Topologies

Single NBU Master/Media server

NetBackup MASTER/ MEDIA Server
Tape Library/Drive(s)

Media Manager

NetBackup Clients

Simplest NetBackup Cluster or backup domain. Cluster consists of a single system which acts as both the NetBackup MASTER server and MEDIA server.

15

Topologies

Single NBU Master/Media server

NetBackup MASTER/ MEDIA Server
Tape Library/Drive(s)

Media Manager

NetBackup Clients

Simplest NetBackup Cluster or backup domain. Cluster consists of a single system which acts as both the NetBackup MASTER server and MEDIA server.

16

Topologies

Separate Master Server & Media server

NetBackup MASTER Server NetBackup MEDIA Server

Tape Library/Drive(s)

Media Manager

Media Manager

NetBackup Clients

In this example one system is acting as the NetBackup MASTER server (no attached storage devices for backups) and one system is acting as a NetBackup MEDIA server.

17

Topologies

Master Server and Multiple Media servers

NetBackup MASTER Server NetBackup MEDIA Server
Library/Drive(s)

Media Manager

NetBackup MEDIA Server

Library/Drive(s)

Media Manager

Media Manager

NetBackup Clients

In this cluster example one system is acting as the NetBackup MASTER server (no attached storage devices for backups) and there are multiple systems acting as NetBackup MEDIA servers. The number of MEDIA servers is virtually unlimited. One reason for adding a MEDIA server is to localize the backup traffic on a local network. By backing up client systems to a MEDIA server on the same network, backup traffic is kept of the slower WAN.

18

Topologies

Master Server & Media Servers splitting the Tape drives in a large library
NetBackup MASTER Server

NetBackup MEDIA Server

NetBackup MEDIA Server

Media Manager

Media Manager

Media Manager

NetBackup Clients

This example shows a common technique used in NetBackup clusters, where the drives in a library are split between multiple NetBackup MEDIA severs. DO NOT confuse this with the NetBackup SHARED STORAGE OPTION.

19

Topologies

Tape drive(s) shared between multiple NBU Media servers drive(s)

NetBackup MASTER Server
Tape Drive

Media Manager
NetBackup MEDIA Server
Fiber

NetBackup MEDIA Server

Fiber Hub/Mux/ Switch

Media Manager

Fiber

Media Manager

NetBackup Clients

In this example the tape library is connected to a Fibre channel switch. Multiple Media servers access the same Tape library and Robot.

20

NetBackup Terminology

Images Storage Units Volumes Classes/Backup Policies Netbackup Databases Media Manager Databases

21

NetBackup Image

Is a collection of all backup data from a client stream during a particular backup session
clients backup data
Written with NetBackups gnutar

tar image

tNetBackup Image The collection of all data being backed up from a client during a

particular backup session is called an image. written in with gnutar can be read with tar (unless multiplexed) on most systems name of image is {client_name}_{unix_ctime} information about backup is recorded in the NeBackup Images database, in two files: header file (information about backup) files file (contents of backup) ctimes can be decoded with bpdbm ctime command (example: # bpdbm ctime 0946000893)

22

Storage Unit

Is a Logical destination for backups. Logical

Two StandardTypes: Media Manager - optical or tape drives Disk Third (optional) Type NDMP

NetBackup knows nothing about physical storage devices that is Media Managers job. NetBackup deals with destinations for backups using a concept called the Storage Unit. A Storage Unit is a logical destination to which NetBackup can write a backup. A Storage Unit can contain one or more physical drives. There are a few rules for Storage Units: 1. All tape drives that are members of a Storage Unit must be attached to the same host (NetBackup Media Server). 2. All tape drives that are members of a Storage Unit must be of the same type/density (all DLT, for example). 3. Standalone and robotic drives must be in separate Storage Units. 4. Define a separate Storage Unit for each robot that is attached to a Media Server that controls a drive attached to that Media Server. 5. If a robot controls drives of differing densities you must create a Storage Unit for each each density. There are two standard types of Storage Units: 1. Media Manager Storage Units (those controlled by the Media Manager application) optical or tape 2. Disk Storage Units (which define the use of magnetic disk) which are managed by NetBackup A third type of Storage Unit that is available as an optional (billable) feature is NDMP. VERITAS NetBackup NDMP (Network Data Management Protocol).

23

NetBackup Terminology

Volume - removable media (tape or optical). An optical platter is actually two actually volumes because it can be written on either side - each side being defined as a volume. volume Volume Pool - a set (bunch, pile) of volumes defined for a specific purpose. Example: volumes that are defined to house backups from the engineering engineering group workstations. Volume Pools are not defined by geography. Tapes that belong to the same pool can be located in several robotic libraries and/or libraries standalone. Volume Group - tapes that are defined by their location (geography). Example: All the tapes that are housed in the same tape carrier. This tape carrier can be tape carrier extracted from/inserted into a tape library, thus inserting/extracting a group of inserting/extracting group tapes all at once.

24

Volumes
A00001 A00002 Media ID
(1 to 6 characters in length)

B00001 B00002

Volume
Each volume has an entry in the Volume Database (vsnDB/volDB). This entry is created at the time the Volume is created. The entry for the volume is modified when the volume is moved,modified, or deleted by the administrator, or automatically by Media Manager when a volume is assigned or un-assigned. evsn external volume serial number rvsn - recorded volume serial number A00006 Volumes are created and managed through the use of: vmadm, xvmadm, jnbSA-Media and Device Management (Java GUI in v3.2) B00006

A00003

B00003

A00004 A00005

B00004 B00005

25

Volume Pools
Volume Group
A00001 A00002

Volumes Pools

Volume Group
B00001 B00002

Pool engpool

A00003

B00003

A00004 A00005

B00004 B00005

Pool oracle
A00006 B00006

Volume Pools are created through the use of: vmadm, xvmadm, jnbSA-Media and Device Management (Java GUI in v3.2) Each pool has an entry in the Media Manager database file poolDB. As Volumes are created they are assigned to an existing pool. UNASSIGNED Volumes may be moved between pools.

26

Backup Class/Policy
List

of parameters that defines the details of how backups will be performed main components:
Attributes Where (destination), other Client List Who (will be backed up?) Schedules When (will backups occur?) Files List What (will be backed up?)

Four

Unlimited

number of classes in a NetBackup

domain
Classes/Backup

Policies (in NT) only exist/defined on the NetBackup MASTER Server

After NBU 4.5 the word Classes has been discontinued and it has been standardized on Policies. Backup policies define the rules that NetBackup follows when backing up clients. A backup policy can apply to one or more clients. Every client must be covered by at least one backup policy. The best approach to configuring backup policies is to divide clients into groups according to their backup and archiving requirements, then create a policy for each group.

27

Netbackup Databases
Located in <install path>/openv/netbackup/db class ** config ** error < >openv/netbackup/db jobs
** this database will be kept only on the NetBackup Master server * this database will be exist on ALL NetBackup Media servers (which may include the Master)

** **

images ** media *

The directory tree in <install_path>/openv/netbackup/db contains the following directories: class - contains a directory for each NetBackup class. These directories contain the details (who, what, when, where) of how backups will be accomplished. config - contains the global NetBackup configuration parameters and the definition of storage_units used by NetBackup to perform backups. error - contains the daily logs keep by NetBackup. These logs are used to create a number of NetBackup reports. Not to be confused with debug logs. jobs - contains information about the NetBackup backup/restore jobs. These files are referenced by the NetBackup Job Monitor GUI interface. images - directory which contains a sub-directory for each NetBackup client that has executed a backup. Contained within the images directory structure are files which contain information about each backup image and files that contain the list of files backed up during each backup job. media - contains a file (mediaDB) which contains a record for each media ID which has been assigned to NetBackup on a particular Media Server. This record contains information about each image that has been written to the media ID. The mediaDB file is present on each NetBackup Media Server which has written images that have not yet expired. The mediaDB file represents information about those media IDs which have been used on this media server.

28

Media Manager Databases

Located in <install path>/openv/volmgr/database

ltidevs * robotic_def *
<>openv/volmgr/database

volDB **

* these two files comprise the devices database for Media Manager. The files will exist on each NetBackup Media Server on which tape or optical drives are configured. ** this is the VOLUME DATABASE. When NetBackup/Media Manager is properly setup the Volume Database should be maintained only on the NetBackup MASTER SERVER.

The directory tree in <install_path>/openv/netbackup/db contains the following directories: class - contains a directory for each NetBackup class. These directories contain the details (who, what, when, where) of how backups will be accomplished. config - contains the global NetBackup configuration parameters and the definition of storage_units used by NetBackup to perform backups. error - contains the daily logs keep by NetBackup. These logs are used to create a number of NetBackup reports. Not to be confused with debug logs. jobs - contains information about the NetBackup backup/restore jobs. These files are referenced by the NetBackup Job Monitor GUI interface. images - directory which contains a sub-directory for each NetBackup client that has executed a backup. Contained within the images directory structure are files which contain information about each backup image and files that contain the list of files backed up during each backup job. media - contains a file (mediaDB) which contains a record for each media ID which has been assigned to NetBackup on a particular Media Server. This record contains information about each image that has been written to the media ID. The mediaDB file is present on each NetBackup Media Server which has written images that have not yet expired. The mediaDB file represents information about those media IDs which have been used on this media server.

29

Media Manager Databases

30

Module Review
NetBackup Media Manager Versions 3-Tier Architecture Master Server Media Server Cients Images Volumes Pools Storage Units Backup Policy/Class Databases

31

Learning Check

32

33