cancel
Showing results for 
Search instead for 
Did you mean: 

Backup fails with a CPIO error even though starting with DD

Former Member
0 Kudos

Hi All,

I have started a db backup of a sap system directly onto a tape.

I am using DD since size of each datafile is more than 2 GB.

In a total of 112 data files, 109 got copied but suddenly, the following error came and brbackup got terminated.

This has happened for the second time and that too after using a separate set of tapes.

Can you please provide me your views on it. I am unable to understand why should the error contain "CPIO" if i am using DD.

The parameter settings have been made correctly in the init<SID>.sap file.

Regards,

Hari Kishan

-


BR0351I Restoring /oracle/OBC/sapbackup/.tape.hdr0

BR0355I from /dev/rmt726.1 ...

BR0278E Command output of 'LANG=C cd /oracle/OBC/sapbackup && LANG=C

cpio -iuvB .tape.hdr0 < /dev/rmt726.1':

Can't read input

If you want to go on, type device/file name when ready

10 blocks

.tape.hdr0

BR0280I BRBACKUP time stamp: 2009-12-09 00.57.43

BR0279E Return code from 'LANG=C cd /oracle/OBC/sapbackup && LANG=C

cpio -iuvB .tape.hdr0 < /dev/rmt726.1': 0

BR0359E Restore of /oracle/OBC/sapbackup/.tape.hdr0 from /dev/rmt726.1

failed due to previous errors

BR0218E Checking label on volume in device /dev/rmt726.1 failed

BR0056I End of database backup: becbufwv.ant 2009-12-09 00.57.43

BR0280I BRBACKUP time stamp: 2009-12-09 00.57.45

BR0054I BRBACKUP terminated with errors

-


Accepted Solutions (0)

Answers (3)

Answers (3)

volker_borowski2
Active Contributor
0 Kudos

Hello,

please check your initSID.sap parameters for

both(!) tape address values (rewind and no-rewind)

When did you do the last compress run?

Volker

former_member204746
Active Contributor
0 Kudos

to add to Joe Bo's post:

check if you have a tape in the tape drive

if this is DLT, make sure that door is closed

if all else fails, ask your HP-UX admin to check device /dev/rmt726.1

Former Member
0 Kudos

Hello,

in addition to all the backup files, brbackup will always write one more file to the tape, right at the beginning. This file is called .tape.hdr0. It contains, in essence, the name of the tape and date of the current backup. As far as I know this file will always be written by cpio, no matter what your tape_copy_command is. At the end brbackup will check this file again, and that step failed here.

So it seems there is a problem with either your tape or your tape drive.

But don't worry about cpio!

hope this helps