Hello everyone,

I finally upgraded our master/media server from 6.5.3 to 7.0 (and then quickly 
applied 7.0.1).  All seems to be working fine but noticed some new 
"informational" messages on our "Standard" policies for our Linux jobs.  These 
messages appear on the details tab for the job.  Here is an example (the jobs 
exits with a 0 status):

Info bpbrm(pid=4240) from client dbsrv33: TRV - /u01 is in a different file 
system from /. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /var is in a different file 
system from /. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /dev is in a different file 
system from /. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /proc is on file system type 
PROC. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /u02 is in a different file 
system from /. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /boot is in a different file 
system from /. Skipping.
Info bpbrm(pid=4240) from client dbsrv33: TRV - /sys is in a different file 
system from /. Skipping

I have "ALL LOCAL DRIVES"  for this policy and the "cross mount-points" option 
set.  As I mentioned, the job exits successfully and when I check if the other 
filesystems were backed up (/u01, /var, /u02) they were indeed backed up.

Don't you think these "informational" messages are misleading?  I was worried 
while the job was running (when I saw these messages) thinking the job was 
indeed skipping all these other filesystems.  Of course, I don't worry about 
/sys, /proc, /dev etc (.I already had them on the "exclude_list").

I'll appreciate your comments.

Best regards,
Jorge

_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to