fbackup (3103) WRITE ERROR

[Tim Meehan]

When invoking fbackup using sam or crontab I receive fbackup (3103) WRITE ERROR part way into the backup. Has anyone else seen this error?

[Patrick Wallek]

Are there any other messages give when you receive this? My first thought is that you have either a problem with the tape or with the tape drive you are writing to.

Have you tried new media? Have you tried that tape using tar to see if you can write to the whole tape?

[Cheryl Griffin]

3103 most often indicates a problem with the tape drive. Does the drive work with fbackup outside of cron?

[Steven E. Protter · Accepted solution]

Very little info.

Most common causes:

1) No tape
2) Write protected tape
3) Bad tape
4) Bad tape drive or cableing or scsi conflict

If it works outside of cron its go to be 1 2 or 3.

SEP

[Jeroen Peereboom]

L.S.

My advice would be to clean the tapedrive first (only if it is a DDS drive, not for DLT!) and use a different (new?) tape.
Are you specifying the correct drive?

JP.

[Tim Meehan]

The drive is a DLT vs80. I have tried several different (inc. new) tapes. The error is the same (and occurs at about the same point during backup) using sam interactive backup or using cron. The SCSI conflict is an interesting one - I might try a different ID...