I leveraged a FreeBSD jail to install my S3 client (s3cmd) tooling, and mount my storage to that jail. I’ve setup a private BackBlaze B2 bucket and applied a lifecycle policy that removes any files older than 7 days. I have a bunch of files on a FreeNAS storage server that I need to backup daily and send to the cloud. If you don’t have too much to backup you could get creative with lifecycle policies and stick within the 10GB free limit. The S3 client tooling available can of course be leveraged everywhere too ( s3cmd, aws s3, etc…).īackBlaze B2 gives you 10GB of storage free for a start. Sticking to this means that one can generally use the same backup/restore scripts for just about any service.
The reason for sticking to “S3” is because there are tons of cloud provided storage service implementations of the S3 API. To configure BIND, we edit /usr/local/etc/namedb/’ve been constantly evolving my cloud backup strategies to find the ultimate cheap S3 cloud backup solution. # if you do not have /usr/ports, run portsnap fetch & portsnap extract # install bind (for this, just took defaults when prompted) # determine jail ID for the newly created jail To install Bind, we want to get to a shell on the FreeNAS system (ssh works too). All the other options are defaults though check the IP address and netmask are what you wish to use (type=standard, ipv4-dhcp unchecked, IP aliases=, IP bridge config=, sysctls=allow.raw_sockets=true, autostart=checked, vimage=checked, NAT=unchecked). All the other options are defaults (sync=inherit/standard, compression=inherit/lz4, share-type=unix, enable-atime=inherit/on, zfs-deduplicatoin=inherit/off, quotas=0/unlimited, reserved-space=0/none, read-only=inherit/off, record-size=inherit). You can name it as you wish … though jails is a handy one. To create it, go to Storage and select the location you want to use, then click Create Dataset. If this is already setup, you can reuse it. The first thing you will need is storage for jails. These notes are with respect to FreeNAS 11 and Bind 9.
0 kommentar(er)
