ofla.blogg.se

Backblaze b2 s3 compatible
Backblaze b2 s3 compatible









backblaze b2 s3 compatible

Tar -exclude='./some-optional-stuff-to-exclude' -zcvf "/root/$TIMESTAMP-backup.tgz". Here is a quick and easy shell script to demonstrate compressing a directory path and all of it’s contents, then uploading it to a bucket with s3cmd. S3cmd -version A simple backup shell script Here is a page that describes the settings you’ll need in addition to your access / secret key.Īfter gpg was compiled and installed you should find it under the path /usr/local/bin/gpg, so you can use this for your s3cmd configuration too.ĭouble check s3cmd and gpg are installed with simple version checks. Once complete, you should be able to run s3cmd –configure to set up your defaults.įor BackBlaze you’ll need to configure s3cmd to use a specific endpoint for your region. The compile and install process takes a number of minutes. # make install gpg for encryption supportĬd /usr/ports/security/gnupg/ & make -DBATCH install clean If you don't want defaults then leave this bit off. # Note -DBATCH will take all the defaults for the compile process and prevent tons of pop-up dialogs asking to choose. Portsnap extract # skip this if you've already run extract before

backblaze b2 s3 compatible

You can use portsnap to get everything downloaded and ready for compilation. The first step in a clean/base jail is to get s3cmd compiled and installed, as well as gpg for encryption support. Mount the FreeNAS storage path you’re interested in backing up as read-only to the jail.

backblaze b2 s3 compatible

You can follow the steps below if you would like to setup something similar: Step-by-step setup guideĮnable VNET, DHCP, and Auto-start. 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.

backblaze b2 s3 compatible

I’ve been constantly evolving my cloud backup strategies to find the ultimate cheap S3 cloud backup solution.











Backblaze b2 s3 compatible