Related to my offsite-backup with restic project I recently wanted to choose an cloud-provider as backup target. But that seems not an easy decision. Besides the costs for storage and traffic things getting complicated when it comes to restore: Pricing differs here from $10 to $1300 for a single restore of 500GB!
Although I use mainly AWS for my business projects I consider to use google cloud storage for my private backup. Main reason for me is that the restore options for AWS S3 Glacier are not easy to predict and the costs could be very different.
„Cloud storage cost calculation (backup/restore)“ weiterlesen
Yes, I’ve tried multiple approaches in the past to get an offsite-backup up and running. I’ve used rsync first and then obnam and duplicity with encryption. Both successful with remote ssh-hosts.
But times are changing and I wanted to use a cloud-storage provider now instead of a dedicated remote host for my backups – so I started with duplicity/duply to get AWS S3 access running – that worked quite good.
But for some reason I discovered restic on github and gave it a try (maybe because of this introduction)
Things I like:
- growing user base on GitHub
- its encrypted (very interesting read on this)
- uses deduplication
- usage is straightforward, no hard to read config-files with dozens of options
- no full-/incremental backups, every backup is a „snapshot“
- they’re promise to not change the repository format in the future
- access to cloud providers (tested AWS S3 and Google Cloud Storage) went very easy
- its using a local cache to speed up (but is not sticked to that)
- you could move the backups to different locations using standard tools and they’re still usable
- local backups (like on USB-drives) could be achieved the same way: every destination is considered as „remote“ and is encrypted
Documentation is good, so I won’t share usage details here. But I’ve started backups to Google Cloud Storage last week and it feels great…
Short note: redirect local root mails (cron, mdadm, …) to an external address:
# install postfix
apt-get install postfix
# add alias for root
echo "root: email@example.com" >> /etc/aliases
# reload aliases for postfix
The Vigor 130 works very well as VDSL (Vectoring) modem in connection with a Sophos UTM. Therefore the modem is configured in PPPOE pass-through mode – this way all connection related details like credentials are configured by the Sophos UTM.
Because the vigor 130 has only one Ethernet interface I always had to re-plug some network cables just to watch the DSL status via the webinterface of the „modem“.
Here are some hints on how to connect to the modem interface (using just basic routing).
In my case my LAN subnet is 192.168.23.0/24.
Place the modem into an additional Subnet
here: 192.168.24.0/24, ip of the modem: 192.168.24.2
create a static route
the vigor allows not to change the default route, but that is also not neccessary if you have only one LAN subnet.
Add an additional address to the Sophos WAN interace
In my setup the WAN interface is used as PPPOE interface for the modem, but its easy to add the modem subnet on top of it:
you should now be able to connect to your modem webinterface from your LAN via http://192.168.24.2/