Kern Sibbald writes:
When I was first researching the kind of basic organization I wanted for
Bacula, I took a look at Amanda, read a bit on their email list, and talked
to a user who had used Amanda, which basically from what I understand works
much like that. That is Amanda figures out what
Hello,
On 5/5/2006 3:49 PM, Bill Moran wrote:
On Fri, 5 May 2006 14:47:12 +0200
Kern Sibbald <[EMAIL PROTECTED]> wrote:
Hello,
Thanks for your thoughts.
When I was first researching the kind of basic organization I wanted for
Bacula, I took a look at Amanda, read a bit on their email lis
Back on the discussion at hand, adding those directives might be interesting from a compliance POV. You set up the SLA's and then you set up your backup schedule. It can then inform you when you are not incompliance with your stated goals. That way you still have the ability to set whatever sche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doesn't that directive already exist, to a certain extent (rerun failed
jobs, or something like that?). In some cases it doesn't work, but
server down I'd think it would.
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Us
Woudn't this works just as well?Rerun Failed Levels =
If this directive is set to yes (default no), and Bacula detects that
a previous job at a higher level (i.e. Full or Differential) has failed,
the current job level will be upgraded to the higher level. This is
particularly u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In Samba's case, you certainly do continue to have the option of editing
it manually, BTW. I don't use SWAT much, but I did switch between
editing the file and using SWAT on it when I was first starting out.
Seemed to work fine.
_ _ _ _ ___ _
Kern Sibbald wrote:
> That said, I have often thought of adding directives to guarantee that
> certain
> levels are performed at specified intervals (i.e. Differental at least once a
> week, ...). In the future, I could see adding some additional resources such
It would be nice if Ba
On Fri, 5 May 2006 14:47:12 +0200
Kern Sibbald <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Thanks for your thoughts.
>
> When I was first researching the kind of basic organization I wanted for
> Bacula, I took a look at Amanda, read a bit on their email list, and talked
> to a user who had used
Hello,
Thanks for your thoughts.
When I was first researching the kind of basic organization I wanted for
Bacula, I took a look at Amanda, read a bit on their email list, and talked
to a user who had used Amanda, which basically from what I understand works
much like that. That is Amanda fi
My reason for writing this is to share my thoughts with the Bacula
community before I move on to another project and forget all this.
The other day, I was documenting the backup procedure here, and how
it fit in with our DRP and business policy. As I was trying to
document our Bacula config and
10 matches
Mail list logo
