# backups Published articles for backups. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Iran Strikes On Amazon Data Centers Caused Permanent Loss of Customer Data DevFeed: [Iran Strikes On Amazon Data Centers Caused Permanent Loss of Customer Data]() Original publisher: [Read original article]() Author: EditorDavid Published: 2026-09-17T20:34:00Z Content type: news Language: en Sources: [Slashdot]() Topics: [Amazon Web Services](), [data centers](), [Cloud](), [Availability](), [backups](), [data]() Tags: [amazon](), [amazon-web-services](), [availability](), [backups](), [cloud](), [data-centers](), [iran](), [strikes]() ### AI overview Amazon Web Services acknowledged that some customer data and resources hosted in war-damaged data centers in Bahrain and the United Arab Emirates were permanently lost or remain inaccessible. The damage affected multiple availability zones, exceeding the resilience designed for the regional and multi-AZ services. ### Source excerpt Ars Technica reports: Half a year after Iranian drone strikes knocked out multiple Amazon data centers, the US tech company has acknowledged the permanent loss of some customer data that was hosted in Bahrain and the United Arab Emirates. Amazon Web Services was "unable to restore access to the resources and data" hosted in some of the war-damaged data centers, according to an AWS dashboard update posted on September 15. The development was first reported by Reuters and suggests that the Iranian strikes inflicted catastrophic damage on the data centers. Customer data was irretrievably lost in one of three AWS availability zones in the United Arab Emirates region, specifically the mec1-az2 availability zone. Each availability zone is serviced by one or more Amazon data centers. The company is still working on "recovering regional resources" and restoring resources hosted in the other two availability zones in the United Arab Emirates... But the destruction was apparently even more widespread for the data centers in the Bahrain region, because Amazon said it was unable to restore access to resources and data across all three availability zones there. "The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand," the AWS update said. The company had already suspended customer billing in the affected AWS regions in Bahrain and the United Arab Emirates and has spent the past six months attempting to restore normal operations... [When the war began] AWS immediately urged customers to migrate resources to other cloud regions and use remote backups to restore any "inaccessible resources." The cloud service also reportedly issued $150 million in customer credits following the initial Iranian strikes in March. Read more of this story at Slashdot. ## Introducing TIN: full-text search for Postgres DevFeed: [Introducing TIN: full-text search for Postgres]() Original publisher: [Read original article]() Author: Patrick Reynolds Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [benchmarking]() Tags: [backups](), [benchmark](), [benchmarks](), [bm25](), [engineering](), [full-text-search](), [index](), [performance](), [postgres](), [reddit](), [replication](), [search](), [text](), [wikipedia]() ### AI overview PlanetScale announces TIN, a full-text search extension for Postgres and Neki databases. The article describes supported query and matching features, transaction and update behavior, and benchmark workloads and corpora used to assess performance. ### Source excerpt TIN is a fast, full-featured, full-text search index for Postgres ## Kubernetes 1.36 restores a lost guarantee for database backups DevFeed: [Kubernetes 1.36 restores a lost guarantee for database backups]() Original publisher: [Read original article]() Author: Shubham Pampattiwar Published: 2026-09-15T13:00:00Z Content type: news Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack](), [The New Stack]() Topics: [Kubernetes](), [PostgreSQL](), [Databases]() Tags: [backups](), [cncf](), [consistency](), [database](), [databases](), [kubernetes](), [post-contributed](), [postgresql](), [snapshots](), [sponsor-cncf](), [sponsored-post-contributed](), [stateful](), [storage]() ### AI overview The article explains how Kubernetes 1.36 restores coordinated snapshots for applications whose state spans multiple volumes, addressing inconsistent database backups caused by taking individual PersistentVolumeClaim snapshots at different times. ### Source excerpt It's 2 a.m., and you're restoring a PostgreSQL cluster from last night's backup. Its data directory lives on one PersistentVolumeClaim The post Kubernetes 1.36 restores a lost guarantee for database backups appeared first on The New Stack. ## If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things DevFeed: [If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-11T12:53:06Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Proxmox](), [backups](), [Docker](), [Docker Compose]() Tags: [backups](), [docker](), [docker-compose](), [home-lab](), [home-server](), [proxmox](), [virtualization]() ### AI overview A practical two-hour home lab maintenance plan covering selective updates, backup verification, storage health, reboot checks, and focused remediation. It discusses Proxmox hosts, Docker images, Docker Compose stacks, and optional automatic updates. ### Source excerpt Let's face it, our time in the home lab among other things we have going on in our lives and families may be hard to come by and there are... The post If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things appeared first on Virtualization Howto. ## Stefan Fercot Joins Percona to Contribute to pgBackRest DevFeed: [Stefan Fercot Joins Percona to Contribute to pgBackRest]() Original publisher: [Read original article]() Author: Percona Team Published: 2026-09-09T15:55:38Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [Percona](), [backups]() Tags: [backups](), [percona](), [percona-live](), [postgres](), [postgresql]() ### AI overview Stefan Fercot joined Percona's Postgres engineering team to increase its contributions to pgBackRest, a backup and restore tool. The article describes his prior advocacy for the project and Percona's sponsorship of its development. ### Source excerpt If you have spent any time in the Postgres community, you already know the name pgstef. Stefan Fercot has spent years as one of the most visible advocates for pgBackRest, a familiar face at European Postgres conferences, and countless hallway conversations about backups, high availability, and everything in between. Now he is doing that work ... Continued The post Meet pgstef: Why Stefan Fercot Joined Percona, and Why You Should Find Him at Percona Live Amsterdam appeared first on Percona. ## 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 ## Maintenance release: Godot 4.7.2 DevFeed: [Maintenance release: Godot 4.7.2]() Original publisher: [Read original article]() Author: Thaddeus Crews Published: 2026-08-18T12:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [releases](), [Windows](), [Wayland]() Tags: [backups](), [changelog](), [crash](), [git](), [maintenance](), [release](), [releases](), [wayland](), [windows]() ### AI overview Godot 4.7.2 is the second 4.7 maintenance release. It includes 57 fixes across areas such as the editor, input, networking, rendering, navigation, multiplayer, Wayland, and Windows. ### Source excerpt The second 4.7 maintenance release has arrived! ## rclone: sincroniza y cifra tus datos en la nube DevFeed: [rclone: sincroniza y cifra tus datos en la nube]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-05T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Linux](), [backups](), [Amazon S3]() Tags: [backups](), [linux](), [s3]() ### AI overview A practical Spanish-language guide to using rclone from Linux to configure cloud-storage remotes, protect credentials, synchronize and verify files, and automate encrypted backups. It warns that synchronization can delete destination files and recommends testing with a dry run first. ### Source excerpt Guía práctica de rclone: instala, configura remotos, sincroniza con cifrado y automatiza copias hacia almacenamiento en la nube desde Linux. ## Vaultwarden: gestor de contraseñas autoalojado DevFeed: [Vaultwarden: gestor de contraseñas autoalojado]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker](), [Docker Compose](), [TLS (Transport Layer Security)](), [nginx](), [proxy](), [backups]() Tags: [backups](), [bitwarden](), [compose](), [docker](), [docker-compose](), [hardening](), [homelab](), [https](), [nginx](), [proxy](), [tls](), [vaultwarden]() ### AI overview A Spanish-language tutorial explains how to self-host Vaultwarden, an unofficial Rust server compatible with Bitwarden clients. It covers Docker Compose deployment, HTTPS behind an Nginx reverse proxy, admin-token hardening, and backups, while noting the trade-off between community support and the official Bitwarden server. ### Source excerpt Instala Vaultwarden con Docker: servidor ligero compatible con los clientes de Bitwarden, con HTTPS, hardening del admin token y backups. ## RAID por software con mdadm: guía práctica DevFeed: [RAID por software con mdadm: guía práctica]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-07-27T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Mdadm](), [RAID](), [Linux](), [backups](), [Homelab]() Tags: [backups](), [homelab](), [linux](), [mdadm](), [raid]() ### AI overview A practical Spanish-language guide to using mdadm on Linux to create and manage software RAID 0, 1, 5, and 10 arrays. It compares capacity, performance, and fault tolerance, explains monitoring with email alerts, and covers recovery after a disk failure. ### Source excerpt Crea arrays RAID 0, 1, 5 y 10 con mdadm en Linux, monitoriza su estado con alertas por email y recupera un array tras el fallo de un disco. ## Managing Databases on Kubernetes Requires Platform Engineering and Automation DevFeed: [Managing Databases on Kubernetes Requires Platform Engineering and Automation]() 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: [Kubernetes](), [Databases](), [Platform Engineering](), [internal developer platform](), [Provisioning](), [opensearch](), [Redis]() Tags: [anynines](), [automation](), [backups](), [databases](), [devops](), [internal-developer-platform](), [kubernetes](), [monitoring](), [opensearch](), [platform-engineering](), [post](), [provisioning](), [redis](), [sponsor-anynines](), [sponsored-post]() ### AI overview The article argues that application teams should not be expected to manage the full operational burden of databases and data services on Kubernetes. It recommends internal developer platforms and Kubernetes-native automation so developers can request services while centralized systems handle provisioning, backups, patching, monitoring, recovery, and governance. ### 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. ## Dev snapshot: Godot 4.8 dev 1 DevFeed: [Dev snapshot: Godot 4.8 dev 1]() Original publisher: [Read original article]() Author: Thaddeus Crews Published: 2026-07-06T12:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [Development]() Tags: [backups](), [new-features](), [pre-release](), [release](), [testing](), [version-control]() ### AI overview This release article introduces the first Godot 4.8 development snapshot, highlighting new features and functionality while warning that pre-release use carries a risk of data loss or corruption. It also mentions the Web, XR, and Android editors and a new default docked game view in the editor. ### Source excerpt The cycle begins anew ## Spotlight on SIG Storage DevFeed: [Spotlight on SIG Storage]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-06-15T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [systems](), [data]() Tags: [backups](), [containers](), [distributed-system](), [kubernetes](), [storage](), [volumes]() ### AI overview An interview with Xing Yang, co-chair of Kubernetes SIG Storage, covering the group's role in persistent data and volume management, Kubernetes CSI maintenance, recent storage features, and data protection work such as Volume Group Snapshot and Changed Block Tracking. ### Source excerpt In our ongoing SIG Spotlight series, we shine a light on the groups that keep the Kubernetes project moving forward. This time, we catch up with SIG Storage , the group responsible for persistent data, volume management, and the interfaces that connect Kubernetes workloads to the storage systems beneath them. We spoke with Xing Yang , Co-Chair of SIG Storage and Software Engineer at VMware by Broadcom, about the SIG's history, the features shipping in recent Kubernetes releases, and where storage in Kubernetes is headed as AI workloads become the norm. Introductions Could you introduce yourself and share your role(s) within SIG Storage? My name is Xing Yang , a software engineer at VMware by Broadcom. I'm a co-chair in SIG Storage, alongside another co-chair Saad Ali from Google. There are also two Tech Leads in SIG Storage: Michelle Au from Google and Jan Šafránek from Red Hat. What first drew you to storage in Kubernetes, and how did you start contributing? I have always been working in the storage domain, so SIG Storage was a natural place for me to get started when I began to learn Kubernetes. I started attending SIG Storage meetings , trying to figure out what I could do to help. This was before the first Container Storage Interface (CSI) release -- lots of things were still evolving. It was a very exciting time. What subprojects or areas do you actively maintain or review today? I'm a maintainer in Kubernetes CSI. There are multiple CSI sidecars -- such as csi-provisioner, csi-attacher, csi-resizer, and csi-snapshotter -- that we need to release following every Kubernetes release. I'm also a co-chair for a Data Protection Working Group co-sponsored by SIG Storage and SIG Apps . Several features have come out of that WG aimed at filling gaps in data protection support within Kubernetes. One is Volume Group Snapshot , which provides crash-consistent group snapshots for multiple volumes used by an application. Changed Block Tracking (CBT) is another critical feature ## CockroachDB Bring Your Own Cloud (BYOC) Is Now Available in Public Preview DevFeed: [CockroachDB Bring Your Own Cloud (BYOC) Is Now Available in Public Preview]() Original publisher: [Read original article]() Author: David Bressler,Devarshi Shah Published: 2026-05-11T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Cockroach Labs](), [Cloud](), [Amazon Web Services](), [AWS IAM](), [Security](), [Azure](), [backups](), [observability]() Tags: [audit-trail](), [aws](), [azure](), [backups](), [cloud](), [cockroach-labs](), [cockroachdb](), [iam](), [observability](), [preview](), [provisioning](), [security]() ### AI overview CockroachDB announces the public preview of Bring Your Own Cloud (BYOC) for CockroachDB Cloud Advanced. BYOC runs clusters in a customer's AWS, GCP, or Azure account while Cockroach Labs manages provisioning, upgrades, backups, and day-to-day database operations. ### Source excerpt For a certain set of customers, the conversation about CockroachDB Cloud always hits the same wall. ## How CockroachDB v26.1 Uses Elastic Admission Control and Go Scheduler Changes for Background Work DevFeed: [How CockroachDB v26.1 Uses Elastic Admission Control and Go Scheduler Changes for Background Work]() Original publisher: [Read original article]() Author: David Taylor Published: 2026-04-14T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Go Language](), [Concurrent Programming](), [Latency](), [cpu]() Tags: [background-work](), [backups](), [cockroachdb](), [elastic](), [latency](), [processes](), [statistics](), [work]() ### AI overview This article explains how CockroachDB v26.1 uses elastic admission control and a change to the Go runtime scheduler to let background work use spare CPU capacity while limiting its impact on query latency. ### Source excerpt CockroachDB runs background work -- backups, schema changes, statistics collection, changefeeds -- in the same processes that serve user queries. Traditionally, this creates a tension... ## From Single Instance to Split-Brain: A Database Scaling Journey DevFeed: [From Single Instance to Split-Brain: A Database Scaling Journey]() Original publisher: [Read original article]() Author: Alok Mishra Published: 2026-03-31T18:40:52Z Content type: tutorial Language: en Sources: [Walmart Global Tech]() Topics: [Databases](), [Replication](), [MySQL](), [PostgreSQL](), [Self-hosted](), [backups](), [Cloud](), [Monitoring](), [Amazon EC2](), [Kubernetes]() Tags: [architecture](), [backups](), [bare-metal](), [cloud](), [cloud-services](), [cloud-sql](), [cockroachdb](), [database](), [ec2](), [failover](), [google](), [google-cloud](), [google-cloud-sql](), [kubernetes](), [monitoring](), [mysql](), [postgresql](), [production](), [read-replica](), [recovery](), [software-architecture](), [software-development](), [software-engineering]() ### AI overview This article explains how database scaling commonly uses a single-leader architecture with asynchronous read replicas. It discusses replication lag, stale reads, split-brain risks, read/write traffic separation, and the operational responsibilities of self-managed versus fully managed database services. ### Source excerpt I used to think adding a 'Read Replica' was a magic button for scaling applications. I was wrong. While splitting read and write traffic is a standard system design pattern, implementing it introduces a world of pain - from stale reads to the dreaded Split-Brain problem. Here is how database replication actually works, and how to survive the transition. When people talk about "scaling databases" or "adding read replicas", they are almost always thinking about one specific architecture: Single-leader (Primary-Replica) architecture with asynchronous replication This is the architecture used by: MySQL + replicas PostgreSQL + streaming replication Google Cloud SQL PlanetScale, Neon, Supabase, etc. There is exactly one node that accepts writes -> called the Primary (or Leader/Master). All other nodes are Read Replicas -> they apply changes from the primary as fast as they can, but always with some delay (replication lag). This is the default and dominant model in 99% of applications today. Alternative architectures exist (multi-primary, leaderless, CRDTs, etc.), but they are rare and come with their own very different trade-offs. The second axis that actually matters in practice is: Who manages the replicas and failover for you?1. Self-hosted / Self-managed You run MySQL or PostgreSQL yourself (on EC2, Kubernetes, bare metal, etc.). You are 100% responsible for: Setting up replication Promoting a new primary when the old one dies Routing traffic correctly Handling replication lag Monitoring, backups, point-in-time recovery, etc. 2. Fully-managed cloud services RDS, Aurora, PlanetScale, Neon, Supabase, CockroachDB, Spanner, YugabyteDB, etc. The provider gives you a single connection string (or two: one for writes, one for reads) and magically keeps it pointing to healthy nodes, handles failover in seconds, and often hides (or eliminates) replication lag headaches. This second axis is the one that determines how much pain you will actually feel in production. Now, suppose yo ## ccloud CLI: The "Agent-Ready" Database CLI DevFeed: [ccloud CLI: The "Agent-Ready" Database CLI]() Original publisher: [Read original article]() Author: Biplav Saraf Published: 2026-03-25T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Database](), [AI Agent](), [Command-line interface](), [alert triage](), [Automation](), [Security](), [Slack](), [backups](), [Replication]() Tags: [agent](), [agents](), [ai](), [ai-agents](), [alert-triage](), [automation](), [backups](), [cli](), [cockroachdb](), [database](), [replication](), [security](), [slack]() ### AI overview This article describes how CockroachDB's ccloud CLI enables AI agents to automate database operations, including alert triage, cluster health checks, maintenance-window management, backup verification, audit-log review, and replication-health checks. It emphasizes permission-based guardrails and auditable CLI actions. ### Source excerpt Production database operations for AI agents, with enterprise security built in. ## Waiting for PostgreSQL 19 - Add non-text output formats to pg\_dumpall DevFeed: [Waiting for PostgreSQL 19 - Add non-text output formats to pg\_dumpall]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-17T10:29:38Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [backups](), [Databases]() Tags: [backup](), [backups](), [compression](), [maintenance](), [pg-dump](), [pg-dumpall](), [pg19](), [postgresql](), [uncategorized](), [waiting]() ### AI overview The article examines a PostgreSQL 19 patch that adds custom, directory, and tar output formats to pg_dumpall. It describes the resulting files and explains how the formats can support more selective restoration and simpler backups. ### Source excerpt On 26th of February 2026, Andrew Dunstan committed patch: Add non-text output formats to pg_dumpall pg_dumpall can now produce output in custom, directory, or tar formats in addition to plain text SQL scripts. When using non-text formats, pg_dumpall creates a directory containing: - toc.glo: global data (roles and tablespaces) in custom format - map.dat: ... Continue reading "Waiting for PostgreSQL 19 - Add non-text output formats to pg_dumpall" ## Comandos esenciales de LVM: guía rápida DevFeed: [Comandos esenciales de LVM: guía rápida]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-20T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [LVM](), [Linux](), [backups](), [Mdadm](), [RAID](), [rsync](), [Homelab]() Tags: [backups](), [homelab](), [libre](), [linux](), [lvm](), [mdadm](), [raid](), [rsync]() ### AI overview A Spanish-language cheat sheet covering essential LVM commands for managing physical volumes, volume groups, and logical volumes on Linux. It explains common workflows such as extending volumes and filesystems, creating and reducing volumes, migrating data, and creating snapshots for backups. ### Source excerpt Cheatsheet con los comandos más usados de LVM (Logical Volume Manager) para la gestión de volúmenes lógicos en Linux. ## Why Squarespace migrated global data workloads from PostgreSQL to CockroachDB DevFeed: [Why Squarespace migrated global data workloads from PostgreSQL to CockroachDB]() Original publisher: [Read original article]() Author: Becca Weng Published: 2026-02-18T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [PostgreSQL](), [Scalability](), [Replication](), [Resilience]() Tags: [backups](), [cockroachdb](), [distributed](), [postgresql](), [replication](), [resilience](), [scalability]() ### AI overview The article describes how Squarespace migrated global data workloads from PostgreSQL to CockroachDB. It presents PostgreSQL's single-primary model as a limiting factor for horizontal and multi-region scaling, resilience, upgrade operations, and observability, and describes CockroachDB's replication, automated failover, and horizontal scaling capabilities. ### Source excerpt Every year at RoachFest, we hear directly from the teams running some of the most demanding data workloads in production. RoachFest 2025 was no different--except this year, a clear theme emerged across customer sessions: primary data and metadata are often mission-critical. ## 300-Node Clusters Now Supported in CockroachDB DevFeed: [300-Node Clusters Now Supported in CockroachDB]() Original publisher: [Read original article]() Author: David Bressler,Dipti Joshi Published: 2026-02-12T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Cockroach Labs](), [data-platforms](), [Benchmark](), [Cloud](), [Resilience]() Tags: [backups](), [benchmark](), [cloud](), [cockroach-labs](), [cockroachdb](), [data-platforms](), [distributed](), [performance](), [resilience](), [sql]() ### AI overview Cockroach Labs announces support for 300-node clusters in CockroachDB v25.4.4 and later, with up to 2.2M tpmC and 1.2PB of data. The article also describes testing involving operational stress and reports performance results from that test cycle. ### Source excerpt As AI-driven and agentic applications push data platforms into new territory, data architects are increasingly forced to choose between correctness, simplicity, and scale. Today, we're removing that tradeoff -- announcing support for 300-node clusters with 2.2M tpmC and 1.2PB of data in CockroachDB v25.4.4 and beyond. On CockroachDB Cloud, we're announcing support for 64 vCPU per node. Testing to this scale is important to ensure that we're testing ahead of customer deployments, and this milestone does just that. We believe these tests represent the largest node-scale testing completed by any distributed SQL vendor. And we're just getting started. ## Backups incrementales con rsync en Linux DevFeed: [Backups incrementales con rsync en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-16T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [backups](), [rsync](), [Linux](), [Script](), [ssh](), [systemd]() Tags: [backup](), [backups](), [filesystem](), [incremental](), [linux](), [nas](), [rsync](), [ssh](), [systemd]() ### AI overview A tutorial on implementing incremental backups with rsync and hardlinks on Linux servers. It explains how unchanged files are hardlinked to save space, warns that hardlinks are not independent copies, discusses filesystem compatibility and destructive synchronization risks, and covers SSH transfers, exclusions, systemd timers, and integrity checks. ### Source excerpt Cómo implementar una estrategia de backups incrementales usando rsync y hardlinks para ahorrar espacio y tiempo en tus servidores. ## Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide DevFeed: [Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide]() Original publisher: [Read original article]() Author: Amine El Kouhen, Ph.D. Published: 2026-01-14T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Software as a service](), [Databases](), [Authentication](), [Authorization](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [consistency](), [Open Source](), [backups](), [patches](), [Entra ID]() Tags: [access-control](), [authentication](), [authorization](), [availability](), [backups](), [cockroachdb](), [consistency](), [databases](), [distributed](), [guide](), [high-availability](), [iam](), [identity-and-access-management](), [keycloak](), [oidc](), [openid-connect](), [patches](), [saas](), [saml](), [security]() ### AI overview This guide explains how Phase Two's managed Keycloak platform can be deployed with CockroachDB to support authentication, authorization, enterprise SSO, and multi-tenant SaaS applications. It describes Keycloak's identity-management capabilities and CockroachDB's globally distributed SQL database, transactional consistency, and tenant isolation. ### Source excerpt Today's SaaS products face twin demands: the digital identity layer must be seamless and enterprise-grade, and the data layer must scale globally while remaining reliably consistent. ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. [Next page]()