>> 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. >> > 2 things to rsync > good it syncs only changes, but if a file on server1 is deleted and > server2 syncs with server1 the file is back :-) > rather make a del-dir, where user can place the files and every 10 > days or so delete the dir. make a 10 day grace period. :-)) > the best thing here is a cluster imho! cause everything will be > written on one machine and sync it to the slave.
Deleting is not so important, it's only for the local sysadmin and he can do it by hand on both sides as he has full access to the shares. -- Ariën Huisken Xilay Software _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
