Google Cloud Backup and DR deprecates the legacy appliance management console: new backups end 30 September 2027, restores 31 March 2028

Google Cloud Backup and DR deprecates the legacy appliance management console: new backups end 30 September 2027, restores 31 March 2028

30 September 2026 — Google Cloud announced on 30 September 2026 that backing up and restoring workloads managed through the legacy appliance management console of its Backup and DR service is deprecated. The release note sets two milestones: after 30 September 2027 new backups can no longer be run on the legacy stack, and support for standard restores, exports and migrations through the console ends on 31 March 2028.

Not yet independently verified. Both sources are Google's own pages. The deprecations page is undated, so it is dated by the day it was read. Which customers still use the appliance console was not checked against any customer's own project. We will update this when it can be confirmed, and remove this note.

What changed

Google's deprecations page lists the affected workloads: Compute Engine instances managed through the legacy console, Db2 instances, Oracle Database, SAP HANA, Microsoft SQL Server, Google Cloud VMware Engine, generic application consistency groups, and other user-managed applications (file system, system state, NFS and CIFS). The page also records that new deployments of the affected databases in the console stopped being supported after 31 July 2026.

A separate, earlier deprecation covers backup of SAP ASE, SAP IQ, SAP MaxDB, MariaDB, MySQL and PostgreSQL databases in the same console. For those, Google lists 31 July 2027 as the end of new backups and 30 December 2027 as the deadline for migrating retained backup data out of the console.

Who is affected

Organisations that use the Backup and DR appliance console to protect self-managed databases, virtual machines or file shares on Google Cloud or on VMware Engine are affected. Google states that first-party managed services are unaffected: Compute Engine VMs and disks, Cloud SQL, AlloyDB for PostgreSQL and Filestore keep their support.

What to do

Google names the following migration routes on its deprecations page:

• Compute Engine: move to appliance-free, native Backup and DR backups for Compute Engine.
• User-managed databases such as Oracle and Db2: use Compute Engine VM or persistent disk backups with the guest-flush framework and custom scripts.
• SAP HANA: use the Google Cloud SAP Backint agent or disk snapshots.
• General VMs and other workloads: use native disk snapshots or a third-party product from Google Cloud Marketplace.
• MySQL and PostgreSQL: consider the managed Cloud SQL or AlloyDB for PostgreSQL services.

Buyers should inventory which protected workloads still sit in the console, record the earliest relevant date for each (31 July 2027 for the older database group, 30 September 2027 for the newer group), and check restore-retention needs against the 31 March 2028 end of standard restores. Backup data that must be kept for compliance should be migrated or exported well before the restore deadline, as Google's page does not promise restores after it.

Why it matters

Backup tooling is rarely revisited until it fails a restore test. A dated end of restore support for a console-based product turns a quiet infrastructure choice into a planned migration with a hard stop, and it affects contracts, licences for replacement tools and any recovery-time objectives written around the current product. Teams that run SAP HANA or Oracle on Google Cloud are likely to need the most lead time because the replacements involve different backup mechanisms rather than a like-for-like upgrade.

The release note and the deprecations page are Google's own statements. TrustList has not tested any migration path, and customers should confirm dates and affected workloads against their own Backup and DR project and their account team.

Company profile on TrustList: Google Cloud

Sources

• Google Cloud release notes, Backup and DR (30 September 2026) — 30 September 2026
• Google Cloud Backup and DR feature deprecations (read 2026-10-05) — 5 October 2026