{"id":1457,"date":"2020-03-04T09:02:22","date_gmt":"2020-03-04T15:02:22","guid":{"rendered":"http:\/\/blog.ls-al.com\/?p=1457"},"modified":"2020-04-12T11:57:05","modified_gmt":"2020-04-12T16:57:05","slug":"restic-recover-os","status":"publish","type":"post","link":"https:\/\/blog.ls-al.com\/restic-recover-os\/","title":{"rendered":"Restic recover OS"},"content":{"rendered":"<h3>My test to recover an Ubuntu server OS from a backup.<\/h3>\n<p>Note the following:<\/p>\n<ul>\n<li>I used Ubuntu 20.04 (focal) which is still beta at the time of this POC. In theory Ubuntu 18.04 should work the same or better.<\/li>\n<li>For an OS recovery I documented the backup elsewhere. It was something like this for me and yours will vary of course:<br \/>\n*<em>restic --exclude={\/dev\/<\/em>,\/media,\/mnt\/<em>,\/proc\/<\/em>,\/run\/<em>,\/sys\/<\/em>,\/tmp\/<em>,\/var\/tmp\/<\/em>,\/swapfile} backup \/ \/dev\/{console,null}**<\/li>\n<li>For the partition recovery I saved it on the source server to a file for easy copy\/paste during the recovery: <strong>sfdisk -d &gt; \/tmp\/partition-table<\/strong><\/li>\n<li>I tested restic repo\\'s with both sftp and AWS s3.<\/li>\n<li>Used a Virtualbox VM named u20.04-restic-os-restored. Made the recover server disk 15G (5G larger than the original 10G where backup was done)<\/li>\n<li>My POC consist of a very simple disk layout ie one ext4 partition only. It was just the default install from this Ubuntu 20.04 desktop install. Complicated boot disk layouts may be very different. I am not interested in recovering servers with complicated OS disk layouts. To me that does not fit with modern infrastructure and concepts like auto scaling. Boot disks should be lean and easily recovered\/provisioned through scripting; and configuration applied with configuration management tools.<\/li>\n<li>boot liveCD, set ubuntu user password and install and start ssh so we can ssh into and easier to copy\/paste etc.<\/li>\n<li>Abbreviated commands (removed most output to shorten)<\/li>\n<\/ul>\n<pre><code class=\"language-bash\">$ ssh ubuntu@192.168.1.160\n$ sudo -i\n\n# export AWS_ACCESS_KEY_ID=&lt;secret..&gt;\n# export AWS_SECRET_ACCESS_KEY=&lt;secret..&gt;\n# export RESTIC_PASSWORD=&lt;secret..&gt;\n# export RESTIC_REPOSITORY=sftp:rr@192.168.1.111:\/ARCHIVE\/restic-os-restore-poc\n# cd \/usr\/local\/bin\/\n# wget https:\/\/github.com\/restic\/restic\/releases\/download\/v0.9.6\/restic_0.9.6_linux_amd64.bz2\n# bzip2 -d restic_0.9.6_linux_amd64.bz2 \n# mv restic_0.9.6_linux_amd64 restic\n# chmod +x restic \n# mkdir \/mnt\/restore\n# sfdisk -d \/dev\/sda &lt; partition-table\n# mkfs.ext4 \/dev\/sda1\n# mkdir \/mnt\/restore\/\n# mount \/dev\/sda1 \/mnt\/restore\/\n# \/usr\/local\/bin\/restic snapshots\n# time \/usr\/local\/bin\/restic restore latest -t \/mnt\/restore --exclude &#039;\/etc\/fstab&#039; --exclude &#039;\/etc\/crypttab&#039; --exclude &#039;\/boot\/grub\/grub.cfg&#039; --exclude &#039;\/etc\/default\/grub&#039;\n\n# mount --bind \/dev \/mnt\/restore\/dev\n# mount -t sysfs sys \/mnt\/restore\/sys\n# mount -t proc proc \/mnt\/restore\/proc\n# mount -t devpts devpts \/mnt\/restore\/dev\/pts\n# mount -t tmpfs tmp \/mnt\/restore\/tmp\n# mount --rbind \/run \/mnt\/restore\/run\n# mount -t tmpfs tmp \/mnt\/restore\/tmp\n\n# chroot \/mnt\/restore \/bin\/bash\n# lsblk | grep sda\n# grub-install \/dev\/sda\n# update-grub\n# blkid | grep sda\n\n# UUID=$(blkid | grep sda | cut -d&#039; &#039; -f2 | cut -d\\ -f2)\n# echo $UUID \/ ext4    errors=remount-ro 0       1 &gt; \/etc\/fstab\n\n# sync\n# exit\n# init 0<\/code><\/pre>\n<p><strong>Note:<\/strong><\/p>\n<p>New server booted and worked but graphics (GNOME login) login for ubuntu account stalled on login. This fixed it: <strong><em>dconf reset -f \/org\/gnome\/<\/em><\/strong><\/p>\n<p>My restic backup command works but just for reference since restic has no include flag rsync seem to have a better exclude\/include functionality syntax like this: *<strong>rsync --include=\/dev\/{console,null} --exclude={\/dev\/,\/proc\/,\/sys\/,\/tmp\/,\/run\/,\/mnt\/,\/media\/<em>,\/lost+found}<\/em><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>My test to recover an Ubuntu server OS from a backup. Note the following: I used Ubuntu 20.04 (focal) which<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[99],"tags":[115],"class_list":["post-1457","post","type-post","status-publish","format-standard","hentry","category-restic","tag-restic"],"_links":{"self":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts\/1457","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/comments?post=1457"}],"version-history":[{"count":0,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts\/1457\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/media?parent=1457"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/categories?post=1457"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/tags?post=1457"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}