This is just my own notes on Veritas Netbackup Command Line Guide, feel free to copy-paste;-):
————————————————————————————-
/usr/openv/netbackup/bin/jnbSA >>run NBU GUI
/usr/openv/netbackup/bin/bpadm >>NBU Menu Interface
/usr/openv/volmgr/bin/vmquery -deassignbyid QOSFEB 1 0 >>deassign media
/usr/openv/netbackup/bin/admincmd/bpexpdate -m QOSFEB -d 0 -force >>Expired
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -L >
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -add -max_jobs 99 >>set max jobs to 99
/usr/openv/netbackup/bin/bplist -C aziz -t 4 -R / >>chek list file that backed up already
/usr/openv/netbackup/bin/bpbackup -i -p test -s full -S sunserver1 >>Run jobs
/usr/openv/volmgr/bin/ltid -nsu >>robot will’t unload tape
/usr/openv/volmgr/bin/stopltid >>stop ltid
/usr/openv/netbackup/bin/admincmd/bperror -statuscode 96 >>explanation error
/usr/openv/netbackup/bin/admincmd/bpbackupdb >>backup catalog
/usr/openv/netbackup/bin/bpclntcmd -pn >>query master server communication
/usr/openv/netbackup/bin/bpclntcmd -sv >>query master server version
/usr/openv/netbackup/bin/admincmd/get_license_key >>add/remove license key
#/usr/openv/netbackup/bin/admincmd/:
bpmedia -movedb -ev -oldserver -newserver
bpmedia -movedb -ev PR0161 -oldserver drsskdb1 -newserver masterbackup >>move database to newserver
bpimage -newserver masterbackup -oldserver drsskdb1 -id BI0336 >>
/usr/openv/volmgr/bin/vmoprcmd -crawlreleasebyname
/usr/openv/netbackup/bin/bpdbm -consistency >>Catalog Backup Integrity check
Restore Catalog:
—————–
/usr/openv/netbackup/bin/admincmd/bprecover –help
/usr/openv/netbackup/bin/admincmd/bprecover -r all -dpath f: >>restore dari catalog di disk
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d dlt >>tape model dlt
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d 8mm >>tape model 8mm
/usr/openv/netbackup/bin/admincmd/bprecover -r all -tpath /dev/rmt/0cbn >>
bprecover -l -tpath /dev/rmt/hc2d4
————
{Verify the Netbackup communication daemons are listening for request:
netstat -a |grep bpcd
netstat -a |grep vnetd
{UNFREEZE TAPE MEDIA MARKED AS FROOZEN:
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT738L4
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT626L4
c:\Program Files\Veritas\Netbackup\bin> bpmedia -unfreeze -m -h
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -U -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -L -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bpmedialist -summary
c:\Program Files\Veritas\Netbackup\bin\goodies\available_media
{Remove information about existing media ID from NBU Catalog then delete the existing media ID:
/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m
{initiate import media ID JKT152:
./bpimport -create_db_info -id JKT152
——————————————————————————————–
TUNING AND TWEAKING:
/usr/openv/netbackup
cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo “65536” > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
/usr/openv/netbackup/db/config:
NUMBER_DATA_BUFFERS
SIZE_DATA_BUFFERS
NUMBER_DATA_BUFFERS_RESTORE
NUMBER_DATA_BUFFERS:
8 for non-multiplexed backups
4 for multiplexed backups
8 for non-multiplexed restore, verify, import and duplicate
SIZE_DATA_BUFFERS:
32768 for non-multiplexed backups
65536 (64512 on Solaris) for multiplexed backups
NUMBER_DATA_BUFFERS_RESTORE:
12 (only effects restores of multiplexed backups)
—-
tpautoconf -report_disc , this command will list what device that had been missing or found.
tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device
{STOP NEXT SHCEDULE BACKUP REQUEST:
bprdreg -terminate >>WILL STOP BPRD services
{SHARED SYMANTEC PROCESS:
check with bpps -x command:
/opt/VRTSpbx/bin/vxpbx_exchange start
/opt/VRTSpbx/bin/vxpbx_exchange stop
Pingback: Other DBA Related « Center Point for Oracle DBA & Kuwait Info
Hi Aziz,
May I have your kind advise regarding jnbSA?
This is regarding status code 505 in Solaris 9. This machine was relocated from site A to site B. I’ve changed the IP’s. But when I want to launch the jnbSA below error occured :
Error
Unable to login, status: 505
Can not connect to the NB-Java authentication service on on the configured port – 13722.
Exception: java.lang.NullPointerException
Exception message: null
Action Taken :
Follow from Symantec Web.
*http://www.symantec.com/business/support/index?page=content&id=TECH47405&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=HOWTO51123&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=TECH66075&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=TECH35899&actp=search&viewlocale=en_US&searchid=1333019069849
Perhaps you can direct me to where should i look.
Warmest Regards,
Razali Shoib
Hello Razali, check below tech guide: http://www.symantec.com/business/support/index?page=content&id=TECH9545 If still unable to login via Java console, try to download and install the latest MP.
Hi Aziz,
Thanks for the replied. I will try as per suggested, may I know, currently the version are :
NetBackup-Solaris9 5.1MP6.
What MP should I apply ? And what command should I use to determined which MP that have been installed?
Write more, thats all I have to say. Literally, it seems as though you relied on the video to make your point. You obviously know what youre talking about, why throw away your intelligence on just posting videos to your site when you could be giving us something enlightening to read? dadfkdaebdfe