The problem with a VNC-only solution (or other remote desktop app), as already aluded to by another poster, is that you're still stuck on ONE computer (whichever one you're talking to). Sure you can log in from anywhere, but if the hardware fails on the "server" you're talking to, you still suffer as much downtime as before.
What you need is to combine VNC with a distributed (ie. multiple-computer, at multiple-locations, with multiple-ISPs on multiple-backbones) setup. I'm not aware of any automated products for this, what I've done in the past is to have an main CVS repository on one box, and a cron-job that updates it every night from a different machine. If you lose that main box, you'll have a worst-case day old copy of the repository on the other machine, and can still continue to do your work. If it's a big problem with several days of downtime, you can then set the backup as the main CVS server.
This could work for any number of "backup" computers, but even having two will pretty much eliminate the downtime you've suffered before. And you can use CVS to backup all sorts of stuff (code, IDE config files, even binary data).
In the *nix world, esp. if you're used to a command-prompt instead of a GUI, using VNC is often overkill - I tend to use an OpenSSH java applet (such as AppGate's excellent MindTerm), which can run over slow connections without issue, and can be served from any number of computers.
(However, for a Wintel solution, you'd have to find a configuration-management tool that can automatically update stuff for you - not sure if Source-Safe or StarTeam can do this).
Slashdot Mirror
What you need is to combine VNC with a distributed (ie. multiple-computer, at multiple-locations, with multiple-ISPs on multiple-backbones) setup. I'm not aware of any automated products for this, what I've done in the past is to have an main CVS repository on one box, and a cron-job that updates it every night from a different machine. If you lose that main box, you'll have a worst-case day old copy of the repository on the other machine, and can still continue to do your work. If it's a big problem with several days of downtime, you can then set the backup as the main CVS server.
This could work for any number of "backup" computers, but even having two will pretty much eliminate the downtime you've suffered before. And you can use CVS to backup all sorts of stuff (code, IDE config files, even binary data).
In the *nix world, esp. if you're used to a command-prompt instead of a GUI, using VNC is often overkill - I tend to use an OpenSSH java applet (such as AppGate's excellent MindTerm), which can run over slow connections without issue, and can be served from any number of computers.
(However, for a Wintel solution, you'd have to find a configuration-management tool that can automatically update stuff for you - not sure if Source-Safe or StarTeam can do this).