Difference between revisions of "Cloud Backup"

From Funtoo
Jump to navigation Jump to search
(fix layman commands malformed uris →‎Install etckeeper via layman)
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:HOWTO]]
This howto will describe a method for automatically backing up your funtoo install to the internet, in this case dropbox, but any online storage will do. Gentoo describes a method of creating a stage 4 archive. The problem with a stage 4 is that it is large and it archives a lot of unnecessary files. Such as applications that can be reinstalled from an emerge world. Instead, this method will aim for more of a "stage 3.5."
 
This howto will describe a method for automatically backing up your funtoo install to the internet, in this case dropbox, but any online storage will do. Gentoo describes a method of creating a stage 4 archive. The problem with a stage 4 is that it is large and it archives a lot of unnecessary files. Such as applications that can be reinstalled from an emerge world. Instead, this method will aim for more of a stage 3.5.


Note: this method does not attempt to backup everything. The intention is only to backup the system. Optionally you can also archive and copy your /home folder if you have enough online storage.
{{fancynote| This method does not attempt to backup everything. The intention is only to backup the system. Optionally you can also archive and copy your <tt>/home</tt> folder if you have enough online storage.}}


= Use Case =
== Use Case ==
A backup machine currently provides network drives on a home LAN to allow clients on the LAN to backup to, using apps such as Time Machine (Mac) and Genie Timeline (Windows). As this machine ''is'' the backup machine it doesn't have anywhere to backup to itself. In this situation a backup solution is provided by backing up to somewhere online - dropbox. If a restore from the backup is required, the client machine's backups would be trashed, and the backup machine restored.
A backup machine currently provides network drives on a home LAN to allow clients on the LAN to backup to, using apps such as Time Machine (Mac) and Genie Timeline (Windows). As this machine ''is'' the backup machine it doesn't have anywhere to backup to itself. In this situation a backup solution is provided by backing up to somewhere online - dropbox. If a restore from the backup is required, the client machine's backups would be trashed, and the backup machine restored.


= Automatic Backup Archives With Etckeeper =
== Automatic Backup Archives With Etckeeper ==
Etckeeper is a tool that is used to save versions of /etc, including meta-data in a version control repository such as git.
Etckeeper is a tool that is used to save versions of <tt>/etc</tt>, including meta-data in a version control repository such as git.
As etckeeper is not in the funtoo portage tree, layman is used to provide an overlay.
As etckeeper is not in the funtoo portage tree, layman is used to provide an overlay.
== Install etckeeper via layman ==
 
Before you install layman it is worth mentioning that you probably want USE="git subversion" in /etc/make.conf. After adjusting use flags, to install layman you run:
=== Install etckeeper via layman ===
<pre>
Before you install layman it is worth mentioning that you probably want <tt>USE="git subversion"</tt> in <tt>/etc/portage/make.conf</tt>. After adjusting use flags, to install layman you run:
# emerge layman
<console>
</pre>
###i## emerge layman
</console>
In order to backup the layman configuration, but not the portage overlay trees, make the following modifications to the default install.
In order to backup the layman configuration, but not the portage overlay trees, make the following modifications to the default install.
Tell Portage about layman-fetched repositories by adding the following line to /etc/make.conf
Tell Portage about layman-fetched repositories by adding the following line to <tt>/etc/portage/make.conf</tt>:
<pre>
<pre>
source /etc/layman/make.conf
source /etc/layman/make.conf
</pre>
</pre>
Modify the following lines in /etc/layman/layman.cfg
 
Modify the following lines in <tt>/etc/layman/layman.cfg</tt>:
<pre>
<pre>
storage  : /var/lib/layman
storage  : /var/lib/layman
Line 27: Line 27:
make_conf : /etc/layman/make.conf
make_conf : /etc/layman/make.conf
</pre>
</pre>
Add the bgo-overlay. As described on their web page, bgo.zugaina.org.  
 
<pre>
Add the bgo-overlay. As described on their web page, [http://bgo.zugaina.org/ bgo.zugaina.org].  
# layman -o http://gpo.zugaina.org/lst/gpo-repositories.xml -L
<console>
# layman -a bgo-overlay -o http://gpo.zugaina.org/lst/gpo-repositories.xml
###i## layman -o http://gpo.zugaina.org/lst/gpo-repositories.xml -L
</pre>
###i## layman -a bgo-overlay -o http://gpo.zugaina.org/lst/gpo-repositories.xml
(http is all one word but was blocked by the spam filter)
</console>


More information about layman can be found here: http://www.gentoo.org/proj/en/overlays/userguide.xml
More information about layman can be found here: http://www.gentoo.org/proj/en/overlays/userguide.xml


Then unmask and install etckeeper.
Then unmask and install etckeeper.
<pre>
<console>
# emerge etckeeper --autounmask-write
###i## emerge etckeeper --autounmask-write
# emerge etckeeper  
###i## emerge etckeeper  
</pre>
</console>
Note: To update layman overlays do:
{{fancynote| To update layman overlays do:}}
 
<console>
###i## layman -S
</console>


<pre>
If you see the following error, apply this fix:
# layman -S
<console>
</pre>
###i## emerge etckeeper
At the time of writing, there was a problem with the etckeeper (sys-apps/etckeeper-0.58-r2) ebuild which needed fixed by doing the following.
If you see the following error then apply this fix:
<pre>
# emerge etckeeper
Calculating dependencies... done!
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/var/lib/layman/bgo-overlay/sys-apps/etckeeper/files/etckeeper-gentoo-0.58.patch'
!!! A file is not listed in the Manifest: '/var/lib/layman/bgo-overlay/sys-apps/etckeeper/files/etckeeper-gentoo-0.58.patch'


# cd /var/lib/layman/bgo-overlay/sys-apps/etckeeper
###i## cd /var/lib/layman/bgo-overlay/sys-apps/etckeeper
# ebuild etckeeper-0.58-r2.ebuild manifest
###i## ebuild etckeeper-0.58-r2.ebuild manifest
# emerge etckeeper
###i## emerge etckeeper
</pre>
</console>


== Configure etckeeper ==
== Configure etckeeper ==
Move any config files that do not live in /etc. i.e.  
Move any config files that do not live in <tt>/etc</tt>. i.e.  
Check /root for any files to be archive, such as iptables scripts and move them to /etc.
Check <tt>/root</tt> for any files to be archived, such as iptables scripts, and move them to <tt>/etc</tt>.


Note: because funtoo uses boot-update, this means /boot/grub/grub.cfg does not need to be archived.
{{fancynote| because funtoo uses [[Boot-Update]], this means that <tt>/boot/grub/grub.cfg</tt> does not need to be archived.}}


To ensure your portage world file is archived, make the following link:
To ensure your portage world file is archived, make the following link:
<pre>
<console>
# ln /var/lib/portage/world /etc/world
###i## ln /var/lib/portage/world /etc/world
</pre>
</console>
Initialise the git repository.
 
<pre>
Initialize the git repository:
# etckeeper init
<console>
###i## etckeeper init
Initialized empty Git repository in /etc/.git/
Initialized empty Git repository in /etc/.git/
# etckeeper commit "Initial commit."
###i## etckeeper commit "Initial commit."
</pre>
</console>
 
If you don't already have a cron daemon installed, emerge one now:
<console>
###i## emerge vixie-cron
</console>


If you don't already have cron installed, do it now.
{{fancynote| git will only create a new version (commit) if there are changes from the previous one.}}
<pre>
Write a cron job to save an hourly version of <tt>/etc</tt> by creating the file <tt>/etc/cron.hourly/etckeeper</tt>:
# emerge vixie-cron
</pre>
And write the cron job to save an hourly version of /etc.
Note: git will only create a new version (commit) if there are changes from the previous one.


/etc/cron.hourly/etckeeper
<syntaxhighlight lang="bash">
<pre>
#! /bin/bash
#! /bin/bash
etckeeper commit "Hourly auto-commit"
etckeeper commit "Hourly auto-commit"
</pre>
</syntaxhighlight>


== Encrypt and copy backups online ==
== Encrypt and copy backups online ==
=== Copy To Dropbox ===
=== Copy To Dropbox ===
<pre>
<console>
# emerge dropbox
###i## emerge dropbox
</pre>
</console>
Add a dropbox user
 
<pre>
Add a dropbox user:
# useradd dropbox
<console>
</pre>
###i## useradd dropbox
Write the dropbox init files.
</console>


/etc/conf.d/dropbox  
Write the dropbox init files in <tt>/etc/conf.d/dropbox</tt>:
<pre>
<syntaxhighlight lang="bash">  
DROPBOX_USERS="dropbox"  
</pre>
/etc/init.d/dropbox
<pre>
#!/sbin/runscript  
#!/sbin/runscript  
# Copyright 1999-2004 Gentoo Foundation  
# Copyright 1999-2004 Gentoo Foundation  
Line 111: Line 108:
# $Header: /var/cvsroot/gentoo-x86/sys-fs/dropbox/files/dropbox.init-1.0,v 1.4 2007/04/04 13:35:25 cardoe Exp $  
# $Header: /var/cvsroot/gentoo-x86/sys-fs/dropbox/files/dropbox.init-1.0,v 1.4 2007/04/04 13:35:25 cardoe Exp $  


DROPBOX_USERS="dropbox"
NICENESS=5  
NICENESS=5  


Line 144: Line 142:
     eend $?  
     eend $?  
}
}
</pre>
</syntaxhighlight>
Start dropbox now and at boot time.
Start dropbox now and at boot time:
<pre>
<console>
# chmod 0755 /etc/init.d/dropbox  
###i## chmod 0755 /etc/init.d/dropbox  
# /etc/init.d/dropbox start
###i## /etc/init.d/dropbox start
# rc-update add dropbox default
###i## rc-update add dropbox default
</pre>
</console>


After starting the dropbox daemon, it will provide a http link. You will need to visit this site just once to associate your computer with your dropbox account.
After starting the dropbox daemon, it will provide a http link. You will need to visit this site just once to associate your computer with your dropbox account.


Write the cron job to make the backup archive and move it online.
Write the cron job to make the backup archive and move it online. Create the file <tt>/etc/cron.daily/backup</tt>:
/etc/cron.daily/backup  
<syntaxhighlight lang="bash">
<pre>
#! /bin/bash
#! /bin/bash
cd /etc
cd /etc
Line 162: Line 159:
cd /tmp
cd /tmp
mv -v -f backup.bundle /home/dropbox/Dropbox/Private/
mv -v -f backup.bundle /home/dropbox/Dropbox/Private/
</pre>
</syntaxhighlight>
Make the script executable.
 
<pre>
Make the script executable:
# chmod +x /etc/cron.daily/backup  
<console>
</pre>
###i## chmod +x /etc/cron.daily/backup  
</console>


=== Encrypt Backups ===
=== Encrypt Backups ===
It is a good idea to encrypt your backup before moving it online. This can be done with gpg, using a symmetric (password only) or public/private key encryption. Additionally you can chose to sign the backup to check its integrity before restoring.
It is a good idea to encrypt your backup before moving it online. This can be done with gpg, using a symmetric (password only) or public/private key encryption. Additionally you can chose to sign the backup to check its integrity before restoring.
<pre>
<console>
# emerge gpg
###i## emerge gpg
</pre>
</console>


==== Symmetric Encryption ====
==== Symmetric Encryption ====
There is no preparation required to use a symmetric key as all that is required is simply a passphrase.  Just modify the cron job. /etc/cron.daily/backup
There is no preparation required to use a symmetric key as all that is required is simply a passphrase.  Just modify the cron job. Edit <tt>/etc/cron.daily/backup</tt>:
<pre>
 
<syntaxhighlight lang="bash">
#! /bin/bash
#! /bin/bash
cd /etc
cd /etc
Line 183: Line 182:
echo 'encryption_password' | gpg -o backup.gpg --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -c backup.bundle
echo 'encryption_password' | gpg -o backup.gpg --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -c backup.bundle
mv -v -f router.gpg /home/dropbox/Dropbox/Private/
mv -v -f router.gpg /home/dropbox/Dropbox/Private/
</pre>
</syntaxhighlight>
Remember to change "encryption_password"
{{fancyimportant| Remember to change <tt>encryption_password</tt>}}
{{fancywarning| If you forget this password the backup will be unusable. Lose the password and you lose the backup.}}


{{fancywarning|If you forget this password the backup will be unusable. Lose the password and you lose the backup.}}
As there is now sensitive information in this file, you might want to remove read permission:
 
<console>
As there is now sensitive information in this file you might want to remove read permission.
###i## chmod og-r /etc/cron.daily/backup  
<pre>
</console>
# chmod og-r /etc/cron.daily/backup  
</pre>


==== Private/Public key Encryption ====
==== Private/Public key Encryption ====
Make a private/public encryption/decryptions key pair. The public key will be used to encrypt and the private key to decrypt.
Make a private/public encryption/decryptions key pair. The public key will be used to encrypt and the private key to decrypt.
<pre>
<console>
# gpg --gen-key
###i## gpg --gen-key
</pre>
</console>
The public key is used to create the encrypted backup and needs to live on the computer being backed up. A copy of the private key needs to be made and stored securely in another place. If this machine becomes unbootable, and this is the only place the private key lives, the backup dies with it.
The public key is used to create the encrypted backup and needs to live on the computer being backed up. A copy of the private key needs to be made and stored securely in another place. If this machine becomes unbootable, and this is the only place the private key lives, the backup dies with it.
The private key should not be kept:
The private key should not be kept:
# In the same place as the back up
* In the same place as the back up
# On the machine being backed up
* On the machine being backed up
{{fancywarning|The private key is the only key that will decrypt the backup. Lose this key and/or it's password and you lose the backup.}}
{{fancynote| The private key is the only key that will decrypt the backup. Lose this key and/or it's password and you lose the backup.}}
List the private keys.
 
<pre>
List the private keys:
# gpg -K
<console>
###i## gpg -K
/root/.gnupg/secring.gpg
/root/.gnupg/secring.gpg
------------------------
------------------------
Line 211: Line 210:
uid                  my_key <noone@example.com>
uid                  my_key <noone@example.com>
ssb  2048R/67417FEB 2012-01-21
ssb  2048R/67417FEB 2012-01-21
</pre>
</console>
 
The private key can be exported using either the key name or key number. In this case "my_key" or "0EF13559".
The private key can be exported using either the key name or key number. In this case "my_key" or "0EF13559".
To cut and paste the key. Ie, if logging in remotely.
To cut and paste the key. Ie, if logging in remotely.
<pre>
<console>
# gpg -a --export-secret-key 0EF13559
###i## gpg -a --export-secret-key 0EF13559
</pre>
</console>
To create a key file.
 
<pre>
To create a key file:
# gpg -o private_decryption.gpgkey --export-secret-key 0EF13559
<console>
</pre>
###i## gpg -o private_decryption.gpgkey --export-secret-key 0EF13559
</console>
 
Now store this key somewhere secure. The backup is only as secure as the private key.
Now store this key somewhere secure. The backup is only as secure as the private key.


Modify the cron job. /etc/cron.daily/backup
Modify the cron job at <tt>/etc/cron.daily/backup</tt>:
<pre>
 
<syntaxhighlight lang="bash">
#! /bin/bash
#! /bin/bash
cd /etc
cd /etc
Line 231: Line 234:
gpg -o backup.gpg -r 'my-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle
gpg -o backup.gpg -r 'my-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
</pre>
</syntaxhighlight>
Replace "my-key" with the appropriate name from the key list.
 
Also note the change from -c for symmetric encryption to -e for private/public key encryption
{{fancynote| Replace "my-key" with the appropriate name from the key list. Also note the change from -c for symmetric encryption to -e for private/public key encryption. }}


==== Sign Backups ====
==== Sign Backups ====
Create a 2nd private/public (signing) key pair. The private key is used to sign and the public key is used to check the authenticity/integrity.
Create a 2nd private/public (signing) key pair. The private key is used to sign and the public key is used to check the authenticity/integrity.
<pre>
<console>
# gpg --gen-key
###i## gpg --gen-key
</pre>
</console>
Note: The password for this key will be required in the script below.
 
{{fancynote| The password for this key will be required in the script below.}}
In this case the private key is required to sign the backup and the public key is used to check the integrity of the backup.
In this case the private key is required to sign the backup and the public key is used to check the integrity of the backup.
Follow a similar process as above to copy the public key to to another computer/storage media.
Follow a similar process as above to copy the public key to to another computer/storage media.


List the private keys
List the private keys:
<pre>
<console>
# gpg -k
###i## gpg -k
</pre>
</console>
Note: -K lists private keys while -k lists public keys.
{{fancynote| <tt>-K</tt> lists private keys while <tt>-k</tt> lists public keys.}}
 
Then export this public key via cut and paste:
<console>
###i## gpg -a --export <key name or number>
</console>
 
Or to create a key file:
<console>
###i## gpg -o public_signing.gpgkey --export <key name or number>
</console>


Then export this public key via cut and paste.
<pre>
# gpg -a --export <key name or number>
</pre>
Or to create a key file.
<pre>
# gpg -o public_signing.gpgkey --export <key name or number>
</pre>
Now store this key somewhere secure.
Now store this key somewhere secure.


Modify the backup cron job.
Modify the backup cron job at <tt>/etc/cron.daily/backup</tt>:
/etc/cron.daily/backup  
 
<pre>
<syntaxhighlight lang="bash">
#! /bin/bash
#! /bin/bash
cd /etc
cd /etc
Line 269: Line 275:
echo 'signing_key_password' | gpg -s -o backup.gpg -r 'my-encryption-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle  
echo 'signing_key_password' | gpg -s -o backup.gpg -r 'my-encryption-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle  
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
</pre>
</syntaxhighlight>
Note: the script will require the password for your private (signing) key to sign the backup. Replace "password" with the password for your signing private key.
 
And as there is sensitive information in this file don't forget to remove read permission.
{{fancynote| the script will require the password for your private (signing) key to sign the backup. Replace "password" with the password for your signing private key.
<pre>
And as there is sensitive information in this file don't forget to remove read permission.}}
# chmod og-r /etc/cron.daily/backup  
<console>
</pre>
###i## chmod og-r /etc/cron.daily/backup  
</console>


= To Restore From A Backup =
== To Restore From A Backup ==
This restore will assume your are starting with a new blank disk.
This restore will assume your are starting with a new blank disk.
Start by performing a stage 3 install, upto and including section 5 "Chroot into your new system." http://www.funtoo.org/wiki/Funtoo_Linux_Installation
Start by performing a stage 3 install, upto and including section 5 "Chroot into your new system." http://www.funtoo.org/wiki/Funtoo_Linux_Installation
Line 295: Line 302:


(Need to check if this needs done before chrooting into the new install).
(Need to check if this needs done before chrooting into the new install).
<pre>
<console>
# cd /etc
###i## cd /etc
# rm -rf *
###i## rm -rf *
# cd /tmp
###i## cd /tmp
# wget h t t p://dl.dropbox.com/link-to-backup-file/backup.gpg
###i## wget http://dl.dropbox.com/link-to-backup-file/backup.gpg
</pre>
</console>
(Again http is all 1 word, but was blocked by the spam filter).


Note: If you have to copy the link from another computer and therefore can not cut and paste it, there is a "shorten link" option
{{fancynote| if you have to copy the link from another computer and therefore can not cut and paste it, there is a "shorten link" option.}}


== Decrypt ==
== Decrypt ==
Line 312: Line 318:
# The signing key is the public key of the signing key pair - public_signing.gpgkey
# The signing key is the public key of the signing key pair - public_signing.gpgkey


To import the keys by cut and paste.
To import the keys by cut and paste:
<pre>
<console>
# gpg --import <<EOF
###i## gpg --import <<EOF
</pre>
</console>
Note: The last line after pasting the key should be "EOF"
{{fancynote| The last line after pasting the key should be "EOF"}}
Repeat for both keys.
Repeat for both keys.


To import the keys by file.
To import the keys by file:
<pre>
<console>
# gpg --import private_decryption.gpgkey
###i## gpg --import private_decryption.gpgkey
# gpg --import public_signing.gpgkey
###i## gpg --import public_signing.gpgkey
</pre>
</console>


Decrypt the backup.
Decrypt the backup:
<pre>
<console>
# gpg -d backup.gpg > backup.bundle
###i## gpg -d backup.gpg > backup.bundle
</pre>
</console>


If the backup was signed and you have correctly imported the signing public key you should see a message similar to:
If the backup was signed and you have correctly imported the signing public key you should see a message similar to:
<pre>
<console>
gpg: Good signature from "my_signing_key <noone@example.com>"
gpg: Good signature from "my_signing_key <noone@example.com>"
</pre>
</console>


== Clone ==
== Clone ==
<pre>
<console>
git clone /tmp/backup.bundle /etc/
###i## git clone /tmp/backup.bundle /etc/
</pre>
</console>


== Link world file ==
== Link world file ==
<pre>
<console>
# ln /etc/world /var/lib/portage/world
###i## ln /etc/world /var/lib/portage/world
</pre>
</console>


== Emerge world ==
== Emerge world ==
<pre>
<console>
# emerge --sync
###i## emerge --sync
# layman -S
###i## layman -S
# emerge -uDaNv world
###i## emerge -uDaNv world
</pre>
</console>


== Compile the kernel (genkernel)==
== Compile the kernel (genkernel)==
If you have genkernel set to save config files (the default).
If you have genkernel set to save config files (the default):
<pre>
<console>
# cp /etc/kernels/kernel-config-x86_64-<latest version>-gentoo /usr/src/linux/.config  
###i## cp /etc/kernels/kernel-config-x86_64-<latest version>-gentoo /usr/src/linux/.config  
</pre>
</console>
Otherwise use the currently loaded kernel's config
 
<pre>
Otherwise use the currently loaded kernel's config:
# zcat /proc/config.gz > /usr/src/linux/.config  
<console>
</pre>
###i## zcat /proc/config.gz > /usr/src/linux/.config  
Then compile the kernel
</console>
<pre>
 
# genkernel --oldconfig --no-mrproper all  
Then compile the kernel:
</pre>
<console>
###i## genkernel --oldconfig --no-mrproper all  
</console>


== Restore grub bootloader ==
== Restore grub bootloader ==
<pre>
<console>
# grub-install --no-floppy /dev/sda
###i## grub-install --no-floppy /dev/sda
# boot-update
###i## boot-update
</pre>
</console>
 
Adjust the device as required if installing to another location.
Adjust the device as required if installing to another location.


== Reboot ==
== Reboot ==
<pre>
<console>
# reboot
###i## reboot
</pre>
</console>
 
[[Category:First Steps]]
[[Category:HOWTO]]

Revision as of 18:30, June 27, 2014

This howto will describe a method for automatically backing up your funtoo install to the internet, in this case dropbox, but any online storage will do. Gentoo describes a method of creating a stage 4 archive. The problem with a stage 4 is that it is large and it archives a lot of unnecessary files. Such as applications that can be reinstalled from an emerge world. Instead, this method will aim for more of a "stage 3.5."

   Note
This method does not attempt to backup everything. The intention is only to backup the system. Optionally you can also archive and copy your /home folder if you have enough online storage.

Use Case

A backup machine currently provides network drives on a home LAN to allow clients on the LAN to backup to, using apps such as Time Machine (Mac) and Genie Timeline (Windows). As this machine is the backup machine it doesn't have anywhere to backup to itself. In this situation a backup solution is provided by backing up to somewhere online - dropbox. If a restore from the backup is required, the client machine's backups would be trashed, and the backup machine restored.

Automatic Backup Archives With Etckeeper

Etckeeper is a tool that is used to save versions of /etc, including meta-data in a version control repository such as git. As etckeeper is not in the funtoo portage tree, layman is used to provide an overlay.

Install etckeeper via layman

Before you install layman it is worth mentioning that you probably want USE="git subversion" in /etc/portage/make.conf. After adjusting use flags, to install layman you run:

root # emerge layman

In order to backup the layman configuration, but not the portage overlay trees, make the following modifications to the default install. Tell Portage about layman-fetched repositories by adding the following line to /etc/portage/make.conf:

source /etc/layman/make.conf

Modify the following lines in /etc/layman/layman.cfg:

storage   : /var/lib/layman
installed : /etc/layman/installed.xml
make_conf : /etc/layman/make.conf

Add the bgo-overlay. As described on their web page, bgo.zugaina.org.

root # layman -o http://gpo.zugaina.org/lst/gpo-repositories.xml -L
root # layman -a bgo-overlay -o http://gpo.zugaina.org/lst/gpo-repositories.xml

More information about layman can be found here: http://www.gentoo.org/proj/en/overlays/userguide.xml

Then unmask and install etckeeper.

root # emerge etckeeper --autounmask-write
root # emerge etckeeper 
   Note
To update layman overlays do:
root # layman -S

If you see the following error, apply this fix:

root # emerge etckeeper
Calculating dependencies... done!
>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/var/lib/layman/bgo-overlay/sys-apps/etckeeper/files/etckeeper-gentoo-0.58.patch'

root # cd /var/lib/layman/bgo-overlay/sys-apps/etckeeper
root # ebuild etckeeper-0.58-r2.ebuild manifest
root # emerge etckeeper

Configure etckeeper

Move any config files that do not live in /etc. i.e. Check /root for any files to be archived, such as iptables scripts, and move them to /etc.

   Note
because funtoo uses Boot-Update, this means that /boot/grub/grub.cfg does not need to be archived.

To ensure your portage world file is archived, make the following link:

root # ln /var/lib/portage/world /etc/world

Initialize the git repository:

root # etckeeper init
Initialized empty Git repository in /etc/.git/
root # etckeeper commit "Initial commit."

If you don't already have a cron daemon installed, emerge one now:

root # emerge vixie-cron
   Note
git will only create a new version (commit) if there are changes from the previous one.

Write a cron job to save an hourly version of /etc by creating the file /etc/cron.hourly/etckeeper:

#! /bin/bash
etckeeper commit "Hourly auto-commit"

Encrypt and copy backups online

Copy To Dropbox

root # emerge dropbox

Add a dropbox user:

root # useradd dropbox

Write the dropbox init files in /etc/conf.d/dropbox:

 
#!/sbin/runscript 
# Copyright 1999-2004 Gentoo Foundation 
# Distributed under the terms of the GNU General Public License, v2 or later 
# $Header: /var/cvsroot/gentoo-x86/sys-fs/dropbox/files/dropbox.init-1.0,v 1.4 2007/04/04 13:35:25 cardoe Exp $ 

DROPBOX_USERS="dropbox"
NICENESS=5 

depend() { 
    need localmount net 
    after bootmisc 
} 

start() { 
    ebegin "Starting dropbox..." 
    for dbuser in $DROPBOX_USERS; do 
        start-stop-daemon -S -b -m --pidfile /var/run/dropbox-$dbuser.pid  -N $NICENESS -u $dbuser -v -e HOME="/home/$dbuser" -x /opt/dropbox/dropboxd 
    done 
    eend $? 
} 

stop() { 
    ebegin "Stopping dropbox..." 
    for dbuser in $DROPBOX_USERS; do 
        start-stop-daemon --stop --pidfile /var/run/dropbox-$dbuser.pid 
    done 
    eend $? 
} 

status() { 
    for dbuser in $DROPBOX_USERS; do 
        if [ -e /var/run/dropbox-$dbuser.pid ] ; then 
            echo "dropboxd for USER $dbuser: running." 
        else 
            echo "dropboxd for USER $dbuser: not running." 
        fi 
    done 
    eend $? 
}

Start dropbox now and at boot time:

root # chmod 0755 /etc/init.d/dropbox 
root # /etc/init.d/dropbox start
root # rc-update add dropbox default

After starting the dropbox daemon, it will provide a http link. You will need to visit this site just once to associate your computer with your dropbox account.

Write the cron job to make the backup archive and move it online. Create the file /etc/cron.daily/backup:

#! /bin/bash
cd /etc
git bundle create /tmp/backup.bundle --all
cd /tmp
mv -v -f backup.bundle /home/dropbox/Dropbox/Private/

Make the script executable:

root # chmod +x /etc/cron.daily/backup 

Encrypt Backups

It is a good idea to encrypt your backup before moving it online. This can be done with gpg, using a symmetric (password only) or public/private key encryption. Additionally you can chose to sign the backup to check its integrity before restoring.

root # emerge gpg

Symmetric Encryption

There is no preparation required to use a symmetric key as all that is required is simply a passphrase. Just modify the cron job. Edit /etc/cron.daily/backup:

#! /bin/bash
cd /etc
git bundle create /tmp/backup.bundle --all
cd /tmp
echo 'encryption_password' | gpg -o backup.gpg --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -c backup.bundle
mv -v -f router.gpg /home/dropbox/Dropbox/Private/
   Important
Remember to change encryption_password
   Warning
If you forget this password the backup will be unusable. Lose the password and you lose the backup.

As there is now sensitive information in this file, you might want to remove read permission:

root # chmod og-r /etc/cron.daily/backup 

Private/Public key Encryption

Make a private/public encryption/decryptions key pair. The public key will be used to encrypt and the private key to decrypt.

root # gpg --gen-key

The public key is used to create the encrypted backup and needs to live on the computer being backed up. A copy of the private key needs to be made and stored securely in another place. If this machine becomes unbootable, and this is the only place the private key lives, the backup dies with it. The private key should not be kept:

  • In the same place as the back up
  • On the machine being backed up
   Note
The private key is the only key that will decrypt the backup. Lose this key and/or it's password and you lose the backup.

List the private keys:

root # gpg -K
/root/.gnupg/secring.gpg
------------------------
sec   2048R/0EF13559 2012-01-21
uid                  my_key <noone@example.com>
ssb   2048R/67417FEB 2012-01-21

The private key can be exported using either the key name or key number. In this case "my_key" or "0EF13559". To cut and paste the key. Ie, if logging in remotely.

root # gpg -a --export-secret-key 0EF13559

To create a key file:

root # gpg -o private_decryption.gpgkey --export-secret-key 0EF13559

Now store this key somewhere secure. The backup is only as secure as the private key.

Modify the cron job at /etc/cron.daily/backup:

#! /bin/bash
cd /etc
git bundle create /tmp/backup.bundle --all
cd /tmp
gpg -o backup.gpg -r 'my-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
   Note
Replace "my-key" with the appropriate name from the key list. Also note the change from -c for symmetric encryption to -e for private/public key encryption. 

Sign Backups

Create a 2nd private/public (signing) key pair. The private key is used to sign and the public key is used to check the authenticity/integrity.

root # gpg --gen-key
   Note
The password for this key will be required in the script below.

In this case the private key is required to sign the backup and the public key is used to check the integrity of the backup. Follow a similar process as above to copy the public key to to another computer/storage media.

List the private keys:

root # gpg -k
   Note
-K lists private keys while -k lists public keys.

Then export this public key via cut and paste:

root # gpg -a --export <key name or number>

Or to create a key file:

root # gpg -o public_signing.gpgkey --export <key name or number>

Now store this key somewhere secure.

Modify the backup cron job at /etc/cron.daily/backup:

#! /bin/bash
cd /etc
git bundle create /tmp/backup.bundle --all
cd /tmp
echo 'signing_key_password' | gpg -s -o backup.gpg -r 'my-encryption-key' --batch --homedir /root/.gnupg -vvv  --passphrase-fd 0 --yes -e backup.bundle 
mv -v -f backup.gpg /home/dropbox/Dropbox/Private/
   Note
the script will require the password for your private (signing) key to sign the backup. Replace "password" with the password for your signing private key.

And as there is sensitive information in this file don't forget to remove read permission.

root # chmod og-r /etc/cron.daily/backup 

To Restore From A Backup

This restore will assume your are starting with a new blank disk. Start by performing a stage 3 install, upto and including section 5 "Chroot into your new system." http://www.funtoo.org/wiki/Funtoo_Linux_Installation

Then the restore process is:

  1. Download backup from dropbox
  2. Decrypt
  3. Clone
  4. Link world file
  5. Emerge world
  6. Compile the kernel
  7. Restore grub bootloader
  8. Reboot

Download backup from dropbox

Log into your dropbox account and find your backup file. Move it to a public area if it isn't already in one. Then right click on it and click "copy public link." Now on the computer to be restored, delete the contents of the /etc folder and download the backup file.

(Need to check if this needs done before chrooting into the new install).

root # cd /etc
root # rm -rf *
root # cd /tmp
root # wget http://dl.dropbox.com/link-to-backup-file/backup.gpg
   Note
if you have to copy the link from another computer and therefore can not cut and paste it, there is a "shorten link" option.

Decrypt

If you used a public/private key to encrypt, and optionally signed the backup, import the decryption and signing keys.

Note:

  1. The decryption key is the private key of the encryption key pair - private_decryption.gpgkey
  2. The signing key is the public key of the signing key pair - public_signing.gpgkey

To import the keys by cut and paste:

root # gpg --import <<EOF
   Note
The last line after pasting the key should be "EOF"

Repeat for both keys.

To import the keys by file:

root # gpg --import private_decryption.gpgkey
root # gpg --import public_signing.gpgkey

Decrypt the backup:

root # gpg -d backup.gpg > backup.bundle

If the backup was signed and you have correctly imported the signing public key you should see a message similar to:

gpg: Good signature from "my_signing_key <noone@example.com>"

Clone

root # git clone /tmp/backup.bundle /etc/

Link world file

root # ln /etc/world /var/lib/portage/world

Emerge world

root # emerge --sync
root # layman -S
root # emerge -uDaNv world

Compile the kernel (genkernel)

If you have genkernel set to save config files (the default):

root # cp /etc/kernels/kernel-config-x86_64-<latest version>-gentoo /usr/src/linux/.config 

Otherwise use the currently loaded kernel's config:

root # zcat /proc/config.gz > /usr/src/linux/.config 

Then compile the kernel:

root # genkernel --oldconfig --no-mrproper all 

Restore grub bootloader

root # grub-install --no-floppy /dev/sda
root # boot-update

Adjust the device as required if installing to another location.

Reboot

root # reboot