Veritas-bu

[Veritas-bu] scheduled production backup did not run

2004-01-06 16:59:51
Subject: [Veritas-bu] scheduled production backup did not run
From: RLMarkham AT hafeleamericas DOT com (Markham, Richard)
Date: Tue, 6 Jan 2004 16:59:51 -0500
I have an Oracle class, which three schedules: HOT_FULL, ARCHIVE_LOGS and
the required Default-Policy.
A backup under schedule HOT_FULL should have ran at 0300 hours but did not.
There is an error showing for the schedule ARCHIVE_LOGS, but this doesn't
have any set times and gets submitted from a cronjob on a client based on
disk usage, a backup under this schedule did occur around 0100 hours. I
don't know if this is contributing to the problem or not.

Not sure what else to check.

03:04:37 [17267] <4> build_worklists_scheduled:   CLASS
oracledb_RMAN_PROD...
03:04:37 [17267] <2> any_window_open: checking class oracledb_RMAN_PROD
03:04:37 [17267] <2> in_backup_window:   checking schedule HOT_FULL
03:04:37 [17267] <2> in_backup_window:   in HOT_FULL backup window for
Tuesday
03:04:37 [17267] <4> build_worklists_scheduled:     CLIENT oracledb
(Solaris/Solaris8) in class oracledb_RMAN_PROD part 0...
03:04:37 [17267] <4> find_work: looking for work for client oracledb in
class oracledb_RMAN_PROD part 0
03:04:37 [17267] <4> find_work: checking all schedules
03:04:37 [17267] <4> find_work: checking schedule HOT_FULL
03:04:37 [17267] <2> get_image_list: oracledb_RMAN_PROD_1025882493_FULL
FOUND
....{removed several get_image_list lines here so ouput would be
shorter}....
03:04:37 [17267] <2> get_image_list: oracledb_RMAN_PROD_1073372101_UBAK
FOUND
03:04:37 [17267] <4> last_full_backup: Last backup=0
03:04:37 [17267] <2> in_backup_window:   checking schedule HOT_FULL
03:04:37 [17267] <2> in_backup_window:   in HOT_FULL backup window for
Tuesday
03:04:37 [17267] <4> in_interval_mode: IN INTERVAL MODE
03:04:37 [17267] <4> backup_due:  using window_start: Tue Jan  6 03:00:00
2004
03:04:37 [17267] <4> backup_due:  days_ago=1, backup IS due(Overdue=0
03:04:37 [17267] <4> find_work: checking schedule ARCHIVE_LOGS
03:04:37 [17267] <2> get_failure_count: 4 matches in past 12 hours for
oracledb/oracledb_RMAN_PROD/ARCHIVE_LOGS
03:04:37 [17267] <4> log_in_errorDB: skipping backup of client oracledb,
class oracledb_RMAN_PROD, schedule ARCHIVE_LOGS because it has exceeded the
configured number of tries

Solaris 8
Netbackup Datacenter 3.4.2

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] scheduled production backup did not run, Markham, Richard <=