08-03-2012 02:31 AM
Hello!
I have a problem with a scheduled Oracle backup that doesn't start.
With the same client we run other backups (Standard policy + other Oracle instances) but we have the problem only with a particular policy.
I run the command:
/usr/openv/netbackup/bin/vxlogview -o 116 -t 3:00:00
And I found this error:
08/03/12 10:40:31.624 [Error] V-116-258 could not get last backup data for policy pol-vi1.eoe.ora.renetta.thoray48, client renetta.unix.t-systems.it, job(s) will not be run
Every time I try to run the policy I get this error, also with "manual backup".
I try to:
- upgrade to 7.1.0.4 (master server + media server + client)
- make a new policy
but it didn't work.
Actually I run the backup script directly from the client with a crontab.
Please help me!!!
Thank you very much
Simone
Solved! Go to Solution.
11-23-2012 01:29 AM
so, the case seems to be resolved.
Symantec told me to delete these files after shutdown netbackup master server services:
/usr/openv/netbackup/db/jobs/pempersist*
and then I create a new policy manually (not copied by the existent policy).
The latest schedulations are ok.
Thank you
08-03-2012 02:56 AM
tt
08-03-2012 02:57 AM
here is the other lines from vxlogview command executed before:
08/03/12 08:36:00.264 [Info] V-116-80 received start immediate backup request for client=*, policy=pol-vi1.eoe.ora.renetta.thoray48, schedule=sch-aut.day, stream
#=0, client type=MS-Windows (13), parent jobid=-1
08/03/12 08:36:00.265 V-116-254 [PolicyClientTask::cancel] scheduling for policy pol-vi1.eoe.ora.renetta.thoray48, client renetta.unix.t-systems.it, has been aba
ndoned because of execution of new job, will recalculate after job completes
08/03/12 08:36:00.265 V-116-214 [ExtReqTask::run_specificPolicy] Immediate backup request for client=renetta.unix.t-systems.it, policy=pol-vi1.eoe.ora.renetta.th
oray48, schedule=sch-aut.day submitted for execution
08/03/12 08:36:00.266 [Error] V-116-258 could not get last backup data for policy pol-vi1.eoe.ora.renetta.thoray48, client renetta.unix.t-systems.it, job(s) will
not be run
08/03/12 08:36:00.747 [Info] V-116-14 CLIENT renetta.unix.t-systems.it POLICY pol-vi1.eoe.ora.renetta.thoray48 SCHED sch-aut.day EXIT STATUS 207 (error obtain
ing date of last backup for client)
08/03/12 08:36:01.192 [Error] V-116-85 backup of client renetta.unix.t-systems.it exited with status 207 (error obtaining date of last backup for client)
08-03-2012 03:37 AM
Please post Policy config:
bppllist <policy-name> -U
We need to see how schedules are configured in the policy.
08-03-2012 04:12 AM
------------------------------------------------------------
Policy Name: pol-vi1.eoe.ora.renetta.thoray48
Policy Type: Oracle
Active: yes
Effective date: 02/03/1991 20:25:54
Block Incremental: no
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 99999
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: stg-mic.dd880vi02.se
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 0 seconds
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: Solaris Solaris10 renetta.unix.t-systems.it
Include: /usr/openv/netbackup/scripts/hot_database_backup_thoray48.bash
Schedule: sch-app.wee
Type: Application Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 11 (5 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: sch-aut.wee
Type: Automatic Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 10 (45 days)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 2
Sunday, Week 3
Sunday, Week 4
Sunday, Week 5
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 14:00:00 --> Monday 08:00:00
Schedule: sch-aut.mon
Type: Automatic Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 6 (6 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 1
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 14:00:00 --> Monday 08:00:00
Schedule: sch-app.mon
Type: Application Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 6 (6 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
Schedule: sch-aut.day
Type: Cumulative Incremental Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
SPECIFIC DATE 0 - 04/05/2012
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
EXCLUDE DATE 0 - 04/07/2011
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Monday 20:30:00 --> Tuesday 06:30:00
Tuesday 20:30:00 --> Wednesday 06:30:00
Wednesday 20:30:00 --> Thursday 06:30:00
Thursday 20:30:00 --> Friday 06:30:00
Friday 20:30:00 --> Saturday 06:30:00
Schedule: sch-app.day
Type: Application Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00
08-03-2012 04:39 AM
schedule=sch-aut.day is Cumulative Incremental Backup.
When last did a Full backup run?
Incremental backup is based on Full backup within the same policy.
08-03-2012 05:32 AM
is a long time that this schedule backup doesn't work... if the backup image corresponding to the automatic full schedule is expired I can't performe a new incremental backup, right?
Thank you very much, I'l try to perform a new full backup.
08-06-2012 01:52 AM
I tried but the full scheduled backup doesn't start like the incremental backup. We got the same error
EXIT STATUS 207 (error obtaining date of last backup for client)
Any ideas?
thank you very much
Simone
09-25-2012 12:56 PM
Perhaps you are thinking of filesystem backup. Oracle database schedules should be seperate policies.
09-25-2012 12:59 PM
You have multiple Application Backup schedules in one policy presumably for different retention levels for Oracle daily/weekly/monthly jobs. You need to break this up into separate policies.
10-05-2012 05:59 AM
any update, cimo?
10-09-2012 02:23 AM
we have a lot of Oracle policy with multiple application schedule, and they run without problems. I have to open a case on support.
10-31-2012 01:44 PM
I'd be curious to what they have to say. You can combine all into one policy like you have with some fancy client-side scripting. My experience is not worth the trouble. Admin Guide 'About configuring the runtime environment' touches on Oracle environment variables that are needed.
11-23-2012 01:29 AM
so, the case seems to be resolved.
Symantec told me to delete these files after shutdown netbackup master server services:
/usr/openv/netbackup/db/jobs/pempersist*
and then I create a new policy manually (not copied by the existent policy).
The latest schedulations are ok.
Thank you