Your solution is working well and it is similar to my current configuration
(all laptop are syncing their D drive to the home dir of the user that owns 
the laptop on a Filer:user work saved).
The problem is that due to multiple instances of the same file on the server, 
we run out of space (80 laptops 60GB each even if not full is pretty much).

So we bought a DELL SCSI Bay that has 1.6TB of storage space for backuppc
thinking that we would reconver our Filer in project storage only.

Currently, our vital data from our servers is stored using bacula with offsite 
clones and lpatop are backed up with BackupPC while still being synced to our 
Filer (until I find a solution to offsite backup my BackupPC server using my 
available resources).
Thus in case of hard drive crash, I can quickly recover the hard drive and in 
case of DRP, I have the Offsite Tapes of the Filer.

My dream would be to have my servers backed-up using BackupPC with a remote 
BackupPC as failover in case of DRP. That would greatly reduce tape usage as 
I would avoid daily tape incrementals, I would reduce tape usage beacause of 
single instance storage and I wouldn't need offsite storage anymore (full 
tape bacups would only be used for long term archiving).

> The real solution here is to make sure the users save all their work
> on a server instead of their desktops and run the backups of the
> server during off hours.  That's not always possible, especially
> for laptops.  One approach that might work for you at the expense
> of some disk space (which is pretty cheap these days) is to do
> a scripted rsync from the desktops to a uncompressed copy on a
> local server.  You can give the user a read-only share via samba
> so they can quickly grab a copy of yesterday's file if you want.
> Then let one or both of your backuppc servers back up the server
> copy which will be compressed and linked efficiently for the
> older versions at least.  I do something similar to this in
> some remote offices so one copy is available locally and I
> can let backuppc use rsync over ssh which doesn't work well
> directly to a windows box.

Anyway, your solution is interresting and will surely fits some readers needs.

BTW, maybe it could be interresting to have a backup strategy page in the FAQ 
of BackupPC with pro and cons for each?

--
        Olivier LAHAYE
        Motorolalabs IT manager
        Saclay, FRANCE


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Reply via email to