DB Refresh using HANA Studio DB Restore
with SID Modification - NON SAPinst
The DB restoration option in HANA Studios, followed by hdbuserstore, makes the
entire system transfer process a lot easier. The target schema would still be the
source, which is the only restriction.
The purpose of this blog is to demonstrate how to perform a simple homogenous
system copy of a HANA-based system using HANA Studio to restore the source
backup on the destination HANA DB.
In this scenario, we'll look at transferring a Prod backup and refreshing it in an
already operational quality system.
These are the salient steps involved in achieving this
Step 1 ) Take a complete DB backup of the source Database
Step 2) Move the database backup to the Target system
Step 3) Using HANA Studio recover the source db in the target HANA box
Step 4) Supply the license text so that the HANA Studio can automatically apply the
license after install
Step 5) Modification of Schema access at the target DB
Step 6) Modify the default key using the hdbuserstore on the application servers and DB
instance.
Step 7 ) Start sap
Step 8 ) Post activities.
Activities in the Source System:
Step 1 - Backup of the source DB .
Use the HANA studio backup studio to take a complete DB backup either at the disk
level or using Backint.
Normally, this should suffice to do a DB Refresh, but if you're looking for a point-in-
time recovery, you may want to add the backups from the log area as well.
Step 2 ) : Move the database backup to the Target system
Once the backup is complete, you'll need to move it to a target system directory. You
should have four unique files with your backup prefix. The prefix in this example is
“COMPLETE DATA BACKUP 20122015.”
Activities in the Target system
Step 3 ) Using HANA Studio recover the source db in the target HANA box
→ Shutdown SAP Application alone
→ Open HANA Studio and right click on the SID ( target) where you want to perform
the recovery.
You will have to specify the destination location and the Backup Prefix for the HANA
studio to recognize the backups .
You can use the option “Initialize Log Area” if you only have a complete data backup
and do not intend to recover log segments... This is similar to how Oracle resets
logs.
Step 4) Supply the license text so that the HANA Studio can automatically apply the
license after install
Your existing HANA Licensing will be invalid after the recovery, thus this is a good
time to provide the licence text so that it may be installed automatically. If not, this
can be done later by hand.
STEP 5) Continue on with the recovery. Please keep in mind that the configuration of
the target and source versions must be same. Is there any setting in the target
system that needs to be done manually as part of the Post steps?
Following recovery, you should be able to see the Memory and Host Details in HANA
Studio's Overview tab.
You could expect to see all of the schemas under Catalog, but it will fail as seen
below. When you try to expand Content, the same thing happens.
The reason for this is that the new SID will most likely be looking for a schema
named SAPSID and will be unable to identify one, necessitating a few adjustments in
the target system.
Step 6) On the application servers and the DB instance, change the default key
hdbuserstore.
Go to /usr/sap/<SID>/hdbclient and execute the below
hdbuserstore set default <dbhost>:<dbport> <dbuser> <dbpassword>
Let's say our target host is host01, the source SID is PRD, the system number is 00,
and the source schema is SAPPRD with the password sapprd#!
hdbuserstore set default host01:30015 SAPPRD sapprd#!
The above example is for the Unix system for Windows its a bit different (Refer SAP
Note 1709838)
Execute a hdbuserstore list you should find the new Key set as below
KEY DEFAULT
ENV:host01:30015
User: SAPPRD
This confirms that the key is set .
This has to be done on the appservers , else R3trans -d would fail.
Return to HANA Studio, and the contents should be visible
under Catalog and Contents. Under Catalog, you should also
discover the source Schema.
Before we start the apps on the target system, there is one
more thing that needs to be done.
Modify the /dbs/hdb/schema to SAPPRD ( or whatever your source schema is ) in
the DEFAULT profiles.
You are now ready to begin using SAP.
From then, proceed with the regular Post Refresh operations.
A few things to keep in mind
- > Before starting SAP, you may want to disable the btc processes. - > Perform
typical post actions like SE06/STMS/BDLS, as well as activities particular to your
situation.
SAP HANA system copy Procedure- Below is the HANA
System copy using Recovery method from PRD to QAS using
Hana Studio
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 application Server:
o Modify the default key hdbuserstore on the application servers and the DB instance.
Go to /usr/sap/<SID>/hdbclient and execute the belowhdbuserstore set default
<dbhost>:<dbport> <dbuser> <dbpassword>
o Unlock the SAP<SID> and DBACOCKPIT ids in HANA DB.
o Change the /dbs/hdb/schema parameter value to <Source schema value> in RZ10
DEFAULT.PFL
o 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.
