# Backup Published articles for Backup. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 Blog | Cloud Storage & Cloud Backup]() 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 ## New Git repositories added as backup Libreboot mirrors DevFeed: [New Git repositories added as backup Libreboot mirrors]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [Git](), [libreboot](), [coreboot]() Tags: [article](), [backup](), [bios](), [canoeboot](), [coreboot](), [free-software](), [git](), [libre](), [libreboot](), [news](), [opensource](), [repositories](), [uefi]() ### AI overview Libreboot announces official mirrors for its Git repository on additional hosting platforms. The mirrors back up the main Codeberg mirror and include the lbmk build system and lbwww website files, with more mirrors planned. ### Source excerpt Article: New Git repositories added as backup Libreboot mirrors Web link: https://libreboot.org/news/mirrors.html ## pgBackRest Compression: How Much CPU Is a Smaller Backup Worth? DevFeed: [pgBackRest Compression: How Much CPU Is a Smaller Backup Worth?]() Original publisher: [Read original article]() Author: Agustín Gallego Published: 2026-09-16T21:43:06Z Content type: comparison Language: en Sources: [Blog - Percona]() Topics: [Compression](), [Algorithms](), [PostgreSQL](), [postgresql 18](), [backups](), [Percona]() Tags: [algorithms](), [backup](), [compare](), [compression](), [cpu](), [percona](), [postgresql](), [postgresql-18](), [uncategorized]() ### AI overview This comparison measures pgBackRest compression algorithms and levels on Percona Distribution for PostgreSQL 18.4. It finds that low-level Zstandard offers a favorable balance between CPU use and backup size, with zst(3) near the efficiency curve's shoulder. ### Source excerpt In this blog post, we'll compare pgBackRest's compression algorithms and levels to find where spending more CPU stops buying a meaningfully smaller backup. The short version of the answer, which we'll build up to with real numbers, is that Zstandard at a low level is the sweet spot, and its default (zst(3)) already sits right ... Continued The post pgBackRest Compression: How Much CPU Is a Smaller Backup Worth? appeared first on Percona. ## Stories from our latest intern class DevFeed: [Stories from our latest intern class]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-12-21T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Programming](), [Mobile](), [JavaScript](), [Ionic](), [AdventureX 2026]() Tags: [backup](), [blog-post](), [email](), [engineering](), [github](), [hackathon](), [intern](), [ionic](), [javascript](), [mobile](), [news](), [programming](), [project](), [stories](), [web-frontend]() ### AI overview This article shares reflections from Khan Academy's 2015 intern class. It describes a hackathon project that used Ionic to build a mobile app for browsing and playing JavaScript projects, and discusses backing up Khan Academy mailing-list data. ### Source excerpt By 2015 Interns We sent an email out to all of the 2015 interns in early November, shortly ... Read more ## KDE Plasma 6.8 Beta Released With Many Great Improvements, Kup Backup Scheduler DevFeed: [KDE Plasma 6.8 Beta Released With Many Great Improvements, Kup Backup Scheduler]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-10T16:39:24Z Content type: release Language: en Sources: [Phoronix]() Topics: [Wayland](), [Multi-GPU](), [GPU](), [monitor]() Tags: [backup](), [desktop](), [desktop-linux](), [gpu](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [monitor](), [multi-gpu](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [remote](), [server](), [tool](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview KDE Plasma 6.8 Beta introduces improvements to Wayland support, vRAM usage, remote desktops, multi-GPU and multi-monitor handling, theming, and other desktop functionality. It also includes Kup as the Plasma desktop backup scheduler. ### Source excerpt Ahead of the stable release of Plasma 6.8 due out on 14 October that also marks the 30th anniversary of the KDE project, out today is the much anticipated beta release... ## \[Crypto\] Time-based one-time password (TOTP) for 2FA, part I DevFeed: [\[Crypto\] Time-based one-time password (TOTP) for 2FA, part I]() Original publisher: [Read original article]() Published: 2026-09-09T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [passwords](), [QR Code](), [Google](), [Python](), [Unix](), [App](), [email](), [Code]() Tags: [account](), [app](), [argument](), [backup](), [code](), [crypto](), [env-file-security](), [github](), [google](), [password](), [protection](), [python](), [run](), [server](), [smartphone](), [unix]() ### AI overview This tutorial explains how time-based one-time passwords work for two-factor authentication. It covers importing a base32-encoded secret from a QR code into Google Authenticator, generating 6-digit login codes, and calculating them with HMAC-SHA-1 from the secret and Unix time. It also discusses backup codes and securely storing TOTP secrets separately from passwords. ### Source excerpt [Crypto] Time-based one-time password (TOTP) for 2FA, part I ## Jellyfin 12.0 Is Out: What Breaks Before You Upgrade DevFeed: [Jellyfin 12.0 Is Out: What Breaks Before You Upgrade]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-08T06:32:10Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [Database Migration](), [Database](), [Security](), [Server]() Tags: [article](), [backup](), [bug](), [data](), [database](), [jellyfin](), [jellyfin-12-0-is](), [jellyfin-news](), [news](), [release](), [security](), [server](), [update]() ### AI overview Jellyfin 12.0 introduces a new versioning scheme and a database rewrite that makes upgrading a consequential operation. Users must meet the supported upgrade path, back up and verify restoration of their configuration and database, complete a full library scan, remove or recompile third-party plugins, and account for removed legacy API and login support. ### Source excerpt Jellyfin 12.0 shipped on September 7, 2026, after months stuck in release candidate limbo. It's the biggest Jellyfin release since the project forked from Emby in 2018, and the version number itself is the first clue: this build reports as 12.0, not 10.12.0. That's not a typo. Jellyfin has dropped the "10" major prefix that led its version numbers since the fork. ## BTRFS boot failure and easy GUI methods for system recovery DevFeed: [BTRFS boot failure and easy GUI methods for system recovery]() Original publisher: [Read original article]() Author: Alex Genovese Published: 2026-09-04T20:54:40Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [boot](), [Fedora](), [GUI](), [Linux](), [dnf](), [Software]() Tags: [backup](), [boot](), [btrfs](), [desktop](), [dnf](), [faqs-and-guides](), [fedora-project-community](), [for-system-administrators](), [gui](), [how-to](), [installation](), [iso](), [linux](), [recovery](), [snapshots](), [usb](), [using-hardware](), [using-software](), [workstation]() ### AI overview This how-to article explains GUI-based recovery options for Fedora Linux systems using BTRFS. It covers booting from a USB live ISO, checking whether the operating system uses BTRFS, and recovering earlier system states with snapshot tools such as btrfs-assistant and snapper. ### Source excerpt A few short how-to's with screenshots, showing easy ways to boot up off a USB live ISO and return back to previous points in time with BTRFS ## Kubernetes Backup and Disaster Recovery: What to Protect and How? DevFeed: [Kubernetes Backup and Disaster Recovery: What to Protect and How?]() Original publisher: [Read original article]() Author: Urolime Technologies Published: 2026-09-04T14:50:25Z Content type: article Language: en Sources: [Kubernetes Archives - Urolime Blogs]() Topics: [Kubernetes](), [Disaster Recovery](), [Availability](), [Cloud Native Ecosystem]() Tags: [applications](), [availability](), [backup](), [cloud-native](), [disaster-recovery](), [kubernetes](), [kubernetes-backup-and-disaster-recovery]() ### AI overview The article explains that Kubernetes high availability and self-healing do not provide disaster recovery. It describes why Kubernetes backup is complex and identifies persistent data, Kubernetes resources, configurations, secrets, and cluster configuration as protection targets, along with several disaster scenarios. ### Source excerpt Kubernetes has been the bedrock on which most modern-day cloud-native apps have been built- thus providing organizations with a highly efficient way of deploying and managing their workloads. The self-healing nature, automatic scaling, and high availability features of Kubernetes give a false sense that applications are inherently resilient against failures. However, high availability is not [...] ## Announcing the S3 API: Use any S3 client with Appwrite Storage DevFeed: [Announcing the S3 API: Use any S3 client with Appwrite Storage]() Original publisher: [Read original article]() Author: Torsten Dittmann Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Amazon S3](), [API](), [Amazon Web Services](), [SDKs](), [Command-line interface](), [migration]() Tags: [announcements](), [api](), [aws](), [backup](), [cli](), [code](), [commands](), [data](), [files](), [migration](), [reuse](), [s3](), [sdk](), [sdks](), [server](), [storage](), [tools]() ### AI overview Appwrite Storage now exposes an S3-compatible API that supports AWS CLI, AWS SDKs, rclone, s3cmd, and other S3 clients. Existing buckets and files remain available through both the native Storage API and the S3 API, with support for standard operations, multipart uploads, and presigned URLs. ### Source excerpt Appwrite Storage now exposes an S3-compatible API. Point the AWS CLI, the AWS SDKs, and tools like rclone at your Appwrite buckets, with no migration required. ## 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 ## Omdia Study Highlights Declining Ransomware Recovery Rates and the Immutability Gap in Backup Storage DevFeed: [Omdia Study Highlights Declining Ransomware Recovery Rates and the Immutability Gap in Backup Storage]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-01T15:42:11Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [ransomware](), [Resilience](), [Security]() Tags: [backup](), [data-protection](), [enterprise](), [ransomware](), [recovery](), [research](), [resilience](), [security](), [third-party]() ### AI overview An Omdia study commissioned by Object First reports declining enterprise ransomware recovery rates despite increased awareness of data protection strategies. The findings show frequent attacks, worsening data recoverability, missed recovery objectives, and a substantial gap between the perceived importance of immutable backup storage and its actual implementation. The study also highlights demand for independent validation of vendor immutability claims. ### Source excerpt A recent study by the analyst firm Omdia, commissioned by Object First, reveals that enterprise ransomware recovery rates are declining despite growing awareness of modern data protection strategies. According to the research, 83 percent of surveyed organizations experienced a successful ransomware attack in the past 24 months, up from 66 percent in 2024. Among those The post Omdia Study Highlights Declining Ransomware Recovery Rates and the Immutability Gap in Backup Storage appeared first on StorageReview.com. ## 【etcd】运维与升级：member change、backup/restore 与 3.5-\>3.6/3.7 门 DevFeed: [【etcd】运维与升级：member change、backup/restore 与 3.5-\>3.6/3.7 门]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [upgrade](), [Kubernetes](), [migration]() Tags: [backup](), [distributed](), [etcd](), [kubernetes](), [learner](), [member-change](), [migration](), [operations](), [raft](), [recovery](), [restore](), [snapshot](), [upgrade](), [v3](), [v3-5](), [v3-5-33](), [v3-6](), [v3-7]() ### AI overview A Chinese-language operational guide to etcd v3.5.33 covering member replacement and learner promotion, live snapshot backup and restore, Kubernetes control-plane recovery, patch upgrades, and documented upgrade gates from etcd 3.5 to 3.6 and 3.7. ### Source excerpt member add/remove/replace 与 learner promote 检查单；snapshot backup/restore 及 K8s 语境 revision bump；3.5.33 补丁线与 3.6/3.7 官方升级门禁项，不超前写未钉 tag 能力。 ## 【etcd】选型收束与开放问题：排除树与系列边界关闭 DevFeed: [【etcd】选型收束与开放问题：排除树与系列边界关闭]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes]() Tags: [apiserver](), [backup](), [compaction](), [distributed](), [etcd](), [exclusion-tree](), [foundationdb](), [guide](), [k8s](), [kubernetes](), [lease](), [open-questions](), [raft](), [selection](), [tikv](), [v3](), [v3-5-33](), [zookeeper]() ### AI overview This concluding article presents a mechanism-based decision tree for deciding when to retain etcd and when to migrate to TiKV or FoundationDB. It defines etcd's fit for small data sets with Watch and Lease dependencies, identifies disqualifying conditions such as quota pressure, sharding needs, cross-key transactions, Watch backpressure, and insufficient operational capacity, and clarifies the boundaries between related article series. ### Source excerpt 用机制排除树收束何时该留 etcd、何时迁 TiKV/FDB/ZK；回收 distributed/39、tikv-htap/18、foundationdb/18 的 etcd 叶；列出 Watch 背压、Lease+fencing、quota 迁移等开放问题；以 ADR 语言关闭续作边界。 ## What else runs on your Postgres server, and how do we stop it from taking the database down? DevFeed: [What else runs on your Postgres server, and how do we stop it from taking the database down?]() Original publisher: [Read original article]() Author: Kaushik Iska Published: 2026-08-21T14:11:30Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [Database](), [Availability](), [Processes](), [Server](), [Monitoring](), [Go Language](), [systemd]() Tags: [availability](), [backup](), [cpu](), [database](), [go](), [logging](), [memory](), [metrics](), [monitoring](), [postgres](), [process](), [processes](), [prometheus](), [server](), [systemd]() ### AI overview ClickHouse Managed Postgres isolates supporting services with runtime budgets and cgroup v2 limits so leaks, CPU saturation, and memory pressure do not compromise database availability. ### Source excerpt ClickHouse Managed Postgres uses runtime budgets, cgroup limits, and disk-full session exemptions to keep supporting services from compromising database availability. ## Incremental backup on AWS Glacier with rustic DevFeed: [Incremental backup on AWS Glacier with rustic]() Original publisher: [Read original article]() Published: 2026-08-19T21:04:01Z Content type: tutorial Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [backups](), [restic](), [Amazon Web Services](), [Amazon S3](), [Rust](), [Open Source](), [Feathers]() Tags: [aws](), [aws-glacier-deep-archive](), [backblaze-b2](), [backup](), [backups](), [client](), [config](), [cost](), [data](), [encryption](), [encryption-at-rest](), [incremental](), [lifecycle](), [open-source](), [password](), [restic](), [restore](), [rust](), [rustic](), [s3](), [snapshots]() ### AI overview A practical guide to using rustic, a Rust implementation compatible with restic, for incremental backups with AWS Glacier cold storage. It explains keeping backup data in cold storage while maintaining metadata in S3 Standard or Backblaze B2 so snapshots, incremental backups, and targeted restores remain possible. ### Source excerpt I have been a heavy restic user for several years. In Jan of this year, I tried making restic work with AWS Glacier deep archive but it did not work out. AWS Glacier Deep Archive, for those who may not know, is one of the cheapest storage options, with costs as low as $1/TB, but with very expensive retrieval due to high egress charges from AWS, in addition to retrieval fees, API charges, etc. It can act as a backup of last resort, kind of like insurance if everything else fails, since it costs roughly 1/7th of what Backblaze B2 charges for the same data ($6.95/TB/month). Restic by design is not compatible with Glacier because it stores a mix of data blobs and tree blobs inside /data. Thus, as AWS lifecycle rules move data from S3 Standard to Glacier, basic repo operations start failing. They do have some experimental support as per FAQ, but it did not work out for me when I tried in Jan. A few days back, I came across an open-source project named rustic -- it's a restic implementation in Rust and supports cold storage. The rustic client is compatible with a traditional restic repo. Rustic and cold storage Rustic supports AWS Glacier as well as OVH cold storage. The way it works is: they keep all data in cold storage and a copy of the metadata in hot storage. This additional copy of metadata in hot storage allows operations like incremental backups, viewing snapshots, and requesting restores where only the specific data blobs needed for the restore are pulled from Glacier. This additional hot storage can sit on S3 standard or even Backblaze B2 (which I prefer due to zero API cost). Demo 1) Create repo Let's create two buckets - one in S3 (to store data in Glacier) and one on Backblaze B2 to hold an additional copy of metadata. > rclone mkdir s3:rustic-demo-cold > rclone mkdir b2:rustic-demo-hot 2) Create rustic config profile This file will define the cold and hot repo locations, along with the password file location, restoration command syntax, etc. [repository] repo ## 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 ## Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO DevFeed: [Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-11T05:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Disaster Recovery](), [Kubernetes](), [MinIO](), [nginx](), [TLS (Transport Layer Security)](), [Amazon S3](), [Availability]() Tags: [availability](), [backup](), [data-recovery](), [disaster-recovery](), [failover](), [high-availability](), [how-to](), [kubernetes](), [minio](), [nginx](), [postgresql](), [recovery](), [s3](), [tls](), [tutorials]() ### AI overview A tutorial on using Crunchy PostgreSQL Operator on Kubernetes to implement multi-region PostgreSQL disaster recovery and failback. It covers secure MinIO-backed WAL storage through an NGINX TLS reverse proxy, regional failover, and reversing roles without timeline conflicts or archive poisoning. ### Source excerpt This blog talks about multiregion PostgreSQL disaster recovery using Crunchy PGO. It has some detailed steps to understand better. The post Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO appeared first on CYBERTEC PostgreSQL | Services & Support. ## Massively parallel Postgres backups DevFeed: [Massively parallel Postgres backups]() Original publisher: [Read original article]() Author: Ben Dicken Published: 2026-07-31T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [neki](), [cloud-infrastructure](), [Amazon S3](), [Orchestration](), [Server](), [MySQL](), [Terraform]() Tags: [amazon-s3](), [backup](), [building](), [databases](), [engineering](), [infrastructure](), [mysql](), [neki](), [orchestration](), [postgres](), [scale](), [servers](), [storage]() ### AI overview PlanetScale describes how Neki, its sharded Postgres system, performs consistent encrypted backups at petabyte scale. The approach combines filesystem backups, archived WAL replay, object storage such as Amazon S3, and massive parallelism to back up databases without affecting production queries. ### Source excerpt PlanetScale backs up petabyte-scale sharded Postgres databases in hours using parallel infrastructure, object storage, and WAL replay. ## Postgres backups under the hood DevFeed: [Postgres backups under the hood]() Original publisher: [Read original article]() Author: Josh Brown Published: 2026-07-24T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [data](), [SQL](), [IO](), [Filesystems]() Tags: [backup](), [data](), [database](), [engineering](), [how-to](), [io](), [postgres](), [recovery](), [sql]() ### AI overview This article explains how Postgres backups work, focusing on logical backups and their tradeoffs. It describes consistent snapshots, SQL or custom output formats, resource costs at large data volumes, the lack of point-in-time recovery, and the use of MVCC for online backups. ### Source excerpt With backups being such a vital part of keeping your data safe, how do they actually work? ## Adding a backup Internet WAN on my OPNsense Router DevFeed: [Adding a backup Internet WAN on my OPNsense Router]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-07-23T21:00:00Z Content type: tutorial Language: en Sources: [Jeff Geerling]() Topics: [Firewall](), [networking](), [configuration](), [5G](), [Software]() Tags: [5g](), [backup](), [ethernet](), [firewall](), [internet](), [networking](), [opnsense](), [outage](), [router]() ### AI overview A practical guide to adding a portable 5G gateway as a backup WAN on an OPNsense router. It covers assigning a second Ethernet interface, configuring DHCP and outbound NAT, and manually changing gateway priorities to fail over between connections. ### Source excerpt AKA "Spectrum has gone down two weeks in a row and I'm sick of it". I've been borrowing a portable 5G gateway from my Dad for a few weeks, for testing... and two weeks in a row, I've used it as a backup Internet option, since my Spectrum Business cable Internet has gone down. And yes, I'd get AT&T Fiber if I had the option, sadly they don't yet provide service at my studio. So I'm stuck with only one high speed wired provider. I may add on my own 5G backup Internet connection in the future, but we're getting off track. ## How a laptop failure highlights the importance of the 3-2-1 backup rule DevFeed: [How a laptop failure highlights the importance of the 3-2-1 backup rule]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2026-07-06T21:18:28Z Content type: opinion Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [data](), [Cloud](), [USB]() Tags: [backup](), [cloud](), [data](), [personal](), [usb]() ### AI overview After water damaged the author's laptop and the repair shop could not recover it, the author reflects on lost files and recommends automating backups using the 3-2-1 rule: three copies of data on two storage types, with one copy stored remotely. ### Source excerpt Last week I spilled water on my laptop. This is the story of what I lost, what I learned, and the 3-2-1 backup system I wish I'd had a week earlier. ## Mastering Linux Administration: 20 Powerful Commands to Know DevFeed: [Mastering Linux Administration: 20 Powerful Commands to Know]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-07-06T03:56:38Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Command-line interface](), [Monitoring](), [Filesystems](), [IO](), [cpu]() Tags: [administration](), [automated](), [backup](), [blog](), [command-line](), [commands](), [cpu](), [examples](), [files](), [https-linuxblog-io-tag-commands](), [io](), [linux](), [memory](), [monitoring](), [ncurses](), [sysadmins]() ### AI overview A tutorial introducing 20 Linux commands for system administrators, with examples and explanations of their uses. The supplied text specifically discusses vmstat for monitoring system and memory statistics, inotifywait for tracking filesystem events, and ncdu for analyzing disk usage. ### Source excerpt Linux is a powerful and versatile operating system that can be used for a wide range of purposes. For many system administrators, the command line interface is the primary way to interact with the system. Continue reading... ## Resty Desktop, a GUI for the Restic Backup Application DevFeed: [Resty Desktop, a GUI for the Restic Backup Application]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-06-26T12:00:00Z Content type: article Language: en Sources: [Nic Raboy]() Topics: [GUI](), [Tauri](), [App](), [cross-platform](), [Open Source]() Tags: [applications](), [backup](), [cross-platform](), [desktop](), [gui](), [open-source](), [restic](), [rust](), [tauri](), [typescript]() ### AI overview The article introduces Resty Desktop, an open-source GUI wrapper for the Restic command-line backup application. It describes repository management, backup plans, snapshot browsing and restoration, file-level restoration, snapshot comparison, and scheduled backups. Resty Desktop relies on Restic for its core backup and restore operations, while caching repository data locally and encrypting repository passwords at rest. ### Source excerpt There are quite a few backup applications in circulation, each with their own set of benefits. I have personally become very fond of the Restic backup application because of it being quick, reliable, ... The post Resty Desktop, a GUI for the Restic Backup Application appeared first on The Polyglot Developer. [Next page]()