Bob MacCallum wrote: > Thanks for all the ideas on this. > > re: userfiles/db sync, would this work..? > > backup: > > 1. mysqldump to date-stamp-named files > 2. rsync -arv /data/base2/files/ /backup/base2/files > (note, no --delete option on purpose) > > restore: > > 1. undump whichever mysqldump is needed > 2. copy over all files that are older than the mysqldump >
There is nothing in BASE that guarantees that the name of a deleted file is not reused by another file later on. However, it is very unlikely that this should happen with the current implementation. I think you need to upload a file, delete it, upload another within the same second AND the system must choose the same random filename for both files. Even if this happens it would only matter if you started a mysqldump after the upload of the first file, but before the deletion of it. For all practical reasons, I think you can assume that files will always have unique pathnames, and if rsync is just adding new files to the backup directory you should be able to restore the file system to any point in time. > The one problem I see is that the restore can bring back files that had been > deleted in BASE. I doubt these would interfere with the running of BASE > however. A small program could be written to delete any files that are not > known about by the db (unless there is already something to do this). No there is no such program. > Alternatively, one can add the --delete option to rsync and live with only > being able to restore the latest dump (which is OK for us for now). /Nicklas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
