Hi Sergey,

Some thoughts:

-UFS is definately supported. We use it.

-Make sure that you haven't got any old/stale SNAPs (check snaplist). If 
so, delete them using snapoff.

-You may want to check out the bpbkar log file for corresponding 
errors...also make sure you get the details with VERBOSE=5 in bp.conf

-Make sure that the SOURCE is not a symbolic link. I have seen this file 
when trying to back up /databases, which was really a symbolic link to 
/u0/data/database1.45, for example. You may see a reference to this if 
it the issue in your corresponding 'bpfis' log.

-Make sure you have enough shared memory and semaphores set. We had this 
problem (error 11 & 5) initially.


HTH

Cheers!

--Chris



> Does nbu_snap support ufs filesystem?
>
>     -----Original Message-----
>     *From:* veritas-bu-bounces at mailman.eng.auburn.edu
>     [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] *On Behalf Of
>     *Evsyukov, Sergey
>     *Sent:* 16 October 2006 09:47
>     *To:* veritas-bu at mailman.eng.auburn.edu
>     *Subject:* [Veritas-bu] NBU_SNAP issue
>
>     Hello, we have business important issue with advanced client.
>      
>     OS - Solaris 9
>     NBU - 5.1MP2
>     SNAPSHOT METHOD - NBU_SNAP
>
>     Backup failed with STATUS = 156 In ~/log/online_util/log.101606 we
>     have found:
>     11:57:43.833 [24864] <2> onlfi_vfms_logf: INF - nbu_snap_freeze:
>     Cannot turn on snapshot; snapshot source=/export, cache
>     =/dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01, snap error=5
>     11:57:43.834 [24864] <4> delete_mount_point: INF - Deleted mount
>     point /tmp/_vrts_frzn_img__export_24864
>     11:57:43.834 [24864] <32> onlfi_freeze_fim_fs: FTL - VfMS error
>     11; see following messages:
>     11:57:43.834 [24864] <32> onlfi_freeze_fim_fs: FTL - Fatal method
>     error was reported
>     11:57:43.834 [24864] <32> onlfi_freeze_fim_fs: FTL - vfm_freeze:
>     method: nbu_snap, type: FIM, function: nbu_snap_freeze
>     11:57:43.834 [24864] <32> onlfi_freeze_fim_fs: FTL - VfMS method
>     error 5; see following message:
>     11:57:43.834 [24864] <32> onlfi_freeze_fim_fs: FTL -
>     nbu_snap_freeze: Cannot turn on snapshot; snapshot source=/export,
>     cache=/dev/vx/rdsk/snapshot_dg/snapshot_vol, snap error=5
>      
>     When we have tryed to create snapshot from CLI, we have got:
>     root at sf6800a <mailto:root at sf6800a> #
>     /usr/openv/netbackup/bin/driver/snapon /export
>     /dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01
>     matched /export to mnttab entry /export mount device:
>     /dev/vx/dsk/exportdg/export fstype: ufs
>     snapon on /export failed err=11 snerrno=5
>      
>     In /var/adm/messages we have found:
>     Oct 16 12:18:40 sf6800a snapctl: [ID 803675 kern.warning] WARNING:
>     addcache: id 22604 cache path =
>     /dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01
>     Oct 16 12:18:45 sf6800a snapctl: [ID 389476 kern.warning] WARNING:
>     addcache: sn_freecache failed, cache path =
>     /dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01, err = 5, block 16777216
>     Oct 16 12:18:45 sf6800a snapctl: [ID 470943 kern.warning] WARNING:
>     addsnap: sn_addcache failed err=5
>     snc_path=/dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01
>     Oct 16 12:18:45 sf6800a snapctl: [ID 576187 kern.warning] WARNING:
>     ioctl_snapon: ioctl_snapon failed error 5
>     Oct 16 12:18:45 sf6800a snapctl: [ID 209424 kern.warning] WARNING:
>     ioctl_snapon: son_snapof=/dev/vx/rdsk/exportdg/export
>     son_cache=/dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01
>      
>     /dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01 seems good:
>      
>     root at sf6800a <mailto:root at sf6800a> # dd if=/dev/zero
>     of=/dev/vx/rdsk/bishouse_dg_01/bishouse_vol_01 bs=65536 count=1024
>     1024+0 records in
>     1024+0 records out
>      
>     What can be reason of problem?
>      
>     Thanks for any help, Sergey
>
> ------------------------------------------------------------------------
>
> *
> Egg is a trading name of the Egg group of companies which includes:
> Egg plc (reg no
> 2448340), Egg Financial Intermediation Ltd
> (reg no 3828289), and Egg Banking plc (reg
> no 2999842). Egg Banking plc and Egg
> Financial Intermediation Ltd are authorised
> and regulated by the Financial Services
> Authority (FSA) and are entered in the FSA
> register under numbers 205621 and 309551
> respectively. These members of the Egg group
> are registered in England and Wales.
> Registered office: 1 Waterhouse Square, 138-
> 142 Holborn, London EC1N 2NA.
>
>
> This e-mail is confidential and for use by
> the addressee only. If you are not the
> intended recipient of this e-mail and have
> received it in error, please return the
> message to the sender by replying to it and
> then delete it from your mailbox. Internet e-
> mails are not necessarily secure. The Egg
> group of companies do not accept
> responsibility for changes made to this
> message after it was sent.
>
>
> Whilst all reasonable care has been taken to
> avoid the transmission of viruses, it is the
> responsibility of the recipient to ensure
> that the onward transmission, opening or use
> of this message and any attachments will not
> adversely affect its systems or data. No
> responsibility is accepted by the Egg group
> of companies in this regard and the
> recipient should carry out such virus and
> other checks as it considers appropriate.
>
> This communication does not create or modify
> any contract.
> *
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>