Solved: file skip problem

Sagar_Kolhe · ‎03-11-2014

Need the solution for the below file skip problem.

-is in a different file system

-is a door file

-is on file system type mntfs

02/07/2014 12:17:57 - Info bpbrm (pid=5467) from client : TRV - /home/atsadmin is in a different file system from /home. Skipping.

02/07/2014 12:17:57 - Info bpbrm (pid=5467) from client : TRV - /home/atsappsup is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/atsora is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/atstemp is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/ccssvc01 is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/oracle is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/r1855 is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/s15232 is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /home/wipro is in a different file system from /home. Skipping.

02/07/2014 12:17:58 - Info bpbrm (pid=5467) from client : TRV - /opt/CA/SC/Csam/SockAdapter/.csam_broker is a socket special file.

02/07/2014 11:32:39 - Info bpbrm (pid=9261) from client : TRV - [/etc/mnttab] is on file system type mntfs. Skipping

02/07/2014 11:32:43 - Info bpbrm (pid=9261) from client : TRV - [/etc/dev/.devfsadm_synch_door] is a door file. Skipping

02/07/2014 11:32:43 - Info bpbrm (pid=9261) from client : TRV - [/etc/dev/.devname_lookup_door] is a door file. Skipping

02/07/2014 11:32:50 - Info bpbrm (pid=9261) from client : TRV - [/etc/sysevent/piclevent_door] is a door file. Skipping

02/07/2014 11:32:50 - Info bpbrm (pid=9261) from client : TRV - [/etc/sysevent/devfsadm_event_channel/1] is a door file. Skipping

02/07/2014 11:32:50 - Info bpbrm (pid=9261) from client : TRV - [/etc/sysevent/devfsadm_event_channel/reg_door] is a door file.

NBU Version : 7.5.0.6

Regds,

Sagar

Marianne · ‎03-11-2014

Perfectly normal. Therefore no 'solution' as none of these is a problem or error.

There are certain files and/or filesystems that NBU will skip by default as they are not needed during a restore. See http://www.symantec.com/docs/TECH52350

-is in a different file system
is because 'Cross mount points' is NOT selected in the policy. So when / filesystem is getting backed up, no other filesystems will be backed up as part of / (root filesystem).

If you have ALL_LOCAL_DRIVES in backup selection with 'allow multiple data streams', you will see a different job for this filestem. If not selected, you will see this (and other) filesystem(s) being backed up after / backup has completed.

DO NOT check 'Cross mount points' when ALL_LOCAL_DRIVES is in backup selection.

This will result in duplicate backups - as part of / and when it gets to the mount point.

Seeing the message when / is backed up is perfectly normal. Separate filesystems must not be backed as part of /.

The only time that it would be okay to select 'Cross mount points' is when you only have "/" in the Backup Selection.

See page 613 of NBU Admin Guide for UNIX and Linux, Volume I http://www.symantec.com/docs/DOC3650

"Note: Do not use the Cross mount points attribute in policies on UNIX systems where
you use the ALL_LOCAL_DRIVES directive in the backup selection list."

Handy NetBackup Links

View solution in original post

RamNagalla · ‎03-11-2014

Sagar,

you just need not to worry about these.. these are just informational messages.

as look as your backup is running fine and compleating with status code 0 , you are good

Marianne · ‎03-11-2014