[Vchanger-users] vchanger vs Bacula 13 Storage Groups

[Justin C. <jus...@gm...>]

Hi all,

originally I was looking into vchanger because I intend to store my tier-2 backups on externally attached USB HDDs, where not all of the required storage space fits on a singe USB HDD. Let’s call this use case (a)

As I understood vchanger, it would allow me to define a disk changer that subsumes several individual USB HDDs, even though their file volumes need to have a different type because they live in different paths. 

My questions:

(1)
Now someone on the Bacula-users mailing list told me that vchanger would actually not(!) fill up the disks one by one, i.e. fill up one disk, then leave it alone and fill up another disk. Is that correct?

(2)
Bacula 13 introduces Storage Groups, where I could place individual externally attached USB HDDs as storage devices into the same storage group. Would that actually already help me to dynamically add additional USB HDDs when then already attached HDDs are full?

(3)
Considering we are just talking about my use case (a), what are the differences of what Bacula V13 Storage Groups and vchanger can do? Does vchanger offer significant benefits over storage groups in this use case?

Thanks for considering my questions.
 J/C