There is a new committed use discount (CUD) for customers using Backup and DR Service to protect Oracle databases into a backup vault

## Announcement There is a new committed use discount (CUD) for customers using Backup and DR Service to protect Oracle databases into a backup vault. This is a way to lower backup costs in consideration of a 1-year or 3-year commitment. You can purchase CUDs from Google Cloud Marketplace via the standard process. ## Feature Introduced logging and alerting capabilities to monitor the health and status of your backup/recovery appliances. You can configure email notifications via Cloud Logging to receive timely alerts on appliance status changes or potential issues. ## Feature Backup and DR Service now supports backup and restore of Db2 databases using persistent disk snapshots. This is typically faster and simpler than previous methods and in some cases may also reduce costs. ## Fix These issues have been fixed: * An issue in which multiple snapshot/Direct OnVault jobs became stuck in an unresponsive state after attempting to connect to vCenter with an openssl command. * An issue in which database persistent disk snapshot backup jobs failed with the unhelpful error message `resource not found` now has a useful error message. * An issue in which Log explorer was showing some spurious "read error, check permissions" results on backup/recovery appliances. * An issue in which a backup/recovery appliance could come out of synchronization with a management console following a `Trying to release lock` or `Failed to acquire lock` error. * A rare issue in which a backup/recovery appliance became unresponsive after a very heavy load exhausted all job threads and /var/log/ was 100% full. Thread management is now more efficient. * An issue in which persistent disk database snapshot images were failing to import log backups, and the recovery range was missing on imported backups. * An issue in which some backups of PostgreSQL version 15 failed due to a premature timeout. * An issue in which some mount jobs failed if the host's lvmconfig has global/system\_id\_source set to `uname`. * An issue in which database names provided in mount screen were not honored correctly when creating child applications on the target host. * The `Staging disk is full` error message has been made more useful. ## Security Vulnerabilities CVE-2024-42301, CVE-2024-42284, and CVE-2024-41092 have been fixed at kernel version 4.18.0-553.33.1.el8\_10. ## Feature Introduced management console events for the Appliance Connectivity Events and Dynamic Protection Events.