Re: [Bacula-users] waiting on max Job jobs - not cancelled?

[Bernie Elbourn]

On 01/04/2020 16:10, Bernie Elbourn wrote:

Oddly, jobs run sequentially as follows rather than duplicates being cancelled:

Running Jobs:
Console connected at 29-Mar-20 12:36
 JobId  Type Level Files Bytes  Name  Status
==
 70172  Back Diff    120    36.70 M Backup-pc is running
 70173  Back Incr  0 0  Backup-pc is waiting on max Job jobs


Are there any pointers to trace why the duplicate job 70173  is not cancelled? 


So I have cloned the system (less backup volumes) to test system with a test pc. That test system has  exactly the same 
database and same bacula sever and same pc setup.


On the test system the second incremental job IS cancelled. The reason is 
pretty clear

12-May 15:35 sv-dir JobId 71204: Fatal error: JobId 71202 already running. 
Duplicate job not allowed.

Is there any logging or tracing information available on an actual live system that might reveal why the production 
bacula system decides to wait on max job jobs?


Thanks




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

Re: [Bacula-users] areas for improvement?

[Thomas Lohman]

Bacula DOES NOT LIKE and does not handle network interruptions _at all_
if backups are in progress. This _will_ cause backups to abort - and
these aborted backups are _not_ resumable


Hi,

My feeble two cents is that this has been a bit of an Achilles heel for 
us even though we are a LAN backup environment (e.g. backups don't leave 
our local network).  We are still running an older "somewhat/slightly" 
customized/modified version of community bacula so I have not explored 
the restarting of stopped jobs option that has come with newer versions. 
Given that, I can recall when we initially deployed our "backups to 
disk" setup, I would see backups of large file systems/data (e.g. 1TB) 
write 3/4ths of their data to volumes and then error out due to some 
random network interruption.  I didn't like the idea that this meant 
e.g. 750GBs worth of our volume space was taken up by an 
errored/incomplete job that would never be used.  Because of this, I had 
to implement spooling which typically people would only do if their 
backups were then being written to sequential media (tape).  So, we now 
spool all jobs to dedicated spool disks and then bacula writes that data 
to the disk data volumes.  It fixed the "cruft" issue and made large 
backups more stable (along with other options).  But I can imagine a 
scenario where we would not have had to do this if Bacula could more 
easily recover from network glitches and automatically restart jobs 
where it last left off (thinking along the lines of the concept of 
checkpointing in a RDBMS).


As someone else said, this would require non-trivial changes to Bacula 
(i.e. I won't be making those changes to our version - :) ) and the 
devil would be in the details in practice.  Still, if it was put to a 
vote, I'd probably vote for this as "a nice feature to have."


cheers,


--tom



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

[Bacula-users] Fwd: Client-initiated backup communications problem

[David Brodbeck]

I wanted to give this a bump, because with more of my users working
off-site due to COVID-19 the lack of client-initiated backups has become a
major issue.

I think the main question I have is, does *anyone* have client-initiated
backups working in a situation where the client has a dynamic IP? I'd like
to know if this is even possible or if I'm barking up the wrong tree and
need to start looking for a different backup system for these machines.
Bacula has worked great for me where I had control over client IP
allocations and DNS, but this is a case where I don't have control of
either.

The docs as I read them indicate that this should work, that Bacula should
re-use the same TCP connection that the FD made to the director to run the
job, but in practice this isn't what happens -- the director tries to open
a new connection to the FD, by looking up the hostname from the Client { }
stanza.

-- Forwarded message -
From: David Brodbeck 
Date: Tue, Mar 24, 2020 at 12:18 PM
Subject: Client-initiated backup communications problem
To: bacula-users 


I'm having trouble getting client-initiated backups to work. My test system
is a laptop that normally has a fixed IP but is currently on a dynamic one.
I can connect to the FD with bconsole on the client, run the "proxy"
command to get a connection to the director, and launch a job; however,
when the job runs it tries to call the client back directly instead of
going through the proxy, which doesn't work because the client is on a
dynamic IP. I think I'm missing some configuration piece to tell Bacula not
to make a direct connection.

Here are the relevant config file stanzas (scrubbed):

---FD Config---
Director {
  Name = sh-dir
  Password = "XXX"
  Remote = yes
}

Console {
  Name = sh-fdcons
  DIRPort = 9101
  address = sh.example.net
  Password = "YYY"
}

Bconsole config on client:
Director {
  Name = eltanin-fd
  DIRport = 9102
  address = localhost
  Password = "notused"
}

Console {
  Name = sh-dir
  Password = "XXX"
}

Relevant director stanzas:
Console {
  Name = sh-fdcons
  Password = "YYY"
  CommandACL = run, restore, wait, .status, .jobs, .clients, .storages,
.pools, .filesets, .defaults, .estimate
  jobacl = *all*
  poolacl = *all*
  clientacl = *all*
  storageacl = *all*
  catalogacl = *all*
  filesetacl = *all*
}

Client {
  Name = eltanin-fd
  Address = eltanin.example.net
  FDPort = 9102
  Catalog = MyCatalog
  Password = "XXX"  # password for FileDaemon
  Job Retention = 60 days
  AutoPrune = yes
  Maximum Concurrent Jobs = 1
}

Job {
  Name = "eltanin"
  Client = eltanin-fd
  JobDefs = "StaffDesktopIncremental"
  FileSet = "eltanin"
}

JobDefs {
  Name = "StaffDesktopIncremental"
  Type = Backup
  Level = Incremental
  Allow Mixed Priority = yes
  Allow Duplicate Jobs = no
  FileSet = "OS X Desktop"
  Schedule = "StaffDesktopIncrementalSked"
  Messages = Standard
  Pool = DataCenterPool
  Accurate = yes
  SpoolAttributes = yes
  Priority = 10
  Write Bootstrap = "/opt/bacula/working/%c.bsr"
  Backups To Keep = 14
  Delete Consolidated Jobs = yes
  Next Pool = DataCenterPool
  Reschedule On Error = yes
  Reschedule Interval = 6 hours
  Reschedule Times = 3
  RunScript {
RunsWhen = Before
FailJobOnError = No
RunsOnClient = No
Command = "/usr/local/bin/wake-by-host.sh %h %l"
  }
  # On macOS we need to temporarily turn off sleep after WOL, or the machine
  # will go back to sleep faster than a teenager who's hit the snooze
button.
  #
  # Note that we intentionally use /var/run instead of /tmp for the
temporary
  # file; since we're running as root, we need to consider symlink attacks.
  RunScript {
RunsWhen = Before
FailJobOnError = No
RunsOnClient = Yes
Command = "sh -c \"/usr/bin/pmset -g live | /usr/bin/grep '^ *sleep' |
/usr/bin/sed -E 's/ sleep[[:space:]]+([0-9]+)[^0-9]*/\\1/'
>/var/run/bacula-insomnia.%j && /usr/bin/pmset sleep 0\""
  }
  RunScript {
RunsWhen = After
FailJobOnError = No
RunsOnClient = Yes
Command = "sh -c \"/usr/bin/pmset sleep `cat
/var/run/bacula-insomnia.%j` && rm /var/run/bacula-insomnia.%j\""
  }
}

-- 
David Brodbeck
System Administrator, Department of Mathematics
University of California, Santa Barbara
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] areas for improvement?

[Heitor Faria]

Hello Alan,

>>> Bacula DOES NOT LIKE and does not handle network interruptions _at all_
>>> if backups are in progress. This _will_ cause backups to abort - and
>>> these aborted backups are _not_ resumable

I wonder if anyone has ever tried changing the tcp_retries values on Linux and 
how they would affect the Bacula clients' connections 
.

Regards,
-- 
MSc Heitor Faria 
CEO Bacula LATAM 
mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ]


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

Re: [Bacula-users] areas for improvement?

[Alan Brown]

On 27/05/2020 15:13, Gary R. Schmidt wrote:
> On 27/05/2020 23:17, Alan Brown wrote:
>>
>>
>>
>> Bacula DOES NOT LIKE and does not handle network interruptions _at all_
>> if backups are in progress. This _will_ cause backups to abort - and
>> these aborted backups are _not_ resumable
>>
>> Similarly, if there's any kind of disruption between the director and
>> database, the only fix is to restart the director
>>

>> Opinion: I know bugs aren't sexy to work on but these need fixing, not
>> being brushed off. This is the difference between LAN-quality and actual
>> Enterprise grade software.
>>
> I do not consider these to be bugs - they aren't simple errors where
> someone made a mistake or used the wrong sized variable - they require
> a large amount of re-design and reimplementation of Bacula's
> communication modules, and the scheduler, and no doubt other bits to
> go away.


Nonetheless they need to be done. There are a lot of assumptions made
about networks that simply do not hold true or only work in SOHO/SMB scale.


>
> Bacula started life twenty years ago, and the environment has changed
> since then, and, while Bacula has kept up with a some things, disk as
> a target rather than tape, frex, something like re-startable jobs is,
> as I have said, not just an extension or addition to what is there,
> but a big change to a large part of Bacula.


Restarting is there for stopped jobs already. The question is how much
work is needed to extend that to aborted or errored jobs


> And, from the commercial stand-point, that the changes could be made
without interrupting the existing income stream. 

There's a "cost of not implementing". I'm facing pressure to replace
Bacula and this is pointed to as one of the reasons - bear in mind we're
a paying customer who would go away if this isn't sorted


>
> Then there's the projected time-line before it could be released?

You can't project that if it's not even on your TODO list and right now
it keeps being swept into the "WON'T DO" basket.


> I don't want to think about that, Bacula is fragile as it is, ripping
> it apart and stitching it back together would be a massive task!


This is exactly why I _do_ want to think about it. This is _where_ it's
fragile and what most fundamentally needs fixing.

Enteprise software needs to be robust. Bacula is not - in extremely
critical areas


"If carpenters built buildings the way programmers write programs, the
first woodpecker that came along would destroy civilization."


> And Bacula does not have that capability, not in the OSS space nor in
> the Enterprise space.
>
> All the above said, I think that re-startable jobs would be a great
> enhancement for Bacula, but how often and for how long does it try by
> default before giving up?  :->
>

restartable, or reconnecting? (and why not just set defaults - then let
the users decide on #attempts/timeouts?)


The single most fragile part of Bacula:  If the database connection
glitches for _any_ reason the only solution is to restart the entire
program - and you lose _everything_ that was underway at the time.

As I said, that includes using a high availability database (postgresql,
etc). As soon as heads are switched there's a necessary glitch in the
connection.


Database connections are _supposed_ to be stateless. Bacula breaks that
and as such it's a fundamental bug, whether by design or not.






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

Re: [Bacula-users] areas for improvement?

[Gary R. Schmidt]

On 27/05/2020 23:17, Alan Brown wrote:


I've been running Bacula for ~15 years (community/enterprise) and have
identified a few areas which are in desperate of improvement:

For an "enterprise" grade backup system, it's amazingly fragile in a few
areas (particularly in actual Enterprise networks!)


Bacula DOES NOT LIKE and does not handle network interruptions _at all_
if backups are in progress. This _will_ cause backups to abort - and
these aborted backups are _not_ resumable

Similarly, if there's any kind of disruption between the director and
database, the only fix is to restart the director


What that means is that Bacula _cannot_ be used with a High Availability
database because network interruptions (when switching servers) are part
of the HA paradigm.

It also means that operators have to be _extremely_ careful about
allowing automated or other system upgrades


In days of multi-TB backup sets, this is turning into a showstopping
problem.

As we are an Enteprise customer this has been raised with Baculasystems
but been given _very_ low priority.   I'd like to hear opinions from the
wider community on this


Opinion: I know bugs aren't sexy to work on but these need fixing, not
being brushed off. This is the difference between LAN-quality and actual
Enterprise grade software.

I do not consider these to be bugs - they aren't simple errors where 
someone made a mistake or used the wrong sized variable - they require a 
large amount of re-design and reimplementation of Bacula's communication 
modules, and the scheduler, and no doubt other bits to go away.


Bacula started life twenty years ago, and the environment has changed 
since then, and, while Bacula has kept up with a some things, disk as a 
target rather than tape, frex, something like re-startable jobs is, as I 
have said, not just an extension or addition to what is there, but a big 
change to a large part of Bacula.


And that's a massive risk, it's the sort of task I would be looking at 
having a whole team work on, a couple of designers, six to ten 
programmers, and a QA team with a nasty manager who was not restricted 
from saying, "No!" when things don't work quite right.


And the mob above all have a *really* good understanding of how the 
various bits of Bacula work, and interact, and are capable of and 
allowed to replace ancient groaning bits of code with newer versions 
that just aren't as wrong.  (First task - rename all files so the 
extensions represent the C++ code inside them, and for the really 
cruddy^Wannoying stuff, G++.)


And, from the commercial stand-point, that the changes could be made 
without interrupting the existing income stream.


Then there's the projected time-line before it could be released?
I don't want to think about that, Bacula is fragile as it is, ripping it 
apart and stitching it back together would be a massive task!


And Bacula does not have that capability, not in the OSS space nor in 
the Enterprise space.


All the above said, I think that re-startable jobs would be a great 
enhancement for Bacula, but how often and for how long does it try by 
default before giving up?  :->


Cheers,
GaryB-)


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

[Bacula-users] areas for improvement?

[Alan Brown]

I've been running Bacula for ~15 years (community/enterprise) and have
identified a few areas which are in desperate of improvement:

For an "enterprise" grade backup system, it's amazingly fragile in a few
areas (particularly in actual Enterprise networks!)


Bacula DOES NOT LIKE and does not handle network interruptions _at all_
if backups are in progress. This _will_ cause backups to abort - and
these aborted backups are _not_ resumable

Similarly, if there's any kind of disruption between the director and
database, the only fix is to restart the director


What that means is that Bacula _cannot_ be used with a High Availability
database because network interruptions (when switching servers) are part
of the HA paradigm.

It also means that operators have to be _extremely_ careful about
allowing automated or other system upgrades


In days of multi-TB backup sets, this is turning into a showstopping
problem.

As we are an Enteprise customer this has been raised with Baculasystems
but been given _very_ low priority.   I'd like to hear opinions from the
wider community on this


Opinion: I know bugs aren't sexy to work on but these need fixing, not
being brushed off. This is the difference between LAN-quality and actual
Enterprise grade software.





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

Re: [Bacula-users] Update via rpm repository

[Luca De Rugeriis]

Ok thanks for your input, I surely will be looking into it!

Best regards,
Luca

Il giorno mer 27 mag 2020 alle ore 12:10 Per Qvindesland  ha
scritto:

> Hi Luca
>
> TO be honest I have no idea if it’s the same packages as bacula has on
> their site or not, but I been using his repo for a long time now on 200+
> centos 7 and 8 instances with no problems and it’s updated at the same time
> as Bacula releases so it’s really stable.
>
> Have a look here https://copr.fedorainfracloud.org/coprs/slaanesh/Bacula/ and
> here for his release cycle
> https://copr.fedorainfracloud.org/coprs/slaanesh/Bacula/package/bacula/
>
> I could never get the bacula repo to work properly in Katello.
>
> Regards
> Per
>
>
>
>
> On 27 May 2020, at 08:02, Luca De Rugeriis 
> wrote:
>
> Hi Per, thanks for helping!
> I'm using
> http://www.bacula.org/packages/${bacula_key}/rpms/9.6.3/el7/x86_64/
> as per official documentation (where $bacula_key is an alphanumeric key
> they sent me by email when I subscribed to bacula.org website).
>
> Are the rpms on fedoraproject.org any different from bacula's ones?
>
> Best regards,
> Luca
>
> Il giorno mar 26 mag 2020 alle ore 21:48 Per Qvindesland  ha
> scritto:
>
>> Hi Luca
>>
>> Have you tried adding in
>> https://copr-be.cloud.fedoraproject.org/results/slaanesh/Bacula/epel-7-x86_64/
>>  to
>> your repo server? I update all my instances with foreman/katello in this
>> way.
>>
>> Regards
>> Per
>>
>>
>>
>> On 26 May 2020, at 19:59, Luca De Rugeriis 
>> wrote:
>>
>> Hi Davide and thanks for chiming in!
>> Configured with redhat satellite just means that we use satellite (a
>> standard for Redhat enterprise) to get software updates but it is the same
>> as configuring bacula repo with yum on a single host.
>> What I’d like to know is: how we can get say from bacula 9.6.3 to (say)
>> 9.6.4, since we are pointing at 9.6.3 repository...
>> I couldn’t find much explanation reading the docs. Thanks!
>>
>> Il giorno mar 26 mag 2020 alle 18:57 Davide Franco 
>> ha scritto:
>>
>>> Hi Luca,
>>>
>>> Can you elaborate a bit more what you mean by
>>>
>>> - configured the repo with red hat satellite
>>>
>>> Thanks for your feedback
>>>
>>> Davide
>>>
>>> On Tue, 26 May 2020 at 15:24, Luca De Rugeriis <
>>> luca.deruger...@gmail.com> wrote:
>>>
 Hi,
 does anyone know something about these repos? Or where may I ask? The
 just get security updates maybe, and I have to change repo manually if I
 want to upgrade bacula version?

 Thanks!
 Luca

 Il giorno mer 20 mag 2020 alle ore 15:57 Luca De Rugeriis <
 luca.deruger...@gmail.com> ha scritto:

> Hi everyone, my first post here and thanks for the amazing software!
> I just configured the community repo with Redhat Satellite and
> migrated to the latest Bacula version.
> The URL I'm using for the repository contains a specific Bacula
> version (9.6.3), what I'd like to accomplish is to have the software
> updating automatically (like 9.6.4, 9.6.5, 9.7...) is that possible?
>
> Thanks for your help,
> Luca
>
 ___
 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
>>
>>
>>
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] PHP exception for restores after retention period

[Yakup Kaya]

Hello Marcin,

Thank you very much for all your help, and for creating a feature request.

Kind regards,

Yakup Kaya 

From: Marcin Haba 
Sent: Wednesday, May 27, 2020 5:58 AM
To: Yakup Kaya
Cc: bacula-users@lists.sourceforge.net; Markus Flaisch
Subject: Re: [Bacula-users] PHP exception for restores after retention period

Hello Yakup,

Yes, I would really like to add this feature. I opened a feature
request for that:

https://bugs.bacula.org/view.php?id=2546

To see progress in this task, please observe above ticket.

Best regards,
Marcin Haba (gani)

On Tue, 26 May 2020 at 22:32, Yakup Kaya  wrote:
>
> Hello Marcin,
>
> Thank you very much for your fast reply. And thank you very much for your 
> time,
>
> Then I assume that this is the default behavior for now. Would it be right to 
> think that this maybe a feature planned, for future releases maybe?
>
> Kind regards,
>
> Yakup Kaya
> 
> From: Marcin Haba 
> Sent: Tuesday, May 26, 2020 7:03 PM
> To: Yakup Kaya
> Cc: bacula-users@lists.sourceforge.net; Markus Flaisch
> Subject: Re: [Bacula-users] PHP exception for restores after retention period
>
> Hello Yakup,
>
> This type of restore is not supported yet. To prepare restore Baculum
> uses the Bacula Bvfs interface that uses Bvfs cache. If file records
> for a job in the catalog are pruned then the Bvfs cache for those
> records is removed as well.
>
> Best regards,
> Marcin Haba (gani)
>
> On Tue, 26 May 2020 at 16:54, Yakup Kaya  
> wrote:
> >
> > Hi everybody,
> >
> >
> > We have a problem that we cannot make a restore from the job history 
> > details, if the retention period has passed for a job (and the file list is 
> > deleted), or the file list is manually purged. But restore from bconsole 
> > still works for that job id.
> >
> >
> > When we try to restore with the restore wizard on Baculum, we get the 
> > following exception from RestoreWizard PHP file. To reproduce the problem 
> > one can just purge files for a job id as follows using bconsole, and try to 
> > restore all files from the baculum interface fort that job. Or try to 
> > restore with a job id, for which the retention time for deleting the file 
> > list has already passed.
> >
> >
> > *purge files jobid=1996;
> >
> >
> > Here is the exception after running restore wizard from Baculum:
> >
> >
> > -
> >
> > Prado\Exceptions\TPhpErrorException
> > Description
> >
> > [Notice] Undefined variable: ret (@line 897 in file 
> > /usr/share/baculum/htdocs/protected/Web/Pages/RestoreWizard.php).
> > Source File
> >
> > /usr/share/baculum/htdocs/protected/Web/Pages/RestoreWizard.php (897)
> >
> > 0886:
> > 0887: $ret = $this->getModule('api')->create(array('jobs', 
> > 'restore'), $restore_props);
> > 0888: $jobid = 
> > $this->getModule('misc')->findJobIdStartedJob($ret->output);
> > 0889: // Remove temporary BVFS table
> > 0890: $this->getModule('api')->set(array('bvfs', 'cleanup'), 
> > array('path' => $path));
> > 0891: }
> > 0892: $url_params = array();
> > 0893: if (is_numeric($jobid)) {
> > 0894: $url_params['jobid'] = $jobid;
> > 0895: $this->goToPage('JobHistoryView', $url_params);
> > 0896: } else {
> > 0897: $this->RestoreError->Text = implode('', 
> > $ret->output);
> > 0898: $this->show_error = true;
> > 0899: }
> > 0900: }
> > 0901:
> > 0902: /**
> > 0903:  * Load restore jobs on the list.
> > 0904:  *
> > 0905:  * @return none
> > 0906:  */
> > 0907: private function loadRestoreJobs() {
> > 0908: $restore_job_tasks = 
> > $this->getModule('api')->get(array('jobs', 'resnames', '?type=R'))->output;
> > 0909: $jobs = array();
> >
> > Stack Trace
> >
> > #0 /usr/share/baculum/htdocs/protected/Web/Pages/RestoreWizard.php(897): 
> > Prado\PradoBase::phpErrorHandler(8, 'Undefined varia...', 
> > '/usr/share/bacu...', 897, Array)
> > #1 
> > /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/TComponent.php(1169):
> >  RestoreWizard->wizardCompleted(Object(Prado\Web\UI\WebControls\TWizard), 
> > Object(Prado\Web\UI\WebControls\TWizardNavigationEventParameter), 
> > 'oncompletebutto...')
> > #2 
> > /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/Web/UI/WebControls/TWizard.php(664):
> >  Prado\TComponent->raiseEvent('OnCompleteButto...', 
> > Object(Prado\Web\UI\WebControls\TWizard), 
> > Object(Prado\Web\UI\WebControls\TWizardNavigationEventParameter))
> > #3 
> > /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/Web/UI/WebControls/TWizard.php(1365):
> >  
> > Prado\Web\UI\WebControls\TWizard->onCompleteButtonClick(Object(Prado\Web\UI\WebControls\TWizardNavigationEventParameter))
> > #4 
> > /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/Web/UI/TControl.php(1470):
> >  
> > 

Re: [Bacula-users] Recommendation for NAS Appliance that Supports Bacula Community

[Andrea Venturoli]

On 2020-05-26 19:10, J W wrote:

I want to run Bacula Director on the NAS rather than mounting the NAS 
storage on the server and running Director on the server so that if 
something goes wrong and overwrites everything on the server then it 
does not overwrite the NAS as well.


Any suggestions? I have been looking at FREENAS, Synology, Qnap , and 
ReadyNAS so far.


Not exactly what you are asking, but...
I've never run the Director on a NAS; I've been running the Storage 
Daemon on Zyxels and QNAPs.

The latter are overall better (which is normal, given they cost more).
I've never had many troubles, anyway.

Just my 2c.

 bye
av.


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