[CentOS] Re: Bacula -- near-line disk, off-line tape, diffs, windows, etc...

Tue Aug 2 22:02:43 UTC 2005
Bryan J. Smith <b.j.smith at ieee.org>

Aleksandar Milivojevic <alex at milivojevic.org> wrote:
> Can I have my backups go to the disk, instead of using
> tapes?  Can I have some on disk, and some on tapes?
> On-site disk, off-site tapes combination?

Paul Heinlein <heinlein at madboa.com> wrote:
> Yes to all of the above.

Bryan Cardillo <dillo+centos at seas.upenn.edu> wrote:
> monthly fulls, first weekend of the month, start
> early saturday am, sometimes run until monday am.
> weekly diffs and daily incrementals run in an 8
> hour nightly window I should also mention, we're
> using disk spooling, an lto3 drive (soon to be two),
> hardware compression, and a dedicated gig network.

It's coincidental that the "disk and tape" as well as "backup
window" concepts were discussed today, because Sys Admin just
came out with its new issue on storage:  
  http://www.samag.com/  

I've been spoiled by the FalconStor VTL (Virtual Tape
Library) solution.

Now I don't expect Freedomware solutions to offer the same
level of "transparent tape virtualization," but I would be
interested in any Open Source framework that uses a
combination of near-line disk and off-line tape approaches.

E.g.,
1) nodes only rsync diffs over network to the "host" backup
server
2) the "host" backup server manages those diffs/volumes as
near-line
3) the "host" backup server committs to tape for off-line as
the discretion of the sys/netadmin

Any Freedomware solution that makes this easy to manage is
definitely of great interest to me.  I reguarly go to clients
who believe they "have to" not only commit to tape, but do it
in real-time (end-system to end-tape) and only during their
backup windows (instead of sending diffs over the window, and
then letting a backup server commit as scheduled).



-- 
Bryan J. Smith                | Sent from Yahoo Mail
mailto:b.j.smith at ieee.org     |  (please excuse any
http://thebs413.blogspot.com/ |   missing headers)