Someone wrote an end of file on the beginning of the Volume, you
probably should see if there are multiple files on that tape. If so,
you may be able to recover some valid data after the tape end of file,
but this is generally tricky and time consuming.
btape has commands that will allow you to
I can't even use bextract or bcopy on that one tape. it gives me the same
errors.
Warning: acquire.c:265 Read acquire: Requested Volume AOB760L4 on
tape_Drive (/dev/nst0) is not a Bacula labeled Volume, because:
ERR=block.c:1023 Read zero bytes at 0:0 on device tape_Drive (/dev/nst0)
I used btape to check it and idd it says it has no files on it and no label
either. sigh...
+--
|This was sent by c...@belnet.be via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
I used btape to check it and idd it says it has no files on it and no label
either. sigh...
now, if I relabel that one tape.
Will it have impact on a restore with the other 3 tapes?
I, myself have no other options either, after troubleshooting this matter.
Other than trying to find out what
From your posts: during the restore, it selects the 3 other tapes
correctly, but it does not
complete the restore, because of the 4th tape.
I suppose you are saying that Bacula restores the files in the others
3 volumes and then fails the job just in this last tape. If this is
correct, you
On 24.10.2014 13:34, Che_m wrote:
According to the bacula database, the tape has 500GB of data written on it.
I'm trying to check out on the tape itself, but knowledge of the mtx script
is limited.
However, the difference of nst0 and st0 is, the first one does not
autorewind. and as
I already did,
found nothing useful than you should relabel it, or use /dev/nst0 instead of
/dev/st0.
I've always used /dev/st0
The correct tape is in the drive, the tape is labeled correct. I can mount all
28 tapes in the library, except that one.
The last status of the tape was marked append
I already did,
found nothing useful than you should relabel it, or use /dev/nst0 instead of
/dev/st0.
I've always used /dev/st0
The correct tape is in the drive, the tape is labeled correct. I can mount all
28 tapes in the library, and are all recognized. Except for that one.
The last
I already did,
found nothing useful than you should relabel it, or use /dev/nst0 instead of
/dev/st0.
I've always used /dev/st0
The correct tape is in the drive, the tape is labeled correct. I can mount all
28 tapes in the library, and are all recognized. Except for that one.
The last
From the little I have seen, it looks like your tape was never written
(the data may be on another tape -- please check) or the tape was
overwritten. Using /dev/st0 could *possibly* cause the tape to be
overwritten, but Bacula attempts to avoid that.
On 14-10-24 04:10 AM, Che_m wrote:
I
According to the bacula database, the tape has 500GB of data written on it.
I'm trying to check out on the tape itself, but knowledge of the mtx script is
limited.
However, the difference of nst0 and st0 is, the first one does not autorewind.
and as stated by kern, bacula avoids rewinding the
hi all,
I need to perform a restore, and one of the tapes the restore needs is not
being recognised. The error is as follows
23-Oct 10:04 bacula-sd JobId 133822: Warning: acquire.c:265 Read acquire:
Requested Volume AOB760L4 on tape_Drive (/dev/st0) is not a Bacula labeled
Volume, because:
I need to perform a restore, and one of the tapes the restore needs is not
being recognised. The error is as follows
23-Oct 10:04 bacula-sd JobId 133822: Warning: acquire.c:265 Read acquire:
Requested Volume AOB760L4 on tape_Drive (/dev/st0) is not a Bacula
labeled Volume, because:
13 matches
Mail list logo
