Arno Lehmann wrote: > Hello, > > On 5/28/2007 10:50 AM, Rich wrote: > >> On 2007.05.28. 10:55, Stefan Wintermeyer wrote: >> >>> Hi, >>> >>> we'd like to use Bacula as our one and only backup solution. But >>> we have a problem with all home-office-installations. They normaly >>> work with an asynchron DSL connection. It would take days to >>> backup to our normal backup server in the internet. And normaly they >>> only have a couple of hours during the night. >>> >>> Having a bright moment I thought: "hmmm... why don't we install >>> some sort of proxy at the home offices? People could backup their >>> stuff to the proxy and the proxy syncs with the central server. >>> Time wouldn't be such a big issue (even if it takes a couple of >>> days to sync)." >>> > > Only that you won't have reliable backups in your central office during > that time :-( > > >> well, maybe clustered bacula servers might be helpful here, if those >> ever get implemented ;) >> >> currently your best bet probably is to use rsync at some point, which >> would work nicely for syncing. >> > > Yup. > > I'd do that like this: > > Set up an SD on the home workers computers. Send their backups to the > local SD only. > Set up the local SDs to write only small files. > Use rsync to sync these volumes to your central backup server. As there > are only small files, the overhead for rsync shouldn't be too bad. >
Or maybe: Setup local SDs on the home office computers with a FileStorage type device writing to NFS shares on the central server over a VPN connection. Setup local SDs to write only small volumes (files). Turn on data spooling so that the local SDs spool to local disk before writing to the NFS share on the central server. Restores would then use an NFS share on the central server and would not require any additional effort. However, rsync might be more robust than using NFS over VPN with an ADSL connection. As Arno points out, there are many possibilities. One must weigh cost vs. performance vs. reliability and etc. > Or rsync your whole computers to your central office and backup from > there. Restores would then need additional effort. > > >>> Has anybody a solution for that problem? >>> > > This is adifficult setup. I don't think a perfect solution is possible - > my work-around from above, for example, requires extra work if you need > to restore from the centrally located volumes (importing the volmes into > the catalog). > > Another possible solution might be to take a full backup after you set > up the home computers in your central facilities and only run > incremental or differential backups when the machines ore off-site. This > leaves a certain amount of unreliability, because you might miss files > (especially relocated ones) in your backups. > > You could also set up a local SD at the home offices which would be used > for full backups to a removable hard disk which would then be mailed to you. > > Or get a better network to your home offices :-) > > Hmm, there are many possibilities, it seems. Which one fits your needs > best is difficult to decide without more detailed information, I guess. > > Arno > > >>> Stefan >>> >> ... >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
