I was planning on running the bacula-sd daemon on the openfiler pair. That is why I was asking about setting up the bacula-sd daemon under pacemaker.<div><br></div><div>our current setup is has the two nfs servers setup in an active-backup cluster, where there is a single IP that floats between the two. I have a partition set aside for storage of backups.</div>
<div><br></div><div>Sean</div><div><br></div><div><div class="gmail_quote">On Wed, Apr 18, 2012 at 2:34 PM, Andreas Kurz <span dir="ltr"><<a href="mailto:andreas@hastexo.com">andreas@hastexo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 04/18/2012 08:50 PM, Sean Roe wrote:<br>
> Hi All,<br>
><br>
> I am a new pacemaker user and I am having a bit of a quandary. I want<br>
> to use my openfiler 2.99 setup as a storage device to backup my<br>
> exisiting servers using bacula. I am running two servers that are<br>
> synced via corosync, drdb and pacemaker. If inderstand it correctly ( I<br>
> am a new openfiler user too) I need to have the bacula-sd daemon<br>
> controlled by pacemaker, is that correct? If so has anyone done a setup<br>
> like this? I have spent the last week or so looking around the web and<br>
> havent found a whole lot of info on this.<br>
<br>
</div></div>What kind of storage does the openfiler export and is the openfiler also<br>
highly available? The storage daemon of bacula needs to run where the<br>
backups are saved ... so if you import an iscsi lun or a NFS export on<br>
the bacula cluster, the sd also needs to run there.<br>
<br>
Regards,<br>
Andreas<br>
<br>
--<br>
Need help with Pacemaker?<br>
<a href="http://www.hastexo.com/services/remote" target="_blank">http://www.hastexo.com/services/remote</a><br>
<br>
><br>
> Thanks,<br>
> Sean<br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
<br>
<br>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div><br></div>