This is why we prefer to use exclude files for our UNIX/Linux OS policies and
tell them to backup / instead of ALL LOCAL DRIVEs. We can exclude any
filesystem we want (especially things that won't backup like /proc and /sys)
then create a separate policy for environment backups (e.g. we might exclude
/database from the OS backup then have a separate policy to backup /database
itself - usually run at a point the database is down.) Using exclude files
also can help you avoid policies that end in status 1 for things they can't
backup - at one job I had management wasn't willing to accept the idea that a
status 1 was (mostly) successful.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
judy_hinchcliffe AT administaff DOT com
Sent: Friday, September 24, 2010 10:29 AM
To: jorge.fabregas AT gmail DOT com; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] 7.0.1 & UNIX/Linux clients backups
I saw the same messages when I was on 6.5.x. I have a AIX master. Don't know
if they just fixed that for Linux in 7 (maybe they missed that before)
All it is telling you is that it is backing up / (root) and in doing so it sees
that /u01 is a separate file system, and it knows you are doing multiply jobs,
so it will not backup /u01 with root but will do it as a separate job.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jorge
Fábregas
Sent: Friday, September 24, 2010 7:48 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 7.0.1 & UNIX/Linux clients backups
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 AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Proud partner. Susan G. Komen for the Cure.
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
