DB Refresh Using HANA Studio DB Restore With SID Modification - NON SAPinst
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
Use the HANA studio backup studio to take a complete DB backup either at the disk level or using Backint.
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.”
Step 3 ) Using HANA Studio recover the source db in the target HANA box
→ 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.
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.
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#!
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
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.
- > 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.