NBU-Tips

10
Posted by:wing7 | February 3, 2008 Netbackup Tips Starting and Stopping Netbackup Stopping Netbackup /usr/openv/netbackup/bin/K77netbackup –> graceful shutdown /usr/openv/netbackup/bin/bpps -a –> check for any remaining processes /usr/openv/netbackup/bin/goodies/bp.kill_all —> kills all remaining netbackup processes, not necessarily graceful /usr/openv/netbackup/bin/bpps -a –> check for any remaining processes kill -9 <pid> for any remaining. NOTE: unkillable processes may require a reboot Starting Netbackup /usr/openv/netbackup/bin/S77netbackup –> after bp.kill_all, to restart Common Tasks Starting the Administration GUI java from the windows client x-windows from the server - /usr/openv/netbackup/bin/xnb & Checking Backup Status Activity Monitor or /usr/openv/netbackup/bin/admincmd/bpdbjobs -report Cleaning a tape manually Identify the drive name to be cleaned o

description

NBU TIPS

Transcript of NBU-Tips

Posted by:wing7 | February 3, 2008

Posted by:wing7 | February 3, 2008

Netbackup Tips

Starting and Stopping Netbackup

Stopping Netbackup

/usr/openv/netbackup/bin/K77netbackup > graceful shutdown

/usr/openv/netbackup/bin/bpps -a > check for any remaining processes

/usr/openv/netbackup/bin/goodies/bp.kill_all > kills all remaining netbackup processes, not

necessarily graceful

/usr/openv/netbackup/bin/bpps -a > check for any remaining processes

kill -9 for any remaining. NOTE: unkillable processes may require a reboot

Starting Netbackup

/usr/openv/netbackup/bin/S77netbackup > after bp.kill_all, to restart

Common Tasks

Starting the Administration GUI

java from the windows client

x-windows from the server - /usr/openv/netbackup/bin/xnb &

Checking Backup Status

Activity Monitor or

/usr/openv/netbackup/bin/admincmd/bpdbjobs -report

Cleaning a tape manually

Identify the drive name to be cleaned

o

tpclean -L

Manually clean the drive:

o

tpclean -C

Determining what tapes were used for a backup

GUIo

Backup and Restore > Find the file system > Preview Media Button

CLIo

Find the correct backup images

bpimagelist -U -client -d -e

o

Find the media used for those images

bpimagelist -U -client -d -e -media

Listing the files in a backup

Find the tape(s) used (above procedure using bpimagelist)cd /usr/openv/netbackup/db/jobs/doneRun the following script and redirect its output to a text file:for file in `grep MOUNTING *|grep |awk {print $1}|sed s/:MOUNTING//`doecho $filegrep PATH_WRITTEN $file|awk {print $3}echo echo ==========================================End ofImage======================================echo done

This process works for NBU V3.4:

cd /usr/openv/netbackup/db/images/

ls -ltr > this will identify the directory with the proper date

verify directory with bpdbm -ctime

cd

ls -ltr > lists all of the backups for this client on this date

cat __.f | awk {print $10} > this prints out the files in the backup

For NBU > V3.4

bpflist help > undocumented netbackup command to list files from a binary .f file

Inventory the Robot

Inventory Robot > /opt/openv/volmgr/bin/vmcheckxxx -rt robot_type -rn robot_number -list (where

robot_type is tld, acs, . . .)

Inventory Robot and Update Configuration > /opt/openv/volmgr/bin/vmupdate -rt robot_type -rn

robot_number -list (where robot_type is tld, acs, . . .)

Listing Properties of the Volume Pools

vmpool -listall

Scratch Tapes

Count scratch tapes: /usr/openv/volmgr/bin/vmquery -pn Scratch | grep -c robot slot

Moving tapes to the scratch pool

o

If Needed - Expire the tape

bpexpdate -ev -d 0 -force -host

o

Move the tape

vmchange -p 2 -m

Checking Drive Usage

/usr/openv/volmgr/bin/vmoprcmd

Taking a drive down or up

/usr/openv/volmgr/vmoprcmd -down

/usr/openv/volmgr/vmoprcmd -up

Performing a Restore

From the GUI

o

user backup & restore > configuration > client

o

user backup & restore > configuration > client to restore

o

directory to search

o

directory depth

o

date range

o

file > browse backups for restore

Adding New Tapes to the Library

Using the GUI

o

Media Management > Actions > New > Single Volume . . >

o

Media Type (ie DLT)

o

Robot Type (ie TLD)

o

Media ID (from Inventory)

o

Slot Number (from Inventory)

o

Robot Number (ie 0)

o

Volume Group

o

Volume Pool (ie Scratch)

Using the CLI

o

vmadd -m -mt -verbose -rt -b -rn -rc1 -p -mm

vmpool -listall > lists all pools, both name and number

o

For example: vmadd -m 000151 -mt dlt -verbose -rt tld -b 000151 -rn 0 -rc1 8 -p 2 -mm 0

Re-using Tapes from other systems or older Netbackups

Expire the media

o

bpexpdate -ev MEDIA_ID -d 0 -force -host HOST

Deassign the media

vmquery -deassignbyid MEDIA_ID 4 0

Move to the scratch pool

vmchange -m MEDIA_ID -p POOL#

Relabel the media

bplabel -ev CIM572 -d dlt -p Scratch

Changing the attributes of media

Changing the barcode

vmchange -barcode CYM100D -m CYM100

Changing the Volume Pool

vmchange -m MEDIA_ID -p POOL#

To expire media

1 > to select TLD 0

Getting help

o

?

Looking at contents of the tape drives

o

sd

Looking at the contents of the library

o

ss

Moving a tape from a drive to a library slot

o

s d > to identify drive number that has tape (Contains Cartridge = yes, Barcode=XXXXXX)

o

s s > to identify an empty slot in the tape library (Netbackup will need to be re-inventoried)

o

m d# s# > from from drive # to slot #

o

s d > verify the tape drive is empty

o

s s > verify the library slot has the tape

Configuration Files

/usr/openv/netbackup/bp.conf

configuration file, sets backup server and backup clients

force statement must be correct

client to browse from

client to restore to

/usr/openv/volmgr/vmconf

Logfiles

To utilize logfiles, create the corresponding directory in /usr/openv/netbackup/logs

Server Logfile directories:

admin - adminstrative commands

bpbrm - backup and restore manager

bpcd - client daemon

bpdbjobs - database manager program process

bpdm - disk manager process

bpjava-msvc - Java application server authentication service

bpjava-usvc - process that services Java requests

bprd - request daemon process

bpsched - scheduler process that runs on master servers

bptm - tape/optical media management process

user-ops - required directory for use by Java programs

xbpadm - X based administration utility

xbpmon - X based job monitor process

Client Logfile directories:

bp - client user interface process

bparchive - archive program

bpbackup - backup program

bpbkar - program that generates golden images

bpcd - client daemon

bpjava-msvc - Java application server authentication service

bpjava-usvc - process that services Java requests

bplist - program that lists backed up and archived files

bpmount - program that determines local mountpoints and wildcard expansion for multiple streams

bphdb - Oracle database backup program start process

db_log - database specific extension log

tar - tar process log during restores

user_opsMedia Manager logging automatically goes to the system log using syslogd logging facility.Logging will only occur if these directories are created. These directories will generate a lot of data and should

be deleted when no longer necessary.

To increase the amount of logging information set VERBOSE=2 in /usr/open/netbackup/bp.conf (default is

VERBOSE=1)

Processes

ltidacsdvmd

Useful Commands

bpcllist - list classesbpclinfo -L > displays info about a classvmpool - volume poolsvmpool -listallvmpool -listscratchbplabel -ev -d hcartbpbackup db > backs up the catalogbpclclients > lists the clients for a particular policy (class)

Troubleshooting

bperror -statuscode this will bring up drive 0 if its control shows as

down

Look for pending requests

o

/usr/openv/volmgr/bin/vmoprcmd or gui > device management

o

If there is a pending request either re-assign it to a drive, or deny the request

Downed drive does not come back up or does not stay up

Check for a hardware problem by looking for messages on the tape library

Make sure there is not a tape stuck in the drive

o

Use robtest (described above) to look at the drives

If there is a tape stuck in the drive, try to remove it using robtest

If robtest fails, then you must manually remove it.

Verify the Client is communicating properly:

bpclncmd -ip > from both client and server

bpclntcmd -hn > from both client and server

bpclntcmd -pn > from client only

Device Actions

Device Management > info about tape drives

dlt

hcart (ultrium)

Media Actions

Media id must agree with # of the tape

Create a media id

actions >new>single volume>dlt cart (not dlt2)

put it into the netbackup volume pool

Netbackup Client

To check things out do this:It could be a couple things. Mostly DNS, bp.conf, or something stupid. On

the client run this command/usr/openv/netbackup/bin/bpclntcmd -pn/usr/openv/netbackup/bin/bpclntcmd -server server name/usr/openv/netbackup/bin/bpclntcmd ip ip_addressOne of these usually fails and your able to fix it right off

1074 ./bpclntcmd -hn corpbu11075 ./bpclntcmd -ip 10.194.1.1291076 ping 10.194.1.1291077 ./bpclntcmd -hn corpldv11078 ./bpclntcmd -hn corpbu1.corporate.vox.net1079 ping corpldv11080 ./bpclntcmd -ip 10.194.1.120