# Backing Up Published articles for Backing Up. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Code42 Is Shutting Down. Is CrashPlan the Safe Choice, or Just the Convenient One? DevFeed: [Code42 Is Shutting Down. Is CrashPlan the Safe Choice, or Just the Convenient One?]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-09-01T16:00:37Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [migration](), [Tooling](), [data loss prevention]() Tags: [alternatives](), [backing-up](), [backup](), [blog](), [businessbackup](), [cloud](), [cloud-storage](), [evaluation](), [featured](), [featured-backing-up](), [migration](), [post]() ### AI overview The article examines whether CrashPlan is an appropriate replacement for Code42 after Code42 stopped new sales in 2025 and plans to end support in 2026, with subsequent deletion of backup archives. It explains that Code42's backup business became a separate CrashPlan company in 2022 and urges IT teams to evaluate alternatives rather than assume CrashPlan is an automatic successor. It highlights migration incentives and a possible 5TB storage cap on some CrashPlan plans. ### Source excerpt Code42 support ends in 2026, but CrashPlan isn't the automatic successor it appears to be. Before migrating, understand the companies' split, CrashPlan's ownership, potential storage limits, evolving positioning, and the questions IT teams should ask when evaluating better backup alternatives. The post Code42 Is Shutting Down. Is CrashPlan the Safe Choice, or Just the Convenient One? appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Jamf Administrators: Your Backup Deployment Just Got Simpler DevFeed: [Jamf Administrators: Your Backup Deployment Just Got Simpler]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-08-19T13:28:18Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [Deployment](), [Provisioning](), [configuration](), [App](), [Orchestration]() Tags: [app](), [backing-up](), [backup](), [businessbackup](), [configuration](), [deployment](), [featured](), [featured-backing-up](), [onboarding](), [provisioning]() ### AI overview This article explains how Backblaze simplifies backup deployment for Mac fleets managed with Jamf. It describes fixed-email matching for devices with known owners, dynamic user detection for devices assigned later, and the ability to combine both methods within one deployment. ### Source excerpt Simplify Mac backup deployment with Backblaze and Jamf. Flexible user matching reduces manual setup, streamlines onboarding, and helps IT teams protect every device using their existing Jamf workflows. The post Jamf Administrators: Your Backup Deployment Just Got Simpler appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Backing up your content from Google Photos DevFeed: [Backing up your content from Google Photos]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2022-04-04T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Google](), [data](), [Chrome](), [Protocol (disambiguation)](), [Linux]() Tags: [archive](), [archiving](), [backing-up](), [backup](), [chrome](), [devtools](), [google](), [google-photos](), [gphotos-cdp](), [linux](), [nas](), [photos]() ### AI overview A tutorial on using gphotos-cdp to automate archiving images from Google Photos while retaining their EXIF metadata. The tool drives Google Chrome through the Chrome DevTools Protocol and is described as tested on Linux. ### Source excerpt Putting your media into Google Photos is easy, taking it out, not as much. ## How to Upgrade, Backup, and Restore Rancher 2 DevFeed: [How to Upgrade, Backup, and Restore Rancher 2]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-06-27T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [rancher](), [Tutorial](), [Docker]() Tags: [backing-up](), [backup](), [container](), [containers](), [docker](), [docker-image](), [guide](), [how-to](), [kubernetes](), [quick-start](), [rancher](), [run](), [upgrade](), [verify]() ### AI overview A tutorial explaining how to back up, upgrade, and restore a single-node Rancher 2 installation running in Docker. It covers creating a backup tarball, pulling a new Docker image, replacing state data, restarting the Rancher server, and verifying the upgrade. ### Source excerpt It use to be hard to back up Rancher, but with Rancher 2 it's super simple.Upgrading, backing up, and restoring your Rancher server should be part of your regular routine.Join me in this tutorial as we walk through backing up, upgrading, and restoring a single node Rancher Docker install in just a couple of minutes.Trust me, you'll feel better after you do. 📺 Watch Video Need to ins... ## Removing Google as a Single Point of Failure Part 2: Gmail DevFeed: [Removing Google as a Single Point of Failure Part 2: Gmail]() Original publisher: [Read original article]() Published: 2020-03-18T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Google](), [data](), [DRIVE](), [Homelab]() Tags: [backing-up](), [data](), [google](), [home-server](), [rsync](), [security]() ### AI overview The article explains how to reduce dependence on Google as a single point of failure while continuing to use Google services as the source of truth. It covers backing up Google Photos and Google Drive to a home server and rsync.net, then describes using a custom domain and Fastmail to preserve email access and support catch-all addresses. ### Source excerpt I want to remove Google as a single point of failure in my life. In the first blog post on this subject I detailed my setup for backing up Google Photos and Google Drive contents onto my home server and remotely to rsync.net. Left out of that post was a solution for Gmail because I hadn't found one yet. Now I have. Source of truth That first post started with an important qualification: This does not mean that I'm going to stop using Google products. Quite the opposite. Gmail, Google Photos, and Google Drive will remain the source-of-truth for all of the things I listed above. What's different is that should Google disappear tomorrow (or just my account) I would lose no data. This was easy to achieve with Photos and Drive because the data is all there is. With email that's unfortunately not true. Incrementally backing up the email data is pretty straightforward-we'll get into that shortly. But with Gmail your email address is still tied to the @gmail.com domain. So if my account or all of Google disappears, I won't be able to receive any more email. Of course the "easy" fix here is to just use a domain that I control. Obviously I own jakewharton.com, and I intend to set that up, but I wanted something shorter. I've owned cob.io for many years with the intention of setting up j@cob.io, but I go by "Jake". Luckily the last few years have seen an influx of new TLDs so I managed to grab ke.fyi. Say hello to j@ke.fyi! Having an email on my own domain doesn't address the problem that there's still hundreds or thousands of services that I've given the Gmail address to. While I can migrate many, there are inevitably those which I can't or that I simply don't know exist. The old address needs to remain working. Fastmail After browsing a few hosted email solutions, I settled on Fastmail (Note: referral link). In addition to a positive recommendation from a friend, there were a few key motivating factors. Domain catch-all A popular feature of Gmail is the ability to append a + ## Efficient Image Recovery at Scale Using Amazon S3 Versioning DevFeed: [Efficient Image Recovery at Scale Using Amazon S3 Versioning]() Original publisher: [Read original article]() Author: Praneeth Peiris I want Published: 2018-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Amazon S3](), [backups](), [Amazon Web Services](), [Availability]() Tags: [amazon-s3](), [backend](), [backing-up](), [high-availability](), [recovery](), [rollback](), [versioning]() ### AI overview trivago's Visual Content team uses Amazon S3 to store images from many hotels. After finding that conventional bulk backups would be too expensive at their scale, the team adopted S3 Versioning to back up changed files reactively and enable recovery of accidentally deleted files. ### Source excerpt Would you book a hotel without seeing the images first? No, right? Hence, it's vital to make sure the images are available all the time. In a scenario where a lot of images were deleted, we must have an efficient way of recovering them. This is how we achieved that with Amazon S3 Versioning. ## Postgres backups: Logical vs. Physical an overview DevFeed: [Postgres backups: Logical vs. Physical an overview]() Original publisher: [Read original article]() Author: Map Published: 2017-09-03T20:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [backups](), [Database](), [Databases](), [data]() Tags: [backing-up](), [backup](), [backups](), [checksums](), [dump](), [environments](), [logical](), [overview](), [pg-dump](), [portable](), [postgres](), [postgresql](), [production](), [sql](), [wal]() ### AI overview This article explains PostgreSQL's two backup types: logical backups, which are portable and can target selected tables but add database load, and physical backups, which consist of the database's bytes on disk. It also discusses checksums, corruption detection, and the role of the write-ahead log. ### Source excerpt It's not a very disputed topic that you should backup your database, and further test your backups. What is a little less discussed, at least for Postgres, is the types of backups that exist. Within Postgres there are two forms of backups and understanding them is a useful foundation for anyone working with Postgres. The two backup types are Physical: which consist of the actual bytes on disk, Logical: which is a more portable format. Let's dig into each a bit more so you can better assess which makes sense for you. Logical backups Logical backups are the most well known type within Postgres. This is what you get when you run pg_dump against a database. There are a number of different formats you can get from logical backups and Postgres does a good job of making it easy to compress and configure this backup how you see fit. When a logical backup is run against a database it is not throttled, this introduces a noticable load on your database. As it's reading the data from disk and generating (in layman terms) a bunch of SQL INSERT statements, it has to actually see the data. It's of note that older Postgres databases (read: prior to 9.3) there were no checksums against your database. Checksums are just one tool for you to help check against data corruption. Because a logical dump has to actually read and generate the data to insert it will discover any corruption that exists for you. This portable format is also very useful to pull down copies from production to different environments. I.e. if you need a copy of production data down on your local laptop pg_dump is the way to do it. Logical backups are also database specific, but then allow you to dump only certain tables. All in all logical backups bring some good features, but come at two cost: Load on your system The backup contains data as of the time when it ran Physical backups Physical backups are another option when it comes to backing up your database. As we mentioned earlier it is the physical bytes on disk ## Backing up with Capistrano DevFeed: [Backing up with Capistrano]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-01-05T20:12:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Automation](), [Linode](), [hosting](), [Server](), [Bash]() Tags: [automated](), [automation](), [backing-up](), [backup](), [bash](), [dropbox](), [hosting](), [linode](), [local](), [os](), [rsync](), [server]() ### AI overview A tutorial on using Capistrano to automate weekly backups from a Linode-hosted web server to a local machine. It creates a compressed tarball remotely, downloads it with scp, stores it in Dropbox, and schedules the task through local cron. ### Source excerpt We all know not backing up has consequences. While losing sentimental files would definitely ruin your day, losing your web server's data could be even worse. I've mentioned before that I use Linode for my server hosting, and while they do offer an automated backup service I decided I'd rather setup my own solution to back up periodically to my local machine. Many people use rsync to do their server backups. In fact Linode even has a guide on how to set it up (there's a better one here). I decided that instead of a 1 for 1 directory backup, I would prefer to have a tarball of the contents. While I could've easily done this with a few bash commands from the server that's not particular ideal for my setup. My local machines don't run 24/7 so if I set it up on the server to automate the backup every week, it may try to initiate the backup when my machine was off (I could try to guess when it's on every week but that's not ideal either). The obvious solution to this is run it from my local machine instead every week. That way once a week when it's powered up it would log in to the server, create the tarball and pull it down. Insert Capistrano ([sudo] gem install capistrano) a RubyGem for 'Remote multi-server automation.' So I wrote a very basic Capfile to automate this for me (replace the path to your www folder accordingly). load 'deploy' $SERVER_USER = "username" $SERVER_IP = "1.1.1.1" desc "Backs up server www files" task :backup, :hosts => $SERVER_IP do run "cd /srv; tar -pvczf ~/backup.tar.gz www/" run_locally "scp #{ $SERVER_USER }@#{ $SERVER_IP }:~/backup.tar.gz ~/Dropbox/Backups/Server" end Then I added this to my crontab on my local machine by running crontab -e and adding the line: @weekly /Users/ksmiley/.rbenv/shims/cap -f ~/path/to/Capfile backup I included the path to the Capistrano executable since cron (on OS X) executes tasks with sh, which isn't setup with my $PATH.