There is a problem with the Netbackup scheduler all the way up through
6.5.2, as has been our experience here.

Thank You,
Dennis Peacock
EBCA
Acxiom Corporation
501-342-6232 (office)
 

-----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 Iverson,
Jerald
Sent: Wednesday, November 05, 2008 9:23 AM
To: Tageson, Jim; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Alert! Backups may not be running

we also occassionally see the problem here (6.0mp4 linux).  certain
clients won't run but others in the same policy will.  we have been
running a cron script every morning on our master servers (since going
to 6.0  2.5 years ago when there were scheduler issues) that checks all
policies/schedules/clients and compares them with what actually ran (via
bpdbjobs) and emails us an alert if any did not run.  we then run them
manually with no problem.  once a client gets into a "stuck" state, it
doesn't run until daemons are restarted.  one time that didn't fix the
problem either so i had to remove the pempersist file and that cleared
the problem.  we haven't had the issue for a couple of months so i
haven't had to troubleshoot it further.  finding a backup hasn't been
running when asked for a restore is not acceptable.

thanks,
jerald

-----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 Tageson,
Jim
Sent: Wednesday, November 05, 2008 8:19 AM
To: dave.markham AT fjserv DOT net
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Alert! Backups may not be running

Maybe it's not an isolated problem after all.  In my case it was not an
entire policy with the problem, it was certain clients within policies
that were not running.  Other clients in those policies were running OK.

I too was able to initially get them to run again by copying them to
other policies.

Jim Tageson
Netbackup Administrator
BayCare Health System
Phone: 727-467-4586
E-mail: james.tageson AT baycare DOT org

-----Original Message-----
From: Dave Markham [mailto:dave.markham AT fjserv DOT net] 
Sent: Wednesday, November 05, 2008 9:11 AM
To: Tageson, Jim
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Alert! Backups may not be running

This is actually something which happens to me quite regularly so i
believe symantec need to take notice of it.

My case is slightly different in that i have a number of policies for
different SSO Media servers.

Out of the blue one of the policies does just not schedule to run yet no
change has been made to it.

A manual backup works fine yet still no scheduled backup works.

The only way i have been able to get around it is this :-
  Copy the policy to a new name
  Delete the old policy
  Copy the new name policy back to the original name
  Delete the new name policy.

I'd like to know why this happens too as as you say its not picked up in
the activity monitor.

I have it on my list to check that my report script has a known list of
clients and to alert if any of them are not present in the daily report.

This i have not yet gotten around to doing though.

Cheers


Tageson, Jim wrote:
>
> We uncovered a situation recently where some client backups in 
> scheduled policies were not running at all. These clients were in 
> active policies with several other clients which were running just 
> fine. We discovered a total of 4 clients in 2 policies which were just
>
> not running their backups at all. Other clients in these 2 policies 
> were being scheduled as expected. We went for 19 days without backups 
> running on these 4 clients. Since they never were scheduled, there 
> were obviously no errors in Netbackup at all and we didn't know we had
>
> a problem until someone requested a restore and we saw no backups had 
> run. We opened a ticket with Symantec and they have escalated it to 
> the highest level. The problem was finally resolved by a recycle of 
> the Netbackup daemons, but no cause has been determined due to lack of
>
> log files during the time of the problem.
>
> Symantec believes the policies somehow got corrupted and they believe 
> this is an isolated issue and probably will not occur again. However 
> if you are not monitoring to see if all your scheduled backups are 
> actually running, you will never know you have a problem.
>
> This is just to alert other users of this issue and to urge them to 
> make sure that this is not a widespread problem.
>
> We are currently running Netbackup 6.0MP6 on an AIX master server.
>
> **Jim Tageson**
> **Netbackup Administrator**
> **BayCare Health System**
> Phone: 727-467-4586
> E-mail: james.tageson AT baycare DOT org <mailto:james.tageson AT baycare DOT 
> org>
>
****************************************************************
Confidentiality Note: The information contained in this message, and any
attachments, may contain confidential and/or privileged material.  It is
intended solely for the person(s) or entity to which it is addressed.
Any review, retransmission, dissemination, or taking of any action in
reliance upon this information by persons or entities other than the
intended recipient(s) is prohibited.  If you received this in error,
please contact the sender and delete the material from any computer.
****************************************************************


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
***************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.
****************************************************************************


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