Mount and migrate other types of database backup images for instant recovery to any target

The Backup and DR Service mount and migrate feature allows near-instant recovery of a volume-level database backup image. Full+Incremental backup images cannot use mount and migrate.

Note: Mount and migrate recovers entire instances. It cannot recover a single database in a database instance. For this you need Recover other database types back to a new location.

Microsoft SQL server, Oracle, and SAP HANA databases have specific procedures for mount-and-migrate.

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.
SAP IQ and SAP MaxDB databases can also use a restore procedure with scripts to recover a volume image to a new target. This method keeps 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.

This page provides instructions for these other supported database types:

• IBM Db2

• MariaDB

• MySQL

• PostgreSQL

• SAP ASE

• SAP IQ

• SAP MaxDB

You can access backup images for these databases in several ways:

• Restore to the source
• Recover to a new target (SAP MaxDB and SAP IQ only)
• Clone
• LiveClone
• Backup and DR Workflow
• Mount

A mount and migrate operation allows you to restore a database by first mounting it and then migrating it to the production storage or in a new location. Users have normal access to the database while it is mounted and during the migration step.

Once you have protected a database or instance with a volume-level backup image, you can mount it and migrate it:

• Mount and migrate back to the source
• Mount and migrate to a new instance

This page describes how to make a standard and virtual database (application aware mount) of the other types of databases.

Mount and migrate back to the source

Use these instructions to mount a database from a backup image and migrate the mounted image back to the source.

1. 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.

2. Disable the backup plan to ensure no new jobs interfere with this job.

   IBM Db2 only

   Mount the image as a standard mount.

   If under mount location, you use the mount point /mydatabase, then the following is true:

   • The database backup is mounted under /mydatabase
   • The log backup is mounted under /mydatabase_archivelog

   Once the mount job is completed, run the mountrecover script with the parameters in Arguments to the script.

   Name of the script: ACT_DB2_mountrecover.sh

   Location of the script: /act/custom_apps/db2/clone/

   Script

   /act/custom_apps/db2/clone/ACT_DB2_mountrecover.sh TARGET_MNT= TARGET_INSTANCE= TARGET_DBNAME_LIST= [UNTIL_TIME ] JOBID=

   Arguments to the script

   TARGET_MNT =

   TARGET_INSTANCE =

   TARGET_DBNAME_LIST =

   JOBID =

   Example

   /act/custom_apps/db2/clone/ACT_DB2_mountrecover.sh TARGET_MNT=/db2gj TARGET_INSTANCE=db2prod TARGET_DBNAME_LIST=ENG,TEST1,IND UNTIL_TIME="2020-02-12 04.14.41" JOBID=Job_12332

   All other database types

   Mount the image as a virtual mount.

3. When the mount operation is finished, the database is recovered and the recovered database is up and running from the backup/recovery appliance. The next step is to migrate the database to your production storage.

Migrate the data from the backup/recovery appliance to the source

The following prerequisites must be met in order to migrate the data:

• The local target host device should not be in use by another process such as a running database since it needs to be taken offline or online at the start of the pvmove process.
• The size of the target host LVM device must be equal to or more than the BackupDR_mount_point size.
• Make sure /etc/fstab has the /dev/mapper entries for production data and log volumes.
• Use the df command to learn the Backup and DR mount point.
• To learn which target logical volume manager devices are available use the lvdisplay command. You need to specify the full logical volume path.
• To learn the job name use Monitor > Jobs
• All other values should be the same as those used during the mount.

1. Once the mountrecover script is completed, run the migration script:

   IBM Db2

   Script name: ACT_DB2_lvm_migrate_newtarget

   Script location: /act/custom_apps/db2/restore/

   /act/custom_apps/db2/restore/ACT_DB2_lvm_migrate_newtarget.sh SOURCE_INSTANCE= TARGET_DBNAME_LIST= JOBID DATAVOL_DISK_MAPPING=: ARCHIVELOG_LOC=

   Arguments to the script

   SOURCE_INSTANCE =

   TARGET_DBNAME_LIST=

   JOBID =

   ARCHIVELOG_LOC = [Mount point should be in local storage]

   DATAVOL_DISK_MAPPING = Colon-separated list of :

   Example

   /act/custom_apps/db2/restore/ACT_DB2_lvm_migrate_newtarget.sh SOURCE_INSTANCE=db2prod TARGET_DBNAME_LIST=TEST1,TEST2 JOBID=Job_4488748 ARCHIVELOG_LOC=/db2gj_archivelog DATAVOL_DISK_MAPPING=/db2gj/db2/data:/dev/mapper/vg00 vol_data,/db2gj/db2/log:/dev/mapper/vg01 vol_log

   MariaDB

   Script name: ACT_MARIADB_lvm_migrate_newTarget.sh

   Script location: /act/custom_apps/mariadb/restore/

   Script:

   /act/custom_apps/mariadb/lvm_migrate/ACT_MARIADB_lvm_migrate.sh JOBID= OSUSER= DBUSER= DBPASSWORD= BASEDIR= MARIADB_CNF= PORT= SOCKET_FILE= CONFIG_FILE= BEGIN_TIME= UNTIL_TIME= LOG_BKP_MNTPT= DATAVOL_DISK_MAPPING=:

   Note: Production_LVM_device should be mounted with source mount point. If MariaDB instance is mounted on /maria/data during backup, during this task also it should be on the same mount point.

   Arguments to the script:

   JOBID: <Simple mount job-id>
   
   OSUSER: <MariaDB OS user>
   
   DBUSER: <MariaDB database user, if empty consider as root>
   
   DBPASSWORD: <MariaDB database user's password>
   
   BASEDIR: <MariaDB home location>
   
   MARIADB_CNF: Target database configuration file with absolute path
   
   PORT: <MariaDB instance port>
   
   SOCKET_FILE: <MariaDB instance's socket file>
   
   CONFIG_FILE: <MariaDB instance's config file>
   
   BEGIN_TIME: <LVM backup begin time (Format: "YYYY-MM-DD HH24:MI:SS")>
   
   UNTIL_TIME: <Recovery time (Format: "YYYY-MM-DD HH24:MI:SS")>
   
   LOG_BKP_MNTPT: <Log backup mount point name> i.e. /mmTST_archivelog
   
   DATAVOL_DISK_MAPPING: Colon separated list of <mount_point>:< production host lvm device name>
   

   Example:

   /act/custom_apps/mariadb/lvm_migrate/ACT_MARIADB_lvm_migrate.sh JOBID=Job_0377678 OSUSER=maria DBUSER=root DBPASSWORD=xxxx BASEDIR=/home/maria/app/mariadb/product/mariaHome_10.3.9 MARIADB_CNF=/act/mnt/Job_12859112_mountpoint_1689356128423/lvmdata/mysqld-auto.cnf PORT=3307 SOCKET_FILE=/home/maria/app/mariadb/admin/mariadb_3307/socket/maria_3307.socket CONFIG_FILE=/home/maria/app/mariadb/admin/mariadb_3307/mariadb_3307.cnf BEGIN_TIME="2020-02-12 21:08:27" UNTIL_TIME="2020-02-12 21:10:00" LOG_BKP_MNTPT=/mmTST_archivelog DATAVOL_DISK_MAPPING=/mmTST/mariadb_3307:/dev/mapper/vg1-m7

   MySQL

   Script name: ACT_MYSQL_lvm_migrate_newTarget

   Script location: /act/custom_apps/mysql/lvm_migrate/

   sh /act/custom_apps/mysql/lvm_migrate/ACT_MYSQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING= <Backup DR MountPoint>:<target LVM device> BASEDIR= <BASEDIR>< /var> DBUSER= <DBUSER> DBPASSWORD= <DBPASSWORD> OSUSER= <OSUSER> PORT= <PORT> JOBID= <JOBID>
   

   Arguments to the script:

   DATAVOL_DISK_MAPPING = Comma-separated list of <BackupDR_mount_point>:<equivalent target host LVM device name>

   BASEDIR = Target host MySQL home location, which was given during application aware mount

   DBUSER = Target instance DB username, which was given during application aware mount

   DBPASSWORD = Target instance password, which was given during application aware mount

   OSUSER = Target database OS user for MySQL, which was given during application aware mount

   PORT = Target instance port number, which was given during application aware mount

   JOBID = Backup DR job name (from the AppAware mount)

   Example:

   /act/custom_apps/mysql/lvm_migrate/ACT_MYSQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/chdb/data_1:/dev/mapper/act1581111994981_1581485847546-act_staging_vol,/chdb/log_1:/dev/mapper/act1581111994981_1581485847590-act_staging_vol DBUSER=root DBPASSWORD=password OSUSER=mysql PORT=3434 BASEDIR=/install/mysql-advanced-5.7.26-linux-glibc2.12-x86_64 JOBID=Job_0070633
   

   PostgreSQL

   Script name: ACT_POSTGRESQL_lvm_migrate_newTarget

   Script location: /act/custom_apps/postgresql/restore/

   Script:

    /act/custom_apps/postgresql/restore/ACT_POSTGRESQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=<Backup and DR_Mount>:<Production_LVM_device> BASEDIR=<BASEDIR> OSUSER=<OSUSER> PORT=<PORT> DBUSER=<DBUSER> DBPASSWORD=<DBPASSWORD> JOBID=<JOBID>
   

   Arguments to the script:

    DATAVOL_DISK_MAPPING = Comma separated list of <Backup and DR_mount_point>:<equivalent target host lvm device name>
   
    BASEDIR = Target instance PostgreSQL home location, which was
    given during application aware mount
   
    OSUSER = Target database osuser for PostgreSQL, which was given
    during application aware mount
   
    PORT = Target instance port number, which is given during appaware mount,
    which was given during application aware mount
   
    DBUSER = Target instance db username, which was given during
    application aware mount
   
    DBPASSWORD = Target instance password, which was given during
    application aware mount
   
    JOBID = Backup and DR Service job id (AppAware mount). To learn the job name
    use Monitor > Jobs.
   

   Example

   /act/custom_apps/postgresql/restore/ACT_POSTGRESQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/chtst/pgData10.3:/dev/mapper/actdevdatapg103_1594980385483 act_staging_vol BASEDIR=/home/postgres/postgresql_home_10.3 OSUSER=postgres PORT=6010 DBUSER=postgres JOBID=Job_0957580
   

   SAP ASE

   Script name: ACT_SYBASE_lvm_migrate_newTarget

   Script location: /act/custom_apps/sybase/lvm_migrate/

   Script:

     /act/custom_apps/sybase/lvm_migrate/ACT_SYBASE_lvm_migrate_newTarget.sh
     DATAVOL_DISK_MAPPING=<DATAVOL_DISK_MAPPING>
     TARGET_SERVER_NAME=<TARGET_SERVER_NAME>
     TARGET_DB_USER=<TARGET_DB_USER> TARGET_DBUSER_PASSWD=<TARGET_DBUSER_PASSWD>
     TARGET_DBNAME_LIST=<TARGET_DBNAME_LIST> JOBID=<JOBID>
   

   Arguments to the script:

     DATAVOL_DISK_MAPPING = Comma separated list of <Backup and DR_mount_point>:<equivalent target host logical volume manager device name>
   
     TARGET_SERVER_NAME = Target ASE server name
   
     TARGET_DB_USER = Target instance db username
   
     TARGET_DBUSER_PASSWD = Target instance password
   
     TARGET_DBNAME_LIST = Comma separated list of <source_db_name>:<Target_db_name> </br>
     //Can be found in /var/act/log/customapp-sybaseinstance.log
   
     JOBID = Backup and DR Service mount job id
   

   Note: Target logical volume manager devices should be empty.

   Example:

   /act/custom_apps/sybase/lvm_migrate/ACT_SYBASE_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/mntNT/log/CU1:/dev/mapper/vg2-lv2,/mntNT/data/CU1:/dev/mapper/vg2 lv1 TARGET_SERVER_NAME=ASE1 TARGET_DB_USER=sa TARGET_DBUSER_PASSWD=sybase TARGET_DBNAME_LIST=CU1:SU2 JOBID=Job_12345

   SAP IQ

   Script name: ACT_SYBASEIQ_lvm_migrate_newTarget

   Script location: /act/custom_apps/sybaseiq/lvm_migrate

   Script:

   /act/custom_apps/sybaseiq/lvm_migrate/ACT_SYBASEIQ_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=: newDBNAME= DBA_USER= DBA_PASSWD= JOBID= [ NSTMNT_CHECK=TRUE ] [ PORTNO= ] [ DBFILE_LOC= ]

   Arguments to the script:

   JOBID = Application aware mount Job ID

   NSTMNT_CHECK = Specify TRUE to continue migration if nested mounts are involved.

   PORTNO = Port number on which the target database needs to start. By default SAP IQ starts the database at random available port

   DBFILE_LOC = Location for target db catalog file, dblog and iqmsg file. By default catalog file and iqmsg files are on same location, dblog file creates at the catalog file's locations

   Example:

   /act/custom_apps/sybaseiq/lvm_migrate/ACT_SYBASEIQ_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/mr/iqlog:/dev/mapper/vg3-log,/mr/iqdata:/dev/mapper/vg3-data newDBNAME=MR DBA_USER=act DBA_PASSWD=passwd JOBID=Job_123456 NSTMNT_CHECK=TRUE PORTNO=2700 DBFILE_LOC=/home/sybaseiq/chdb

   SAP MaxDB

   Script name: ACT_MAXDB_lvm_migrate_newTarget

   Script location: /act/custom_apps/maxdb/lvm_migrate/

   Script:

   /act/custom_apps/maxdb/lvm_migrate/ACT_MAXDB_lvm_migrate_newTarget.sh OSUSER= DBSID= DBUSER= DBPASSWORD= JOBID= LOCAL_PRG_PATH= DATAVOL_DISK_MAPPING=:

   Arguments to the script:

   OSUSER = Target database's owner (The one provided in the previous mount step)

   DBSID = Target database name (The one provided in the previous mount step)

   DBUSER = Target database DBM username (The one provided in the previous mount step)

   DBPASSWORD = Target database DBM user password (The one provided in the previous mount step)

   JOBID = Backup and DR Service mount job ID which ran in the previous step.

   LOCAL_PRG_PATH = Directory path of MaxDB binaries (The one provided in the previous mount step)

   DATAVOL_DISK_MAPPING = Comma separated list of :

   Example:

   /act/custom_apps/maxdb/lvm_migrate/ACT_MAXDB_lvm_migrate_newTarget.sh OSUSER=sdb DBSID=DEMODB DBUSER=dbm DBPASSWORD=password JOBID=Job_0377678 LOCAL_PRG_PATH=/opt/sdb/MaxDB DATAVOL_DISK_MAPPING=/mmTST/maxdbdata:/dev/mapper/vg1-m7

The output is similar to this:

    INFOMSG: pvmove starting ......................
    + pvmove
      /dev/sdi: Moved: 47.07%
      /dev/sdi: Moved: 70.43%
      /dev/sdi: Moved: 93.83%

Once the job is successful, the data moves to the local production storage from backup/recovery appliance-provisioned disks while the database is running. You can validate that the file system for the database created by the mount should now be on a local logical volume rather than the logical volume presented by the mount by running the df command.

1. Once the job is successful, the data is moved to the local production storage from disks provisioned from the backup/recovery appliance while the database is running.
2. Go to the management console and perform Unmount+Delete.
3. Re-enable the backup plan to trigger the scheduled jobs.

Mount and migrate to a new instance

To mount a database image as a virtual database and then migrate it to a new target, perform an application aware mount as detailed in Mount a virtual database from a volume-level backup image.

Note: Enable both Create New Virtual Application and Manage New Application.

Migrate the data

The prerequisites for migrating data are listed below:

• The local target host device should not be in use by another process such as a running database since it needs to be taken offline or online at the start of the pvmove process.
• Make sure the size of target host logical volume manager device is equal to or more than BackupDR_mount_point size.
• Make sure /etc/fstab has the /dev/mapper entries for production data and log volumes.
• Use the df command to learn the Backup DR mount point.
• To learn which target logical volume manager devices are available use the lvdisplay command. You need to specify the full logical volume path.
• To learn the job name use Monitor > Jobs.
• All other values should be the same as those used during the mount.

1. Once the mount is completed, run the ACT_<database type>_lvm_migrate_newtarget script with the parameters in arguments to the script.

   IBM Db2

   Script name: ACT_DB2_lvm_migrate_newtarget.sh

   Script location: /act/custom_apps/db2/restore/

   Script:

   /act/custom_apps/db2/restore/ACT_DB2_lvm_migrate_newtarget.sh SOURCE_INSTANCE TARGET_DBNAME_LIST= JOBID= DATAVOL_DISK_MAPPING=: ARCHIVELOG_LOC=

   Arguments to the script:

   SOURCE_INSTANCE = <DB2 instance name>

   TARGET_DBNAME_LIST = <comma separated list of database names>

   JOBID = <Simple mount job-id>

   ARCHIVELOG_LOC = <Log backup mount point name>(mount point should be in local storage)

   DATAVOL_DISK_MAPPING = Colon-separated list of <Backup and DR_mount_point>:<production host lvm device name>

   Example:

   /act/custom_apps/db2/restore/ACT_DB2_lvm_migrate_newtarget.sh SOURCE_INSTANCE=db2prod TARGET_DBNAME_LIST=TEST1,TEST2 JOBID=Job_4488748 ARCHIVELOG_LOC=/db2gj_archivelog DATAVOL_DISK_MAPPING=/db2gj/db2/data:/dev/mapper/vg00 vol_data,/db2gj/db2/log:/dev/mapper/vg01 vol_log

   MariaDB

   Script name: ACT_MARIADB_lvm_migrate_newTarget.sh

   Script location: /act/custom_apps/mariadb/restore/

   Script:

   /act/custom_apps/mariadb/lvm_migrate/ACT_MARIADB_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=: BASEDIR= DBUSER= DBPASSWORD= OSUSER= PORT= JOBID=

   Arguments to the script:

   DATAVOL_DISK_MAPPING = Comma-separated list of <mount_point>:<equivalent target host lvm device name>

   BASEDIR = Target host MariaDB home location

   DBUSER = Target instance db username

   DBPASSWORD = Target instance password

   OSUSER = Target database osuser for MariaDB

   PORT = Target instance port number, which is given during application aware mount

   JOBID = management console job id of the virtual mount

   Example:

   /act/custom_apps/mariadb/lvm_migrate/ACT_MARIADB_lvm_migrate_newTarget.sh JOBID=Job_1266533 DBUSER=root DBPASSWORD= BASEDIR=/install/maria OSUSER=maria PORT=3434 DATAVOL_DISK_MAPPING=/chdb/data1:/dev/mapper/vgnew-mariaData

   MySQL

   Script name: ACT_MYSQL_lvm_migrate_newTarget.sh

   Script location: /act/custom_apps/mysql/restore/

   Script:

   /act/custom_apps/mysql/lvm_migrate/ACT_MYSQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=<Backup DR MountPoint>:<target LVM device> BASEDIR=<BASEDIR> DBUSER=<DBUSER> DBPASSWORD=<DBPASSWORD> OSUSER=<OSUSER> PORT=<PORT> JOBID=<JOBID>
   
   Arguments to the script:
   
   DATAVOL_DISK_MAPPING=Comma separated list of `<BackupDR_mount_point>:<equivalent target host lvm device name>`
   
   BASEDIR=Target host MySQL home location
   
   DBUSER=Target instance db username
   
   DBPASSWORD=Target instance password
   
   OSUSER=Target database osuser for MySQL
   
   PORT=Target instance port number, which is given during appaware mount
   
   JOBID=Backup and DR Service job id (AppAware mount)
   

   Example:

   /act/custom_apps/mysql/lvm_migrate/ACT_MYSQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/chdb/data_1:/dev/mapper/act1581111994981_1581485847546-act_staging_vol,/chdb/log_1:/dev/mapper/act1581111994981_1581485847590-act_staging_vol DBUSER=root DBPASSWORD=password OSUSER=mysql PORT=3434 BASEDIR=/install/mysql-advanced-5.7.26-linux-glibc2.12-x86_64 JOBID=Job_0070633

   PostgreSQL

   Script name: ACT_POSTGRESQL_lvm_migrate_newTarget.sh

   Script location: /act/custom_apps/postgresql/restore/

   Script:

    /act/custom_apps/postgresql/restore/ACT_POSTGRESQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=<Backup and DR_Mount>:<Production_LVM_device> BASEDIR=<BASEDIR> OSUSER=<OSUSER> PORT=<PORT> DBUSER=<DBUSER> DBPASSWORD=<DBPASSWORD> JOBID=<JOBID>
   

   Arguments to the script:

    ```
    DATAVOL_DISK_MAPPING = Comma separated list of `<Backup and DR_mount_point>:<equivalent target host lvm device name>`
   
    BASEDIR = Target instance PostgreSQL home location, which was
    given during application aware mount
   
    OSUSER = Target database osuser for PostgreSQL, which was given
    during application aware mount
   
    PORT = Target instance port number, which is given during appaware mount,
    which was given during application aware mount
   
    DBUSER = Target instance db username, which was given during
    application aware mount
   
    DBPASSWORD = Target instance password, which was given during
    application aware mount
   
    JOBID = Backup and DR Service job id (AppAware mount). To learn the job name
    use Monitor > Jobs.
    ```
   

   Example:

   /act/custom_apps/postgresql/restore/ACT_POSTGRESQL_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/chtst/pgData10.3:/dev/mapper/actdevdatapg103_1594980385483 act_staging_vol BASEDIR=/home/postgres/postgresql_home_10.3 OSUSER=postgres PORT=6010 DBUSER=postgres JOBID=Job_0957580
   

   SAP ASE

   Script name: ACT_SYBASE_lvm_migrate_newTarget

   Script location: /act/custom_apps/sybase/lvm_migrate/

   Script:

   /act/custom_apps/sybase/lvm_migrate/ACT_SYBASE_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING= TARGET_SERVER_NAME= TARGET_DB_USER= TARGET_DBUSER_PASSWD= TARGET_DBNAME_LIST= JOBID=

   Arguments to the script

    DATAVOL_DISK_MAPPING = Comma-separated list of
    `<Backup and DR_mount_point>:<equivalent target host lvm device name>`
   
    TARGET_SERVER_NAME = Target ASE server name
   
    TARGET_DB_USER = Target instance db username
   
    TARGET_DBUSER_PASSWD = Target instance password
   
    TARGET_DBNAME_LIST = Comma separated list of
    <source_db_name>:<Target_db_name>
    //Can be found in /var/act/log/customapp-sybaseinstance.log
   
    JOBID = Backup and DR Service mount job id
   

   Note: Target lvm devices should be empty.

   Example:

   /act/custom_apps/sybase/lvm_migrate/ACT_SYBASE_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/mntNT/log/CU1:/dev/mapper/vg2-lv2,/mntNT/data/CU1:/dev/mapper/vg2-lv1 TARGET_SERVER_NAME=ASE1 TARGET_DB_USER=sa TARGET_DBUSER_PASSWD=sybase TARGET_DBNAME_LIST=CU1:SU2 JOBID=Job_12345

   SAP IQ

   Script name: ACT_SYBASEIQ_lvm_migrate_newTarget

   Script location: /act/custom_apps/sybaseiq/lvm_migrate

   Script:

   /act/custom_apps/sybaseiq/lvm_migrate/ACT_SYBASEIQ_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=: newDBNAME= DBA_USER= DBA_PASSWD= JOBID= [ NSTMNT_CHECK=TRUE ] [ PORTNO= ] [ DBFILE_LOC= ]

   Arguments to the script:

   JOBID = App-Aware mount Job ID
   
   NSTMNT_CHECK = Specify TRUE to continue migration if nested mounts are involved. 
   
   PORTNO = Port number on which the target database needs to start. By default SAP IQ starts the database at random available port
   
   DBFILE_LOC = Location for target db catalog file, dblog and iqmsg file. By default catalog file and iqmsg files are on same location, dblog file creates at the catalog file's locations
   

   Example:

   /act/custom_apps/sybaseiq/lvm_migrate/ACT_SYBASEIQ_lvm_migrate_newTarget.sh DATAVOL_DISK_MAPPING=/mr/iqlog:/dev/mapper/vg3-log,/mr/iqdata:/dev/mapper/vg3-data newDBNAME=MR DBA_USER=act DBA_PASSWD=passwd JOBID=Job_123456 NSTMNT_CHECK=TRUE PORTNO=2700 DBFILE_LOC=/home/sybaseiq/chdb

   SAP MaxDB

   Script name: ACT_MAXDB_lvm_migrate_newTarget

   Script location: /act/custom_apps/maxdb/lvm_migrate/

   Script:

   /act/custom_apps/maxdb/lvm_migrate/ACT_MAXDB_lvm_migrate_newTarget.sh OSUSER= DBSID= DBUSER= DBPASSWORD= JOBID= LOCAL_PRG_PATH= DATAVOL_DISK_MAPPING=:

   Arguments to the script:

   OSUSER = Target database's owner (The one provided in the previous mount step)
   
   DBSID = Target database name (The one provided in the previous mount step)
   
   DBUSER = Target database DBM username (The one provided in the previous mount step)
   
   DBPASSWORD = Target database DBM user password (The one provided in the previous mount step)
   
   JOBID = Backup and DR Service mount job ID which ran in the previous step.
   
   LOCAL_PRG_PATH = Directory path of MaxDB binaries (The one provided in the previous mount step)
   
   DATAVOL_DISK_MAPPING = Comma-separated list of
   <Backup and DR_mount_point>:<equivalent target host lvm device name>
   

   Example:

   /act/custom_apps/maxdb/lvm_migrate/ACT_MAXDB_lvm_migrate_newTarget.sh OSUSER=sdb DBSID=DEMODB DBUSER=dbm DBPASSWORD=password JOBID=Job_0377678 LOCAL_PRG_PATH=/opt/sdb/MaxDB DATAVOL_DISK_MAPPING=/mmTST/maxdbdata:/dev/mapper/vg1-m7

2. Once the job is successful, the data is moved to the local production storage from disks provisioned from the backup/recovery appliance while the database is running. Go to the management console and perform an Unmount+Delete.