3,054
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 6:
Line 6: + + Line 46:
Line 48: − + − + Line 107:
Line 109: + + + + + + + Line 123:
Line 132: + + + + + + + + + + + + + + Line 147:
Line 170: + + + + + + + + + + + + Line 220:
Line 255: + + + + Line 335:
Line 374: − With ctrl+k you can remove the line with <backup_number>.+ Line 368:
Line 407: + + + + +
→Requirements
{{#smeversion: smeserver-BackupPC }}
{{#smeversion: smeserver-BackupPC }}
{{#smeversion: smeserver-BackupPC4 }}
{{#smeversion: BackupPC }}
{{#smeversion: BackupPC }}
{{#smeversion: BackupPC4 }}
=== Description ===
=== Description ===
=== Requirements ===
=== Requirements ===
*SME Server 7.X, 8.X or 9.X
*SME Server 7.x, 8.x, 9.x or 10.x.
*a dedicated volume is recommended (can be a simple disk or a RAID array)
*A dedicated volume is recommended (can be a simple disk or a RAID array)
=== Installation ===
=== Installation ===
*updates configuration files following the installation
*updates configuration files following the installation
signal-event backuppc-update
signal-event backuppc-update
====install the rpms (SME 10.X)====
yum --enablerepo=smecontribs,epel,fws install smeserver-BackupPC
*updates configuration files following the installation
signal-event backuppc-update
You should now be able to access the interface in the server-manager or directly on https://my.domain.tld/BackupPC
You should now be able to access the interface in the server-manager or directly on https://my.domain.tld/BackupPC
When you submit, the configuration from smeserver-template will be copied on my_server. You then can edit my_server's config
When you submit, the configuration from smeserver-template will be copied on my_server. You then can edit my_server's config
====install the BackupPC4 rpms (SME 9.X)====
Important you can not install both BackupPC (3) and BackupPC4 on the same server.
first the needed repo:
yum install smeserver-extrarepositories-fws smeserver-extrarepositories-epel -y
signal-event yum-modify
then install it:
yum --enablerepo=smecontribs,fws,epel install smeserver-BackupPC4
*updates configuration files following the installation
signal-event backuppc-update
You should now be able to access the interface in the server-manager or directly on https://my.domain.tld/BackupPC
=== Upgrade from smeserver-backuppc.fws-3.0-1 ===
=== Upgrade from smeserver-backuppc.fws-3.0-1 ===
You should be done ;)
You should be done ;)
===upgrade from BackupPC (3) to BackupPC4 rpms (SME 9.X)===
TODO.
You will mostly have some debugging to do regarding the bug {{Bugzilla:10514}}
Also according to BackupPC documentaton this should be doable, but might need some manual tweaking in order to use both v3 and v4 pools during the transition delay:
# http://backuppc.sourceforge.net/BackupPC-4.0.0.html#BackupPC-4.0
# https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_migrateV3toV4
# https://www.srbu.se/index.php?option=com_content&view=article&id=210:migrating-backuppc-v3-pools-to-v4&catid=12&Itemid=121
# https://github.com/backuppc/backuppc/issues/249
=== DB properties ===
=== DB properties ===
(confirm the host key)
(confirm the host key)
*ssh port different from 22
See this post :
https://forums.contribs.org/index.php/topic,53586.0.html
====Restore or migrate a smeserver====
====Restore or migrate a smeserver====
nano /var/lib/BackupPC/pc/<client>/backups
nano /var/lib/BackupPC/pc/<client>/backups
With ctrl+k you can remove the line with <backup_number>.
Relog to your web interface and voila! No more <backup_number>.
Relog to your web interface and voila! No more <backup_number>.
One other way could be to set in the setting of backupPC (RsyncClientCmd)the default value for all hosts
One other 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
config setprop sshd AutoBlock disabled
signal-event remoteaccess-update
{{Tip box|if you disabled Autoblock, install denyhosts or fail2ban not to fall security.}}
=== Uninstall ===
=== Uninstall ===
