Changes

From SME Server
Jump to navigationJump to search

BackupPC (view source)

Revision as of 20:33, 14 February 2024

351 bytes added ,  14 February
m
→‎RPM Installation
Line 6: Line 6:     
{{#smeversion: smeserver-BackupPC }}
 
{{#smeversion: smeserver-BackupPC }}
−
{{#smeversion: smeserver-BackupPC4 }}
  −
{{#smeversion: BackupPC }}
  −
{{#smeversion: BackupPC4 }}
      
===Description===
 
===Description===
Line 49: Line 46:  
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 recommended as it will be easier to manage backups data later. XFS also should facilitate making replicas or backups of the BackupPC data, which is otherwise difficult.
+
(By the way, if you know how to manage LVM, its usage is also recommended as it will be easier to manage backup data later. XFS also should facilitate making replicas or backups of the BackupPC data, which is otherwise difficult.)
      −
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.
+
Note: releases of Koozali SME Server from version 10 on use XFS as the default filesystem. On version 10 you can use XFS or ext4 on a secondary filesystem as preferred: ext3 has rather low size limits given disk sizes 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
 
  mkfs.xfs  -L BACKUPPC /dev/sdb1
 
  mkfs.xfs  -L BACKUPPC /dev/sdb1
   −
(-m sets the percentage of reserved blocks on ext filesystems: XFS autoconfigures itself for RAID volumes.)
+
( -m 1 sets the percentage of reserved blocks on ext filesystems: XFS autoconfigures itself for Linux software RAID volumes.)
    
Now, we need to create the directory:
 
Now, we need to create the directory:
Line 65: Line 63:  
Add the mount point in fstab. Just add something like:
 
Add the mount point in fstab. Just add something like:
   −
  /dev/sdb1    /var/lib/BackupPC      ext3   noatime 0 0
+
  /dev/sdb1    /var/lib/BackupPC      ext4   noatime   0 0
 +
 
 +
or
 +
 
 +
/dev/sdb1    /var/lib/BackupPC      xfs    defaults  0 0
    
And check everything is ok:
 
And check everything is ok:
Line 71: Line 73:  
  mount -a
 
  mount -a
 
  mount | grep BackupPC
 
  mount | grep BackupPC
−
  /dev/sdb1 on /var/lib/BackupPC type ext3 (rw,noatime)
+
  /dev/sdb1 on /var/lib/BackupPC type ext4 (rw,noatime)
    
*create some symlinks
 
*create some symlinks
Line 80: Line 82:  
  ln -s /var/lib/BackupPC/etc /etc/BackupPC
 
  ln -s /var/lib/BackupPC/etc /etc/BackupPC
 
  ln -s /var/lib/BackupPC/log /var/log/BackupPC
 
  ln -s /var/lib/BackupPC/log /var/log/BackupPC
 +
{{Warning box|this contrib configuration is part of the core backup since smeserver-backuppc-0.2-10. However the backup includes /etc/BackupPC but NOT the /var/lib/BackupPC content including the backup pool. This is your responsibility to handle this as most user will have this outside of the core hdd and remove and replace to new server is easy.
 +
Also is it yours to handle the redundancy of your backups.}}
    
====RPM Installation====
 
====RPM Installation====
−
<tabs container><tab name="Backuppc4 For SME 10">
+
<tabs container=""><tab name="Backuppc4 For SME 10">
−
yum install smeserver-extrarepositories-fws
+
  yum --enablerepo=smecontribs install smeserver-BackupPC
−
  yum --enablerepo=smecontribs,fws install smeserver-BackupPC
     −
#you will have following RPM pulled from fws : BackupPC-XS BackupPC4 rsync-bpc
+
You will have all RPMs pulled from CentOS or smecontribs including: BackupPC-XS BackupPC4 rsync-bpc
−
#all other from CentOS or smecontribs.
     −
*no need to updates configuration files following the installation
+
No need to update configuration files following the installation
    
Go to your server-manager.
 
Go to your server-manager.
Line 95: Line 97:     
</tab><tab name="Backuppc4 For SME 9">
 
</tab><tab name="Backuppc4 For SME 9">
−
Important you can not install both BackupPC (3) and BackupPC4 on the same server.
+
Important: you cannot install both BackupPC (3) and BackupPC4 on the same server!
   −
first the needed repo:
+
First prepare the needed repo:
 
  yum install smeserver-extrarepositories-fws smeserver-extrarepositories-epel -y
 
  yum install smeserver-extrarepositories-fws smeserver-extrarepositories-epel -y
 
  signal-event yum-modify
 
  signal-event yum-modify
−
then install it:
+
Then install it:
 
  yum --enablerepo=smecontribs,fws,epel install smeserver-BackupPC4
 
  yum --enablerepo=smecontribs,fws,epel install smeserver-BackupPC4
   −
*updates configuration files following the installation
+
*Update the configuration files following the installation
    
  signal-event backuppc-update
 
  signal-event backuppc-update
Line 112: Line 114:  
  yum --enablerepo=smecontribs install smeserver-BackupPC
 
  yum --enablerepo=smecontribs install smeserver-BackupPC
   −
*updates configuration files following the installation
+
*Update the configuration files following the installation
    
  signal-event backuppc-update
 
  signal-event backuppc-update
Line 124: Line 126:  
  cp /etc/BackupPC/config.pl /etc/BackupPC/config.pl.orig
 
  cp /etc/BackupPC/config.pl /etc/BackupPC/config.pl.orig
 
  cat /etc/BackupPC/config.pl.orig|sed 's/ -E -N -d 1/ -E -d 1 /g'>/etc/BackupPC/config.pl
 
  cat /etc/BackupPC/config.pl.orig|sed 's/ -E -N -d 1/ -E -d 1 /g'>/etc/BackupPC/config.pl
−
regarding upstream :http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=BackupPC_on_Fedora_Core_9
+
Regarding upstream :http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=BackupPC_on_Fedora_Core_9
 
http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Troubleshooting
 
http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Troubleshooting
 
and also bugs : [[bugzilla:7016]] and [[bugzilla:7281]]
 
and also bugs : [[bugzilla:7016]] and [[bugzilla:7281]]
   −
*updates configuration files following the installation
+
*Update the configuration files following the installation
    
  signal-event backuppc-update
 
  signal-event backuppc-update
Line 142: Line 144:  
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
   −
You'll find three sample configuration:
+
You'll find three sample configurations:
   −
*smeserver-template is a sample config file to backup a SME Server.
+
*smeserver-template is a sample config file to backup an SME Server.
 
*localhost-template is a sample config file to backup the server itself.
 
*localhost-template is a sample config file to backup the server itself.
 
*windows-template is a sample to backup a windows host using cygwin+rsyncd
 
*windows-template is a sample to backup a windows host using cygwin+rsyncd
Line 154: Line 156:  
my_server=smeserver-template
 
my_server=smeserver-template
   −
When you submit, the configuration from smeserver-template will be copied to my_server. You then can edit my_server's config directly.
+
When you "Save", the configuration from smeserver-template will be copied to my_server. You can then edit my_server's config directly.
    
===Upgrade from smeserver-backuppc.fws-3.0-1===
 
===Upgrade from smeserver-backuppc.fws-3.0-1===
Line 183: Line 185:       −
===upgrade from BackupPC (3) to BackupPC4 rpms (SME 9.X)===
+
===Upgrade from BackupPC (3) to BackupPC4 rpms (SME 9.X)===
 
TODO.
 
TODO.
 
You will mostly have some debugging to do regarding the bug {{Bugzilla:10514}}
 
You will mostly have some debugging to do regarding the bug {{Bugzilla:10514}}
Line 195: Line 197:  
===DB properties===
 
===DB properties===
   −
there's only two properties you can change:
+
 
 +
There's only two properties you can change:
    
*'''status''': (enabled|disabled) Do you want the service to start automatically when the server boot ?
 
*'''status''': (enabled|disabled) Do you want the service to start automatically when the server boot ?
 
*'''examples''': (enabled|disabled) Do you want the sample configuration files to be added again if they are removed ?
 
*'''examples''': (enabled|disabled) Do you want the sample configuration files to be added again if they are removed ?
−
*'''sudo''': a list of commands backuppc will be able to run as root using sudo. The default is "/usr/bin/rsync,/bin/gtar"
+
*'''sudo''': A list of commands backuppc will be able to run as root using sudo. The default is "/usr/bin/rsync,/bin/gtar"
   −
When you have configured this, you should run
+
When you have configured this, you should run:
 
  signal-event backuppc-update
 
  signal-event backuppc-update
   Line 208: Line 211:  
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. }}
   −
as an example if you want to be able to "Wake on Lan" :
+
As an example if you want to be able to "Wake on Lan" :
 
   config setprop backuppc sudo `config getprop backuppc sudo`,/sbin/ether-wake
 
   config setprop backuppc sudo `config getprop backuppc sudo`,/sbin/ether-wake
 
  signal-event backuppc-update
 
  signal-event backuppc-update
   −
then simply add a script to your prebackup command or your ping command like :
+
– then simply add a script to your prebackup command or your ping command like :
      Line 284: Line 287:  
  cd myrestore/
 
  cd myrestore/
   −
to include and restore everything that is outside of the usual backuped folder in SME:
+
To include and restore everything that is outside of the usual backuped folder in SME:
 
  /usr/share/BackupPC/bin/BackupPC_tarCreate  -h SERVERNAME -n -1 -s /  / > smeserver.tar
 
  /usr/share/BackupPC/bin/BackupPC_tarCreate  -h SERVERNAME -n -1 -s /  / > smeserver.tar
   −
the base backup in the SME Server console would be an equivalent to this :
+
The base backup in the SME Server console would be an equivalent to this :
 
   /usr/share/BackupPC/bin/BackupPC_tarCreate  -h SERVERNAME -n -1 -s  /    home/e-smith etc/e-smith/templates-custom etc/e-smith/templates-user-custom \
 
   /usr/share/BackupPC/bin/BackupPC_tarCreate  -h SERVERNAME -n -1 -s  /    home/e-smith etc/e-smith/templates-custom etc/e-smith/templates-user-custom \
 
  etc/ssh root etc/sudoers  etc/passwd  etc/shadow etc/group etc/gshadow etc/samba/secrets.tdb  etc/samba/smbpasswd > smeserver.tar
 
  etc/ssh root etc/sudoers  etc/passwd  etc/shadow etc/group etc/gshadow etc/samba/secrets.tdb  etc/samba/smbpasswd > smeserver.tar
      −
then you have just to copy this on a USB disk, or alternatively copy it in a virtual disk if your SME will be virtualized and can not plug any USB device
+
Then you have just to copy this on a USB disk, or alternatively copy it in a virtual disk if your SME will be virtualized and can not plug any USB device
 
  mkdir /mnt/MyDisk
 
  mkdir /mnt/MyDisk
 
  mount /dev/disk/by-label/MyDisk /mnt/MyDisk
 
  mount /dev/disk/by-label/MyDisk /mnt/MyDisk
Line 302: Line 305:  
#plug your drive when you see the screen asking for restoration
 
#plug your drive when you see the screen asking for restoration
   −
and you are done.
+
– and you are done.
    
====Backup a Linux host through rsync====
 
====Backup a Linux host through rsync====
Line 418: Line 421:  
   ServerAliveInterval 120
 
   ServerAliveInterval 120
   −
- then restart your ssh service.
+
– then restart your ssh service.
     
Gieres
3,054

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/39684...42509"

Navigation menu