# 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. ## Turns out database backups are NOT trivial DevFeed: [Turns out database backups are NOT trivial]() Original publisher: [Read original article]() Author: Stack Published: 2026-10-29T15:30:13Z Content type: article Language: en Sources: [Stack]() Topics: [backups](), [Database](), [database-consistency](), [transaction-log](), [Transactions](), [DuckDB](), [clickhouse]() Tags: [abstraction](), [agent](), [algorithm](), [analytics](), [api](), [backing-up](), [backup](), [backups](), [convex](), [data](), [database](), [production](), [tables]() ### AI overview A row-by-row backup of a changing database can combine records from different moments and describe a state that never existed. Convex's data sync avoids this by alternating between reading table rows and catching up on the document log, keeping its snapshot within the retention window; it reports `upToDate` when the copy is consistent. Pages may contain repeated rows and arrive out of timestamp order, so callers must apply truncates and values and save pages safely. The endpoint requires a Pro plan and charges for database reads and bandwidth; its cursor can resume syncing within the deployment's retention window. Convex also offers dashboard and CLI backups, scheduled backups on Pro, and faster, cheaper physical backups for dedicated deployments, though those cannot be downloaded or inspected. For analytics at scale, the article says Convex still recommends its Fivetran connector. ### Source excerpt I thought backing up a database was simple, you just loop over the tables and copy the rows out. Nipunn sat me down at a whiteboard and showed me why that can give you a backup of data that never existed, and how Convex gets around it. ## The Mac Backup Problem Most IT Teams Don't See Coming DevFeed: [The Mac Backup Problem Most IT Teams Don't See Coming]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-10-27T15:53:07Z Content type: article Language: en Sources: [Backblaze]() Topics: [backups](), [Data Management]() Tags: [apple-silicon](), [audit](), [backing-up](), [backup](), [backups](), [businessbackup](), [client](), [cloud](), [cloud-backup](), [cloud-storage](), [data-loss](), [deploy](), [deployment](), [design](), [exposed](), [featured](), [featured-backing-up](), [files](), [fleet](), [it](), [mac](), [pricing](), [teams](), [tool](), [uncategorized]() ### AI overview The excerpt reports that Mac fleet backup gaps can leave important laptop data exposed even when a tool lists Mac support: 43% of IT teams do not back up all endpoints, and only 9% say restores are very easy. It attributes the problem to ported clients that compete for resources or are disabled, slow adaptation to macOS changes that can cause missed files or silent failures, manual deployment friction with Jamf, Kandji, Addigy, and Intune, and per-gigabyte pricing that can encourage excluding large, hard-to-recreate files. These issues may surface during offboarding, an incident, or an audit. The post points readers to a white paper with vendor evaluation questions; it does not provide those questions in this excerpt. ### Source excerpt Your backup tool supports Mac, but does it protect your entire fleet? Learn how client design, deployment friction, and pricing can leave critical files exposed--and what IT teams should ask vendors before trusting them with their Mac fleet backups. The post The Mac Backup Problem Most IT Teams Don't See Coming appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Telling swamp what I want DevFeed: [Telling swamp what I want]() Original publisher: [Read original article]() Author: svendowideit Published: 2026-10-24T09:56:58Z Content type: article Language: en Sources: [Swamp Club Feed]() Topics: [static-site-generator](), [Markdown](), [Obsidian](), [AI Chat]() Tags: [backing-up](), [bash](), [bash-shell](), [beam](), [blog](), [caddy](), [cloudflare](), [cloudflare-pages](), [credentials](), [dns](), [extension](), [extensions](), [git](), [html](), [inventory](), [markdown](), [obsidian](), [repository](), [swamp](), [workflow]() ### AI overview The author built a custom swamp workflow to publish existing Obsidian blog posts without creating a separate Git repository. It uses a new @svendowideit/markdown2html extension to progressively enhance HTML using whatever frontmatter is present, and @svendowideit/caddy to set up DNS through the author's existing libdns zone. Publishing to Cloudflare Pages requires a token with Cloudflare Pages edit access and DNS metadata zone scope; the token and account ID are stored in a swamp vault. The workflow is run with inputs for the blog and publish directories, hostname, vault, Caddy and DNS models, site title, and template path. The author says the implementation took a few hours and can later be invoked through opencode by asking it to redeploy the site. ### Source excerpt A developer builds a custom swamp workflow that converts Obsidian markdown blog posts to HTML and publishes them to Cloudflare Pages with automatic DNS setup via Caddy, without requiring a separate git repository. ## Your First Proxmox Server Can Do More Than You Think DevFeed: [Your First Proxmox Server Can Do More Than You Think]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-10-22T12:35:43Z Content type: article Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Proxmox](), [systems](), [virtualization](), [virtual machines](), [Tutorial](), [Service fabric]() Tags: [ansible](), [automate](), [automation](), [backing-up](), [backup](), [backups](), [clone](), [cloud](), [cloud-init](), [cloud-native](), [cloud-technologies](), [cluster](), [clustering](), [clusters](), [configuration](), [hardware](), [home-lab](), [home-server](), [lab](), [proxmox](), [server](), [virtualization]() ### AI overview A single Proxmox host can support substantial lab practice, though virtual nodes on one machine do not provide physical host redundancy. The article recommends separating lab and self-hosted services with distinct VLANs and subnets, while keeping switching and firewalling outside the host to preserve network access if Proxmox fails. Nested Proxmox VMs can be used to practice clustering and shared storage. A dedicated VM is the recommended place to run Docker; Proxmox also offers native LXC containers and, from v9.1, OCI image support that runs through LXC. Snapshots provide rollback points, while cloning lets you test changes on a copy. VM templates, cloud-init and optionally Packer and Ansible enable repeatable guest setup. A small Kubernetes cluster can teach node and scheduling basics, but all nodes stop if the physical host goes down. VM backups to local storage can teach the process, though the article says this is not ideal for data resilience. ### Source excerpt Recently, I wrote up an article looking at the things that you can skip when you want to stand up a really great Proxmox lab, even with little hardware. You... The post Your First Proxmox Server Can Do More Than You Think appeared first on Virtualization Howto. ## Why Your Computer Backup Strategy Determines Whether You Pay the Ransom DevFeed: [Why Your Computer Backup Strategy Determines Whether You Pay the Ransom]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-10-07T16:07:49Z Content type: article Language: en Sources: [Backblaze]() Topics: [backups](), [Disaster Recovery](), [network security]() Tags: [backing-up](), [businessbackup](), [cloud-storage](), [consumerbackup](), [data-protection](), [featured](), [featured-backing-up](), [how-to](), [ransomware](), [ransomware-recovery](), [storage]() ### AI overview The article argues that ransomware recovery depends on backup architecture, including retention length, protected deletion and restore permissions, legal holds, and tested endpoint recovery procedures. It recommends walking through a restore for one laptop to identify gaps before an incident and describes Backblaze Computer Backup with Enterprise Controls as offering a year of version history, legal hold, centrally managed restores, and flat per-device pricing. ### Source excerpt Ransomware recovery depends on more than having a backup. Learn how version history, deleted file retention, legal hold, and restore permissions shape your computer backup strategy--and how to test whether your team can actually recover when an attack hits. The post Why Your Computer Backup Strategy Determines Whether You Pay the Ransom appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## What IT Teams Get Wrong About Immutable Backups and Object Lock DevFeed: [What IT Teams Get Wrong About Immutable Backups and Object Lock]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-09-22T14:34:57Z Content type: article Language: en Sources: [Backblaze]() Topics: [backups](), [locking](), [ransomware](), [Encryption](), [Cloud](), [Security](), [configuration](), [data]() Tags: [backing-up](), [backup](), [backups](), [businessbackup](), [cloud](), [cloud-storage](), [configuration](), [data-security](), [encryption](), [featured](), [featured-backing-up](), [immutability](), [immutable-backup](), [locking](), [ransomware](), [storage]() ### AI overview This article explains common mistakes in configuring immutable backups and object lock for cloud storage. It distinguishes encryption, which prevents unauthorized viewing, from object lock, which prevents modification and deletion, and explains how immutability affects restores and existing bucket contents. ### Source excerpt Object lock can create false confidence when bucket settings, backup software, retention periods, and lifecycle rules are misaligned. Learn the most common immutable backup mistakes--and how to configure ransomware-resistant storage correctly without unexpected access, capacity, or operational transaction-cost surprises. The post What IT Teams Get Wrong About Immutable Backups and Object Lock appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Zero-touch deployment requirements for Mac fleet backup DevFeed: [Zero-touch deployment requirements for Mac fleet backup]() Original publisher: [Read original article]() Author: Kari Wilson Published: 2026-09-17T16:51:35Z Content type: article Language: en Sources: [Backblaze]() Topics: [Deployment](), [Automation](), [Software]() Tags: [agent](), [automation](), [backing-up](), [backup](), [businessbackup](), [deployment](), [featured](), [featured-backing-up](), [fleet](), [mac]() ### AI overview The article argues that zero-touch deployment has become essential for Mac fleets, especially for lean IT teams managing devices through MDM platforms such as Jamf Pro, Kandji, and Addigy. It explains how interactive installers, permission prompts, and registration failures create support work and can leave machines unprotected. ### Source excerpt For lean IT teams, zero-touch Mac backup deployment is no longer optional. Learn what truly silent installation requires and how Backblaze helps admins protect every device across Jamf, Kandji, Addigy, and other MDM-managed fleets without user interaction or follow-up work. The post Zero-Touch or It Doesn't Scale: The New Standard for Mac Fleet Backup appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## 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]() Topics: [migration](), [Developer Tools](), [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]() 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 ## Kubernetes made deploying easy. Nobody warned you about the databases. DevFeed: [Kubernetes made deploying easy. Nobody warned you about the databases.]() Original publisher: [Read original article]() Author: Oliver Wolf Published: 2026-07-21T15:00:00Z Content type: opinion Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [internal developer platform](), [Database](), [internal developer platform automation](), [DevOps](), [infrastructure monitoring]() Tags: [anynines](), [automation](), [backing-up](), [backups](), [caching](), [control-plane](), [data-services](), [database](), [database-management](), [databases](), [developer-platform](), [devops](), [elasticsearch](), [governance](), [helm](), [kubernetes](), [kubernetes-native](), [monitoring](), [opensearch](), [patching](), [platform-engineering](), [post](), [software-developers](), [sponsor-anynines](), [sponsored-post]() ### AI overview The excerpt argues that Kubernetes simplifies database deployment but leaves teams with substantial reliability work: patching, monitoring, backups, and recovery across services such as Postgres, Redis, and OpenSearch or Elasticsearch. It says expecting application developers to build deep database operations expertise can make "you build it, you run it" unrealistic. Instead, an internal developer platform can let developers request databases through Kubernetes-native workflows while a centralized control plane handles provisioning, backups, patching, and governance. The excerpt cites a9s Hub as an example, but does not provide comparative tool details or complete guidance. ### Source excerpt The DevOps movement, set in motion nearly 20 years ago, broke down the traditional divide between software developers and IT The post Kubernetes made deploying easy. Nobody warned you about the databases. appeared first on The New Stack. ## How to Upgrade Ubuntu 22.04 to 24.04 LTS: A Complete Guide DevFeed: [How to Upgrade Ubuntu 22.04 to 24.04 LTS: A Complete Guide]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-04-26T18:25:08Z Content type: tutorial Language: en Sources: [nixCraft]() Topics: [Ubuntu](), [upgrade](), [Linux](), [backups](), [Command-line interface](), [systemd](), [apt]() Tags: [apt](), [backing-up](), [backup](), [backups](), [cli](), [development](), [guide](), [how-to](), [kernel](), [lts](), [opensource](), [systemd](), [ubuntu](), [ubuntu-debian-linux](), [upgrade]() ### AI overview A guide to upgrading Ubuntu 22.04 LTS to Ubuntu 24.04 LTS through an SSH-based CLI session. It covers release timing, backups, package updates, and the Ubuntu release upgrader. ### Source excerpt {nixCraft Patreon supporters content} Below is a sneak peek of this content! Ubuntu 24.04 LTS (Noble Numbat) was launched on April 25th, 2024. This new version will be supported for five years until June 2029. The armhf architecture now provides support for the Year 2038 problem. The upgrades include significant updates to core packages like Linux kernel, systemd, Netplan, [...] The post How to Upgrade Ubuntu 22.04 to 24.04 LTS: A Complete Guide appeared first on Opensource Flare✨. ## Kafka Logging: Strategies, Tools & Techniques for Log Analysis DevFeed: [Kafka Logging: Strategies, Tools & Techniques for Log Analysis]() Original publisher: [Read original article]() Author: Erez Levi Published: 2023-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Ground Cover]() Topics: [Apache Kafka](), [Logging](), [Data pipelines](), [Grafana]() Tags: [backing-up](), [compaction](), [compression](), [kafka](), [log-management](), [logging](), [partitions]() ### AI overview A practical guide to managing Apache Kafka logs and partitions. It explains topic and partition structure, retention and cleanup policies, compaction, compression, cold storage backups, partition sizing, and monitoring with JMX metrics and tools such as Prometheus and Grafana. Recommendations depend on the application's retention needs, workload, and storage constraints. ### Source excerpt Explore Kafka log management. Optimize Kafka partitions for efficient logging, reduce resource usage in clusters, and ensure data accessibility. ## Automated PostgreSQL Backups DevFeed: [Automated PostgreSQL Backups]() Original publisher: [Read original article]() Author: Faraz Patankar Published: 2022-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Railway]() Topics: [backups](), [PostgreSQL]() Tags: [amazon-s3](), [automated](), [aws](), [aws-s3](), [backing-up](), [backup](), [backups](), [blog](), [cloud](), [cron](), [daily](), [database](), [javascript](), [postgresql](), [postgresql-backups](), [railway](), [template]() ### AI overview Railway's PostgreSQL backup template automates backups through a JavaScript service that stores them in an AWS S3 bucket. Setup requires an S3 bucket and IAM access credentials; the guide notes that AmazonS3FullAccess is unsafe for long-term use and suggests narrowing permissions to the specific bucket. Configure the AWS variables and BACKUP_DATABASE_URL, using Railway's DATABASE_URL reference for a database in the same project or its connection URL otherwise. Backups run daily at 5 AM UTC by default; BACKUP_CRON_SCHEDULE can change the cadence. To restore, extract the tar.gz backup and run pg_restore with the destination database URL and extracted folder. Railway says it does not natively support automated backups; this template provides a deployable service workaround. ### Source excerpt A step-by-step guide on automatic PostgreSQL backups on Railway using a one-click template. ## Back Up Encrypted ZFS Data without Unlocking It DevFeed: [Back Up Encrypted ZFS Data without Unlocking It]() Original publisher: [Read original article]() Author: Michael Lynch Published: 2022-07-29T00:00:00Z Content type: article Language: en Sources: [Mtlynch]() Topics: [truenas](), [backups](), [Encryption](), [Replication](), [Homelab](), [restic](), [Cloud](), [Bash](), [Script](), [Synology]() Tags: [backing-up](), [backups](), [bash](), [cloud](), [encryption](), [homelab](), [replication](), [restic](), [synology](), [truenas]() ### AI overview A practical guide to backing up encrypted ZFS data from a TrueNAS server to generic cloud storage. It explains the limitations of TrueNAS replication targets and describes using restic, resticpy, and Bash scripting to work with encrypted backups without unlocking the dataset. ### Source excerpt I recently built my first home TrueNAS server. I use it to store the bulk of my personal and work data, so I've been learning how to make the most of TrueNAS and its filesystem, ZFS. Today, I want to tell you about backing up encrypted data. My homelab TrueNAS server ## 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](), [Google 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 Backup and Restore Your Postgres Database DevFeed: [How to Backup and Restore Your Postgres Database]() Original publisher: [Read original article]() Author: Angelo Saraceno Published: 2021-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Railway]() Topics: [Database](), [Disaster Recovery](), [SQL](), [Heroku Postgres](), [Prisma]() Tags: [backing-up](), [backup](), [cloud](), [database](), [how-to](), [postgres](), [railway](), [restore]() ### AI overview The article explains how to use PostgreSQL's `pg_dump` and `pg_restore` tools to back up a Railway database to a local file and restore it to another PostgreSQL instance. It requires the `psql` client tools and Railway's `PGUSER`, `PGHOST`, `PGPORT`, `PGDATABASE`, and `PGPASSWORD` values; the backup command prompts for the password and may take longer for larger databases. For Heroku sources, the text reports that the specialized dump format may require `pg_dump -F t` for a platform-agnostic backup and says `heroku pg:backups:download` will not work. It provides a corresponding restore command using Railway connection values and notes that Prisma users may see a warning even when data imports normally. ### Source excerpt In this post, we will go over the process of backing up and restoring your Postgres database hosted on Railway. ## 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](), [NVIDIA 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 + ## 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](), [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: [restic](), [hosting](), [scheduling](), [Tool]() Tags: [backing-up](), [capistrano]() ### AI overview The author uses Capistrano from a local machine to create and retrieve a weekly server backup, so the job runs when that machine is powered on. Rather than mirror directories with rsync, the Capfile runs `tar` on the server to create a compressed archive, then copies it locally with `scp` to a Dropbox backup folder. A local crontab entry schedules the task weekly; it specifies the Capistrano executable path because OS X cron uses `sh` without the author's usual `$PATH`. The excerpt says to adjust the `www` path for the server. ### 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.