08-06-2014 12:25 AM
OS:
# uname -a
AIX vmw010150012146 1 6 00F7A5904C00
NBU:7.5 AIX client
RMAN backup log shows:
channel ch00: starting incremental level 0 datafile backup set
channel ch00: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch00: starting piece 1 at 26-JAN-14
RMAN-03009: failure of backup command on ch01 channel at 01/26/2014 19:35:27
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
continuing other job steps, job failed will not be re-run
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 01/26/2014 19:36:12
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
I have checked the hostname and the client name in backup policy,it is the same.
# /usr/openv/netbackup/bin/bpclntcmd -pn
expecting response from server idc-nbu
vmw010150012146 vmw010150012146 10.150.12.146 42585
And I found the time of the system is incorrect:
# date
公元2014年01月27日 星期一 14时38分24秒
(it shows January 27th,2014,monday. )
The backup server’s date is today(Aug 6th,2014,Wednesday)
I wonder why the job would failed?
Does the date affect the backup job?
Solved! Go to Solution.
08-06-2014 12:53 AM
Well the time on your master should be accurate. How do you expect to restore anything if the time is incorrect? Is yesterday really yesterday or is it 5 months ago. Having in an incorrect date might expire all the backups (in theory).
08-06-2014 12:35 AM
vmw010150012146 is this the same name listed in Policy?
what are the outputs of below commands from master
bpclntcmd -hn vmw010150012146
bpclntcmd -ip <ip of the clinet>
08-06-2014 12:45 AM
The client name in policy is vmw010150012146
The outputs of those commands:
D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn vmw010150012146
host vmw010150012146: vmw010150012146 at 10.150.12.146
aliases: vmw010150012146 10.150.12.146
D:\Program Files\Veritas\NetBackup\bin>
D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 10.150.12.146
host 10.150.12.146: vmw010150012146 at 10.150.12.146
aliases: vmw010150012146 10.150.12.146
08-06-2014 12:53 AM
Well the time on your master should be accurate. How do you expect to restore anything if the time is incorrect? Is yesterday really yesterday or is it 5 months ago. Having in an incorrect date might expire all the backups (in theory).
08-06-2014 01:08 AM
... it shows January 27th,2014,....
That is your problem.
Client will look for backups done on dates that correspond with local system time.
Master server creates backup images with current timestamp.
The only way to fix this is to set the system clock on the client to the current date and time.
08-07-2014 04:43 AM
Golly , never seen that to such a degree! How far out of sync?
Use ntp to make the estate tell the same and correct time.
Check on the servers that are incorrect if they run apps that are critically dependant on ToD as moving forward in time in a single step could have unpleasant consequences.
The only other reason to have such a lag could be due to licensing, which is beyond the scope of this forum.
Jim