7/2/2023 0 Comments Spideroak linux command line![]() ![]() ![]() The tarsnap billing model is admittedly a little weird, in that it's pay-as-you-go rather than pay-monthly. (The web interface is a little clunky but, believe me, you don't care because you rarely use the web interface). Head on over to and set yourself up with a new account. Here's how easy it is to get up and running. (It also has the pleasing side effect that the backup script that you wrote 20 years ago to tar directories onto a tape drive can be easily modified to back up to cloud storage.) Its command-line usage closely resembles that of tar, which is awesome if you're old-school like me.It's easy to set up, and it does encryption-at-source straight out of the box.This is super-efficient and helps to keep costs down. It uses block-level de-duplication for both data transfer and data storage.If you're on the lookout for a backup solution for your Linux/Unix servers then I highly recommend tarsnap, especially if your a command-line person like me. The system must comply with all appropriate EU Data Protection (and GDPR) legislation.Each server's backups should be independent, so that if a bad actor does somehow gain access to one of the primary servers then they will not be able to access backups for other servers.Backups should be encrypted at source, so that if a bad actor does somehow gain access to the backup store, the backups will all be useless to them.So, some sort of block-level de-duping would be ideal. Most of the data I backup is source code, config files and database dumps, all of which are text files. The system should be efficient when transferring and storing text files.(Anything that is complex to configure is easy to mess up!) The system should be as simple as possible to configure on any Linux server.Backups are to be pushed rather than pulled. Backups should be initiated on the source server via the command-line/cron.So, I decided to look around and see what else was available. Initiating from source would require multiple user accounts on the destination (in order to prevent servers from having access to the backups from other servers). Backups are initiated from the destination server, which makes it impossible to control backup intervals from the source server.If a bad actor somehow gained access to the backup server, they would have access to backups for all the servers.As more and more VPS providers move from HDDs to SSDs, VPS disk space is not as cheap as it used to be.Disk space used for the backups increases (almost) linearly 1.It's a little cumbersome to set up for each new VPS.This is fine and has always served me well, but I've always been mindful of the following: My backup-solution-of-choice for many years had been rsnapshot-ing onto a remote VPS. I provide managed Linux hosting for a number of my clients. ![]()
0 Comments
Leave a Reply. |