Well, I think something is wrong here. I WOULD NOT write any data or an EOF to any production tapes with valuable data. This will almost certainly lead to data loss. To be perfectly clear, if you rewind a tape and write EOF to that tape, the data previously written to that tape will be inaccessible without specialist hardware! The new (repaired?) drive should be able to read your old backups!
In theory you should be able to take tapes from drive A and read and write them from drive B where both drives are the same LTO generation. Tapes having been labeled in a different drive of the same generation should not have any impact on a different drive of the same generation being able to read or write that tape. If you think about it, organizations often use libraries with multiple tape drives installed inside them and beyond ensuring that the correct tape generation is loaded into the correct drives, backups written by these libraries aren't locked to a specific tape drive. Organizations also ship tapes across the world to other sites for data transfer. Being locked to a single tape drive would be an absolutely unacceptable state of affairs. So something is wrong in your case. Things to try: Please document the specific errors you have been seeing, and the results for the following tests. First, you should be able to insert a previously used tape that should have good data from the old drive on it, and perform a restore against that tape. If this fails, something is definitely wrong. Secondly, if you put a scratch tape with no valuable data on it (THIS TAPE WILL BE OVERWRITTEN AND ALL DATA ON IT WILL BE LOST) and run the btape calibration utility, then run the btape test commands, what results do you get? (Check utility and problem resolution manuals for more info). If this fails, the drive is probably still defective. Third, are you using an encryption key in your drive? If you were, you may need to reload that key into the drive firmware. The repair process may have involved factory resetting the tape drive or otherwise deleting the encryption key from memory. If this is the case, it could explain why you have been having issues with previously labeled tapes. Fourth, please reply back with the results from the above tests, and with any other information you think may be important. Robert Gerber 402-237-8692 r...@craeon.net On Sun, Jun 2, 2024, 4:18 AM Stefan G. Weichinger <li...@xunil.at> wrote: > > the drive was repaired, the head (?) replaced > > Now I have issues with the tapes labeled by the old drive ... > > I assume I should relabel them but that alone doesn't always lead to > bacula correctly recognizing the tapes. > > And the procedure to relabel multiple tapes is a bit of manual work > because I have to do that "mt -f /dev/nst0 weof" step, right? > > Does it make sense to write more to a tape in that step? A GB of random > data or so? > > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
