Re: [Veritas-bu] 6.5.2 Scheduler Bug?
2008-06-30 13:51:55
The failed jobs were Windows, Standard and Exchange policy
types kicked off automatically via calendar based scheduling. Sounds like
you jobs were "application backups" kicked off by the server? I'm assuming
we're having the same issue, or at least the symptoms are the similar. I'm
expecting a call back from tech support any time now. Its interesting that
the frequency based scheduling of these jobs was fine, but the calendar and
"user" backups schedules are effected.
-Jonathan
We updated one of our environments
last week to 6.5.2. Immediately we found any API job queued at midnight would
cancel with a 196 even though the
schedule had a 24x7 window (Oracle, DB2, SQL, etc). Symantec found a problem
with the window calculation and created a binary fix for the issue (which will
not be part of the 6.5.2a release). Is this the issue you are seeing with the
196's at midnight or is the problem broader then APIs as we have seen with this
first upgrade?
Thanks,
Beth
Sexton Backup Service Improvement JPMorganChase Enterprise Storage
Services NA
Elizabeth Sexton ----- Message from "Martin, Jonathan" <JMARTI05 AT intersil DOT com>
on Mon, 30 Jun 2008 11:57:56 -0400 -----
To:
| "Steve Fogarty"
<steve.fogarty AT gmail DOT com>
|
cc:
| VERITAS-BU AT mailman.eng.auburn DOT edu
|
Subject:
| Re: [Veritas-bu] 6.5.2 Scheduler
Bug? | Just to
clarify - I upgraded 2 weeks ago and everything ran fine until now. My
schedules are as follows: Daily Differential Incremental - 8:00PM - 4:00AM
Daily Mon-Thur (Frequency every 10 hours) Weekly Full - 8:00PM Friday - 8:00PM Sunday (Frequency, every 3
days) Monthly Full - 8:00PM Friday
- 8:00PM Sunday (Calendar, last Friday of the month) The dailies and the
weeklies both ran fine for two weeks. In fact, the "overlapping" weekly
ran after the monthly failed (which is a normal occurrence for this schedule
when the monthly fails, say with an error 41 etc..) Further, many
monthlies did in fact run and I suspect that only those in a queued state failed
just after midnight. I'm thinking of ways to test this. Perhaps trying to
write to a tape drive that will be busy tonight with a "last Monday of the
month" backup with an open window all week? I suspect the job will queue
and fail after midnight despite the window being open all week. Since I
don't generally specify that calendar based backups can retry after their run
days I might test two policies one with and one without the extra check box.
-Jonathan
From: Steve Fogarty
[mailto:steve.fogarty AT gmail DOT com] Sent: Monday, June 30, 2008 11:16
AM To: Martin, Jonathan Cc:
VERITAS-BU AT mailman.eng.auburn DOT edu Subject: Re: [Veritas-bu] 6.5.2
Scheduler Bug?
You are having
"somewhat" more luck then me. I have about 25 Polices...and only 2 fire
off period. They don't run out of Window...they just don't start. My
support has been to recreate the policies again. I did that with the the
'/bppolicynew <new_policy> -sameas <old_policy>' command, but no
difference. "Support" now says to create them from scratch. I am
working on that now.
Steve
On Mon, Jun 30,
2008 at 10:21 AM, Martin, Jonathan <JMARTI05 AT intersil DOT com> wrote:
NBU 6.5.2 on Windows 2003 SP2 Just ran my first Monthly
backups since upgrading one of our smaller environments to 6.5.2. I've got about 40
clients that fire the "last Friday of the month" with a generous window that
stays open until Sunday evening. About 35 of those clients fired at 8:00PM
as normal, but they all failed just after midnight with error 196 - backup
window closed. Anyone see anything similar to this? I know adoption
of 6.5.2 is low. I'm about to open a ticket w/ Symantec. -Jonathan Martin
Intersil Corp. Servers and Security Operations Desk:
(321) 724-7314 Cell: (305) 989-0510
_______________________________________________ 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
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument or
as an official confirmation of any transaction. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and
affiliates. This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure under applicable
law. If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained herein
(including any reliance thereon) is STRICTLY PROHIBITED. Although this
transmission and any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it is virus
free and no responsibility is accepted by JPMorgan Chase & Co., its
subsidiaries and affiliates, as applicable, for any loss or damage arising in
any way from its use. If you received this transmission in error, please
immediately contact the sender and destroy the material in its entirety, whether
in electronic or hard copy format. Thank you. Please refer to
http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal
entities.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|