Remote backups are generally a much safer solution than storing a backup on
a local system, because a remote server is generally more reliable—as the saying goes,
don't put all your eggs in one basket.
Depending on your situation, it might make sense to buy a good system with
lots of server-grade hardware, and then buy regular systems to develop on.
Make regular backups of your server.
- CVS
- Neutrino ships with a copy of the CVS (Concurrent Versions System) client utility.
In order to use CVS, you need to have a CVS server (preferably one that
your company administers).
CVS lets you manage your source archives safely and remotely.
For more details, see the
Using CVS
chapter in this guide.
- Remote filesystems
- Storing a second backup on a remote system is often a simple yet effective
way to prevent the loss of data.
For example, if you have a basic archive of your code in a separate directory
on your local system, and then the hard disk breaks down for some unforeseen
reason, you've lost your local backup as well.
Placing a copy on a remote filesystem effectively lowers the chance of
losing data—we highly recommend it.
Note:
If you place a file on a non-Neutrino filesystem, you might lose the file's permissions.
Files under Neutrino (like other UNIX systems) have special file permissions (see
Working with Files)
that are lost if you store individual files on a Windows-based filesystem.
If you create an archive (see
"Archiving your data,"
above), the permissions are preserved.
- Other remote backups
- There are other remote version systems (similar to CVS) that are available
to Neutrino via third-party solutions.
Many of them are free; search the Internet for the tools that are right
for your company and project.