July 2007 This how-to article is based on my experience setting up and maintaining a regular Ubuntu 7.04 install running as the backup server at UCSD. The clients varied in their OS’s; Mac OS X, Windows XP, Linux (Debian and Ubuntu). Except for the install commands (eg apt-get install), this instruction should work with other Linux distros.
Client Set Up
Please click the OS that you use to see the specific instructions.
If you have Cygwin installed or are planning on getting it in the future, please use the link for Win XP with Cygwin. If you do not know what Cygwin is, most likely you don’t have it. However, if you would like to find out, click here to find out.
Server Set Up
This manual is written for the administrator who will be setting up the backup server. You must have a root privilege. The server computer will be the computer that will do the backup and keep the backed up data.
Read more on taksuyama.com
These instructions are provided in the hope that they’ll be useful to others. If you find them useful, please drop me a note: stephen [at] physics.unc.edu. Similarly, if you implement this setup on platforms other than Windows and wish to contribute your code (either under GPL, or transferring copyright to me) please do so.
One common problem plaguing IT professionals is how to backup data on laptops and other mobile devices. There is considerable value in mobile data, but many users seldom, if ever, bring their laptops back to the corporate or academic campus where it may be regularly backed up.
BackupPC is an excellent open-source product for backing up computers. It excels at backing up desktops and servers, but laptops (as moving targets) are especially difficult. By default, BackupPC can be configured to wake up periodically, say hourly, and look for laptops that have appeared on the network. This is not without issues (some of which can be worked around), but these are compounded when laptops do not have static IP addresses.
A better solution is to allow users to backup valuable data on the laptops on-demand. This page details my solution to do this.
Read more on www.physics.unc.edu
Author: Cody Dunne
Last Edited: 12/06/2008
Most of this guide is not original work, and is based substantially on the numerous sources available online for these tools. It does, however, combine many of the disparate sources for this information, add some of my own experience and insights, and provides an excellent backup scheme for Windows XP/Vista clients. Hopefully it will help other users in this process and prevent them from spending as much time getting it working as I did.
Read more on www.cs.umd.edu
Last modified on:
12-15-2008 – Created.
This guide will assist you in setting up BackupPC using the CentOS RPMs in the CentOS testing repository. It will not go into detailed explanations of all the possible BackupPC configurations. It will also assume that you’re setting up BackupPC to do backups across rsync. BackupPC is capable of archive, tar, smb, and rsyncd backups, but this guide will concentrate only rsync to other Linux hosts. BackupPC is heavily documented when it comes to configuration options, and the guide is present in the web interface. Also, BackupPC should reside on it’s own server, because Apache must be run as the BackupPC user created on the system which could affect regular webserver things.
Read mor on wiki.centos.org
RAID devices can be partitioned, like ordinary disks can. This can be a real benefit on systems where one wants to run, for example, two disks in a RAID-1, but divide the system onto multiple different filesystems:
Read more on linux-raid.osdl.org
Author: Falko Timme <ft [at] falkotimme [dot] com>
Last edited 12/12/2008
This short guide explains how you can configure software RAID to send you an email when something’s wrong with RAID, for example if a hard drive fails. I’ve tested this on Debian Etch, but it should apply to all other distributions with minor adjustments to paths, etc.
Read more on Howtoforge.com
Linux has a special mount option for file systems called noatime. If this option is set for a file system in /etc/fstab, then reading accesses will no longer cause the atime information (last access time – don’t mix this up with the last modified time – if a file is changed, the modification date will still be set) that is associated with a file to be updated (in reverse this means that if noatime is not set, each read access will also result in a write operation). Therefore, using noatime can lead to significant performance gains.
Read more on Howtoforge.com