On Jun 4, 2008, at 7:06 AM, Leopold Palomo-Avellaneda wrote:
Hi,changing my current configuration using nfs (local) to another one with rsyncand I have realised that probably I have a missunderstand the dirvish program. So, I would like to ask you if I have done a big mistake.I have a box (ris) with the /home of my users. I have another box (ulises) where I would like to put the backup files. If I mount (nfs) the partition from ulises to ris, and I run dirvish in ris, I can do a local backup, as Ihave done.But, but reading again the documentation I have found that, if I want to use my transport as ssh, I would need to run dirvish in ulises, not in ris, because the server is the box where the backup is stored and the client isthe box where I take the files from.Is this correct? Or can I run dirvish in one box and store the files inanother box using ssh?
You are correct in your reevaluation of how it works. Dirvish is meant to be used on the backup server (it does `pulls', not `pushes').
The reason you can't push is because Dirvish depends on having information about inode numbers for hard-links, which you can't do when you're pushing the data elseware. The only way (I can think of) to save the files remotely is what you were doing first: mount the remote drive via NFS (NFS preserves inode information). In theory, you're still doing a `pull'---just from one location on the virtual filesystem to a second location which happens to be mounted NFS. Assuming you can optimize your NFS options and network as was discussed in the previous thread, there isn't a reason you can't do this. But if you can toss a few perl scripts on ulises (which is all dirvish is, after all) and run them via cron, then you can do a pull over rsync.
-- Eric Searcy OSU Open Source Lab
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
