653
edits
Changes
From SME Server
Jump to navigationJump to search→Known Issues
===Features===
===Features===
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 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.
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.
* 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.
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.
* 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 full set of restore options is supported, including direct restore (via smbclient, tar, or rsync/rsyncd) or downloading a zip or tar file.
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.
* Supports mobile environments where laptops are only intermittently connected to the network and have dynamic IP addresses (DHCP).
* Flexible configuration parameters allow multiple backups to be performed in parallel, specification of which shares to backup, which directories to backup or not backup, various schedules for full and incremental backups, schedules for email reminders to users and so on. Configuration parameters can be set system-wide or also on a per-PC basis.
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.
* Tested on Linux, Freenix and Solaris hosts, and Linux, Windows 95, Windows 98, Windows 2000, Windows XP, and Windows Vista clients.
A full set of restore options is supported, including direct restore (via smbclient, tar, or rsync/rsyncd) or downloading a zip or tar file.
* Detailed documentation.
* Open Source, hosted by SourceForge and freely available under GPL.
Supports mobile environments where laptops are only intermittently connected to the network and have dynamic IP addresses (DHCP).
* Requirements: SME Server 7.x, 8.x, 9.x or 10.x.
*A dedicated volume is recommended (this can be a simple disk or a RAID array).
Flexible configuration parameters allow multiple backups to be performed in parallel, specification of which shares to backup, which directories to backup or not backup, various schedules for full and incremental backups, schedules for email reminders to users and so on. Configuration parameters can be set system-wide or also on a per-PC basis.
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, Windows 95, Windows 98, Windows 2000, Windows XP, and Windows Vista clients.
Detailed documentation.
Open Source hosted by SourceForge and freely available under GPL.
*A dedicated volume is recommended (can be a simple disk or a RAID array)
===Installation===
===Installation===
This part is optional but highly recommended. Backups should always 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 always use ext3 as it's very 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).
Note: releases of Koozali SME Server from version 10 on use XFS as the default filesystem. You can use XFS or ext4 on a secondary filesystem as preferred: ext3 is not directly available and also has rather low size limits nowadays.
Note: releases of Koozali SME Server from version 10 on use XFS as the default filesystem. On cersion 10 you can use XFS or ext4 on a secondary filesystem as preferred: ext3 is not directly available and also has rather low size limits nowadays.
mkfs.ext3 -L BACKUPPC -m 1 /dev/sdb1
mkfs.ext3 -L BACKUPPC -m 1 /dev/sdb1
mkfs.ext4 -L BACKUPPC -m 1 /dev/sdb1
mkfs.ext4 -L BACKUPPC -m 1 /dev/sdb1
(-m sets the percentage of reserved blocks on ext filesystems: XFS autoconfigures itself for RAID volumes.)
(-m sets the percentage of reserved blocks on ext filesystems: XFS autoconfigures itself for RAID volumes.)
Now, we need to create the directory
Now, we need to create the directory:
mkdir -p /var/lib/BackupPC
mkdir -p /var/lib/BackupPC
/dev/sdb1 /var/lib/BackupPC ext3 noatime 0 0
/dev/sdb1 /var/lib/BackupPC ext3 noatime 0 0
And check everything is ok
And check everything is ok:
mount -a
mount -a
*When restarting the BackupPC service you may receive the error as indicated below :<br />
*When restarting the BackupPC service you may receive the error as indicated below :<br />
[root@backuppc ~]# service backuppc restart<br />
[root@backuppc ~]# service backuppc restart<br />
'''To remove the warning''' <br />
'''To remove the warning''' <br />
You should create a custom template '''/etc/e-smith/templates-custom/etc/updatedb.conf/10conf''' (copy the default /etc/e-smith/templates/etc/updatedb.conf/10conf)<br />
mkdir -p /etc/e-smith/templates-custom/etc/updatedb.conf/
mkdir -p /etc/e-smith/templates-custom/etc/updatedb.conf/
cp /etc/e-smith/templates/etc/updatedb.conf/10conf /etc/e-smith/templates-custom/etc/updatedb.conf/
cp /etc/e-smith/templates/etc/updatedb.conf/10conf /etc/e-smith/templates-custom/etc/updatedb.conf/
Add the directory /var/lib/BackupPC to the PRUNEPATHS list, then:
expand-template /etc/updatedb.conf
expand-template /etc/updatedb.conf
*“aborted by signal=PIPE”
*“aborted by signal=PIPE”
Sometimes the backup fails with this error, this error is related to the remote ssh service. You must set in the /etc/ssh/ssh_config of your remote host:
ServerAliveInterval 120
ServerAliveInterval 120
then restart your ssh service
- then restart your ssh service.
Another way could be to set in the setting of BackupPC (RsyncClientCmd) the default value for all hosts:
$Conf{RsyncClientCmd} = '$sshPath -o ServerAliveInterval=120 -q -x -l root $host $rsyncPath $argList+';
$Conf{RsyncClientCmd} = '$sshPath -o ServerAliveInterval=120 -q -x -l root $host $rsyncPath $argList+';
*trying backing up a SME Server you might encounter error or timeout on ssh, this is because of the AutoBlock function on sshd
*trying to back up a SME Server you might encounter an error or timeout on ssh, this is because of the AutoBlock function on sshd.
For an SME10:
config setprop sshd AllowHost backuppcIP/255.255.255
config setprop sshd AllowHost backuppcIP/255.255.255
signal-event remoteaccess-update
signal-event remoteaccess-update
Prior to SME10:
config setprop sshd AutoBlock disabled
config setprop sshd AutoBlock disabled
signal-event remoteaccess-update
signal-event remoteaccess-update
{{Tip box|if you disabled Autoblock, install denyhosts or fail2ban not to fall security.}}
{{Tip box|if you disabled Autoblock, install denyhosts or fail2ban so as not to reduce your level of security.}}
*Since SME10 my old configuration for backupin my local server fails. You need to edit your configuration. You have two choices : use ssh for rsync which is kind of not the best approach for localhost , or you can edit your config to change this
*Since SME10 my old configuration for backup in my local server fails!
*You need to edit your configuration. You have two choices : use ssh for rsync which is not ideal for localhost, or you can edit your config changing this:
Conf{RsyncSshArgs} = ['-e', '$sshPath -l root']
Conf{RsyncSshArgs} = ['-e', '$sshPath -l root']
to this
to this:
$Conf{RsyncSshArgs} = ['-e', '/usr/bin/sudo -p']
$Conf{RsyncSshArgs} = ['-e', '/usr/bin/sudo -p']
You can also do that using the GUI in edit configuration / XFER search for RsyncSshArgs. New installation have the default template already modified.
You can also do that using the GUI in edit configuration / XFER; search for "RsyncSshArgs". New installations have the default template already modified.
<br />
===Uninstall===
===Uninstall===
yum remove smeserver-BackupPC BackupPC
yum remove smeserver-BackupPC BackupPC
