On 12/11/2012 7:44 PM, Dan Langille wrote:
> On Dec 11, 2012, at 7:11 PM, Phil Stracchino wrote:
>
>> On 12/11/12 16:47, ccspro wrote:
>>> And make sure your Catalog backup has the lowest priority (say 99) so
>>> it will be completed after all Jobs are done for the day.
>> Personally, I don't both
On 12/11/12 19:44, Dan Langille wrote:
>
> On Dec 11, 2012, at 7:11 PM, Phil Stracchino wrote:
>
>> On 12/11/12 16:47, ccspro wrote:
>>> And make sure your Catalog backup has the lowest priority (say 99) so
>>> it will be completed after all Jobs are done for the day.
>>
>> Personally, I don't bo
On Dec 11, 2012, at 7:11 PM, Phil Stracchino wrote:
> On 12/11/12 16:47, ccspro wrote:
>> And make sure your Catalog backup has the lowest priority (say 99) so
>> it will be completed after all Jobs are done for the day.
>
> Personally, I don't bother with a catalog backup job separate from my D
On 12/11/12 16:47, ccspro wrote:
> And make sure your Catalog backup has the lowest priority (say 99) so
> it will be completed after all Jobs are done for the day.
Personally, I don't bother with a catalog backup job separate from my DB
backups, since my Bacula catalog is by far the largest schem
2012/11/29 Dan Langille
> On Nov 29, 2012, at 4:56 PM, Jonathan Horne wrote:
>
> If i have say, 2 data base servers, can i set bacula to ensure they are
> not being backed up at the same time? Even if they are the last 2 jobs
> running, id like to not back them both up simultaneously.
>
> Firs
On Nov 29, 2012, at 4:56 PM, Jonathan Horne wrote:
> If i have say, 2 data base servers, can i set bacula to ensure they are not
> being backed up at the same time? Even if they are the last 2 jobs running,
> id like to not back them both up simultaneously.
>
First guess: Set them as different
