trg template -backup

8/11/2019 Trg Template -Backup

http://slidepdf.com/reader/full/trg-template-backup 1/98

Prepared By - Date –

Netbackup 6.X

TrainingPresenter Name : Aashutosh & Anay

Presenter Division : Storage

Date : 7th March 2011




Backup hardware devices




Tape Library




Tape Library console




Tape drive connectivity




Tapes


http://slidepdf.com/reader/full/trg-template-backup 7/98Prepared By - Date –

Tape Barcodes



IM containers



Demo of Library

http://www.quantum.com/flash/i500/i500.html



5.1 and 6.x Architectural Differences.6.x Architecture in detail.



11

Underlying Database

Management NBU 5.x

NBU 6.0• Product-private data stored in

scattered, for-purpose flat files,

managed with for-purpose code

volDB poolDB ruleDB

globDB mediaDB ltidevs

robotic_def

.namespace.checksum (NDMP)

Storage Units

Vault Containers (attribute of volume)

•Data stored in, and managed

with Sybase ASA, through

VxDBMS, accessed with

standard SQL queries

EMM Database consolidates all media& device data onto the EMM Server,

the Master Server by default



12

Device Configuration and

Communication NBU 5.x

NBU 6.0Device configuration & status

data scattered across multiple

systems requiring Media

Server-to-Media Server

communication

High firewall impact

Consolidated and centralized

configuration & status data.

Media Server-to-Media Server

communication eliminated

except for robotic control needsReduced firewall impact



13

Media and Device Selection

NBU 5.x

NBU 6.0Media & Device selection logic

split across multiple

components

– Media Server & STU by bpsched

– Media by bptm – Tape Drive by ltid/robotic

daemon

Selection handled completely

within EMM

B k P li i I ACL



14

Backup Policies, Images, ACLs,

and Catalogs NBU 5.x NBU 6.0

Backup Policy data stored in for-

purpose filesNo change

Backup Image data stored in for-

purpose files

No change

NetBackup Access Control data

stored in own Sybase ASA

database

No change

NetBackup Catalog Backupindependent of DB client option

No change



NetBackup 6.0 Architecture – Multiple

Tiers

• NetBackup 6.0 uses a multi-tieredarchitecture

1. Master Server

2. Media Server

3. Enterprise Media Manager (EMM) Server

4. Client

• EMM Server was introduced byNetBackup 6.0




NetBackup 6.0 Environment Mappings

The Enterprise Media Manager

(EMM) Server

Can service either one NetBackup6.0 Master

Server or multiple NetBackup 6.0

Master

Servers

Master Server

Media Server

Client

Master Server

Media Server

Client

•Master Server

•Media Server•Client

EMM Server




Environment Mappings: Master /EMM

Server

NetBackup 6.0 Master/

EMM Server

NetBackup 6.0

Media Server

NetBackup 6.0

Media Server

NetBackup 6.0

Clients

NetBackup 6.0

Clients




Default installation path

• Netbackup:

C:\program files\VERITAS\Netbackup

/usr/openv/netbackup




• Media manager

c:\Program Files\VERITAS\volmgr

/usr/openv/volmgr




• EMM

C:\Program Files\VERITAS\NetbackupDB

/usr/openv/var




• License keys

C:\Program Files\VERITAS\Netbakup\var\

/usr/openv/var




• JAVA

C:\Program Files\VERITAS\java

/usr/openv/java




Netbackup Components & 6.X services




Components of netbackup

• Introduction to components of netbackup

6.0




Lessons included

• Master server components

• EMM server components

• Media server components• Client components

• Netbackup admin console

• Netbackup communication




Master server components

• bprd bpjobd-- jobs DB

• Nbnos bpbdm-M Server

catalog

• Nbsl nbjm

• Nbsvcmon nbgenjob

• Bpcompatd nbproxy• Nbpem VERITAS_PBX




Bprd- legacy master server component

• Netbackup req manager

- Runs only on master server , once startedruns continually

- Listens on TCP port 13720

Responsibilities:

Starts database manager[ bpdbm]

Builds netbackup server list

Verifies the netbackup licenses




• Initiates recycling of debug logs, recycles

each day

• Initiates cleaning of the job database

• Enables/allows the policy execution

manager to resume schedulling of jobs




Database manager –bpdbm

- Started initially by bprd at netbackup startup

- Runs only on master server

. Once started runs continually

.listens on the port 13721

--maintains update and queries several

netabckup master server catalogsincluding: images,behaviour,clients,retention levels , syncand others.




Job database manager - bpjobd

• Runs only on master server

- Running dependent upon bpbdm

- Listens at port 13723

- Updates to backup job entries in jobs databse areprovided to bpjobd by the process that is responsible for

the operation

- Queries to the jobs database are initiated by the activity

monitor and/or via bpdbjobs command




Netbackup notification services- nbnos

• It runs as a service/daemon

• Notifies policy execution manager, nbpem, of certain changes as soon as they

occur.• Changes include policy additions, changes

and deletions

• Changes also include image expirationand storage unit additions , changes anddeletions




• As a result of a backup policy change

notification , nbpem will re-evaluate the

‘next due jobs’ worklist

• Backup jobs which have already been

submitted by nbpem to nbjm for execution

are not affected by backup policy

changes.




Bpcompatd-new master server component

• Netbackup compatibility daemon

• Daemon/service used to allow newnetbackup 6.0 daemons/services to

communicate with legacydaemons/processes

-runs as daemon/ service on netbackup 6.0

servers- May be run as a command




Nbpem

• Policy execution manager – nbpem(1)

- Main tasks are to build and maintain the

‘next Due jobs’ worklist and to signal the

job manager , nbjm , when a job is due to

run

- Requests for manual ( immediate )

backups or user –initiated backups resultin a ‘run once’ job being added to the

worklist. Job removed when completed




• Once the ‘next due jobs’ worklist has beencreated nbpem re-evaluates it on an eventdriven basis

- when a backup policy is added, modifiedor removed

- when backup images are expired

- when a job becomes due- when a ‘job try’’is completed




• Nbpem maintains ‘out of window’ timer for

each job

- worklist entries for which ‘ multiple data

streams’ is indicated are a special case

Initially only a parent job entries exists in the

worklist. More on this later in this lesson




Nbpem

• Policy execution manager- nbpem (2)

- Nbpem is started initially by bprd

- Once started nbpem runs continually- if bprd goes down

schedulling of backup jobs by nbpem continues

- If bprd is shutdown by request( normally) , it sends a

request to nbpem to suspend schedulling{ In this case

wen bprd is started manually then it sends a message to

nbpem to resume schedulling}




Nbjm

• Job manager – nbjm- Part of intelligent resource manager(IRM)

- Started by startup scripts

- Runs continuallyon master server system

- Nbjm requires/uses ‘veritas_pbx’to communicate withother IRM/EMM components

- Nbjm handles Job Management for all backup jobs

- Nbjm requests and obtains resources for all jobs

- Nbjm releases these resources when a job is completed




Nbgenjob

• Generic Job- nbgenjob

- Netbackup generic Job- nbgenjob is anIRM process in netbackup 6.0

- Nbgenjob is initiated on the master

server system by the job manager,nbjm




Nbjenjob tasks

• Streams discovery on client for multi-stream backups• Performs snapshot creation/Snapshot deletion

• Runs ‘bmrsavecfg’ when backup policy is configures togather BMR information for a client

• Runs job star/end notify scripts for parents of multi-streaming backups

• Initiates Vault run

• Initiates synthetic backup

• Initiates catalog backups

• Initiates Sharepoint Portal server resolver




EMM Server Components

• Its new to 6.0 release

• Simplified description: the EMM Server is a centralized

group of services which perform the management and

allocation of resources required for all netbackup

operations including backups, restores, duplication ,vaulting, imports , catalog backups and more

• Resources include, but are not limited to, media and

drives- both tape drives and optical disks and drives




EMM server benefits

• - the EMM server replaces functions that

were previously spread across various

components of the master server and

media server system

• This results in the following:

a) Centralized resource management and

allocation avoids conflict which occurreddue to multiple ‘managers’




b) New code which implements EMM is

more efficent than its predecessors ,

removing bottlenecks and therefore

improving performance

c) The EMM database is implemented under

a new database engine providnig the

benefits associated with relationaldatabase mgmt systems




EMM server And Master servers

• EMM Server and Master servers

-An EMM server may provide service to multiple Netbackup

6.0 Masters servers

- It is anticipated that generally an EMM server will provide

resource mgmt and allocation to a single Netbackup 6.0

Master server enviroment

- Each Netbackup master server enviroment may access

one and only one Emm server.




• The master server system (default)

• A media server system

• At some point – Not At 6.0 release – the

EMM server may be installed ona system

independent from other netbackup

functions.




EMM server list components

• nbrb – resource broker

• emmlib – programming interface

• nbemm – enterprise media manager

• emmdb(with DB_dbsrv or dbsrv9) EMM

database server

• Emmdb(NBDB.db) – EMM database

b b tb k




nbrb – netbackuo resource

broker• A component of intelligent resource manager[IRM]• Runs continouslly on EMM server system

• Started by startup script (or by nbsvcmon)

• Uses VERITAS_PBX to communicate with other IRM

components and with EMM service(nbemm)• Uses the new unified logging (VxUL) logging method

• Performs resource allocation for all netbackup activitieswhich require resources – backups , restores,duplication, catalog backups, imports , verifies etc.

lib EMM




emmlib – EMM server

component• emmlib

-- allows for netbackup components writtenin C programming language to access

EMM – which uses a CORBA interface (emmlib provides a ‘C’ wrapper around theCORBA EMM interface)

-- does not generate a debug log – information is written to logs of processeswhich communicate with emmlimb

b EMM




nbemm – EMM server

component• Netbackup enterprise media manager• Runs continouslly as a service on EMM Server system

• Uses VERITAS_PBX to communicate

• Uses new unified logging (VxUL) logging method

• Is the EMM database manager• Maintains device (tape and optical drives) and media

configuration and status, as well as data previouslyassociated with numerous Netbackup and mediamanager 5.x (and earlier) databases/catalog.




nbemm tasks

• Accepts requests for resources form mds and requests

to add/modify/delete/change status of db entries via

GUI/CLIs (via emmlib APIs)

• NB_dbsrv provides interface to EMM database to :

Reserve devices and media( resources) to meet requests

Add/modify/delete resource configuration records

Update device and media status




mds – EMM server component

• Media and device selection ( mds)

NOT a running process requests for

resources from nbrb

Communicates with nbemm to

identify/reserve resources

. De – allocates resources when oprations

are completed.




da – device allocator

• Not a running process ( not a visible with

bpps)

• Monitors drivers via assigned scam

host(s)- via emmlib




Enterprise media manager

• Centralized , relational database

• File is not nbdb.db

• Managed by EMM service(nbemm)

• based upon VERITAS standard multi-platform relationaldatabase defined in the VxDBMS project ( from the

VERITAS shared infrastructure Group – SIG )

• Houses data previously located in NETBACKUP and

Media manager 5.x [previous] databases/catalogs .

MEDIA SERVER




MEDIA SERVER

COMPONENTS• bpbrm – backup /restore manager

• bptm – tape manager

• bpdm – disk manager

• vmd – volume management daemon

• ltid – device manager

• txxd – robotic drive daemon

• txxcd – robotic control daemon

• avrd – auto volume recognition

• oprd – operator request daemon

• vnetd – VERITAS n/w daemon• bpcd – commnicates daemon




bpbrm backup and restore manager

• Manages backup and restore operations• Bpbrm does not continually – is started on a netbackup media

server system as required to perform backup and restore operations

• Nbjm starts bpbrm for single-streamed backup jobs.

• Nbjm starts bpbrm for each stream of multi streamed backup jobs

• Bprd starts bpbrm for restore jobs• -- bpbrm initiates bptm or bpdm for use in backup/restoreoperations[

• -- bpbrm initiates netbackup Client processes for file systembackup/restore operations.

-bpbkar for backups and –tar for restores




Tape manager - bptm

• -bptm does not run continually – it is started as needed

on a netbackup media server system to perform backup

and restore operations ( and other operations ) that

utilize backup and restore operations ( and other

operations) that utilize removable media-tape or opticalmedia

• Bptm is started by bpbrm for backup/restores

• Primary bptm tasks during backups and restores




Disk manager - bpdm

• Bpdm does not run continually – it is started as neededon a netbackup media server system to perform backupand restore operations ( and other operations) that utilizemagnetic DISK media

• Bpdm is started by bpbrm for backup/restores• During backups and restores bpdm writes/reads backup

data to /from disk utilizing the underlying OS and filesystem management software.

• Bpdm is reliant upon ability to perform disk operations

via the Operating System/file system




ltid – media server component

• Device management service/daemon – ltid• Runs on each media server system on which tape and /or optical

drives are configured for netbackup use

In 6.0 the role of ltid has been reduced due ti introduction of the EMMserver and EMM database

ltid obtains status of devices to EMM so that the centralized EMM DBcontains current device status information

ltid recieves requests for mounting/un-mounting of media from bptm.

-- ltid calls appropriate robotic daemons to perform mounts/unmounts




vmd

• Vmd runs on each media server system on which tapeand/or optical drives are configured for netbackup use

• In 6.0 the role of vmd has been reduced due byintroduction of the EMM server/EMM database which

houses information about all removable mediaStarts OPRD and connect to ltid to obatain media

information

Vmd forwards queries/updates for volume information from5.x Media servers to EMM server.




Txxd and txxcd

• Robotic daemons processes• Names vary by the tape of robotic device.

current types: tl4d , tlmd,tl8d/tl8cd,tldd/tldcd,tlhd/tlhcd

Robotic daemons run on a Media server on which devices of that typeare configured

Once started robotic daemons run continually on the media server( untilNetbackup shutdown)

-receives requests for mounting/un-mounting of media from ltid

Communicates to/with robotic devices to perform mount and unmountoperations




avrd

• Automatic volume recognition Daemon

• Controls automatic volume assignment and label

scanning allow media manager to rean labeled tape and

optical disk volumes on standalone drives

• Starts txxcd process to mount and read media label on

robotic drives

• Allows media manager to automatically assign the

associated removable media to requesting processes.




Oprd

• Oprd is started by vmd on Media Server systems• Oprd services the following kinds of requests:

• down/up/reset drives , display drive status

• Deny/re-submit mount requests

• Start/stop ltid , obtain ltid status

• Manage pending actions , assign drives

• Format optical platters

• Clean drives

• Obtain host version and scan shared drives




CLIENT COMPONENTS

• tar

• bmrsavecfg

• vnetd

• bpcd

• bpbkar




bpbkar or bpbkar32

• Initiated on the Netbackup Client System as needed toperform file system backups and archives

• Started by media server backup and restore manager(bpbrm) process

• Generates backup data stream- sends to media server

(bptm/bpdm) to be recorded to backup media• Generates meta-data for backup – sends to media

server . This information is sent to to bpbdm on themaster server which writes it to image database

• Bpbkar may optionally perform software compression

and/or encryption of backup data




tar

Initiated on the netbackup client system as needed toperform file system restores

Started by media server backup and restore manager (bpbrm ) process

Receives data to be restored from media server systemprocess (bptm/bpdm) and writes data to client disk

Tar may perform un-compression and/or decryption of datastream , if data was software compressed and/orencyrpted by the client during the backup operation.




BMR

BMR information gathering process – bmrsavecfg- BMR client software is installed with the netbackup client software

on supported platforms

BMR must be licensed and properly configured ina backup policy inorder for BMR to be sucessfully implemented

Called by new nbgenjob process.Netbackup mount command – bpmount

is a Netbackup Client Process that is used in the STREAMS auto-discovery process to identify configured file systems/mounts pointsand drives

Called by new nbgenjob process , not scheduler.




NetBackup Communications




6.x configuration files




vm.conf




Storage Units




Types of Backup




Media & Device configuration




Backup and Restore




Catalog (off-line & On-line)

C l b k i NBU



Prepared By - Date – 79

Catalog backup in NBU 5.x

• Offline catalog backup

– Single tape solution

• bpbackupdb

– Two steps, multi-tapes solution• Using standard backup to backup all clients’

catalog

• Using bpbackupdb to backup master’s catalog

F t O i




Feature Overview

• This feature is to re-architect the process of NBU catalogbackup

• Why are we doing this feature?

– Officially support Hot backups of the catalog

– Add ability to span tapes

– Allow catalog media management by pool

– Full and Incremental Catalog Backups

– Enable Scheduled Catalog Backups

– Enable to potentially take advantage of standard backupfeatures for releases beyond 6.0. EX: Synthetics Backup, CPR,

Snap Shots.

Catalog Backup methods in





NBU6.0

• Cold, offline catalog backup

– It is bpbackupdb

– Simple and easy

– Be able to have backup windows to do offlinecatalog backup

– For customers who have small catalog which

could be fitted in a single tape and happy withold catalog backup method.






NBU6.0

• Hot, online catalog backup

– For enterprise customers under 24x7 backup

environment

– Rich features• Hot catalog backup

• Full/Incremental catalog backup

• Scheduled catalog backup

• Partial catalog recovery capability through BAR UI

• Catalog backup policy

• UI guided DR catalog recovery

H t C t l B k




Hot Catalog Backup• No need to specify clients for catalog

backup. – Bpdbm automatically figure out all the 5.x

media servers.

– Centralized EMM database.• No need to specify catalog path and files.

– Bpdbm automatically figure out all the catalogfiles which should be backed up.

• Bpbkar uses Catalog Backup APIs toaccess image database.

• Catalog Image locking to achieve hot

backup

H t C t l B k




Hot Catalog Backup process

• Copy 5.x media catalog to Master server.

• Using ASA Sybase agent to backup

catalog (EMM, BMR) stored in ASA

Sybase.

• Creating a check point.

• Backup image database according to

check point to ensure consistencybetween EMM and Image databases.

• Run Catalog DR file (image header file)

rotection.

DR fil t ti th d




85

DR file protection methods



DR il




87

DR email

C t l R




Catalog Recovery

• For hot, online catalog backup imagesonly

• Try to guide user through catalog recovery

• Automate some catalog recovery

processes

• Provide some flexibility on catalog

recovery through manual recovery method

C t l R P




Catalog Recovery Process

• Loading Catalog DR image file (imageheader file)

• Restore DR image file’s body file (image .f

file)

• Restore DR image.

• Restore rest of image database.

• Restore EMM, BMR database.

• Manually restore 5.x media database if it is

necessary.

C t l R Wi d




90

Catalog Recovery Wizard



Load DR file




92

Load DR file

Recovery method




93

Recovery method




6.x Commands




Netbackup Vault configuration

trg template -backup

Documents