# restore Published articles for restore. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CTERA Data Archiving Solution Pairs InsightAI With CTERA Archive to Move Inactive Files Off Primary Storage With an Audit Trail DevFeed: [CTERA Data Archiving Solution Pairs InsightAI With CTERA Archive to Move Inactive Files Off Primary Storage With an Audit Trail]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-17T17:29:28Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [data-processing](), [Artificial Intelligence](), [Security](), [Amazon S3]() Tags: [ai](), [audit-trail](), [data-protection](), [data-storage](), [enterprise](), [object-storage](), [restore](), [retention](), [s3]() ### AI overview CTERA launched a Data Archiving Solution that combines InsightAI with CTERA Archive to identify inactive files and move them from primary storage under retention policies and an audit trail. The solution keeps archived data governed and accessible within the CTERA Intelligent Data Platform, using on-premises or cloud storage tiers. ### Source excerpt CTERA has launched the CTERA Data Archiving Solution, which pairs its InsightAI data service with CTERA Archive so the platform can recommend which files to move off primary storage and then execute the move under retention policy and an audit trail. It's the product follow-through to the Cold Data Storage Report CTERA published a day The post CTERA Data Archiving Solution Pairs InsightAI With CTERA Archive to Move Inactive Files Off Primary Storage With an Audit Trail 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】Watch 机制：watchableStore、synced/unsynced 与 ErrCompacted DevFeed: [【etcd】Watch 机制：watchableStore、synced/unsynced 与 ErrCompacted]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Remote Procedure Call (RPC)](), [Kubernetes]() Tags: [apiserver](), [apply](), [compaction](), [distributed](), [errcompacted](), [etcd](), [io](), [k8s](), [kubernetes](), [lag](), [leader](), [lease](), [mvcc](), [notify](), [raft](), [range](), [restore](), [revision](), [rpc](), [v3-5](), [v3-5-33](), [watch](), [watchablestore]() ### AI overview This article examines the etcd v3.5.33 watchableStore implementation, including synced and unsynced watcher groups, victims caused by backpressure, Apply-time notification, historical synchronization, and the ErrCompacted client resynchronization boundary. It also discusses event ordering, follower watch progress, and interactions with Kubernetes apiserver watch caches. ### Source excerpt 钉 etcd v3.5.33 watchableStore 的 synced/unsynced/victims 三分法、Apply 后 notify 与历史追赶 syncWatchersLoop，以及 CompactRevision 触发 ErrCompacted 时的客户端重同步边界。 ## 【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表 DevFeed: [【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Kubernetes]() Tags: [apiserver](), [applied-index](), [apply](), [committed-index](), [compaction](), [distributed](), [errcompacted](), [etcd](), [five-axes](), [incident](), [keepalive](), [kubernetes](), [lag](), [lease](), [mvcc](), [node-lease](), [raft](), [restore](), [troubleshooting](), [ttl](), [v3](), [v3-5](), [v3-5-33](), [wal](), [watch]() ### AI overview This troubleshooting article organizes etcd failures into five diagnostic axes: Raft consensus, WAL persistence and recovery, MVCC storage and capacity, Watch client synchronization, and Lease TTL semantics. It maps symptoms to axes, explains relevant etcdctl health and status fields, and notes Kubernetes control-plane relationships, including apiserver and Node Lease behavior. The article is anchored to etcd v3.5.33. ### Source excerpt 按 Raft、WAL、MVCC、Watch、Lease 五轴做症状否证；解释 etcdctl endpoint status/health 字段语义；并对照 K8s 控制面 apiserver 超时与 Node Lease 漂移。 ## 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 ## Upgrading ElasticSearch 2 to 5: S3 snapshot/restore strategy DevFeed: [Upgrading ElasticSearch 2 to 5: S3 snapshot/restore strategy]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [elasticsearch](), [migration](), [Amazon S3](), [Docker Compose](), [version](), [Testing](), [MinIO]() Tags: [docker-compose](), [elasticsearch](), [migration](), [minio](), [restore](), [s3](), [snapshot](), [testing](), [version]() ### AI overview This tutorial explains a strategy for migrating an ElasticSearch cluster from version 2 to version 5 by creating test environments, snapshotting the ES2 cluster, and restoring the snapshot on ES5 using S3. It also describes using Docker Compose and MinIO for safe testing before production migration. ### Source excerpt Migrating an ElasticSearch cluster from version 2 to 5 can be challenging, even more if it is a big cluster. ## Inline Extensions DevFeed: [Inline Extensions]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2012-12-13T10:34:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Extension](), [Filesystems]() Tags: [api](), [extension](), [extensions](), [manage](), [postgresql](), [process](), [releases](), [restore](), [version]() ### AI overview The article examines PostgreSQL extensions beyond contrib modules, focusing on managing procedural code and related SQL objects as a single versioned unit. It explains how extensions support dependency tracking, dump and restore workflows, API protection, and upgrade management. ### Source excerpt We've been having the CREATE EXTENSION feature in PostgreSQL for a couple of releases now, so let's talk about how to go from here. The first goal of the extension facility has been to allow for a clean dump and restore process of contrib modules. As such it's been tailored to the needs of deploying files on the file system because there's no escaping from that when you have to ship binary and executable files, those infamous .so, .dll or .dylib things.