Hi folks,
we are running a Linux RedHat 7.5.0.7 NetBackup master. On those, we have several AIX 7.1 clients were the admins regularly do restores via the command line.Unfortunatley every once in a while they don't double check the files they want to restore and attempt to restore files that do not exist in the backup.
/usr/openv/netbackup/bin/bprestore -L /tmp/restore.log -A <FILENAME>
Logfile shows this:
Restore started 04/07/2014 15:31:04
15:31:31 (6448895.xxx) <FILENAME> -s
01/01/1970 00:00:00 -e 04/07/2014 15:31:06 - no files matched in the given date range
15:31:31 (6448895.xxx) INF - Status = Standard policy restore error.
This obviously results in the restore failing and the process ending on the client. Unfortunately the job does not fail on the NetBackup master. It goes into Incomplete and pretty much stays there until someone actually aborts the job. This does create a 150 error code, not the 2800 that it actually was.
Now I have already educated my admins to make sure they check if the file they want to have is actually there before they start the restore. Unfortunately errors do happen and I am sure I'll still find the occasional hanging job. I was only wondering if this is intentional behavior or a bug. Overall I would assume that the job would terminate after a while, but seeing as I already have one job that has been hanging like that in excess of 40 hours I doubt that will happen.
Any one able to shed light on this?
Thanks
Chris