Hi,
I'm currently running a 2.02 server dir and sd with mostly 2.02 clients.
However, two clients are running Debian Stable and the 1.36 bacula-fd.
These two clients seem to be being backed up and restored without
problem. Should I be worried that this will fail at some point?
Thanks,
Michael
Hi,
I'm looking for a way to have restrictions on who can restore certain
machines within my department. The reason for this is because some
machines have sensitive data which should not necessarily fall into the
hands of anybody who can perform a restore. I'm open to any suggestions
you may have.
Hi everyone,
Following the advice of Pierre Bernhardt in a thread started by me
entitled "Password Protection on Restore", I've decided to use data
encryption to not allow everyone who can use bconsole to perform a
restore-job.
To do this, I wish to encrypt data using a master certificate but
Michael Havas wrote:
> Hi everyone,
>
> Following the advice of Pierre Bernhardt in a thread started by me
> entitled "Password Protection on Restore", I've decided to use data
> encryption to not allow everyone who can use bconsole to perform a
> restor
Hi everyone,
I'm using bacula with encryption with Windows Client version 2.02 and
Director/Storage daemons on CentOS 4.4. The client both the PKI Keypair
and Master certificate for encryption.
I've been testing out restores with bacula and encryption. I've found
some disturbing results. Certa
can see, this is precisely the same error I was receiving with
Bacula Client version 2.0.2.
Any help is much appreciated,
Michael
>
> On Friday 30 March 2007 21:24, Michael Havas wrote:
>> Hi everyone,
>>
>> I'm using bacula with encryption with Windows Client version
Hi,
I was wondering if it is possible to perform a verify without having
done an initcatalog previously? I ask because one of our systems
recently experienced a crash resulting in possible data loss. I'd like
to see what data has disappeared since the last backup which was run a
few hours befo
