Backup Backup server - Part 3

 Adding storage and general software.

Now i have planned to create this server for some time.

What made me do it, is that one day googling i found this post. Basically Muffn_ combined some software that i didn't even know existed.

The short version is.

Debian for a stable system

SnapRaid for a flexible storage system, that doesn't use too many resources for my old N40L

Btrfs filesystem and snapshots to keep incomming / moving data safe. I will furthermore use the compression feature of the filesystem, as that will make disk usage more simple.

MergerFs to place the data on the disks.

Power down inactive disks

Turn on the backup server from my Main server, and shut it down, once backup is done, and SnapRaid hashing has been done

But first things are first. I started by removing the compatible wifi usb dongle, to see if the other one would play nicely. The system didn't even hickup as but that was because it was using the new adapter. For some reason it wouldn't change to the old one. Oh well. If i remember i will replace the new for the old on next reboot.

Edit:

Got it.

Used sudo iwconfig to get the interface name.

Then copied the functioning ethernet interface in /ect/network/interfaces, changing the name to the name of the second adapter.

Now it accepts ripping one adapter out, and adding the other one.

Then there the x/KDE thing. Lets disable the autostart at boot, to save resources

we do a 

systemctl set-default multi-user.target

and reboot.

Then on to the router, to assign a fixed Ip

Back to the main course.

i want to do the same as Muffn_ in that i want to use the ssd for caching incoming files. One of the reasons for this is also that i want to enable compression on the storage disks. Having read his blog, i found a very descriptive schematic of what i wanted to do. I wont steal or replicate his diagram, i will instead say this. I have no /mnt/array01 nor /mnt/Array02.

Now heres the fun part.

Muffn_ did at time of writing, not write part 4 of the saga yet. so instead i have to glean the things i can from the descriptions, and see what i can figure out from his ansible script.

Let the digging commense.

Ansible seems to be among other things an automated install script thinghy, so i will steal  learn as much as i can from it.

Having dug around a little bit, i relaised that its just a way of chugging down what you want to do, using a script language i don't know. I do this myself a fair bit when working with my robot... creating code so i don't have to do something. So off i go to try and figure out how this script would work.

Now as far as i could decipher you have to actually run the script on another computer, called a the control node, that then installs on the Managed node. This could be a skill that's useful, so of reading tutorials i go.

My idea now, is to fork the ansible script, and make my adjustmenst as i need them.

More will follow in part 4