Recover IBM Db2, SAP ASE, SAP IQ, and SAP MaxDB databases to a new target
Stay organized with collectionsSave and categorize content based on your preferences.
The following sections include information on recovering IBM Db2, SAP ASE,
SAP IQ, and SAP MaxDB databases from a Full+Incremental backup image
to a new target.
Procedure
To restore a file-based backup image to a new target, follow these instructions:
From theApp Manager Applicationslist, right-click the protected
database and selectAccess.
Select the latest snapshot to recover and clickMount.
Provide a mount point under mount location, for example:/mymountpoint.
The database backup is mounted under/mymountpointand the log
backup is mounted under/mymountpoint_archivelog.
Retrieve theJobIDof the mount from/var/act/log/UDSAgent.logby running
the following command:
grep"mount -t "/var/act/log/UDSAgent.log|grep-w"(mountPoint provided in step 3)"|tail-1
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThis document details the procedure for recovering IBM Db2, SAP ASE, SAP IQ, and SAP MaxDB databases to a new target using Full+Incremental backup images.\u003c/p\u003e\n"],["\u003cp\u003eThe recovery process involves mounting the backup snapshot, locating the \u003ccode\u003eJobID\u003c/code\u003e, and running a specific script that is dependent on the database type using the correct parameters and values.\u003c/p\u003e\n"],["\u003cp\u003eEach database type (IBM Db2, SAP ASE, SAP IQ, and SAP MaxDB) has its own specific script with unique parameters that need to be provided for a successful recovery.\u003c/p\u003e\n"],["\u003cp\u003eThe steps require utilizing the command line and scripts, accessing mounted locations, and verifying database recovery status through database-specific commands.\u003c/p\u003e\n"],["\u003cp\u003eYou must retrieve specific information from system log files to retrieve information, such as \u003ccode\u003eJobID\u003c/code\u003e, mount points, begin time and other parameters.\u003c/p\u003e\n"]]],[],null,["# Recover IBM Db2, SAP ASE, SAP IQ, and SAP MaxDB databases to a new target\n\nThe following sections include information on recovering IBM Db2, SAP ASE,\nSAP IQ, and SAP MaxDB databases from a Full+Incremental backup image\nto a new target.\n\nProcedure\n---------\n\nTo restore a file-based backup image to a new target, follow these instructions:\n\n1. From the **App Manager Applications** list, right-click the protected\n database and select **Access**.\n\n | **Note:** You can use the **Managed Backup Plan** status filter to show only protected databases.\n2. Select the latest snapshot to recover and click **Mount**.\n\n3. Provide a mount point under mount location, for example: `/mymountpoint`.\n\n The database backup is mounted under `/mymountpoint` and the log\n backup is mounted under `/mymountpoint_archivelog`.\n4. Retrieve the `JobID` of the mount from `/var/act/log/UDSAgent.log` by running\n the following command:\n\n grep \"mount -t \" /var/act/log/UDSAgent.log | grep -w \"(mountPoint provided in step 3)\"|tail -1\n\n For example: \n\n # grep \"mount -t \" /var/act/log/UDSAgent.log| grep -w \"/db2mnp\" |tail -1\n 2019-11-18 23:59:19.740 GEN-INFO 22488 Job_0404207 Spawning cmd: mount -t ext4 /dev/act403764_DBDump_1574101677612/act_staging_vol /db2mnp 2\u003e&1\n\n5. `ARCHIVELOG_MNT` is equal to _archivelog. Refer to step three.\n\n6. Login to the database server as root. On the server, change\n the directory to the following:\n\n cd /act/custom_apps/(database type)/dump\n\n7. Run the script from command line as root.\n\n8. Unmount the mounted dump snapshot image.\n\nRequired script\n---------------\n\nBefore you can mount a database to a new target, you must prepare a script. \n\n### IBM Db2\n\n /act/custom_apps/db2/dump/ACT_DB2_dumprestore_newTarget.sh \\\n SOURCE_INSTANCE=\u003cvar label=\"the name of the Db2 instance\" translate=\"no\"\u003eSOURCE_INSTANCE_edited_value\u003c/var\u003e \\\n TARGET_MNT=\u003cvar label=\"mount point provided during the mount job\" translate=\"no\"\u003eTARGET_MNT_edited_value\u003c/var\u003e \\\n DB_LIST=\u003cvar label=\"comma-separated list of databases to restore\" translate=\"no\"\u003eDB_LIS_edited_value\u003c/var\u003e \\\n ARCHIVELOG_MNT=\u003cvar label=\"archive Log backup mount point name\" translate=\"no\"\u003eARCHIVELOG_MNT_edited_value\u003c/var\u003e \\\n SOURCE_LOGARCHMETH1=\u003cvar label=\"Db2 source database archivelog location, must be local disk\" translate=\"no\"\u003eSOURCE_LOGARCHMETH1_edited_value\u003c/var\u003e \\\n UNTIL_TIME=\u003cvar label=\"recovery time in the format: YYYY-MM-DD-HH.MI.SS\" translate=\"no\"\u003eUNTIL_TIME_edited_value\u003c/var\u003e \\\n ACT_JOBNAME=\u003cvar label=\"standard mount jobname\" translate=\"no\"\u003eACT_JOBNAME_edited_value\u003c/var\u003e\n\nReplace the following:\n- \u003cvar translate=\"no\"\u003eSOURCE_INSTANCE\u003c/var\u003e: the name of the Db2 instance\n- \u003cvar translate=\"no\"\u003eTARGET_MNT\u003c/var\u003e: the mount point provided during the mount job\n- \u003cvar translate=\"no\"\u003eDB_LIST\u003c/var\u003e: a comma-separated list of databases to restore\n- \u003cvar translate=\"no\"\u003eARCHIVELOG_MNT\u003c/var\u003e: archive log backup mount point name\n- \u003cvar translate=\"no\"\u003eSOURCE_LOGARCHMETH1\u003c/var\u003e: Db2 source database archivelog location, must be local disk\n- \u003cvar translate=\"no\"\u003eUNTIL_TIME\u003c/var\u003e: recovery time in the format: YYYY-MM-DD-HH.MI.SS\n- \u003cvar translate=\"no\"\u003eACT_JOBNAME\u003c/var\u003e: the jobname of the standard mount job\n- Connect to the Db2 instance and confirm that the databases are recovered and online. \n\n db2 connect to \u003cdbname\u003e\n db2 select db_status FROM SYSIBMADM.SNAPDB\n\n### SAP ASE\n\n /act/custom_apps/sybase/dump/ACT_SYBASE_dumprestore_newTarget.sh\n \u003cvar label=\"target ASE OS user name\" translate=\"no\"\u003eSYBOSUSER\u003c/var\u003e\n \u003cvar label=\"target ASE OCS location ($SYBASE/$SYBASE_OCS)\" translate=\"no\"\u003eSRC_SYBASE_SQLD\u003c/var\u003e\n \u003cvar label=\"target ASE instance username\" translate=\"no\"\u003eTARGET_DB_USER\u003c/var\u003e\n \u003cvar label=\"target ASE instance password\" translate=\"no\"\u003eTARGET_DBUSER_PASSWD\u003c/var\u003e\n \u003cvar label=\"target ASE server name\" translate=\"no\"\u003eACT_NAME\u003c/var\u003e\n \u003cvar label=\"the mount point provided during the mount job\" translate=\"no\"\u003eTARGET_MNT_PNT\u003c/var\u003e\n \u003cvar label=\"a comma separated db list to restore\" translate=\"no\"\u003eSRC_DBNAME\u003c/var\u003e\n \u003cvar label=\"recovery time in the format YYYY-MM-DD-HH.MI.SS\" translate=\"no\"\u003eUNTIL_TIME\u003c/var\u003e\n \u003cvar label=\"dump backup begin time in the format: YYYY-MM-DD HH24:MI:SS\" translate=\"no\"\u003eBEGIN_TIME\u003c/var\u003e\n \u003cvar label=\"logs backup mount point name\" translate=\"no\"\u003eLOG_BKP_MNTPT\u003c/var\u003e\n \u003cvar label=\"source database page_size\" translate=\"no\"\u003eSRC_PAGE_SIZE\u003c/var\u003e\n\nConnect to the SAP ASE instance and confirm that the databases are\nrecovered and online. \n\n isql -U\u003cusername\u003e -P\u003cpassword\u003e -S\u003cSAP ASE server name\u003e\n sp_helpdb\n go\n\n### SAP IQ\n\n /act/custom_apps/sybase/dump/ACT_SYBASE_dumprestore_newTarget.sh\n \u003cvar label=\"SYBASE IQ OSUSER name\" translate=\"no\"\u003eOSUSER\u003c/var\u003e\n \u003cvar label=\"mount point provided during the mount job\" translate=\"no\"\u003eTARGET_MNT\u003c/var\u003e\n \u003cvar label=\"utility database user name\" translate=\"no\"\u003eSRC_DB_DBA_USER\u003c/var\u003e\n \u003cvar label=\"utility database password\" translate=\"no\"\u003eSRC_DB_DBA_PWD\u003c/var\u003e\n \u003cvar label=\"SAP IQ home location\" translate=\"no\"\u003eSYBIQ_HOME\u003c/var\u003e\n \u003cvar label=\"SAP IQ home version\" translate=\"no\"\u003eVERSION\u003c/var\u003e\n \u003cvar label=\"SAP IQ source database name\" translate=\"no\"\u003eACT_NAME\u003c/var\u003e\n \u003cvar label=\"catalog database file location\" translate=\"no\"\u003eCATALOG_DB_FILE\u003c/var\u003e\n \u003cvar label=\"archive log backup mount point name\" translate=\"no\"\u003eLOG_BKP_MNTPT\u003c/var\u003e\n\nConnect to the IQ database and confirm databases are recovered and online. \n\n dbisql -c \"uid=\u003cusername\u003e;pwd=\u003cpassword\u003e;eng=\u003cengine name\u003e;dbn=\u003cdatabase name\u003e;\" -nogui\n\n### SAP MaxDB\n\n /act/custom_apps/maxdb/dump/ACT_Maxdb_dumpRestore_newTarget.conf\n \u003cvar label=\"target MAXDB OS User\" translate=\"no\"\u003eOSUSER\u003c/var\u003e\n \u003cvar label=\"source MaxDB SID of the source database to restore from\" translate=\"no\"\u003eSRC_DBSID\u003c/var\u003e\n \u003cvar label=\"target MaxDB Instance DBM username\" translate=\"no\"\u003eTARGET_DB_USER\u003c/var\u003e\n \u003cvar label=\"target MaxDB Instance DBM password\" translate=\"no\"\u003eTARGET_DBUSER_PASSWD\u003c/var\u003e\n \u003cvar label=\"target MaxDB SID to restore\" translate=\"no\"\u003eTARGET_SERVER_NAME\u003c/var\u003e\n \u003cvar label=\"the full path to the dump backup location (the mount point provided in Step 3)\" translate=\"no\"\u003eDUMPBKPLOC\u003c/var\u003e\n \u003cvar label=\"DBADMIN password for the target database\" translate=\"no\"\u003eDBADMIN_PWD\u003c/var\u003e\n \u003cvar label=\"recovery time in the format: YYYY-MM-DD HH24:MI:SS\" translate=\"no\"\u003eUNTIL_TIME\u003c/var\u003e\n \u003cvar label=\"targetDB log file mount point if the target server directory structure is different from source\" translate=\"no\"\u003eLOG_MNT_PNT\u003c/var\u003e\n \u003cvar label=\"targetDB data file mount point if target server directory structure is different from source\" translate=\"no\"\u003eDATA_MNT_PNT\u003c/var\u003e\n \u003cvar label=\"the JobID of the mount job\" translate=\"no\"\u003eJobID\u003c/var\u003e\n \u003cvar label=\"the location of the MaxDB manifest file\" translate=\"no\"\u003eMANIFEST_FILE_LOC\u003c/var\u003e\n \u003cvar label=\"the full path to the dump log\" translate=\"no\"\u003eLOG_BKP_MNTPT\u003c/var\u003e\n \u003cvar label=\"the begin time in the format: YYYY-MM-DD-HH.MI.SS\" translate=\"no\"\u003eBEGIN_TIME\u003c/var\u003e\n \u003cvar label=\"the version of the source MaxDB database\" translate=\"no\"\u003eSRC_DB_VERSION\u003c/var\u003e\n\n| **Note:** Target MAXDB Instance DBM username and password must be the same as the source DBM username and password or recovery fails. You can change the password after the restore is finished.\n\nYou can get these values by running the following commands:\n\n- DUMPBKPLOC:\n\n df -h | grep \u003cDUMPBKPLOC\u003e | awk '{print $NF}'\n cat /var/act/log/UDSAgent.log | grep -w \u003cDUMPBKPLOC\u003e | tail -1 | cut -d']' -f2 | cut -d' ' -f2\n\n- JobID:\n\n cat /var/act/log/UDSAgent.log | grep \u003cJOBID\u003e | awk -F\"disk at \" '{print $2}'\n\n- MANIFEST_FILE_LOC:\n\n cat /var/act/log/UDSAgent.log | grep -i \"Manifest_File_\" | awk -F\"disk at \" '{print $2}'\n\n- LOG_BKP_MNTPT:\n\n df -h | grep \"_archivelog\" | awk '{print $NF}'\n\n- BEGIN_TIME:\n\n cat /var/act/log/UDSAgent.log | grep \"BEGIN_TIME\" | awk -F\"BEGIN_TIME=\" '{ print $2 }' | cut -d' ' -f1-2 | cut -d'\"' -f2\n\n- SRC_DB_VERSION:\n\n dbmcli -d \u003cSRC_DBSID\u003e dbm_version | grep \"VERSION\" | awk -F\"= \" '{print $2}'\n\nConnect to the MaxDB instance and confirm that the databases are recovered and online: \n\n dbmcli -d \u003cTARGET_SERVER_NAME\u003e -u\n \u003cTARGET_DB_USER\u003e,\u003cTARGET_DBUSER_PASSWD\u003e\n db_state"]]
