>> > Yes, very interested, please post it. Does this also work when >> files on _both_ >> > sides are created, modified and deleted? >> > >> >> Arien, >> I don't think rsync can manage the situation you describe where both >> sides can change. >> >> I hope I'm wrong though. > > You are not wrong. > > Two different filesystems on two different disks will not be able to > handle things like multiple opens of files, files being deleted on one > server, saved on the other, etc, etc. > > What you want is a maybe raid1 (mirroring) over a networked block > device: http://www.it.uc3m.es/~ptb/nbd/ This way you have 1 filesystem, > although I'm not sure if this will work in a "access on both sides" > setup. I have never done this and have no idea about speed issues etc, > but it should work. There might still be a problem with two machines > trying to access the same file at the same time by different users > though. > > If the idea is to have samba shares on different networks, they could > perhaps offer the share to each other, either as smb shares, or using > nfs? Or introducing a third server that holds the actual files and > serves via nfs? > >> I remember reading about solving this kinds of issues on the file system >> level (using an alternate fs). But perhaps someone who knows what he/she >> is talking about can take over from here... :-) > > A netowrked filesystem will better handle this than rsync.
Ok, so the idea is not to use a networked file system because of the slow DSL speed. The goal for these servers is to have one dir on both sides where users can put and modify files, and a nightly batch to sync those two, so users can work at full local speed during the daytime and have all files on the local server. My idea was to rsync both sides, but its a problem when someone deletes a file. Maybe it is a good idea to prevent users from deleting files, since the purpose of these share is to archive documents and should not be deleted. The fact that a file created one one side isn't immediatly copied to the other side is no issue, the next day is fine, because its for backup and archiving only. The customer wants a really safe backup to another location and keep the DSL traffic as low as possible. If someone has a working config, please post it. -- Ariën Huisken Xilay Software _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
