SAP HANA Administration||SAP HANA System Copy Homogeneous Recovery Method Using HANA Cockpit& Studio

SAP HANA 2.0 certification was developed by SAP for technical administrators of SAP systems. Learn if you need to go for it and how to successfully pass it.
Any Queries ping me : sribasis6@gmail.com
Reach me :+919381803376
Certification Code :C_HANATEC_16 SAP Certified Technology Associate - SAP HANA 2.0 SPS 04
In This Video shows how to Perform SAP HANA System Copy- Homogeneous Recovery Method Using HANA Cockpit & Studio
Using SAP HANA cockpit, you can create a copy of an SAP HANA database by using backups of that database to recover to the same system or a different system.
Working in SAP HANA cockpit, follow the instructions on the screen. The actual sequence of steps that you perform depends on the specific options that you choose.
The options offered in SAP HANA cockpit are described in the sections below. To find out more about a set of options, expand its section.
Specify the Database to Copy To
Specify the Database Copy Type
Specify Whether to Use a Backup Catalog
Specify the Source System
Specify the Backup to be Used
Check the Availability of the Backups
Review Your Settings
Start the Database Copy
Result
A copy of the database is created in the location you specified.
When the database copy is completed, a message confirms this.
For a database copy to a point in time, SAP HANA cockpit shows the point in time to which the copy was made.
Note
The point in time that SAP HANA returns after a copy is the point in time of the last COMMIT to the database that has been copied.

For this reason, this point in time may be before the point in time that you specified for the copy.
To allow SAP HANA cockpit to connect to the copied database, you may need to change the credentials of the user that is registered in SAP HANA cockpit.
If you copied a tenant database
The copy of the SAP HANA database is now online and can be used by applications.
If you copied a system database
You now need to copy the tenant databases in the SAP HANA system.
The only difference between copying and moving a tenant database therefore is what happens to the original tenant database after all data has been transferred to the new tenant database in the target system.
In both cases, the new tenant database starts running as a fully separate, independent database.
Several tenant databases can be copied or moved to a system at the same time. It is also possible to copy or move a tenant database to a system with a different isolation level than the source system.
Use Cases for Copying and Movement of Tenant Databases
Copying and moving a tenant database from one system to another in this way has several applications.
Use Cases
● Load balancing between systems
For example, a tenant database is running a more demanding workload than anticipated,so you move it to a system running on a host with more CPU resources.
● Management of deployment environment
For example, you want to copy a tenant database running in your test system to the live production system.
● Tenant-database-specific upgrades
For example, you want to upgrade a single tenant database but not the entire system, so you move the tenant database to a system already running the higher version.
● Template databases
For example, you create a tenant database with a default configuration that you want to reuse as the basis for new tenant databases in other systems. You can simply copy the tenant database as a template to other systems.