As I understand the TechNote, you would only be affected if you had any
EEB's of nbpem applied to your 6.5.2x environment, as the original version
of nbpem in 6.5.2a is unaffected.
The problem only involves backups using the calendar-based backups. When
a backup window opens and the job queues before midnight, and the job goes
active after midnight, the backup would succeed as expected. The problem
is that the next backup may not run as expected due to the bug. In
addition, it does not matter if the backup is a full backup or an
incremental backup.
By using versioninfo, you can verify the version of nbpem. If the version
output list anything other than just NetBackup 6.5.2 / 6.5.2A or
SET1448343 this issue may be experienced.
Since we have calendar backup policies that do span midnight, as the
TechNote states, I have a support call opened, however, I am told that
there is no EEB currently available to correct the issue.
Given all the problems with nbpem, I am sure this involves quite a few
shops as most probably have some version of nbpem other than the original
version.
Mike
- Message from [EMAIL PROTECTED] on Mon, 1 Dec 2008
13:39:10 -0600 -
To:
[EMAIL PROTECTED], VERITAS-BU@mailman.eng.auburn.edu
Subject:
Re: [Veritas-bu] Clarity on new tech alert (some NBU 6.5.x)
Not a problem for me has I have not applied any of the binaries.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cornely,
David
Sent: Monday, December 01, 2008 1:16 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Clarity on new tech alert (some NBU 6.5.x)
Anyone else seen this?
http://seer.entsupport.symantec.com/docs/311581.htm
The description is a bit ambiguous so I?m trying to get clarity:
?A potential for missed backups without notification has been discovered
in NetBackup Server/Enterprise Server when calendar based schedules have a
configured window spanning midnight and go Active after midnight. This may
result in a client backup not running during the next open window for any
calendar based schedules configured in the same policy. This is
independent of the scheduled backup type being configured as Full or
Incremental.?
Does this refer to jobs going active after midnight or the policy itself
being made active after midnight? I think it?s referring to when queued
jobs go active after midnight but wanted to be sure.
TIA,
-Dave
- Message from Len Boyle [EMAIL PROTECTED] on Mon, 1 Dec 2008
14:54:34 -0500 -
To:
Cornely, David [EMAIL PROTECTED],
VERITAS-BU@mailman.eng.auburn.edu VERITAS-BU@mailman.eng.auburn.edu
Subject:
Re: [Veritas-bu] Clarity on new tech alert (some NBU 6.5.x)
I believe that it means that the job goes active after midnight. But you
have to have 6.5.2 or better with an eng binary or 6.5.3 to have the
problem.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cornely,
David
Sent: Monday, December 01, 2008 2:16 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Clarity on new tech alert (some NBU 6.5.x)
Anyone else seen this?
http://seer.entsupport.symantec.com/docs/311581.htm
The description is a bit ambiguous so I?m trying to get clarity:
?A potential for missed backups without notification has been discovered
in NetBackup Server/Enterprise Server when calendar based schedules have a
configured window spanning midnight and go Active after midnight. This may
result in a client backup not running during the next open window for any
calendar based schedules configured in the same policy. This is
independent of the scheduled backup type being configured as Full or
Incremental.?
Does this refer to jobs going active after midnight or the policy itself
being made active after midnight? I think it?s referring to when queued
jobs go active after midnight but wanted to be sure.
TIA,
-Dave
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu