SAP HANA SYSTEM REFRESH
(HANA STUDIO)
> PRE-STEPS:
Sl. No. STEPS
Before starting the refresh process, ensure that you have a backup of both the
1. source and target systems.
This is crucial to prevent data loss in case of any issues during the refresh.
Copy backup file to target system and ensure that the target system is shut
2. down or set to a restricted mode where no users can access it during the
refresh.
3. Take export of user master and authorizations (SAP_USER) in all the clients.
>> Take Screenshots of:
Client settings (SCC4)
Logon groups (SMLG)
Processing groups (RZ12)
AL11, SE03, SM61, DBACOCKPIT, SMQR, SMQS, RZ70
4. Printer details (SPAD)
Operation modes (RZ03, RZ04 and SM63)
RFCs (SM59)
Partner profiles (WE20) and ports (WE21)
Logical systems (BD54)
Services that are active (SICF)
E070L table, settings of SCOT
These screenshots are to be captured because after system refresh, we need
to check and maintain the same settings in target system.
>> As part of pre-refresh steps, we need to take backup of target system.
(Post refresh, we need only transactional data, but we get all the
configurations of source to target system).
Create TOC in target for RFC tables export like:
RFCATTRIB, RFCDES, RFCDOC, RFCSYSACL, RFCDESSECU, RSECTAB,
RSECACTBAT, RFCDEST…
Include all the above tables details in the transport request.
5. Make sure to release this transport before the refresh starts. Otherwise, the
cofile and datafile will not be generated and you will not be able to import
this transport later. If we can’t import request, then we may have to
create/maintain all these configurations manually which will be tedious and
complex task.
6. Take backup of the profile directory.
Take export of certificates and license.
Take copy of SEC directory.
Take HDBUSERSTORE details from OS level.
>> Check source system backup size.
>> Check kernel and oracle version of source and target.
7. >> Check all the process running in target system and start after refresh
>> Check and resize the file systems before performing restore.
> REFRESH ACTIVITY:
Sl. No. STEPS
1. Take source system backup. (ex: PRD)
2. Open HANA Studio and logon.
>> Right click on the system db (SID of target)
3. >> Backup & Recovery
>> Recover tenant db (which is used for restoring).
4. Specify tenant database and click on next.
5. Specify recovery type.
>> Select recover the db to a specific data backup.
6. Specify backup location.
>> Recover without backup catalog & click on next.
7. Specify the backup to recover.
>> Location: - Select the location of the folder (in target system) where the
source system backup is copied.
>> Take recovery of the source backup in target and click on next.
>> The refresh starts & backup will be restored.
> POST REFRESH ACTIVITIES:
Sl. No. STEPS
1. Disable batch processing by setting batch work processes as 0 at OS level.
2. Start SAP system and login with SAP* user.
Install SAP license.
3. >> SAP license key can be requested from Service Marketplace from the
following link:
"http://service.sap.com/licensekey
Prevent batch job from running.
4. >> To hold the jobs to prevent from execution, we need to set the status of
those jobs from “Released” to “Scheduled” using SM37.
5. Delete or recreate TMS for target system using SE06.
6. Import user master for all clients (which was done as part of pre-refresh
steps).
7. Import transports related to AL11, SE03, SMLG, RZ12, SM59, SALE and SM69
backup (which was done in pre-refresh steps).
Execute BDLS transaction.
>> In BDLS Conversion, Production Logical System Name is changed to Quality
Logical System Name.
8. Example:
If we are doing refresh from PRD Client 970 to QAS Client 970 then we need
to run BDLS for
PRDCLNT970 –> QASCLNT970
9. Delete old SAP profiles and import new profiles using RZ10 transaction.
10. Perform spool consistency check in SP12 T – Code.
11. Delete old update records using SM13 transaction.
12. Delete/Reorganize transactional RFC’s using SM58 transaction.
13. Delete batch job logs by executing RSBTCDEL report using SE38 transaction.
14. Delete Old spool requests by executing RSPO0041 report using SE38
transaction.
15. Create/modify necessary partner profiles using WE20 transaction.
16. Modify necessary ports using WE21 transaction.
17. Perform mail configuration using SCOT transaction.
18. Delete old mail related entries using SOST transaction.
19. Execute SGEN transaction or run RSGENINVLAS report (no variant is required)
using SE38.
20. Make necessary services active through SICF transaction.
