Most Recent State: Used for recovering the database to the time as close as possible to the current time. For this recovery the data backup and log backup have to be available since last data backup and log area are required to perform the above type recovery.
Point in Time: Used for recovering the database to the specific point in time. For this recovery the data backup and log backup have to be available since last data backup and log area are required to perform the above type recovery.
Specific Data Backup: Used for recovering the database to a specified data backup. Specific data backup is required for the above type of recovery option.
- Specific Log Position: This recovery type is an advanced option that can be used in exceptional cases where a previous recovery failed.
Restrictions for Recovery
- A #SAP HANA database cannot be recovered to a #SAP HANA database with a lower software version. The #SAP HANA database software version used for the recovery must always be the same version or higher than the #SAP HANA database used to create the backup.
- There can be any number of hosts in the target system, provided that the number and type of services is identical in both the source and the target system.
- With #SAP HANA multi-tenant database containers, recovery using snapshots is not supported yet. Tenant databases can be recoverd via the relevant system database only.
- Note: if we are performing a recovery to different system - Target system and Source system must have the same configuration.IN Particular, the no.of DB services with their own persistence must be the same in both systems.
Prerequisites for Copying a Database Using Backup and Recovery:
The target database has sufficient disk space and memory.
- The target system should have at least the same amount of disk space as the source system. You can copy a database to machines from different vendors and with different hardware configurations, provided that both the source and target machines are compliant with the #SAP HANA appliance specifications.
- The target system can have any number of hosts, provided that the number and type of services is identical in both the source system and the target system.If desired, and if performance limitations are acceptable, a cloned database can be set up on a platform with less memory and CPU capacity and a different number of hosts.
- The target database must have the same number and types of services as the source database.If the source system has 17 worker nodes with one indexserver process running on each node, a target system with one node needs 17 indexserver processes.
- To change the number of indexserver processes in the target system (and the Backint settings, if you are using a third-party tool), a database user with the system privileges SERVICE ADMIN, INIFILE ADMIN, and BACKUP ADMIN is needed in the target system.
- For an #SAP HANA single-container system, you set the number and type of services in the target database using SQL. For this reason, the target database must be online.vFor an #SAP HANA multitenant database container, the number and type of services in tenant databases is set automatically during recovery.
Note
- For a database copy using storage snapshots, the number of hosts and the number and type of services assigned to each host must be the same for the source database and the target database, and the mountpoint IDs must be identical.
- For an #SAP HANA single container system and the system database in an #SAP HANA multitenant database container, you must have the logon credentials of the operating system user (<sid>adm). For an #SAP HANA multitenant database container, you need the authorization DATABASE ADMIN.
- Disable FULL SYNC Option Before Recovery
- If you are running system replication with replication mode SYNC and the FULL SYNC option enabled, the system will not start after a recovery, because no write operations are possible. To prevent this from happening, before you perform a recovery, manually disable the FULL SYNC option in global.ini.
- Take the backup of HANA PRD system
- Copy/Move the backup form PRD Host to QAS Host
- Ensure that QAS is having enough space for Backup.
- Login to Hana Studio of QAS system with ID “SYSTEM”.
- After Login to QAS system, go to Backup and recovery option
- From there select recover system option. Once you select this option database will shut down to process recovery.
- Once the system got shut down, recover screen will open. Kindly select the option based on your requirement. Since I am doing refresh from PRD to QAS with Data backup. I selected the Last option.
If you want to backup from the specific path where the data file is stored, select option “Specify backup without catalog”
- Now provide the backup path and the same backup prefix name there in the “Backup Data file”
Provide the New license key path or you can skip this option and you can update license after recovery.
- Make sure the backup file copied from the PRD system have proper permission of QAS system.
- Once the recovery completed successfully, the database will start automatically. Make sure all services are running in HANA DB.
Please follow below steps at the application Server:
- Modify the default key hdbuserstore on the application servers and the DB instance.
- Unlock the SAP<SID> and DBACOCKPIT ids in HANA DB.
- Change the /dbs/hdb/schema parameter value to <Source schema value> in RZ10 DEFAULT.PFL
- Try to check the R3tans –d in application server to establish a connection to the HANA DB, if the result is RC = 12. Analyse the trans.log file.
After changing all the things in Application server, start the SAP using cmd STARTSAP R3”.
- Next install the license key for application server and HANA if not installed during recovery.
- Once the #SAP system service started, kindly run the transaction to complete the post refresh activities SICK, SGEN, BDLS, RZ10, RZ12, SCOT, SOST do the changes.
- Call transaction SECSTORE.
- Choose “Execute” (F8).In the entries that are displayed, delete the entry /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light.In the entries that are displayed, delete the entry /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light.
- In transaction SE37, execute the function module RFC_PING with the destination NONE. If the system displays an error message, execute the function module RFC_PING again; the error message cannot appear a second time in this case.
No comments:
Post a Comment