On Tue, Dec 18, 2012 at 01:50:37PM +0200, Nasos Nikologiannis wrote:
> I am planning an enterprise-level network backup solution with the
> following requirements/restrictions:
>
> -Local and remote servers with heterogenous operating systems
> (Linux,Windows)
> -Backup policy that dictates backup data availability monthly for a year
> cycle, weekly for a month cycle and daily for a week cycle.
> -No tape device availability, only finite amount of disk storage.
>
> I am using Bacula, currently at testing environment, to implement the
> above. The setup that i am using is the following:
>
> -Full backup every month, differential every week and incremental daily at
> dedicated volumes for each client and each backup type. The volumes
> produced according to this scheme: Client1-Full-Vol, Client3-Diff-Vol etc.
> -Since volume recycling is essential due to finite disk space, the
> respective rules have been applied to the corresponding Pools. There are N
> Pools = clients x backup type(3 types)
>
> My question is if this setup of backup ,for the given requirements, is too
> complicated involving too many volumes and pools.
>
> Any suggestion would be appreciated.
>
> Thanks

This is rather similar to the setup we're running now, except for our
requirement to use copy jobs to move backups to offline storage via
lto5.

How much data are you expecting to back up, how many files and so on?
Our bacula database (mariadb) is about to hit 200G soon, so the File
table already poses a major bottleneck (deleting or recycling a volume
can take several hours, for instance).

Maybe you should consider using separate catalogs so you can avoid
stuffing everything into one large File table, however that comes with
other headaches attached like multiple catalog maintenance and so on.

Apart from that I wouldn't consider your setup too complicated, make
sure you use separate media types for your full, inc and diff pools
unless you keep everything in a single directory on the disk storage.

Cheers, Uwe



--
NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA