Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.

2019-03-22 Thread Mariusz Kruk
Yeah, I can understand why but even if we put away all the usual cloud privacy issues it's completely not feasible for me since I'm setting up my home backup system and at home I have only a 10/1Mbps ADSL line. So imagine uploading few terabytes of data using 1Mbps uplink :-D That's why I'm

Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.

2019-03-19 Thread Bartek R
Yes, I do have statically mounted volume and no off-site backup since i do not need it. Even if this changes i would rather think about S3 instead of removable media. Regards Bart pon., 18 mar 2019 o 19:49 Spadajspadaj napisaƂ(a): > Thanks for the config but if I'm not mistaken it won't let me

Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.

2019-03-18 Thread Spadajspadaj
Thanks for the config but if I'm not mistaken it won't let me do what I mainly wanted to achieve with vchanger - it won't let me plug in and out external drives. That's the whole point of using vchanger for me so I can take one external disk and move it somewhere offline or even off-site, Your

Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.

2019-03-18 Thread Bartek R
Hi, I have tried to start vchanger long time ago but i found it a bit too complex. Since then i am running following configuration: Autochanger { Name = local-sd Changer Device = /dev/null Changer Command = "" Device = drive-0, drive-1, drive-2, drive-3 } Device { Name =

[bareos-users] 3999 Device "vchanger-1" not found or could not be opened.

2019-03-18 Thread Go Away
Hello. I'm trying to set up an environment with removable disks managed by vchanger. I managed to install vchanger, I created the media files but I cannot seem to be able to make bareos see my virtual autochanger. And I'm a bit stuck. Whenever I try to do "update slots" I'm getting the 3999