Dtyjlui

Don't ask why. I need to devise an incremental file backup solution (writing to a USB attached disk array) that has a super easy interface to allow any end user (like even a receptionist) to restore a version of any file to their local workstation.

My initial thoughts would be to devise a solution that stores the last 10 versions (or all versions in the last 30 days) in the same target folder but with an incremental number appended to the filename (filename_1.ext filename_2.ext). The end user can see the filenames date-time to determine when that version was created. The end user could browse the files via a mapped drive in Windows Explorer using SAMBA. I can think of anything easier for the user than that.

Here's some potential challenges on the server side that may need to be addressed:

• Frequency of backup related to performance. We're talking a data storage folder containing probably 100,000 files and 5TB of data. The incremental backup needs to be run at least once an hour. So it's got to be a solution that is architected to handle pretty large file collections. I'm anticipating this may not be an issue though as the volume of file changes is low, maybe 100 files change every hour at most.




• Data duplication. Yes, storage is cheap, but with multiple versions the back storage requirement will be large. I don't think it's possible to have data de-duplication and let the end user be able to browse versions of files with a simple SAMBA file share. (Looked into RDIFF and you need to run the rdiff command to restore.)

So I'd be open to a solution (free or low-cost) that instead of the users mapping a drive to the backup folder, they could bring up a web interface to browse the files and download as needed. Not quite as simple as mapping a drive but this would allow the backend to handle rebuilding a file version.

Any suggestions on solutions?

A low tech solution would be to use rsync with the --link-dest option. This can be set up to create incremental snapshots that appear to the user as full copies. The trick is that changed files are copied over, whereas unchanged files are hard-linked to their copy in the previous snapshot.

The script rsnapshot, available in the Ubuntu software center, automates this use of rsync. Then it is a matter of having different mounts on the user's systems, a writable mount used by the timed backup script, and a read only mount readily visible to the users in their home folder. Or you design another way to access the backup, as you suggested, using a browser.