> [!CAUTION]
> **Caution:** Support for backing up and restoring workloads managed using the legacy appliance management console is deprecated. For more information, see [Feature deprecations](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations.md.txt) in the Backup and DR documentation.

**Caution:** Beginning July 31, 2027, support for backing up SAP MaxDB
databases using the appliance management console is deprecated. To learn
more about this deprecation and alternative backup solutions, see [Migrate from legacy database backups](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations/migrating-legacy-databases.md.txt).

Backup and DR uses a backup/recovery appliance to capture, store, and
recover backups of SAP MaxDB databases running on Microsoft Windows, Linux, and
Unix. Depending on your environment and configuration, Backup and DR
protects SAP MaxDB databases by using either volume-based backups with Linux
Changed Block Tracking (CBT) and Logical Volume Manager (LVM) snapshots, or
file-based dump and log backups.

This document explains the backup and recovery workflows for both volume-based
and file-based approaches, as well as the SAP MaxDB APIs that
Backup and DR uses during these operations.

## How it works: Backup and DR volume-based backup with Linux CBT

Only changed blocks are tracked in the bitmap---no copy-on-writes or
I/O-intensive operations.

Data backup and recovery with volume-based backups and CBT follows these steps:

1. The Backup and DR agent has CBT to track changed blocks in the database data
   area.

2. The agent calls the database API to freeze or pause database for data backup.

3. Agent creates LVM snapshot of database data area and synthesizes a bitmap.

4. Agent call to database API to unfreeze database.

5. Agent copies changed blocks to backup/recovery appliance, which then deletes
   the snapshot and catalogs the backup.

6. The appliance issues an internal snapshot and synthesizes a point-in-time
   virtual full backup.

7. For data recovery, Backup and DR instantly mounts a rewritable
   staging disk and brings the database online.

## How it works: file-based backup

Data backup and recovery with file-based backups follows these steps:

1. Backup and DR agent is deployed in the database server.

2. Mount staging disk on the database server.

3. Invoke Full+Incremental backup using the dump backup command,
   writing the backup to the mounted disk.

4. Backup and DR takes an internal snapshot.
   Log backups are done in a similar fashion directly from the file-system at
   any schedule that you configure.

5. For data recovery, Backup and DR instantly mounts the staging disk to the
   database server and initiates the database restore operation.
   Logs can be played to any point in time after the database is restored.

## SAP MaxDB APIs

Backup and DR uses the following SAP MaxDB backup APIs:

- **Linux CBT and LVM snapshot** : MaxDB `UTIL_EXECUTE SUSPEND LOGWRITER` and
  `UTIL_EXECUTE RESUME LOGWRITER` API with Linux CBT and LVM snapshot

- **File-based backups** : MaxDB
  `dbmcli -d &lt;dbsid&gt; -u &lt;dbm_username&gt;,&lt;dbm_password&gt;backup_start`
  file-based backups API

  This provides the full backup of the database in backup format. The
  prerequisite for data backup is to define the backup template first.
  Recovery API restore db recovers the database by physically overwriting the
  data area.
- **MaxDB log backup**: MaxDB autolog backup must be enabled on the
  application side. Backup and DR copies the log backup files to staging disk
  with cp command. As Autolog Backup is enabled we use os command to purge the
  log backup.

## What's next

[Prepare the database for Backup and DR](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/otherdb-prep-database)

## Other documentation for Backup and DR for MaxDB

This page is one in a series of pages specific to protecting and recovering
MaxDB databases with Backup and DR.
You can find additional information at the following pages:

- [Backup and DR for SAP MaxDB](https://docs.cloud.google.com/backup-disaster-recovery/docs/concepts/maxdb-intro)
- [Prepare the database for Backup and DR](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/otherdb-prep-database)
- [Add a MaxDB database host and discover databases](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/otherdb-add-host)
- [Define policy templates and resource profiles](https://docs.cloud.google.com/backup-disaster-recovery/management-console/create-plan/create-template.md.txt)
- [Set application details and settings](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/app-details-settings-otherdb.md.txt)
- [Check staging disk format and backup method](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-method-staging-disk-otherdb.md.txt)
- [Protect the MaxDB database and its logs](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup/otherdb-protect)
- [Mount a MaxDB database](https://docs.cloud.google.com/backup-disaster-recovery/docs/access-data/otherdb-mounts)
- [Recover MaxDB Backups](https://docs.cloud.google.com/backup-disaster-recovery/docs/restore-data/otherdb-restore)
- [Create a MaxDB Backup and DR Workflow](https://docs.cloud.google.com/backup-disaster-recovery/docs/access-data/otherdb-workflow)