Backup Tool for Unity non-Pro

I found this nifty tool called Areca Backup that does differential/incremental backups. I haven’t used it extensively yet, but I’m hoping it plays nicer with Unity non-Pro than SVN does. It doesn’t add any metadata or database inside your working copy.

In SVN if you moved/copied/renamed files/folders around without using svn mv and the like, the working copy breaks, and you pretty much can’t commit your changes anymore without careful fixing.

Areca doesn’t track changes between file moves. It doesn’t even track changes anymore if you rename the file. But the old unrenamed/unmoved file is still there in the old backup entries, so if you need to get back to it you can do so.

This is slightly better than the manual method of zipping up your project everytime you want a new backup. A version control system is the most ideal but we all know its not possible with Untiy non-Pro.

I did some few fixes to have it running on Macs: http://dl.dropbox.com/u/25260770/Areca/Areca-7.2.3.dmg

Its not perfect, it may hang when you try to exit it. But I’ve tested it and backing up does work properly.

Source code: http://dl.dropbox.com/u/25260770/Areca/areca-7.2.3-mac-src.zip

Svn since new version does not make metadata, but has one database.

I wonder if that fixes it then. The problem is if you want to move a file in an svn working copy, you can’t just do a move, you have to use “svn move” so the metadata (wherever its stored) gets updated properly. If not, the svn working copy breaks.

Unity (at least non-Pro) does simple file moves only, so the svn metadata definitely breaks.

If your main problem with SVN is that it versions per folder, you should probably try out Git + Git Gui.
GIt keeps everything in the top level folder.

Hmmm no, that’s not the only problem. Can git retroactively discover if, say, something moved/copied/renamed a file? What happens is Unity automatically moves folders around in a Unity project’s metadata folder without notifying the version control system. Ideally, the version control system should still be able to track where the files went.

Git doesn’t actually track file copy/move operations itself, instead concentrating on tracking the content of the files. This means you’re fine to move files round using any method.

The one slight issue here though is doing this type of tracking in-depth can be a comparatively slow operation and so Git doesn’t do it by default, instead it can be enabled by passing a ‘–follow’ parameter to Git’s log command which should make it do what you want. I think there’s also a configuration change you can make to enable this permanently but I really can’t remember what it is if there is.

I’m not very proficient with git but I tried it out and it does indeed track a file back to before it was renamed. However I can’t seem to do git diff and see the diffs properly. git diff of a renamed and, at the same time, changed file compares the file to /dev/null