Remote Backup of Windows PC using Cygwin/Rsnapshot/Rsync?

  • Toilet Overflow

    I would like to backup my dad's home computer to a remote server. Challenges:

    • His machine runs Windows XP
    • I would like to backup his whole drive (40GB)
    • His upload bandwidth is not spectacular (384kbps)

    My current plan is to install cygwin on his box, and configure rsnapshot on my remote server to access his machine on a daily basis and download updated files. I prefer this route because other Windows-based backup services make me nervous as I never know when they are not going to run.

    With that said, I am not sure that cygwin/rsnapshot is the best way to approach this. Is there a better configuration I could use to accomplish remote backups in this case?

  • Answers
  • Torben Gundtofte-Bruun

    I can warmly recommend CrashPlan - this is free software (Win/Mac/linux) that lets you back up from one machine to another, over LAN or Internet. CrashPlan makes money by offering cloud storage, but the basic software is free to use.

    CrashPlan will use the network when it's idle. With 40GB it will obviously take a while to get it all, but if it's not time-critical then this is definitely one of the nicest tools.

    I use this on several machines in my family - across several countries!

  • Mike Fitzpatrick

    I also prefer this style of backup over Windows-based backup services but find it is generally only suitable for backup of documents files - not system files. There are many files (registry, mailboxes, etc.) which can be written to by Windows while you are copying them which means your copy may be out of sync or corrupted.

    I do some pre-checks in the Cygwin bash script to make sure certain processes (such as e-mail programs) are not running before proceeding with the rsync.

    Also, if you have physical access to the remote server, you can save a lot of time and bandwidth on the first sync by using an external HDD to copy the contents across from source to destination. I haven't used rsnapshot but this method works fine with rsync.

  • matpol

    I have used the mozy service before. This runs all the time in the background and updates files as they change. Obviously the first backup will take a bit of time and the space does cost but I never had any problems with it. I would recommend this as a simple solution. This will back up you system files too.

  • Related Question

    cygwin cygdrive paths and Windows Command Prompt
  • Matt Baker

    Possible Duplicate:
    cygwin cygdrive paths and Windows Command Prompt

    I'm having a weird issue with cygwin acting inconsistently between installations, specifically scp. I have c:\cygwin\bin in my Windows PATH in both cases. When I run the following command from a Windows Command Prompt, however, I get very different results between the two installations:

    scp /cygdrive/c/something.txt User@server:${HOME}/something.txt

    On the one machine it transfers the file just fine, but on the other machine I get an error:

    /cygdrive/c/something.txt: No such file or directory

    However, if I execute the command this way on the machine that gave me the error, it transfers just fine:

    scp /c/something.txt User@server:${HOME}/something.txt

    Why the differences? Is there something I need to configure within cygwin to make this work with /cygdrive/c?

    I've tried running mount --change-cygdrive-prefix /cygdrive but that doesn't fix the problem.

    UPDATE: Here's something more interesting. If I do ls /c from a Windows command prompt I get what you would expect, as list of everything in C:. However, ls /cygdrive/c says that it doesn't exist. Running those commands from the cygwin bash yields exactly the opposite behavior.

  • Related Answers
  • Gilles

    It looks like your scp and ls commands are not Cygwin versions. Presumably, you start bash, your startup scripts change the PATH to put the Cygwin /bin in front, whereas otherwise your PATH has non-Cygwin versions of scp and ls early on.