Re: [Veritas-bu] Alert! Backups may not be running

2008-11-07 Thread A Darren Dunham
One more piece of information.  To clean up from the no backups being
scheduled issue, you may have luck by stopping Netbackup, deleting (or
moving aside) the pempersist file, then relaunching.  It avoids having
to recreate policies.

Do *NOT* do this if you have any jobs that are suspended or waiting.
Only do this if all your jobs are complete.

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


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Dave Markham
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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]

 Confidential:  This electronic message and all contents contain information
 from BayCare Health System which may be privileged, confidential or otherwise
 protected from disclosure.  The information is intended to be for the 
 addressee
 only.  If you are not the addressee, any disclosure, copy, distribution or use
 of the contents of this message is prohibited.  If you have received this
 electronic message in error, please notify the sender and destroy the original
 message and all copies.
   
 

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

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


[Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Tageson, Jim
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: [EMAIL PROTECTED]

 

Confidential:  This electronic message and all contents contain information
from BayCare Health System which may be privileged, confidential or otherwise
protected from disclosure.  The information is intended to be for the addressee
only.  If you are not the addressee, any disclosure, copy, distribution or use
of the contents of this message is prohibited.  If you have received this
electronic message in error, please notify the sender and destroy the original
message and all copies.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Tageson, Jim
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: [EMAIL PROTECTED]

-Original Message-
From: Dave Markham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 05, 2008 9:11 AM
To: Tageson, Jim
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]

 Confidential:  This electronic message and all contents contain
information
 from BayCare Health System which may be privileged, confidential or
otherwise
 protected from disclosure.  The information is intended to be for the
addressee
 only.  If you are not the addressee, any disclosure, copy,
distribution or use
 of the contents of this message is prohibited.  If you have received
this
 electronic message in error, please notify the sender and destroy the
original
 message and all copies.
   



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

Confidential:  This electronic message and all contents contain information
from BayCare Health System which may be privileged, confidential or otherwise
protected from disclosure.  The information is intended to be for the addressee
only.  If you are not the addressee, any disclosure, copy, distribution or use
of the contents of this message is prohibited.  If you have received this
electronic message in error, please notify the sender and destroy the original
message and all copies.


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


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread netbackup
I have had this problem at more than one site and with more than one version of 
NetBackup, which is why I wrote a Perl script to check every morning to make 
sure everything ran. The script is NOT perfect and would need customization for 
each site, but if anyone is interested let me know.

Regards,

Patrick Whelan


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: [EMAIL PROTECTED]

-Original Message-
From: Dave Markham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 05, 2008 9:11 AM
To: Tageson, Jim
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]

 Confidential:  This electronic message and all contents contain
information
 from BayCare Health System which may be privileged, confidential or
otherwise
 protected from disclosure.  The information is intended to be for the
addressee
 only.  If you are not the addressee, any disclosure, copy,
distribution or use
 of the contents of this message is prohibited.  If you have received
this
 electronic message in error, please notify the sender and destroy the
original
 message and all copies.
   



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

Confidential:  This electronic message and all contents contain information
from BayCare Health System which may be privileged, confidential or otherwise
protected from disclosure.  The information is intended to be for the 
addressee
only.  If you are not the addressee, any disclosure, copy, distribution or use
of the contents of this message is prohibited.  If you have received this
electronic message in error, please notify the sender and destroy the original
message and all copies.


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


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Iverson, Jerald
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tageson,
Jim
Sent: Wednesday, November 05, 2008 8:19 AM
To: [EMAIL PROTECTED]
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED]

-Original Message-
From: Dave Markham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 05, 2008 9:11 AM
To: Tageson, Jim
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


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@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Peacock Dennis - dpeaco
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Iverson,
Jerald
Sent: Wednesday, November 05, 2008 9:23 AM
To: Tageson, Jim; veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tageson,
Jim
Sent: Wednesday, November 05, 2008 8:19 AM
To: [EMAIL PROTECTED]
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED]

-Original Message-
From: Dave Markham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 05, 2008 9:11 AM
To: Tageson, Jim
Cc: veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


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

Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread judy_hinchcliffe
I had the same problem when I did my upgrade from 6.5 to 6.5.2a.

 

I had two policies that had issues.

1 policy only had 1 server in it.  I just copied the policy to a new
name and it started working.

 

The second policy had about 75 servers in it and only 2 did not run.

Again I copied it to a new name and they worked.

 

This only started right after I did the upgrade. Once I gave it a kick
in the pants it has worked ok.

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tageson,
Jim
Sent: Wednesday, November 05, 2008 7:19 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Alert! Backups may not be running

 

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: [EMAIL PROTECTED]

 

Confidential:  This electronic message and all contents contain
information
from BayCare Health System which may be privileged, confidential or
otherwise
protected from disclosure.  The information is intended to be for the
addressee
only.  If you are not the addressee, any disclosure, copy, distribution
or use
of the contents of this message is prohibited.  If you have received
this
electronic message in error, please notify the sender and destroy the
original
message and all copies.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Alert! Backups may not be running (Thanks)

2008-11-05 Thread Tageson, Jim
I have received numerous e-mails from several of you indicating you have
the same or similar problems.

 

I have passed this information on to Symantec to show them that this is
not an isolated problem.

 

Thanks so much for all your responses.  Hopefully we can get this
resolved.

 

Jim Tageson

Netbackup Administrator

BayCare Health System

Phone: 727-467-4586

E-mail: [EMAIL PROTECTED]

 



From: Tageson, Jim 
Sent: Wednesday, November 05, 2008 8:19 AM
To: 'veritas-bu@mailman.eng.auburn.edu'
Subject: Alert! Backups may not be running

 

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: [EMAIL PROTECTED]

 

Confidential:  This electronic message and all contents contain information
from BayCare Health System which may be privileged, confidential or otherwise
protected from disclosure.  The information is intended to be for the addressee
only.  If you are not the addressee, any disclosure, copy, distribution or use
of the contents of this message is prohibited.  If you have received this
electronic message in error, please notify the sender and destroy the original
message and all copies.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread dukbtr

Yes, there is an issue with the schedule since 6.0 GA.  

Symantec support has told us that there is a bug that about every 200 or so 
days for policies. The affected policy/policies might stop running.  They are 
looking into it, but there is no patch or fix for this issue at the moment.  
the only thing you can do is once the policy has been afflicted by this 
FEATURE is to delete and recreate the policy.  Copying the policy will not 
work. 

It is less likely if at all to happen to policies that use frequency based 
shcedules instead of being Calendar based.

Hope this helps shed some light on this.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


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


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Ed Wilts
On Wed, Nov 5, 2008 at 7:18 AM, Tageson, Jim [EMAIL PROTECTED]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.

This is not a new problem and one that pops up regularly.  It's absolutely,
positively the most severe issue that NetBackup can have since data is
silently ignored with no warning to the backup admins.  We've seen it over
the years with 6.0MP2 being the worst example.

We regularly watch not only for failures but also have cronjobs out there
that check to see if any backups have run for specific clients.  For
example, if no database archive logs get backed up, and email is sent out to
the DBAs and backup admins.  We occasionally view the Aptare StorageConsole
volume graphs to see if the patterns make sense - this was our original
trigger into the 6.0 issues.

You can never be too careful with your backups...

.../Ed


Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
[EMAIL PROTECTED]
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread X_S

This sounds very similar with what we went through.  many of our daily 
schedules were configured for 1 day, and for some reason if a backup started 
and completed very close to the end of the backup window, it would wait for 
around the same time the next night.  Depending on how busy the environment 
was, this job would then either fail because the backup window closed, or not 
start at all.  

I forget where i read this but the suggestion was to change the frequency to 
something like every 20 hours, where it was actually tried and start the jobs 
earlier.  This has seemed to help in our environment.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


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


[Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Crowey

Thanks Jim for bringing this to our attention - I for one, was not aware of 
this issue, but I'm certainly concerned about it now.

A few people have mentioned running scripts to check that all jobs have run - 
as still a NetBackup newbie, I for one would be extremely grateful if anybody 
was prepared to share their scripts with us - or even just some hints on how to 
go about it.

My environment is NetBackup 6.0MP4 on Redhat Enterprise Linux 4 (Update 7).

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


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


Re: [Veritas-bu] Alert! Backups may not be running

2008-11-05 Thread Dominik . X . Pietrzykowski
Along with many others here I have been whinning about it to Symantec 
since 6.0MP2 and it still hasn't been fixed.
If I ever restart netbackup I normally delete pempersist so that I know 
it's clean.

I have also moved most policies to calendar based schedule as opposed to 
frequency based.

my 2 cents.

Dominik






Crowey [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
06/11/2008 08:49 AM
Please respond to
VERITAS-BU@mailman.eng.auburn.edu


To
VERITAS-BU@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu]  Alert! Backups may not be running







Thanks Jim for bringing this to our attention - I for one, was not aware 
of this issue, but I'm certainly concerned about it now.

A few people have mentioned running scripts to check that all jobs have 
run - as still a NetBackup newbie, I for one would be extremely grateful 
if anybody was prepared to share their scripts with us - or even just some 
hints on how to go about it.

My environment is NetBackup 6.0MP4 on Redhat Enterprise Linux 4 (Update 
7).

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--


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



This e-mail is sent by or on behalf of the named sender identified above.
If:

(a) you do not wish to receive any e-mail marketing material from this
person in the future, please forward the contents of this email to
[EMAIL PROTECTED] with the word unsubscribe in the subject box.

(b) you wish to unsubscribe from all central e-mail marketing lists used
by our business, please forward the contents of this e-mail to
[EMAIL PROTECTED] with the message unsubscribe from all central
e-mail marketing lists in the subject box.

If you do not forward the contents of this e-mail with your
unsubscription then it may not be able to be implemented.

The information contained in this e-mail communication may be
confidential. You should only read, disclose, re-transmit, copy,
distribute, act in reliance on or commercialise the information if you
are authorised to do so. If you are not the intended recipient of this
e-mail communication, please immediately notify us by e-mail to
[EMAIL PROTECTED], or reply by e-mail direct to the sender and then
destroy any electronic and paper copy of this message. Any views
expressed in this e-mail communication are those of the individual
sender, except where the sender specifically states them to be the views
of a member of the National Australia Bank Group of companies. Any
advice contained in this e-mail has been prepared without taking into
account your objectives, financial situation or needs. Before acting on
any advice in this e-mail, National Australia Bank Limited recommends
that you consider whether it is appropriate for your circumstances. If
this e-mail contains reference to any financial products, the National
recommends you consider the Product Disclosure Statement (PDS) or other
disclosure document before making any decisions regarding any products.
The National Australia Bank Group of companies does not represent,
warrant or guarantee that the integrity of this communication has been
maintained nor that the communication is free of errors, virus or
interference.


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