On Tue, Dec 18, 2012 at 6:50 AM, Nasos Nikologiannis <nasosnik AT gmail DOT 
com> 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.
>

Take a look at the bacula vchanger

http://sourceforge.net/projects/vchanger/

To me this greatly simplifies disk setups especially if you want
concurrency and volumes from different pools loaded at the same time.

John

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users