Hi,
Thanks for the suggestion - we already run auto-recycling with a limit on
the number of volumes (60 full, 60 incremental). Most of our schedules run
full backups once a week and incrementals in between, with a thirty day
expiry on the incremental volumes and three months on the fulls. Rotating
On Thursday 17 March 2005 04:58 am, Mike Winiberg wrote:
> Hi,
>
> We recently had a problem which I haven't been able to fully recover from,
> and would appreciate some advice about the best thing to do should
> something like this happen again:
[...]
> However, when I next tried to run a backup,
> Hi,
>
> We recently had a problem which I haven't been able to fully recover
> from, and would appreciate some advice about the best thing to do
> should something like this happen again:
>
> We run Bacula on Suse 9.0, using network attached storage which is
> mounted locally on /nas
>
> Du
Hello,
The bscan was never meant to put your catalog back exactly as it was. The
purpose is to allow you to use the catalog to recover files on old Volumes.
I recommend that you revert to your previous catalog, possibly deleting the
two volumes in conflict, then do Full saves on everything (sor
> Hi,
>
> We recently had a problem which I haven't been able to fully recover from,
> and would appreciate some advice about the best thing to do should something
> like this happen again:
>
> We run Bacula on Suse 9.0, using network attached storage which is mounted
> locally on /nas
>
> Due t
Hi,
We recently had a problem which I haven't been able to fully recover from,
and would appreciate some advice about the best thing to do should something
like this happen again:
We run Bacula on Suse 9.0, using network attached storage which is mounted
locally on /nas
Due to a daytime power ou
