38
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: − + − + Line 41:
Line 41: − + − + Line 55:
Line 55: − + − + − + Line 79:
Line 79: − + Line 95:
Line 95: − + − + Line 108:
Line 108: − + Line 141:
Line 141: − + + + + + + + + + + +
no edit summary
A clever pooling scheme minimizes disk storage and disk I/O. Identical files across multiple backups of the same or different PCs are stored only once resulting in substantial savings in disk storage and disk I/O.
A clever pooling scheme minimizes disk storage and disk I/O. Identical files across multiple backups of the same or different PCs are stored only once resulting in substantial savings in disk storage and disk I/O.
One example of disk use: 95 latops with each full backup averaging 3.6GB each, and each incremental averaging about 0.3GB. Storing three weekly full backups and six incremental backups per laptop is around 1200GB of raw data, but because of pooling and compression only 150GB is needed.
One example of disk use: 95 laptops with each full backup averaging 3.6GB each, and each incremental averaging about 0.3GB. Storing three weekly full backups and six incremental backups per laptop is around 1200GB of raw data, but because of pooling and compression only 150GB is needed.
Optional compression support further reducing disk storage. Since only new files (not already pooled) need to be compressed, there is only a modest impact on CPU time.
Optional compression support further reducing disk storage. Since only new files (not already pooled) need to be compressed, there is only a modest impact on CPU time.
No client-side software is needed. The standard smb protocol is used to extract backup data on WinXX clients. On linux clients, tar over ssh/rsh/nfs is used to backup the data. With version 2.0.0, rsync is also supported on any client that has rsync or rysncd.
No client-side software is needed. The standard smb protocol is used to extract backup data on Windows clients. On linux clients, tar over ssh/rsh/nfs is used to backup the data. With version 2.0.0, rsync is also supported on any client that has rsync or rysncd.
A powerful web (http/cgi) user interface allows administrators to view log files, configuration, current status and allows users to initiate and cancel backups and browse and restore files from backups.
A powerful web (http/cgi) user interface allows administrators to view log files, configuration, current status and allows users to initiate and cancel backups and browse and restore files from backups.
Users are sent periodic email reminders if their PC has not recently been backed up. Email content, timing and policies are configurable.
Users are sent periodic email reminders if their PC has not recently been backed up. Email content, timing and policies are configurable.
Tested on Linux, Freenix and Solaris hosts, and Linux, Win95, Win98, Win2000 and WinXP clients.
Tested on Linux, Freenix and Solaris hosts, and Linux, Windows 95, Windows 98, Windows 2000, Windows XP, and Windows Vista clients.
Detailed documentation.
Detailed documentation.
Open Source hosted by SourceForge and freely availble under GPL.
Open Source hosted by SourceForge and freely available under GPL.
=== Requirements ===
=== Requirements ===
*Mount a volume on /var/lib/BackupPC
*Mount a volume on /var/lib/BackupPC
This part is optionnal but highly recommanded. Backups should allways be on a separate volume.
This part is optional but highly recommended. Backups should always be on a separate volume.
First, prepare your hard drive for ext3 fs (you can use any fs which support hardlinks, I allways use ext3 as it's verry reliable)
First, prepare your hard drive for ext3 fs (you can use any fs which support hardlinks, I always use ext3 as it's very reliable)
In this example, I use a simple partition /dev/sdb1, it could also be a RAID array (/dev/md3) or a LVM logical volume (or a combination of RAID and lvm).
In this example, I use a simple partition /dev/sdb1, it could also be a RAID array (/dev/md3) or a LVM logical volume (or a combination of RAID and lvm).
By the way, if you know how to manage LVM, its usage is also recommanded as it'll be easier to manage backups data later.
By the way, if you know how to manage LVM, its usage is also recommended as it will be easier to manage backups data later.
mkfs.ext3 -L BACKUPPC -m 1 /dev/sdb1
mkfs.ext3 -L BACKUPPC -m 1 /dev/sdb1
*create some symlinks
*create some symlinks
This part is optionnal but recommanded. With these commands, all BackupPC related files (config and logs) will be stored on the BackupPC volume. You'll then be able to swap the BackupPC disk between two servers.
This part is optional but recommended. With these commands, all BackupPC related files (config and logs) will be stored on the BackupPC volume. You'll then be able to swap the BackupPC disk between two servers.
mkdir -p /var/lib/BackupPC/{etc,log}
mkdir -p /var/lib/BackupPC/{etc,log}
*smeserver-template is a sample config file to backup a SME Server.
*smeserver-template is a sample config file to backup a SME Server.
*localhost-template is a sample to backup the server itself
*localhost-template is a sample config file to backup the server itself.
*windows-tempalte is a sample to backup a windows host using cygwin+rsyncd
*windows-template is a sample to backup a windows host using cygwin+rsyncd
To create a host using a template, create a new host, add =<template_name>
To create a host using a template, create a new host, add =<template_name>
=== Upgrade from smeserver-backuppc.fws-3.0-1 ===
=== Upgrade from smeserver-backuppc.fws-3.0-1 ===
If you allready use the previous version of the contrib, some other steps are needed are the default location of the backups has changed from /opt/backuppc/files to /var/lib/BackupPC
If you already use the previous version of the contrib, some other steps are needed are the default location of the backups has changed from /opt/backuppc/files to /var/lib/BackupPC
The easiest way is just to symlink the old location to the new one:
The easiest way is just to symlink the old location to the new one:
signal-event backuppc-update
signal-event backuppc-update
{{Note box|If you make changes to the "sudo" propertie, you should then check the sudoers syntax to be sure everything is OK. For this, you should run
{{Note box|If you make changes to the "sudo" properties, you should then check the sudoers syntax to be sure everything is OK. For this, you should run
visudo
visudo
And close the file. If visudo detects an error, it'll tell you. }}
And close the file. If visudo detects an error, it'll tell you. }}
=== Operation ===
To configure a SME Server client to be backed up using a configuration based on the provided smeserver-template, configure SSH from the backup server as follows:
[root@backupserver ~]# su -s /bin/bash backuppc
bash-3.2$ ssh-keygen -t rsa -b 2048
(used a blank passphrase)
bash-3.2$ cat /var/lib/BackupPC/.ssh/id_rsa.pub | ssh root@myserver.mydomain.com \
"cat >> /root/.ssh/authorized_keys2"
(confirm the host key)
=== Uninstall ===
=== Uninstall ===