-
Notifications
You must be signed in to change notification settings - Fork 6
Secondary Pi
This article covers the steps for using a second Raspberry Pi to host a few network services and a storage device for backups.
The more you rely on your home server, the more you'll find that it's good to have another copy of the data on it in case disaster strikes. It's also good to have a second set of network services like DNS and LDAP.
You may have an older Pi that's not up to the task of running multiple applications like the Pi 4 can, but is still working. That type of hardware is a good candidate for a secondary system. The examples in this article use a Raspberry Pi 2.
The instructions here assume you've already built a system on a Pi 4. The secondary system uses the same procedure, but since it's not hosting any applications in Docker containers, several steps can be skipped.
TODO: Install and trust new CA or copy the root and intermediate key pairs from the primary host???
The following example shows how to copy the root and intermediate certificates from the primary host (neuromancer) to the secondary host (wintermute).
pi@wintermute:/etc/ssl/certs $ sudo scp [email protected]:/etc/ssl/certs/home_CA.crt .
pi@wintermute:/etc/ssl/certs $ sudo scp [email protected]:/etc/ssl/certs/home.crt .
TODO: Copying private keys. How? cat and copy paste in terminal???
Issue a host cert for secondary host on secondary host.
Reference: https://davescodemusings.github.io/CloudPi/install-cockpit.html
First, Provision Stroage
Then, use cockpit to remove existing logical drives and configure for a single backup volume.
TODO
TODO: zone replication or manual sync?
Reference: https://davescodemusings.github.io/CloudPi/install-dns.html
TODO