Topic: Another Flexbackup tape error

[jonnybb1]

Ok, I get more errors from flexbackup than I do from any other program. I have 6.01using a Seagate IDE 10/20 gb tape backup. The client confirms weekly tape head claning and switches tapes out 3x a week. Tapes are all under 6 months old. Oh and YES, I have had more errors from Flexbackup before, on different machines, using newer and older IDE tape drives, and a plethera of new and old tapes, and changing rpms, reformatting, trying to run manually. Someone please help me PLEASE!!

Here is the output of the eror message.
flexbackup version 1.1.7 (http://flexbackup.sourceforge.net)
/etc/flexbackup.conf syntax OK

|------------------------------------------------------------
| Checking 'buffer' on this machine... Ok
| Checking /bin/sh on this machine... bash2
|------------------------------------------------------------
| Trying "mt defblksize" instead of "mt setblk"
| Doing level 0 backup of set all using tar
| All sets = full (1 tapes)
| Rewinding & erasing tape...
| Found index key 200505161947, next file is 1
| Record for 200505161947:all not found
|------------------------------------------------------------
| Creating index key 200506061947
| Backup set full (/ /boot)
| Tape #0
|------------------------------------------------------------
At block 0.
|------------------------------------------------------------
| File number 1, tape index 200506061947
| Backup of: /
| Date of this level 0 backup: Mon Jun 06 19:47:13 2005
| Date of last level 0 backup: the epoch
|------------------------------------------------------------
| cd "/" && find . -depth -xdev ! -type s ! -regex "news/articles" ! -regex
|   ".*~"$ -print0 | tar --create --null --files-from=-
|   --ignore-failed-read --same-permissions --no-recursion --totals --label
|   "level 0 / Mon Jun 06 19:47:13 2005 tar+gzip from skyline01" --sparse
|   --atime-preserve -b 20 --file - | gzip -4 | buffer -m 3m -s 10k -u 100
|   -t -p 75 -B -o "/dev/nst0"
|------------------------------------------------------------
buffer: cannot open output file: Read-only file system
filename: /dev/nst0

ERROR from backup, exiting
offending command(s):
cd "/" && find . -depth -xdev ! -type s ! -regex "news/articles" !
-regex ".*~"$ -print0 | tar --create --null --files-from=-
--ignore-failed-read --same-permissions --no-recursion --totals --label
"level 0 / Mon Jun 06 19:47:13 2005 tar+gzip from skyline01" --sparse
--atime-preserve -b 20 --file - | gzip -4 | buffer -m 3m -s 10k -u 100
-t -p 75 -B -o "/dev/nst0"
Backup terminated: backup failed - status: 256

[CharlieBrady]

...
buffer: cannot open output file: Read-only file system
filename: /dev/nst0
...

That usually (always?) means just what it says - you are trying to write to a write-protected tape.

[jonnybb1]

Thank you, I have read this output also. However, there is no reason for this message as we are using the same tapes as before. We have checked the "red-tab-lock" on the tape itself and hve NOT made any changes in flexbackup that would make any changes in the r/w attributes of the device.

We have cleaned the drive, changed the tapes and bought a new one and nothing happens.

Any suggestions???

[jackl]

jonnybb1,

How old is the tape drive?
How much data does it backup each night?
Accumulated dirt can form on the heads over a period of time or almost always they just wear out. Cleaning tapes will not always remove this build up.
Have you a spare drive, that you know is ok to slot in to test?
I doubt if it is flexbackup that's causing the problem, we give up using ide drives in MS and SME systems, just too much hassle particularily in anyway dusty environment, plus the media is too expensive.

I realise they are more expensive on initial layout, put scsi DAT drives perform better and the media is a fraction of the price so running costs are less.

If you can swop out the drive with a good one you will know for sure.


Regards
Jack