This repository has been archived by the owner on Aug 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
13 changed files
with
100 additions
and
59 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
.vagrant |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,14 @@ | ||
# rear-workshop-osbconf-2016 | ||
# Relax-and-Recover (ReaR) Workshop | ||
|
||
:author: Gratien Dhaese <[email protected]> | ||
|
||
The Relax-and-Recover (rear) workshop for OSBconf 2016 (Open Source Backup Conference, Cologne, Germany, 26-27 September, 2016) - see http://osbconf.org/workshops/ - is guiding you into setting up rear, how to configure it, and with lots of real use cases, such as with Bareos, NFS, CIFS, RSYNC. | ||
The Relax-and-Recover (ReaR) workshop is guiding you into setting up rear, how to configure it, and with lots of real use cases, such as with Bareos, NFS, CIFS, RSYNC. | ||
|
||
## Setting up your virtual machines | ||
|
||
This document was only tested for the KVM and VirtualBox hypervisors, but it should work fine with other hypervisors. | ||
|
||
I would really appreciate that you test your hypervisor of choice and contribute instructions back (at https://github.com/rear/rear-workshop-osbconf-2016/pulls). | ||
I would really appreciate that you test your hypervisor of choice and contribute instructions back (at https://github.com/rear/rear-workshop/pulls). | ||
|
||
A few words before going to the prerequisites - we use **vagrant** as digital assitant to setup up our virtual images (VMs) to play with rear. Why? Because, in order to speed up the workshop around rear we do install lots of software automatically in the client and server VMs. | ||
|
||
|
@@ -21,10 +21,11 @@ To give an example, when you have setup the _client_ and _server_ VMs by running | |
Before we can start with the content of the workshop you need several things: | ||
|
||
- Host system can be Linux, Mac, Windows | ||
- A hypervisor like KVM, VirtualBox, VMware Player or VMware Fusion, Parallels Desktop | ||
- A hypervisor like KVM, Oracle VirtualBox, VMware Player or VMware Fusion, Parallels Desktop | ||
- Install *vagrant* from your distribution or when not present from https://www.vagrantup.com/downloads.html | ||
- KVM with libvirt needs the *vagrant-libvirt* plugin: _vagrant plugin install vagrant-libvirt_ | ||
- Install *git* to download the workshop: _git clone https://github.com/rear/rear-workshop-osbconf-2016.git_ | ||
- Install *git* to download the workshop: _git clone https://github.com/rear/rear-workshop.git_ | ||
or _git clone [email protected]:rear/rear-workshop.git_ | ||
- Sufficient free disk space for 3 VMs (about 3G per virtual machine should do) | ||
- Optional, vncviewer to approach the recover VM | ||
|
||
|
@@ -36,8 +37,8 @@ At this point we assume you have a hypervisor and vagrant already installed. Als | |
Start with downloading the workshop: | ||
|
||
<pre> | ||
$ git clone https://github.com/rear/rear-workshop-osbconf-2016.git | ||
Cloning into 'rear-workshop-osbconf-2016'... | ||
$ git clone https://github.com/rear/rear-workshop.git | ||
Cloning into 'rear-workshop'... | ||
remote: Counting objects: 160, done. | ||
remote: Total 160 (delta 0), reused 0 (delta 0), pack-reused 160 | ||
Receiving objects: 100% (160/160), 40.76 KiB | 0 bytes/s, done. | ||
|
@@ -48,7 +49,7 @@ Checking connectivity... done. | |
Then, browse into: | ||
|
||
<pre> | ||
$ cd rear-workshop-osbconf-2016/centos7/ | ||
$ cd rear-workshop/centos7/ | ||
$ ls | ||
nodeconfig-centos7.sh provision-centos7.sh Vagrantfile Vagrantfile.libvirt.recover Vagrantfile.virtualbox.recover | ||
</pre> | ||
|
@@ -102,7 +103,7 @@ There are several possibilities to login onto these fresh created VMs: | |
- vncviewer 127.0.0.1:5991 (for the client interface) | ||
- vncviewer 127.0.0.1:5992 (for the server interface) | ||
- vncviewer 127.0.0.1:5993 (for the recover interface) | ||
- Or, via the console of your hypervisor | ||
- Or, via the VM console of your hypervisor | ||
|
||
The passwords for the _vagrant_ and _root_ user are the same: *vagrant* | ||
|
||
|
@@ -123,7 +124,7 @@ And, the vagrant box can be removed as *vagrant box remove centos/7* | |
|
||
# Encountered a problem with setting up the workshop | ||
|
||
Oops, please open a new issue at https://github.com/rear/rear-workshop-osbconf-2016/issues | ||
Oops, please open a new issue at https://github.com/rear/rear-workshop/issues | ||
|
||
# Known Issues | ||
|
||
|
@@ -132,13 +133,13 @@ Oops, please open a new issue at https://github.com/rear/rear-workshop-osbconf-2 | |
When you get to see an error like the following: | ||
|
||
<pre> | ||
=> client: Rsyncing folder: /home/grati/rear-workshop-osbconf-2016/centos7/ => /vagrant | ||
=> client: Rsyncing folder: /home/grati/rear-workshop/centos7/ => /vagrant | ||
There was an error when attempting to rsync a synced folder. | ||
Please inspect the error message below for more info. | ||
|
||
Host path: /home/grati/rear-workshop-osbconf-2016/centos7/ | ||
Host path: /home/grati/rear-workshop/centos7/ | ||
Guest path: /vagrant | ||
Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o ControlMaster=auto -o ControlPath=C:/cygwin64/tmp/ssh.977 -o ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/cygwin64/home/grati/rear-workshop-osbconf-2016/insecure_keys/vagrant.private' --exclude .vagrant/ /home/grati/rear-workshop-osbconf-2016/centos7/ [email protected]:/vagrant | ||
Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o ControlMaster=auto -o ControlPath=C:/cygwin64/tmp/ssh.977 -o ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/cygwin64/home/grati/rear-workshop/insecure_keys/vagrant.private' --exclude .vagrant/ /home/grati/rear-workshop/centos7/ [email protected]:/vagrant | ||
Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. | ||
mm_receive_fd: no message header | ||
process_mux_new_session: failed to receive fd 0 from slave | ||
|
@@ -157,4 +158,4 @@ If you need to contact me for setting a workshop on your premises then see the p | |
|
||
Be aware, this workshop uses *centos/7* as GNU/Linux Operating system. If you want to have it for another version or type of GNU/Linux then you have to pay for it (consultancy fee - see above link). | ||
|
||
Last updated: 09 September 2016 | ||
Last updated: 30 December 2016 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters