{"id":265,"date":"2010-03-23T17:00:39","date_gmt":"2010-03-23T16:00:39","guid":{"rendered":"http:\/\/www.frozax.com\/blog\/?p=265"},"modified":"2015-04-05T08:15:13","modified_gmt":"2015-04-05T08:15:13","slug":"backup-work-ease","status":"publish","type":"post","link":"https:\/\/www.frozax.com\/blog\/2010\/03\/backup-work-ease\/","title":{"rendered":"Backup your work with ease"},"content":{"rendered":"

We all agree that doing backups is really important to prevent dramatic data losses. I have always been pretty lazy about that topic and usually rarely backup anything, or not very often. I think the problem was that I didn’t find easy ways to do it. For my current project, I do backups nearly everyday and thats not taking much time, if any. Here is what I do:<\/p>\n

Source code : Perforce<\/h3>\n

\"p4\"It’s not really “backup” but I think it’s important to use proper source control to save your code. Having the history of the code is a wonderful feature. I especially like what is called Time-lapse view in Perforce because you can see instantly when was added a specific (buggy) line of code.<\/p>\n

Most people go with Subversion<\/a> (SVN) but I chose Perforce<\/a> and I really like it. It is free only for two or less users so it may not suits you if you have a big team. It is very easy to set up, I usually run both the server and the client on the same computer. I use my iBook to connect to the server when doing Mac ports.<\/p>\n

Perforce can also be used for resources but I don’t do it because having different revisions for resources takes up a lot of disk space.<\/p>\n

Resources : SyncBack<\/h3>\n

Even if I am not using real source control \"syncback\"for resources, I backup my resources using SyncBack Freeware<\/a>. In my current setup, it creates a zip file of my root project directory. To save space, I use filters. For example, I do not backup intermediate files made by the compiler or EXE files because they can be built from the source. Same for graphics file, I keep the original resource but don’t save the final png files. About every two or three weeks, I rename my backup with the date of the day and I keep two or three versions of resources.<\/p>\n

SyncBack is very easy to use and there are also more complete SE and Pro version (shareware).<\/p>\n

Online backup : DropBox<\/h3>\n

\"dropbox\"In addition to a local save on another drive in case of a disk crash, it is also important to keep your backups off-site, just in case. First, I used a feature in SyncBack that sent the backup to a FTP. But I now use DropBox<\/a>, an online service that automatically synchronize a folder on your hard drive with an online storage. All you have to do is to set up SyncBack so that the final zip ends up in the folder you synchronize with dropbox. A few minutes later, it is up-to-date online, on a safe and distant server.<\/p>\n

DropBox allows you to have multiple users and private folders but I didn’t try yet. However, I plan on using Dropbox for my future works with art and audio contractors if possible. The free service of DropBox is limited to 2 Gb. There is a paying service and a referral program to get more space. If you plan to subscribe, please use this link<\/a> so that I can get a 250 Mb bonus! \ud83d\ude09<\/p>\n

Conclusion<\/h3>\n

Doing backups is useful only if you do it automatically or at least very regularly. The tools presented here really allows you to do that. Do you use these softwares too? Do you use even better tools?<\/p>\n

<\/a><\/a><\/a><\/a>\n