All news with #backup security tag

🔁 Amazon Elastic Block Store (EBS) now supports snapshot copy for AWS Local Zones, enabling point-in-time local snapshots to be copied to the parent Region or another Local Zone. The feature is generally available and accessible via the AWS Console, CLI, and SDKs. This capability helps customers meet disaster recovery, data migration, and compliance requirements by storing snapshots in Amazon S3 within the chosen Region or Local Zone.

🛡️ Many organizations rely on SaaS project platforms such as Trello and Asana for daily operations, but native protections and short retention windows often leave critical data exposed. The piece highlights human error, misconfiguration, and targeted cyberattacks as leading causes of loss. It recommends adding a third‑party backup layer and presents FluentPro Backup as a solution offering continuous automated backups, granular restores, one‑click project recovery, and Azure‑backed security to ensure recoverability and auditability.

⚙️ Amazon RDS for Oracle now supports Redo Transport Compression, which compresses redo data before it is transmitted to standby databases to reduce network traffic and improve redo transport performance. Because transport is faster, customers can achieve a lower Recovery Point Objective (RPO). Compression and decompression consume CPU on both primary and standby instances, so ensure adequate CPU capacity before enabling. Enable the feature by setting the redo_compression parameter in the instance Parameter Group; it supports mounted and read replicas and requires Oracle Enterprise Edition with Oracle Advanced Compression licensing.

🕒 Amazon RDS for PostgreSQL now supports delayed read replicas, allowing you to specify a minimum time period for a replica to intentionally lag behind its source. This configurable time buffer helps protect against human errors such as accidental table drops or unwanted data modifications by preserving a recoverable replica state. In recovery workflows you can pause replication before problematic changes are applied, resume replication to a specific log position, and promote the replica as the new primary to achieve faster recovery than lengthy point-in-time restores.