AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Backblaze restore 1 file8/1/2023 There are two things in the output shown above which we still need to address: the compression policy and the retention policy.Īs-per Kopia’s documentation, compression can either be enabled per directory with kopia policy set -compression=zstd or for all directories with kopia policy set -global -compression=zstd.Įnabling compression can reduce the required upload bandwidth (potentially making backups faster) and storage requirements (lowering costs), especially if you have a large amount of compressible data, such as text documents, log files or database dumps. Kopia also provides a command to check that the connection to the storage backend works as expected ( great, I love self-checks!): If you want to avoid this, you can set the environment variable $KOPIA_PASSWORD instead of using the -password argument. You should be aware that Kopia stores the credentials used to connect to the storage backend in plaintext in $/.config/kopia/-password. There is lots of output here, but for now the most important line is “Connected to repository”. To change the policy use 'kopia policy set' command. To find more information about default policy run 'kopia policy get'. Latest snapshots: 10 (defined for this target ) Hourly snapshots: 48 (defined for this target ) Weekly snapshots: 4 (defined for this target )ĭaily snapshots: 7 (defined for this target ) Monthly snapshots: 24 (defined for this target ) We will need it in case we want to access the Kopia backups from another machine.Īnnual snapshots: 3 (defined for this target ) You can use your favorite password manager or a tool like pwgen to generate this secret - and make sure to store it somewhere safe! We’ll need them in the next step to configure Kopia for accessing Backblaze.Īdditionally, we’ll also need a “repository password” for Kopia – which is a bit confusing, because this password is not used for authenticating to Backblaze, but instead this is the secret used for encrypting the data on the client-side before sending it to Backblaze (or any other storage backend). Make sure to copy the keyID and applicationKey which are displayed after clicking Create. We don’t need to enable “Default Encryption”, since we’ll be using client-side encryption with Kopia.Īnd then create a new application key which has access only to the bucket created in the previous step: Next, we need to create a storage bucket on Backblaze B2. Type kopia -version into your shell to verify the CLI is installed correctly.Ġ.10.6 build: 766cb57160477fba0935634e98c2bdfd440557f3 from: kopia/kopia The first step is downloading the kopia binary, for which there are several options available in the Kopia documentation. In between I will also mention some of its advanced concepts, such as compression and retention policies.Īll of this is nicely documented in the Kopia docs, but if you are interested in an opionated introduction, follow right along. In this guide I’ll go through Kopia’s basic usage on the command line and how to set it up with Backblaze B2. Thus, I decided that I would give it a go on my new homeserver.
0 Comments
Read More
Leave a Reply. |