-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/05/2014 09:16 PM, Dimitri Maziuk wrote:
> On 09/05/2014 01:41 PM, Josh Fisher wrote:
>>
>> On 9/5/2014 1:48 PM, Dimitri Maziuk wrote:
>>> I've another bacula setup that writes to a single filesystem. It's been
>>> running with about zero problems (knock on wood) and zero maintenance
>>> for years: auto-labelling works, volume recycling works, the only
>>> problems are spinning rust and lsi's ugly raid manglement software.
>>
>> The whole point of vchanger is to use multiple filesystems as a single
>> autochanger. For a single filesystem I would recommend Bacula's
>> built-in disk autochanger capability or else Bacula's standard disk
>> storage handling.
>
> Right, that's my point: when you use bacula's standard disk storage
> handling you get
> - automatic volume labeling,
> - automatic volume recycling,
> and generally near zero maintenance overhead.
>
> With vchanger I
> - have a job split over different disks,
> - need to manually fix the catalog every time I sneeze,
> - get into weird "intervention needed" loops where bacula "mounts" a
> volume it's just filled up and complains it couldn't write to some other
> volume it shouldn't have tried in the first place.
>
> Ergo, if you want to use multiple filesystems, the smart move would be
> to "fake" the standard disk storage over multiple filesystems.
>
> (As for built-in disk autochanger, Kern's explanation of it never made
> much sense to me: maybe it's useful for debugging or something...)
Can you tell me what my explanation of the disk autochanger was and why
it did not make sense to you?
By the way the built-in disk autochanger is typically called the
"virtual autochanger".
Providing you use pools and media types correctly the virtual
autochanger can actually handle multiple filesystems. Even without, I
have documented in the manual how to use multiple filesystems with
symlinks (a slight bit more annoying to setup). I ran very small data
center in that configuration for about 10 years. The only maintenance
was to update Bacula and add additional disk drives when the user's data
volume increased.
A very large number of our enterprise clients are using the virtual
autochanger with a lot of success. As you say, once you install it, it
just runs. I have absolutely nothing against vchanger, because a lot
of people are very happy with it. However, it is not a Bacula product,
and it seems that it works like a tape autochanger which requires much
more maintenance than the virtual autochanger, which is just a simple
extension of individual disk Devices.
Best regards,
Kern
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlQKwWcACgkQNgfoSvWqwEi5vQCff51zbNhqAX/FHugOSq9W7HXz
/bAAoOwykZVB4I0c+66tiOebi8cLv8ms
=VJKk
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
