----------------------------Backup/Restore for XSA on HANA-----------------------------
This Document explains about the steps for Backup-Restore Procedure when XS
Advanced is installed on Either SYSTEMDB/Tenant-DB of a HANA database.
→Some of the persistent data related to XS advanced is stored at the file-system level.
→XS Advanced can be installed on either of SYSTEMDB or Tenant-DB, usually on tenant
databases.
→Please make sure that the source and target databases have the same architecture.
(1) The target database can be of lower or equal version as compared to that of the
source database.
(2) Make sure that XSA installed on the target database is the same version as that of
the source database.
(3) Make sure that the XSA on the target database is upgraded to the level of source
version (At the time of backup) before enabling XSA after restoration.
→If you are planning to do a backup restore for an XSA installed database, make sure
to backup both SYSTEMDB and Tenant-DB and restore them as per the requirement.
Taking Backup on the Source system:
1) It is recommended to disable the XSA on the source system to prevent any
inconsistencies with the below command.
[XSA disable]
2) If there is no approved downtime, then the backup can be taken without disabling
XSA at the source system.
3) Backup the XSA content stored in the file system with execution of below
command with <sid>adm user
[XSA backup-fss]
This command will push the data from file system to the data backup being
triggered in next step for restore.
4) Backup the system database and all the respective tenant databases.
5) Enable the XSA with the below command if disabled in step 1.
[XSA Enable]
Restoring the backup on the Target system:
1) To avoid any issues/inconsistencies during restoration disable the XS advanced
application with the below command.
[XSA disable]
2) Now restore the backups of SYSTEMDB and subsequent tenant databases onto
the target system as per the requirement.
3) If XSA is installed on the tenant database in the source system then only the
tenant restoration can be done.
4) After the restoration is completed, execute the below command to load the data
from restored database to file-system.
[XSA restore-fss]
5) Once the command is executed successfully, XS advanced can be enabled with
the below command.
[XSA enable]
*******Some Important Pointers******
- All XSA commands are to be executed with <sid>adm user.
- XSA can be installed either on SYSTEMDB or Tenant-DB.
The restoration procedure depends upon the above mentioned factor.
- If the source database has XSA installed on SYSTEMDB then at the target side,
XSA can be enabled only when the SYSTEMDB and Tenant-DB restorations are
completed.
- If the source database has XSA installed on tenant-DB then at the target side,
XSA can be enabled after the tenant-DB restoration is completed.
- Make sure that you have the same version of XSA installed on the target
database or you upgrade it to the same as to that of the XSA version present
on the source system before at the time of backup.
-----Gopi Sai Teja Paruchuri

Restore).pdf

  • 1.
    ----------------------------Backup/Restore for XSAon HANA----------------------------- This Document explains about the steps for Backup-Restore Procedure when XS Advanced is installed on Either SYSTEMDB/Tenant-DB of a HANA database. →Some of the persistent data related to XS advanced is stored at the file-system level. →XS Advanced can be installed on either of SYSTEMDB or Tenant-DB, usually on tenant databases. →Please make sure that the source and target databases have the same architecture. (1) The target database can be of lower or equal version as compared to that of the source database. (2) Make sure that XSA installed on the target database is the same version as that of the source database. (3) Make sure that the XSA on the target database is upgraded to the level of source version (At the time of backup) before enabling XSA after restoration. →If you are planning to do a backup restore for an XSA installed database, make sure to backup both SYSTEMDB and Tenant-DB and restore them as per the requirement. Taking Backup on the Source system: 1) It is recommended to disable the XSA on the source system to prevent any inconsistencies with the below command. [XSA disable] 2) If there is no approved downtime, then the backup can be taken without disabling XSA at the source system. 3) Backup the XSA content stored in the file system with execution of below command with <sid>adm user [XSA backup-fss] This command will push the data from file system to the data backup being triggered in next step for restore. 4) Backup the system database and all the respective tenant databases. 5) Enable the XSA with the below command if disabled in step 1. [XSA Enable]
  • 2.
    Restoring the backupon the Target system: 1) To avoid any issues/inconsistencies during restoration disable the XS advanced application with the below command. [XSA disable] 2) Now restore the backups of SYSTEMDB and subsequent tenant databases onto the target system as per the requirement. 3) If XSA is installed on the tenant database in the source system then only the tenant restoration can be done. 4) After the restoration is completed, execute the below command to load the data from restored database to file-system. [XSA restore-fss] 5) Once the command is executed successfully, XS advanced can be enabled with the below command. [XSA enable] *******Some Important Pointers****** - All XSA commands are to be executed with <sid>adm user. - XSA can be installed either on SYSTEMDB or Tenant-DB. The restoration procedure depends upon the above mentioned factor. - If the source database has XSA installed on SYSTEMDB then at the target side, XSA can be enabled only when the SYSTEMDB and Tenant-DB restorations are completed. - If the source database has XSA installed on tenant-DB then at the target side, XSA can be enabled after the tenant-DB restoration is completed. - Make sure that you have the same version of XSA installed on the target database or you upgrade it to the same as to that of the XSA version present on the source system before at the time of backup. -----Gopi Sai Teja Paruchuri