The idea here is that I don't want to leave all of my computers on all the time. So when they boot up, or if they happen to be on, once per day, it creates a file on the server via ssh. The server, having detected this file via inotify, then immediately proceeds to backup the server. This cuts down on the error messages cron sends me, and also allows for simultaneous backups.
I don't want dirvish to run every time any file on the client changes, only when a specific file is created on server. As an example, a computer named monkey creates a file via a cron job called /tmp/dirvish/monkey, which triggers the server to run dirvish on all vaults for the computer monkey. Then the computer monkey is turned off for a week. Cron and dirvish don't freak out and send me notifications for this time period. Then, when monkey is turned on, it creates the file on boot, and gets backed up immediately. Either way, I just need to know how to run dirvish and dirvish-expire on a specific vault via command line. I have the rest figured out. On Thursday 07 February 2008 02:03:19 pm Bernd Haug wrote: > Red Mop wrote: > > Anyone have any corrections for this? > > More in the principles than in the details: > > dirvish seems ill-fit for a system that gets triggered on inotify > because it will poll the whole tree again after getting triggered, > annihilating the whole performance benefit of being event-driven. > > I don't think it's at all possible to build an "ongoing backup" system > with rsync as its basis. > > Maybe I completely misunderstand what you're doing, but if you're trying > to build your own Time Machine, I guess that's not a practical way to do > it, unless you want to lock up your machine. > > Sorry if I misunderstood you, > Bernd > _______________________________________________ > Dirvish mailing list > [email protected] > http://www.dirvish.org/mailman/listinfo/dirvish _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
