Recover SAP IQ and SAP MaxDB databases from a volume-based backup image to a new location

Both of these procedures require you to customize and run a config file.

The following sections detail how to recover a volume-based backup image of an SAP IQ or SAP MaxDB database to a new location.

To recover a volume-level backup image of an IBM Db2, MariaDB, MySQL, PostgreSQL, SAP ASE, SAP IQ, or SAP MaxDB database to a new target, you can also use the instant mount and migrate of a database to a new target procedure.

Note: Mount and migrate is a quick mount; the database is immediately available from the staging disk, then the data moves in the background from the staging disk to the target storage. If users are active in the database, this takes time and impacts performance.
The restore procedures on this page keep the database down for the entire time of the restore procedure, often some hours, but at the end the database is available on the target storage at full performance, with no impact of background migration or reading from a staging disk.
To recover a Full+Incremental backup image of an IBM Db2, PostgreSQL, SAP ASE, SAP IQ, and SAP MaxDB databases to a new target, see Recover a Full+Incremental backup image of other databases to a new target.

Recovery procedure

To recover a volume-level backup image to a new target, follow these steps:

From the App Manager Applications list, right-click the protected database and select Access. You can use the Managed Backup Plan status filter to show only protected databases.
Select the latest snapshot to recover, and choose Mount.
Provide a target mount point under mount location, for example, /dmpRstNew. This is used as the variable TARGET_MNT_PNT.

The database backup is mounted under /dmpRstNew (TARGET_MNT_PNT) and the log backup is mounted under /dmpRstNew_archivelog (LOG_BKP_MNTPT).
Log into the database server as root. Change the directory to /act/custom_apps/<database type>/restore.
Run the script.
SAP IQ
```
/act/custom_apps/sybaseiq/restore/act_sybaseiq_lvm_customdb_recovery.sh TARGET_MNT OSUSER CATALOG_DB_FILE SRC_DB_DBA_USER SRC_DB_DBA_PWD LOG_BKP_MNTPT RECOVERY_TIME JOBID INCR_BKP_LOC
```
Note: You can get ACT_JOBNAME from the management console Monitor > Jobs tab.

After the script has run, connect to the IQ database and confirm that the databases are recovered and online.
```
dbisql -c "uid=username;pwd=password;eng=engine name;dbn=database name;" -nogui
```
SAP MaxDB
```
  /act/custom_apps/maxdb/restore/ACT_MAXDB_lvmRestore_newTarget.sh \
  OSUSER \
  TARGET_SERVER_NAME \
  TARGET_DB_USER \
  TARGET_DBUSER_PASSWD \
  SOURCE_DBSID \
  MANIFEST_FILE_LOC \
  SRC_DB_VERSION \
  ACT_JOBNAME \
  TARGET_MNT_PNT \
  LOG_BKP_MNTPT \
  UNTIL_TIME \
  BEGIN_TIME
```
Note: TARGET_DB_USER and TARGET_DBUSER_PASSWD must be the same as the source DBM username and password. You can change the password after the restore operation is finished.
Note: You can get ACT_JOBNAME and TARGET_MNT_PNT from the management console Monitor > Jobs tab.

Connect to the MaxDB database and confirm that the databases are recovered and online:
```
  dbmcli -d TARGET_SERVER_NAME -u TARGET_DB_USER,TARGET_DBUSER_PASSWD db_state
```
After the database is restored, take a dump database backup to generate a backup history point in backup_history_list, which is required to take log backups. For example, the following:
```
   dbmcli -d DB -u DBM_USER,DBM_PASSWORD -c backup_start TEMPLATE_NAME DATA AUTOIGNORE
```
Without this, future volume level backups fail with the error fail to trigger autolog backup template.
Unmount the mounted snapshot image.

Change the password

In some cases, you may need to change the database password.

SAP IQ

Log into the target database. For a database named TARGET_SERVER_NAME, with db user SRC_DB_DBA_USER and password SRC_DB_DBA_PWD, the command to sign in is as follows.
```
dbisql -nogui -onerror exit -c 'uid=SRC_DB_DBA_USER;pwd=SRC_DB_DBA_PWD;dbn=TARGET_DB_NAME;eng=TARGET_SERVER_NAME;
```

Run the following command to change password.

ALTER USER SRC_DB_DBA_USER IDENTIFIED BY NEW_PASSWORD

dbisql -nogui -onerror exit -c 'uid=SRC_DB_DBA_USER;pwd=NEW_PASSWORD;dbn=TARGET_DB_NAME;eng=TARGET_SERVER_NAME;

SAP MaxDB

To change the password, sign in to the target database as DBM user:
```
dbmcli -d TARGET_SERVER_NAME -u TARGET_DB_USER,TARGET_DBUSER_PASSWD
user_changepwd dbm new_password
```
For example, for a DBM user changing the password from abcdef to fedcba, sign in:

dbmcli -d glxn -u dbm,abcdef
Run the following command:

user_changepwd dbm abcdef
Sign in again with the new password:

dbmcli -d glxn -u dbm,fedcba