uvbackup &stdout query

[Joanne Keegan]

Hi,

After running uvbackup (Universe command) on our server (HP-UX 10.20) a stdout (called stdout) file was produced which filled up the root directory. The script for uvbackup hasn't been modified, and this is the first time this problem has occurred. If it was a scripting problem, surely this would have happened before now.

Does anyone know why this may have occurred? Is it a unix problem or universe?

The uvbackup command that is used is:

find $FINDVAR -print | uvbackup -f -v -b 8192 - > $DRIVE

Thanks for your help.

Regards,

Joanne

[Rodney Hills]

Is it possible that your variable $DRIVE got set to "stdout"?

I ran uvbackup and all the output went to the file specified after the ">". uvbackup displayed the summary information on standard error (stderr). This is on version UV9.5.17D.

[Joanne Keegan]

Hi Rodney,

Sorry, I should have mentioned that the stdout file seemed to contain data from towards the end of the backup. It is as if some condition was reached and then the output was redirected to this file. $DRIVE is directed to the tape.

Thanks for your input.

Joanne

[Rodney Hills · Accepted solution]

The documentation for uvbackup states you can have 1-10 -t option to specify multiple tape drives.

This implies when uvbackup gets to the end of a tape, it auto switches to the next device.

Seeing how you only had the one tape drive, it looks like a bug in uvbackup is closing it when it reached the end and defaulting to the disk for the rest.

I'd call Informix (aka Vmark)

[Joanne Keegan]

Hi Rodney,

I tend to agree with you concerning the tape. I'm yet to verify that an additional tape was required, but it seems the most logical reason at this stage.

Regards,

Joanne