Re: [Bacula-users] Disk Volumes Showing 1B Read-Only

2024-06-03 Thread Bill Arlofski via Bacula-users

On 6/3/24 12:03 PM, Ken Mandelberg wrote:


My Volumes are all Disk files. Several now show up as 1B Read-Only. In fact, as files "ls -l" shows them at their correct 
size, with modification dates that go back correctly to when they were filled.


This is likely due to my transition from Ubuntu 23.10 to 24.04. There was a period during the transition where the file 
system containing these backup volumes was either not mounted or had ownerships set incorrectly.


I'm guessing that bacula noticed that and marked those backup files 1B Read-Only. These files are the oldest of the backup 
files, the slightly more recent ones are fine.


Is there any way to convince bacula that they are good?



Hello Ken,

What does this bconsole command show?:

* list volume=xxx

If they have a volstatus of `Error`, and they really are good volumes on disk you can just try changing their volstatus back 
to Append with:


* update volstatus=Append volume=


B
UT, keep in mind that if they are old, then they will probably be past their retention periods and Bacula will probably 
immediately recycle and re-use them. If this is OK, then you are all set. Otherwise, if the data on them is important to you 
then you should disable these volumes until you are sure there is no data that you might need/want to restore:


* update enabled=no volume=

or

* update volstatus=Read-Only volume=


Then, Bacula will not touch these volumes except to read for restores, copies, 
migrations, or verifies.


Hope this helps,
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Disk Volumes Showing 1B Read-Only

2024-06-03 Thread Ken Mandelberg


My Volumes are all Disk files. Several now show up as 1B Read-Only. In 
fact, as files "ls -l" shows them at their correct size, with 
modification dates that go back correctly to when they were filled.


This is likely due to my transition from Ubuntu 23.10 to 24.04. There 
was a period during the transition where the file system containing 
these backup volumes was either not mounted or had ownerships set 
incorrectly.


I'm guessing that bacula noticed that and marked those backup files 1B 
Read-Only. These files are the oldest of the backup files, the slightly 
more recent ones are fine.


Is there any way to convince bacula that they are good?
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] HP 1/8 G2 Autoloader

2024-06-03 Thread Stefan G. Weichinger

Am 02.06.24 um 17:00 schrieb Rob Gerber:
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!


You are right.
And no worries, I only write that WEOF to tapes I want to "reset", I 
don't expect to read any data from them after doing so.


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.


Right again. Makes me worry ...


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.


I will try that later today.

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.


I ran the test last week after receiving the repaired drive and the 
tests were completely OK.


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.


no encryption key

Fourth, please reply back with the results from the above tests, and 
with any other information you think may be important.


I will do asap. Right now I wait for their admin to swap all the tapes etc



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users