Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am looking for a backup solution to handle large documents well. I don't think that "back-up" software is what I am looking, but it is the best term I can see. We are not interested in recoverability or restoring the system as it is.

My wife is a photographer that takes about ~3GB/week worth of pictures. She would like to have to store all the pictures in an external storage. Yet, she would rather work on the pictures locally, when she uploads the pictures from camera or edits them.

We are looking for a tool that that treats the local drive like a cache rather than desired state to be restorable. So here are the requirements that we desire:

  1. You can work on your local data offline. We cannot just operate on the external storage directly.
  2. Any addition/modification changes to the local data will be propagated to the external storage the next time it is connected. Hopefully automatically.
  3. Any deletion on the local drive shouldn't be propagated to the external storage.
  4. Deletions on the storage drive would propagate to the local one, or at least once it is deleted it is never imported again from the local drive
  5. Not interested in state restoration. We don't care about how the storage was like two weeks ago. We'll never want to restore that stage.

Desires, but not requirements:

  1. Track file content rather than file names/paths. We would like to be able to change the directory hierarchy of the external storage without confusing the tool.
  2. Restoration of a file state. While we aren't interested in the state of the entire backup, it will be nice to see the changes each document went through.

In my simple view, this is what a document backup should look like; as opposed to system backup where I am always interested in restoring the system if it fails. Are there any software that uses this model? Any suggestions for my backup flow?

share|improve this question

closed as off-topic by Tog, random May 12 '14 at 11:45

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking product, service, or learning material recommendations are off-topic because they become outdated quickly and attract opinion-based answers. Instead, describe your situation and the specific problem you're trying to solve. Share your research. Here are a few suggestions on how to properly ask this type of question." – Tog, random
If this question can be reworded to fit the rules in the help center, please edit the question.

A version control system (VCS) like git would meet most (all?) of your requirements, at the cost of being more technical and likely requiring command-line use for some operations. That said there are good GUIs for most popular VCS on all major operating systems.

Addressing your points:

  1. You can 'check out' the latest version of all files to work on, then 'push' the changes back to the main storage.
  2. Automatically pushing changes back would be quite easy to set up with some scripting.
  3. You choose which changes to keep. Any mistake can be reverted.
  4. You can remove files from the current state of the files easily, and undo this if it was in error.
  5. It is possible to remove history from version control, but this would be a weak point in this solution (and probably the most technical part).
  6. git tracks files by content. You perform moves and renames with its tools without losing history of the files.
  7. Version control allows any version of any file to be easily accessed.

Some programs to check out: git home page and on StackOverflow, mercurial/hg. A lot of resources are available on the web on the subject although much of it will be aimed at programmers.

PS - I know this is a crazy solution :)

share|improve this answer
+1 because CSV are indeed the closest to what i want. Git won't work because git needs to pull the entire repo. With SVN, you can checkout individual folders. – notnoop Aug 14 '09 at 23:39

I really think the Time Machine will do just what you want here. Am I overlooking something?

Also, have you looked at Apple's Aperture? It has pretty comprehensive workflows for photographers, including image archival and versioning.

share|improve this answer
With time machine, if I delete a picture on the harddrive it'll be deleted in the most recent backup. To access that picture, I need to go back in time till I see it. I would like to open the harddrive and just see all the pictures at once whether I have them now on my harddrive or not. – notnoop Aug 14 '09 at 21:40
Also Time machine doesn't let you control which files want to delete if the backup is filling up. I would rather go and delete the not so nice picture rather than delete all of my "old" backups that contain nice images. – notnoop Aug 14 '09 at 21:47
Time Machine supports Finder search, so you can track down deleted files a bit more easily than you describe. Plus, you can manually tell Time Machine to perform a backup (useful if you're about to do something risky). And as far as disk usage: Time Machine just runs with the mentality of filling up the entire backup disk and deleting the oldest weeks when necessary. You really might want to give it a shot. – Kevin L. Aug 14 '09 at 23:46

Not the answer you're looking for? Browse other questions tagged or ask your own question.