# backups A backup is a copy of files or data maintained so it can be restored after loss. 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. ## 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. ## 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 ## 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. ## 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. ## 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. ## Breaking the Loop: How we migrated our backup catalog for 250+ MySQL clusters to AWS DevFeed: [Breaking the Loop: How we migrated our backup catalog for 250+ MySQL clusters to AWS]() Original publisher: [Read original article]() Author: Ioannis Androulidakis Published: 2026-02-19T14:19:52Z Content type: article Language: en Sources: [Booking.com Development - Medium]() Topics: [migration](), [Amazon RDS](), [MySQL](), [Amazon Web Services](), [backups](), [Cloud](), [on-prem]() Tags: [amazon-rds](), [aws](), [backup](), [cloud](), [cloud-migration](), [data-backup](), [database](), [databases](), [migration](), [mysql](), [on-prem](), [relational-databases](), [reliability-engineering]() ### AI overview Booking.com's Database Engineering team describes migrating the backup catalog orchestrator's backend for more than 250 production MySQL clusters from a self-managed on-premises MySQL database to managed Amazon RDS for MySQL in AWS. The article discusses the migration's challenges, implemented solutions, and lessons learned. ### Source excerpt This post was originally published internally on May 9, 2025 and has been reworked for a public audience. Authors: Ioannis Androulidakis, Mohammed Gaafar Intro The Database Engineering team at Booking.com is constantly looking for ways to improve database reliability and support scaling our business. In 2025 we completed a major milestone in our effort to modernize our infrastructure: we seamlessly migrated the backend of the orchestrator that schedules and manages the daily backups of 250+ production MySQL clusters. More specifically, we moved from a self-managed MySQL database running on premises to a managed Amazon RDS MySQL database running in the cloud. This blog post delves into the challenges we faced, the solutions we implemented, and some key lessons we learned along the way. We are moving to the cloud (gradually) Cloud adoption is a journey, not a switch. Over the past few years the adoption of AWS solutions at Booking.com has been growing rapidly across different business units, allowing teams to be more autonomous, run their databases in the cloud and solve known issues with their old on-premise setup. Like customer teams, we are running our own databases to power the core services that we offer and manage databases efficiently at scale. To name a few: automatic failover of writable primaries, auto-scaling of read-only replicas, service discovery, capacity planning, online schema changes, user access management, volume backups, etc. Traditionally, the Database Engineering team has been running databases on-premises. In the emerging era of cloud databases, we wanted to compare our in-house offerings with existing cloud databases and bridge the gap between the two. Knowing that we lacked deep, hands-on experience with the operational realities of running critical infrastructure on AWS, we saw this as a unique opportunity to learn more about cloud databases while also improving the reliability of our systems. Long story short, we decided to prioritize the m ## 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. ## 20 years of Getting Things Done DevFeed: [20 years of Getting Things Done]() Original publisher: [Read original article]() Author: Tom Published: 2025-11-27T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [systems](), [DevOps](), [Monitoring](), [backups](), [health checks](), [Disaster Recovery]() Tags: [2](), [advice](), [backup](), [best-practices](), [devops](), [getting-things-done](), [gtd](), [leadership](), [learnings](), [linux](), [monitoring](), [productivity](), [recovery](), [time-management](), [workshop]() ### AI overview A reflection on 20 years of using Getting Things Done, including how external systems shaped the author's work as a system administrator and DevOps engineer. It describes replacing manual backup checks with failure notifications and introducing monitoring and health checks to move operations from reactive to proactive. ### Source excerpt Reflections and practical tips from 20 years using Getting Things Done, plus a short workshop plan for leaders who want actionable routines. ## Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17 DevFeed: [Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17]() Original publisher: [Read original article]() Author: Kavya Premkumar Published: 2025-05-29T15:30:32Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [upgrade](), [Database](), [maintenance](), [Security](), [Availability](), [backups](), [Vulnerabilities](), [Monitoring](), [releases]() Tags: [availability](), [backups](), [bug-fixes](), [cli](), [compatibility](), [database](), [engineering](), [features](), [guide](), [heroku](), [heroku-postgres](), [performance](), [platform-updates](), [postgres](), [provisioning](), [security](), [upgrade](), [vulnerabilities]() ### AI overview This guide explains why Heroku Postgres databases should be upgraded and introduces the simplified process for moving to Postgres 17 on Heroku. It covers security updates, bug fixes, performance improvements, new features, compatibility, and Heroku's version-support lifecycle. ### Source excerpt If you've ever deployed an app on Heroku, chances are you've used Heroku Postgres -- our fully managed, reliable, and scalable Postgres database service. It's the backbone for millions of applications, from weekend side projects to enterprise-grade systems running in production. But Postgres, like all software, continues to evolve. With new versions released each year, [...] The post Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17 appeared first on Heroku. ## Partitioning a large table in PostgreSQL with Rails DevFeed: [Partitioning a large table in PostgreSQL with Rails]() Original publisher: [Read original article]() Published: 2025-04-28T00:00:00Z Content type: tutorial Language: en Sources: [Aha! Engineering Blog]() Topics: [PostgreSQL](), [Rails](), [Database](), [Amazon RDS](), [backups](), [Amazon S3](), [etl](), [Disaster Recovery](), [datadog]() Tags: [active-record](), [amazon-rds](), [amazon-s3](), [backups](), [datadog](), [disaster-recovery](), [etl](), [latency](), [migration](), [partitioning](), [performance](), [postgresql](), [rails]() ### AI overview This article explains how Aha! partitioned a very large PostgreSQL audit table used with Rails. It covers the migration strategy, operational and performance problems caused by billions of rows, and an archival process that moves audits older than 12 months to Amazon S3. ### Source excerpt Keeping a reliable history of changes is essential for our users. They need to know when a record was updated, who made the change, and why. They could be anxiously awaiting a notification about a dependency that is blocking their work. Maybe they w ## Rsync Versions 3.3.0 and Earlier Affected by Multiple Security Vulnerabilities DevFeed: [Rsync Versions 3.3.0 and Earlier Affected by Multiple Security Vulnerabilities]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-01-15T18:04:24Z Content type: news Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [rsync](), [Vulnerabilities](), [Exploit](), [Linux](), [Command-line interface](), [Unix](), [backups]() Tags: [backups](), [buffer-overflow](), [centos](), [client](), [command-line](), [debian-linux](), [exploit](), [freebsd](), [linux](), [linux-news](), [open-source](), [race-condition](), [rsync](), [security](), [server](), [sysadmin](), [unix](), [vulnerability]() ### AI overview Rsync versions 3.3.0 and earlier are affected by multiple security vulnerabilities, including heap-based buffer overflow, information disclosure, symbolic-link race conditions, and path traversal. The document recommends patching rsync on both client and server systems. ### Source excerpt Rsync is a opensource command-line tool in Linux, macOS, *BSD and Unix-like systems that synchronizes files and directories. It is a popular tool for sending or receiving files, making backups, or setting up mirrors. It minimizes data copied by transferring only the changed parts of files, making it faster and more bandwidth-efficient than traditional copying methods provided by tools like sftp or ftp-ssl. Rsync versions 3.3.0 and below has been found with SIX serious vulnerabilities. Attackers could exploit these to leak your data, corrupt your files, or even take over your system. There is a heap-based buffer overflow with a CVSS score of 9.8 that needs to be addressed on both the client and server sides of rsync package. Apart from that info leak via uninitialized stack contents defeats ASLR protection and rsync server can make client write files outside of destination directory using symbolic links. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post Critical Rsync Vulnerability Requires Immediate Patching on Linux and Unix systems appeared first on nixCraft. ## Understanding fault tolerance in distributed systems DevFeed: [Understanding fault tolerance in distributed systems]() Original publisher: [Read original article]() Author: Lauren Bennett Published: 2025-01-08T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [distributed-systems](), [systems](), [Availability](), [Cloud](), [Replication](), [backups]() Tags: [availability](), [backups](), [cloud](), [data](), [distributed](), [distributed-systems](), [downtime](), [failover](), [fault-tolerance](), [hardware](), [outage](), [replication](), [services](), [software](), [systems](), [temporal-concepts](), [user]() ### AI overview An explanation of fault tolerance in distributed systems, including how it keeps systems operating during failures and limits disruptions, downtime, and data loss. It describes redundancy, replication, failover mechanisms, graceful degradation, and the relationship between high availability and fault tolerance. ### Source excerpt Discover what fault tolerance is and how it ensures reliable systems with key principles and examples in cloud environments. ## How to find hard disk (SSD) serial numbers in Linux DevFeed: [How to find hard disk (SSD) serial numbers in Linux]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-11-16T21:38:35Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Linux](), [Command-line interface](), [systems](), [reliability](), [backups]() Tags: [backups](), [command](), [easy](), [hard-disk](), [hdd](), [how-to](), [linux](), [smart](), [ssd]() ### AI overview A Linux tutorial showing how to find hard-disk and SSD serial numbers with smartctl and lsblk, including installation commands for several Linux distributions. ### Source excerpt You need to use the smartctl command to display the hard disk (SSD) serial numbers in Linux. This is useful when changing your hard disk if it goes bad. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to find hard disk (SSD) serial numbers in Linux appeared first on nixCraft. ## How to upgrade OpenSUSE 15.5 to 15.6 using the CLI DevFeed: [How to upgrade OpenSUSE 15.5 to 15.6 using the CLI]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-06-30T11:03:25Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Command-line interface](), [upgrade](), [Linux](), [backups](), [version](), [Terminal](), [boot](), [ssh](), [Kernel]() Tags: [advanced](), [backup](), [boot](), [cli](), [developers](), [how-to](), [kernel](), [linux](), [opensuse](), [ssh](), [suse](), [terminal](), [tutorial](), [upgrade]() ### AI overview A tutorial explains how to upgrade openSUSE Leap from version 15.5 to 15.6 using the command line. It covers backups, repository checks and updates, kernel verification, rebooting, SSH access, and an alternative GUI-based method. ### Source excerpt The most recent release of OpenSUSE Linux, version 15.6 "Leap," is now available. This version incorporates the SUSE Linux Enterprise (SLE) source and community developments, making it the ideal option for a stable Linux experience for users, developers, and system administrators. This page provides instructions on upgrading from OpenSUSE version 15.5 to 15.6 using the command-line interface (CLI). Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to upgrade OpenSUSE 15.5 to 15.6 using the CLI appeared first on nixCraft. [Next page]()