Re: [Bacula-users] Understanding virtual autochanger default config

2020-05-15 Thread Josh Fisher


On 5/14/2020 7:23 AM, Alberto Bortolo wrote:

Hello,
I'm completely a newbie with Bacula: I'm studying all the guides and 
just few days ago I've been able to us it! Success!


But I still cannot understand how the virtual autochangers work:
I touched very little from the default config and I just created for 
different network shares and mounted them in the main root.


This is my config (I just leave relevant parts)

Autochanger {
  Device = FileChgr1-Dev1, FileChgr1-Dev2
  Changer Command = ""
  Changer Device = /dev/null
...
}

Device {
  Name = FileChgr1-Dev1
  Media Type = File1
  Archive Device = /backup/bacula1
...
}

Device {
  Name = FileChgr1-Dev2
  Media Type = File1
  Archive Device = /backup/bacula1-alt
...
}

The result is I made a successful backup on /backup/bacula1/Volume1 
but when I try to restore it, the job is looking in the other File1 
device ( /backup/bacula1-alt/Volume1 ) that of course is empty, 
because Volume1 was created in the other path.



Yes. if you are going to use multiple Archive Device paths, then you 
must use a different Media Type for each different Archive Device path. 
That may or may not work for your use scenario. If you want multiple 
mountpoints to be treated as one group of volumes with the same media 
type and any Device to load any volume on any of the mountpoints, then 
look into vchanger on Sourceforge.





I was supposing that during restoration the program will scan to both 
autochanger paths to see which one has the most recent record, but 
seems it doesn't work in this way.
If I try to setup the "Archive Device" option to the same path it 
works flawlessy (and it seems the "Best Practices for DiskBased 
Backup" guid recommends something like that) so I cannot understand 
the difference of making an autochanger with just one device.



The Archive Device for FileChgr1-Dev2 can be the same as the Archive 
Device for FileChgr1-Dev2. You can have as many Device entries as 
wanted, all with the same Archive Device. The reason would be to allow 
multiple simultaneous jobs to run. A Device can have only one volume 
file open at a time, but multiple Devices with the same Archive Device 
can each have a different file on that mountpount opened.





Thank you in advance for the explanations!

--
Alberto


___
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


Re: [Bacula-users] Installation/Startup Issues

2020-05-15 Thread Jeff Thomas
No, same issue.


On Fri, May 15, 2020 at 5:43 AM Radosław Korzeniewski <
rados...@korzeniewski.net> wrote:

> Hello,
>
> czw., 14 maj 2020 o 18:03 Jeff Thomas  napisał(a):
>
>> Problem solved.   FQDN needed in bconsole.conf
>>
>>
> I'm very glad that you've solved your issue! Great!
>
> So, it seems you have a different issue then previously reported, right?
>
> 13-May 11:23 bacula-dir JobId 0: Fatal error: Could not open Catalog
> "MyCatalog", database "bacula".
> 13-May 11:23 bacula-dir JobId 0: Fatal error: postgresql.c:332 Unable to
> connect to PostgreSQL server. Database=bacula User=bacula
> Possible causes: SQL server not running; password incorrect;
> max_connections exceeded.
> 13-May 11:23 bacula-dir ERROR TERMINATION
> Please correct configuration file: bacula-dir.conf
>
> best regards
> --
> Radosław Korzeniewski
> rados...@korzeniewski.net
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Installation/Startup Issues

2020-05-15 Thread Radosław Korzeniewski
Hello,

czw., 14 maj 2020 o 18:03 Jeff Thomas  napisał(a):

> Problem solved.   FQDN needed in bconsole.conf
>
>
I'm very glad that you've solved your issue! Great!

So, it seems you have a different issue then previously reported, right?

13-May 11:23 bacula-dir JobId 0: Fatal error: Could not open Catalog
"MyCatalog", database "bacula".
13-May 11:23 bacula-dir JobId 0: Fatal error: postgresql.c:332 Unable to
connect to PostgreSQL server. Database=bacula User=bacula
Possible causes: SQL server not running; password incorrect;
max_connections exceeded.
13-May 11:23 bacula-dir ERROR TERMINATION
Please correct configuration file: bacula-dir.conf

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users