1

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

Veritas NBU 5.0Training

Ramesh N - ISDU

2

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

3

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 manager2. NetBackup

4

Netbackup 5.0 Architecture concepts• NBU Has a 3 tier architecture

NetBackup Master NetBackup Master ServerServer

NetBackup NetBackup Clients/Clients/AgentsAgents

NetBackup NetBackup Media ServersMedia Servers

NetBackup Global NetBackup Global Data ManagerData Manager

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 ServerA 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) ServerA 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 ClientsA 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 ManagerA software product that uses a Java Interface to administer multiple NetBackup domains (Master servers)

5

Supported Server PlatformsMaster ServerMaster Server

Media Server(s)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-to-date information.

http://deptwebs.veritas.com/prodman/products/

6

Supported NetBackup client PlatformsApple 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.

7

Media Manager Architecture•Two Separate applications

•Netbackup•Media Manager

•Must be the same version (On all servers)•Clients may be of older version

•Distributed on the same CD-ROM•Solaris CD•UNIX (non-solaris)•Windows CD

The applications don’t install separately and don’t 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,

8

Netbackup Architecture Explanation•• Defines backup details: who, when, what, whereDefines backup details: who, when, what, where•• NetBackup NetBackup ‘‘schedulerscheduler’’ initiates automated backupsinitiates automated backups•• Accepts/Processes requests Accepts/Processes requests --User backups/restoresUser backups/restores•• Maintains Maintains database(sdatabase(s) which track location/contents of all ) which track location/contents of all

backupsbackups•• Writes/Reads tape labelsWrites/Reads tape labels•• Reads from client/writes to media Reads from client/writes to media -- during backupsduring backups•• Reads from media/writes to client Reads from media/writes to client -- during restoresduring restores•• Provides administrative interfaces/toolsProvides administrative interfaces/tools•• Communicates with Media Manager for device/media Communicates with Media Manager for device/media

requestsrequests

9

Media Manager Architecture•• Provides interface/control of Storage Devices (tape drives, Provides interface/control of Storage Devices (tape drives,

optical drives)optical drives)•• Provides Media (removable) Management tracks Provides Media (removable) Management tracks

location/status of location/status of ‘‘volumesvolumes’’ in Volume Databasein Volume Database•• Provides interface to applications which require itsProvides interface to applications which require its’’ services services

(NetBackup and Storage (NetBackup and Storage MigratorMigrator))•• Provides administrative interfacesProvides administrative interfaces•• Receives requests for media from NetBackup, locates media Receives requests for media from NetBackup, locates media

which meets criteria, determines location of mediawhich meets criteria, determines location of media•• Controls robotic devicesControls robotic devices

10

Media Manager Architecture•• 3 3 –– TiersTiers

•• Master ServerMaster Server•• Media Media server(sserver(s))•• ClientsClients

•• Allows for scalability of the productAllows for scalability of the product•• Optional features Optional features –– GDMGDM

•• Adds a 4Adds a 4thth TierTier

•• VxSSVxSS (Security Services)(Security Services)•• For securing the Netbackup OperationsFor securing the Netbackup Operations

11

Master Server Architecture•• Only One Master Server Only One Master Server ‘‘backup domainbackup domain’’•• Houses configuration that defines backupsHouses configuration that defines backups•• Runs Scheduler that initiates automated backupRuns Scheduler that initiates automated backup•• Accepts/Processes requests for user backup/restoreAccepts/Processes requests for user backup/restore•• Maintains Databases that tracks location/contents of all Maintains Databases that tracks location/contents of all

backupsbackups•• Provides administrative interfaces/informationProvides administrative interfaces/information•• Communicates with Media Servers to initiate backup/restoreCommunicates with Media Servers to initiate backup/restore

NetBackup and Media Manager support both master server and mediaservers. A masterserver manages the NetBackup backups, archives, and restores. Media servers typicallyprovide additional storage by allowing NetBackup to use the storage devices that areattached.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.

12

Media Server Architecture•• Unlimited (virtually) in a backup domainUnlimited (virtually) in a backup domain•• Receive requests for backups/restores from master serverReceive requests for backups/restores from master server•• Communicates with Media Manager (on the same System) Communicates with Media Manager (on the same System)

to select Media for backup/restoreto select Media for backup/restore•• Communicates with NBU Client during a backup/restore Communicates with NBU Client during a backup/restore

operationoperation•• Received backup DataStream from client on backup Received backup DataStream from client on backup –– writes to writes to

storage device (backup)storage device (backup)•• Reads restore DataStream from backup device/media Reads restore DataStream from backup device/media -- writes to writes to

clients (restore)clients (restore)

•• Monitors status of storage devicesMonitors status of storage devices•• Works in conjunction with NBU Security to control user Works in conjunction with NBU Security to control user

access to the access to the vmdvmd

Media manager Features-Robotic and Standalone Drive Support

In Media Manager, a robot is a peripheral device for the automated mounting anddismounting of volumes in tape drives. A standalone drive is a drive that is notassociated with a robot.Media Manager supports a wide range of robots and automates the handling ofvolumes in these devices. Except for initial setup and loading of tapes or anequipment failure, manual intervention is not required.

Visit the VERITAS support web site for a list of the platforms and peripherals thatMedia 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 storagedevices.-Media Location Tracking

MediaManager maintains a volume database that shows the location of all media (forexample, the robot and slot). This information permits Media Manager to find mediawhen it is required to satisfy a request.

-Media Statistics TrackingMediaManager 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).

-SecurityMedia 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 UpdateMedia 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

13

Media Manager Hosts•• Media manager is automatically installed during NBU Media manager is automatically installed during NBU

Installation.Installation.•• Has the following hosts:Has the following hosts:

•• Master ServerMaster Server•• Media serversMedia servers•• SAN Media serversSAN Media servers

•• Volume Database hostVolume Database host•• Global Device Database HostGlobal Device Database Host

Master ServersNetBackup 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 ServersA host with Media Manager software installed and devices attached is termed a media server. The use ofMediaservers 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 (knownas a robot control host).

SAN Media ServersThis is a NetBackup Enterprise Server topic.VERITAS also licenses SAN media servers that can only back up their own data to shared drives—no backing up of data residing on other clients is allowed.

Volume Database HostA 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.

14

Clients Architecture•• Unlimited number (virtually) in a Unlimited number (virtually) in a ‘‘backup domainbackup domain’’•• May (if allowed) request backups/restores (user) May (if allowed) request backups/restores (user) –– user user

request is directed to the MASTER serverrequest is directed to the MASTER server•• Scheduled backups initiated by MASTER serverScheduled backups initiated by MASTER server•• Communicates with MEDIA server during backups and Communicates with MEDIA server during backups and

restoresrestores•• Validates connection requests from NetBackup serversValidates connection requests from NetBackup servers•• Supports compression of backup streamSupports compression of backup stream•• Supports Include/Exclude listsSupports Include/Exclude lists•• Provides User Interfaces (backup/restore/browse)Provides User Interfaces (backup/restore/browse)

15

Topologies•• Single NBU Master/Media serverSingle NBU Master/Media server

Tape Library/Drive(s)NetBackupMASTER/

MEDIAServer

MediaManager

NetBackup NetBackup ClientsClients

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•• Single NBU Master/Media serverSingle NBU Master/Media server

Tape Library/Drive(s)NetBackupMASTER/

MEDIAServer

MediaManager

NetBackup NetBackup ClientsClients

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

17

Topologies•• Separate Master Server & Media serverSeparate Master Server & Media server

Tape Library/Drive(s)NetBackup

MEDIAServer

MediaManager

NetBackup NetBackup ClientsClients

NetBackupMASTER

Server

MediaManager

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.

18

Topologies…•• Master Server and Multiple Media serversMaster Server and Multiple Media servers

NetBackup NetBackup ClientsClients

NetBackupMASTER

Server

MediaManager

Library/Drive(s)NetBackupMEDIAServer

MediaManager

Library/Drive(s)NetBackupMEDIAServer

MediaManager

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.

19

Topologies…•• Master Server & Media Servers splitting the Tape drives in a Master Server & Media Servers splitting the Tape drives in a

large librarylarge library

NetBackup NetBackup ClientsClients

NetBackupMEDIAServer

MediaManager

NetBackupMEDIAServer

MediaManager

NetBackupMASTER

Server

MediaManager

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’.

20

Topologies…•• Tape Tape drive(sdrive(s) shared between multiple NBU Media servers) shared between multiple NBU Media servers

NetBackup NetBackup ClientsClients

NetBackupMEDIAServer

MediaManager

NetBackupMEDIAServer

MediaManager

NetBackupMASTER

Server

MediaManager

Fiber Fiber

Fiber Hub/Mux/Switch

Tape Drive

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

21

NetBackup Terminology•• ImagesImages•• Storage UnitsStorage Units•• VolumesVolumes•• Classes/Backup PoliciesClasses/Backup Policies•• Netbackup DatabasesNetbackup Databases•• Media Manager DatabasesMedia Manager Databases

22

NetBackup Image•• Is a collection of all backup data from a client stream during Is a collection of all backup data from a client stream during

a particular backup sessiona particular backup session

client’s backup

data

Written with NetBackup’s

‘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)

23

Storage Unit•• Is a Is a –– ‘‘LogicalLogical’’ destination for backups.destination for backups.

Two StandardTypes:ØMedia Manager - optical or tape drivesØDiskThird (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 tape2. 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).

24

NetBackup Terminology•• Volume Volume -- removable media (tape or optical). An optical platter is actuallremovable media (tape or optical). An optical platter is actually two y two

volumes because it can be written on either side volumes because it can be written on either side -- each side being defined as a each side being defined as a ‘‘volumevolume’’..

•• Volume PoolVolume Pool -- a set (bunch, pile) of volumes defined for a specific purpose. a set (bunch, pile) of volumes defined for a specific purpose. Example: volumes that are defined to house backups from the engExample: volumes that are defined to house backups from the engineering ineering group workstations. Volume Pools are not defined by geography. group workstations. Volume Pools are not defined by geography. Tapes that Tapes that belong to the same pool can be located in several robotic librarbelong to the same pool can be located in several robotic libraries and/or ies and/or standalone.standalone.

•• Volume GroupVolume Group -- tapes that are defined by their location (geography). Example:tapes that are defined by their location (geography). Example:All the tapes that are housed in the same tape carrier. This taAll the tapes that are housed in the same tape carrier. This tape pe ‘‘carriercarrier’’ can be can be extracted from/inserted into a tape library, thus inserting/extrextracted from/inserted into a tape library, thus inserting/extracting a acting a ‘‘groupgroup’’ of of tapes all at once.tapes all at once.

25

Volumes

Each volume has an entry in the Volume Database (vsnDB/volDB). This entry is created at the time theVolume 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

Volumes are created and managed through the use of:vmadm, xvmadm, jnbSA-Media and Device Management (Java GUI in v3.2)

A00001

A00002

A00003

A00004

A00005

A00006

B00001

B00002

B00003

B00004

B00005

B00006

Media ID (1 to 6 characters in length)

Volume

26

Volume PoolsVolumes Pools

A00001

A00002

A00003

A00004

A00005

A00006

B00001

B00002

B00003

B00004

B00005

B00006

Pool “engpool”

Pool “oracle”

Volume Group Volume Group

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.

27

Backup Class/Policy•• List of parameters that defines the details of how List of parameters that defines the details of how

backups will be performedbackups will be performed•• Four main components:Four main components:üüAttributes Attributes –– Where (destination), otherWhere (destination), otherüüClient List Client List –– Who (will be backed up?)Who (will be backed up?)üüSchedules Schedules –– When (will backups occur?)When (will backups occur?)üüFiles List Files List -- What (will be backed up?)What (will be backed up?)

•• Unlimited number of classes in a NetBackup Unlimited number of classes in a NetBackup domaindomain

•• Classes/Backup Policies (in NT) only exist/defined Classes/Backup Policies (in NT) only exist/defined on the NetBackup MASTER Server 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.

28

Netbackup DatabasesLocated in <install path>/openv/netbackup/db

class **

config **

error **

jobs **

images **

media *

< >openv/netbackup/db

** 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)

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 DatabasesLocated in <install path>/openv/volmgr/database

ltidevs *robotic_def *

volDB **

<>openv/volmgr/database

* 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.

30

Media Manager Databases

31

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

32

Learning Check

33