Netbackup ERROR: V-3-26255: "FS" is not a file, block or character device

[albatroz19]

Hi all,

I've configured a standard FS policy backup of solaris client. It's finish in status ok, but on session log i see these lines:

12/18/2018 10:26:24 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /home is not a file, block or character device

12/18/2018 10:26:28 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /extra is not a file, block or character device

12/18/2018 10:48:53 - Info bpbkar (pid=10518) 250000 entries sent to bpdbm

12/18/2018 10:58:05 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /product/app is not a file, block or character device

12/18/2018 11:01:01 - Info bpbkar (pid=10518) 300000 entries sent to bpdbm

12/18/2018 11:02:36 - Info bpbkar (pid=10518) 350000 entries sent to bpdbm

12/18/2018 11:05:02 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /product/maestro/FTA is not a file, block or character device

12/18/2018 11:05:25 - Info bpbkar (pid=10518) 399998 entries sent to bpdbm

12/18/2018 11:05:37 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /product/Tibco is not a file, block or character device

12/18/2018 11:05:53 - Error bpbrm (pid=264243) from client ssc60057.bck: ERROR: V-3-26255: /product/connect is not a file, block or character device

I looked for this error, but i don't found nothing about it.  Please someone has already managed this behaviour?

Thanks in advance,
Best Regards

[Nicolai]

can you do do a bpmount and a df -h and show us the result. I expect those file system to be "remote" - e.g NFS.

If you want to backup to areas, you need to checkmark "follwo NFS" / Cross Mount points. Be aware you don't backup the same data twice - remote via e.g NFA and on the NFS server itself.

https://www.veritas.com/support/en_US/article.100000526.html

[Marianne]

@albatroz19

I would rather expect info messages similar to '/FS is a socket special file. Skipping ', rather than these error messages. 

NBU will not backup certain file or filesystem types:
https://www.veritas.com/support/en_US/article.000010016
https://www.veritas.com/support/en_US/article.TECH52350

What are the filesystem types for these directories/filesystems? 
Can you show us output of 'mount -p' on the client?

Please create bpbkar log folder on the client and increase the logging level to 1. (Anything higher might just create a very large log file that will be impossible to upload here). 

Please copy bpbkar log to bpbkar.txt after next backup and upload here.

[albatroz19]

Hi Nicolai, Marianne,

sorry for delay. I've excuted the commands, and i attacched the commands log and bpbkar logs.

I've already tried backup with check "Follow NFS" and "Cross Mountpoint".

The client is a Solaris 5.10 Generic_Virtual sun4v sparc sun4v
The Master/Media Server are Linux 2.6.32-504.23.4.el6.x86_64 

[Amol_Nair · Accepted solution]

It seems that all the filesystems which report the error are vxfs.. The logs show message similar to the below ones

12:26:09.625 [14435] <2> mount build_mount_list: INF - Processing (vxfs) /extra on /extra
12:26:09.625 [14435] <2> mount build_mount_list: INF - Mount options for /extra are <rw,suid,delaylog,largefiles,qio,ioerror=mwdisable,mntlock=VCS,xattr,zone="Client",nozonemod,sharezone=51,dev=500e290>
12:26:09.625 [14435] <4> bpbkar SelectFile: INF - Couldn't get VxFS file system layout: /database/dati is not a file, block or character device

12:26:09.625 [14435] <8> bpbkar SelectFile: WRN - [/database/dati] is in a different file system from [/]. Skipping
12:26:09.625 [14435] <4> bpbkar SelectFile: INF - VxFS filesystem is /database/indici for /


I would suggest to log a call with our infoscale team to get this checked if there is some filesystem corruption

Once the filesystem side issues have been addressed I would recommend running a full backup with forced rescan as you have accelerator option enabled.

Below are a couple of links for your reference
https://www.veritas.com/support/en_US/article.000017179

https://www.veritas.com/support/en_US/article.000020959

[albatroz19]

Hi,

after sysadmin verify,  it was a filesystem corruption. Thanks all for support.

Best Regards,