Defining a backup strategy, we are evaluating our previous different policies, mostly based on Bacula and rsnapshot.
Bacula here is used with different media (tape, tape library, virtual changer with RDX disks, ...) but we are considering for this a 'File' storage type. The goal is to have a 'quick and efficient' backup system that have some level of history, but minimizing space, and that can be used as a 'intermediate' level for subsequent backups (eg, on a tape library). Rsnapshot is very efficient, and even if the data to backup is HUGE, can be initialized very easy, simply 'waling' to the data repository, do an initial rsync on a disks, and then copy that as a startbase for rsnapshot. Also, being a folder structure, can be easily put on other media. Coons are that is very insecure: backup have to be originated by the backup server, that need ssh root access to the client, possibly screwing all the client (ok, we can think of chrooting something, but...). I'm trying to give a try to bacula with a 'VirtualFull' job, but i'm a bit confused... i suppose job consolidation is done on the pool, not on a media; but if yes, how media get rotated? Also, there's some way to 'offline init' a full backup in a 'VirtualFull', eg a way not to trasfer 4TB of data at 10Mbit/s for the initial full backup? Someone have some hints, or some examples? Thanks. -- Alla fiera dell'est, per due soldi un topolino mio padre compro` (A. Branduardi) _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
