cancel
Showing results for 
Search instead for 
Did you mean: 

FlashBakup fails on NB 3.4

474900351
Level 2
The log file is:
17:27:52 <8> bpbkar process_file: WRN - /dev/vx/rdsk/rootvol is a character special file. Backing up the raw partition.
17:27:52 <4> bpfsmap: INF - init_msgs: lc_messages = C, lc_ctype = C
17:27:52 <4> bpfsmap: INF - lc_time = init_msgs, lc_collate = C lc_numeric = C
17:27:52 <4> bpfsmap: INF - settmpdir: tmpdir=/usr/openv/netbackup/BPFSMAP_TMPDIR
17:27:52 <4> bpfsmap: INF - bpfsmap: process locked into memory
17:27:52 <4> bpfsmap: INF - bpfsmap: arg list: brmpid 19281 rawdisk /dev/vx/rdsk/rootvol datafd -1 inctime 0
17:27:52 <4> bpfsmap: INF - bpfsmap recnumber 4
17:27:52 <4> bpfsmap: INF - bpfsmap butime 1105615669 clientname snmmaskhz1 hostname snmappkhz1 buid snmmaskhz1_1105615669
17:27:52 <4> bpfsmap: INF - bpfsmap classname rootdg, schdtp 0 filnum 0 snapcache /dev/vx/rdsk/ossdg/flash
17:27:52 <4> bpfsmap: INF - init_globals(): initializing global variables
17:27:52 <4> bpfsmap: INF - init_globals(): inomap cache limit = 10
17:27:52 <4> bpfsmap: INF - rawtoblock: block device name=/dev/vx/dsk/rootvol
17:27:52 <4> bpfsmap: INF - getmount: filesystem name=/
17:28:23 <16> bpfsmap: ERR - open_snapdisk: NBU snapshot enable failed error 19
17:28:23 <32> bpfsmap: FTL - bpfsmap: can't open snapshot disk /dev/vx/rdsk/rootvol errno 0
17:28:23 <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 12: file open failed
17:28:23 <4> bpbkar Exit: INF - EXIT STATUS 12: file open failed
17:28:23 <2> bpbkar Exit: INF - Close of stdout complete

Standart bakup is woking fine.

{root}: uname -a
SunOS snmmas 5.8 Generic_108528-20 sun4u sparc SUNW,Sun-Fire-880
{root}: ls -l /usr/kernel/drv/snapctl.conf
-r--r--r-- 1 root root 32 Jan 13 12:30 /usr/kernel/drv/snapctl.conf
{root}: ls -l /usr/kernel/drv/sparcv9/snapctl
-r-xr--r-- 1 root root 240472 Jan 13 12:30 /usr/kernel/drv/sparcv9/snapctl
2 REPLIES 2

Stumpr2
Level 6
I found the following similiar error in a reame at:
http://seer.support.veritas.com/docs/252350.htm

Description:
The buffer used to create the mount command for setting the VxFs snapshot
was inadequate unless very short volume names were used. This caused the
snapshot creation to fail. An example of the error message is:

09:37:14 <16> bpbkar: ERR - vx_snap: snap mount cmd /sbin/mount
-F vxfs -o snapof=/dev/vx/dsk/rootdg/250M_image
/dev/vx/dsk/rootdg/100MB_cache /usr/openv/netbackup/BPFSMAP_TMPDIR/vxsna
failed
09:37:14 <32> bpbkar: FTL - bpfsmap: can't open snapshot disk
/dev/vx/rdsk/rootdg/250M_image errno 0
09:37:14 <16> bpbkar: ERR - bpbkar FATAL exit status = 12: file
open failed
09:37:14 <4> bpbkar: INF - EXIT STATUS 12: file open failed

Workaround:
The problem may be eliminated by making the volume names very short.Message was edited by:
Bob Stump

474900351
Level 2
I reinstall cumulative patch NB_FSH_34_5:
Patch NB_FSH_34_5 has been previously installed.
Do you wish to reinstall patch NB_FSH_34_5? (y/n) y
But problem is exacly same.

How can I make volume names very short?

Is it possible have more information for message:
17:28:23 <16> bpfsmap: ERR - open_snapdisk: NBU snapshot enable failed error 19
Because if I delite CACHE=/dev/vx/rdsk/ossdg/flash in log I have:
12:25:16 <16> bpfsmap: ERR - open_snapdisk: NBU snapshot enable failed error 3

Thanks for information.Message was edited by:
474900351