This guide explains how to use MaxBack to create SAP system copies — for example, copying a production system to a QA or development environment.

A traditional SAP system copy with MaxDB involves exporting and importing the entire database, which can take hours for large systems. With MaxBack, you can perform a system copy by restoring only the data volumes from a backup and using autorecovery to bring the database online on the target system.

Performing a System Copy

Before you begin, make sure you have:

MaxBack on both systems

MaxBack installed and configured on both the source and target systems.

A recent backup

A recent backup of the source system (Veeam, Azure Backup, or Windows Server Backup).

Matching MaxDB version

The target system has MaxDB installed with the same version as the source.

Administrator access

Administrator access to the target system.

Step 1: Restore the data volumes

Restore the MaxDB data volumes from the source system backup to the target system. The exact procedure depends on your backup solution:

From Veeam: Use Veeam volume restore to restore only the data volume files to the target server. You can attach them to a new device.
From Azure Backup: Restore the managed disk containing the data volumes and attach it to the target VM.

Data Volumes Only

Only the data volumes need to be restored — not the entire VM or system drive.

Step 2: Run autorecovery

On the target system, first check that the restored volume is active and has a drive letter assigned.

Then open an elevated command prompt:

Autorecovery

maxback.vssclient db autorecovery -m C:\path\to\metadata

The metadata file is created by MaxBack during the backup snapshot and stored alongside the data volumes. It contains the recovery information needed to bring the database to a consistent state — in particular, the file system structure of the source database.

Batch Mode

Add the -b flag for batch mode if you don't need the Session Logviewer GUI.

Step 3: Post-recovery steps

After autorecovery completes:

The database is running and consistent.
Update the SAP user in the database schema and reset its password.
Run SAP post-copy activities (BDLS, client copy, etc.).

How it works

During a normal backup, MaxBack writes recovery metadata to the file system alongside the database data volumes. This metadata includes:

The database state at the time of the snapshot
Base database settings like the database name, which is used to identify a system copy

When you run autorecovery on the target system, MaxBack uses this metadata to:

Detect that the data volumes are from a different system
Adopt the file definitions of the existing database to the new files
Adopt permissions on the new files
Reset the log volumes

Troubleshooting

If the metadata file is not found, check that it was included in the data volume restore — in most cases this means the source backup was not set up correctly.
Ensure the target MaxDB version matches the source.
Check the Session Logviewer for detailed recovery progress.
See Troubleshooting for more diagnostic steps.