How to do Client Copy (LOCAL/REMOTE), Client Export/Import Explained.

Copy the data from one client to another client called client copy.

There are three types of client copies exist in any SAP System.
1. Local Client Copy
2. Remote Client Copy
3. Client Export/Import

1.Local Client Copy:
To copy the data from one client to another client within the system called Local Client Copy.

Login to the Target client(100) with DDIC or sap*-->Execute SCCL-->Select the respective profile and source client-->Schedule the Background job

So, once the job client copy* got finished the respective data will be available in target client and you can check the log in SCC3.

2. Remote Client Copy:
To copy the data between the two different systems called Remote Client Copy. The remote client copy data should be less than the 1TB data and region should be same.

Pre-requisite Step: Establish the RFC connection b/w the two systems. If it is ABAP system create the ABAP RFC connection(3 Type RFC). Or if it is non-ABAP create the HTTP connection to External Server (G Type RFC).

Login to the Target System’s Target Client(100) with DDIC or sap*--> Execute SCC9-->Select the respective profile, source client and source destination i.e. 3 type or G type--> Schedule the Background job

3. Client Export/Import:
To copy the data between the two different systems called Client Export/Import Copy. But Client Export/Import should perform If the client Copy data more than the 1TB with different regions.
 
Pre-requisite Step: To perform the Client Export/Import both source and target systems should be in same transport directory.

Login to the source System with DDIC or sap*-->Execute SCC8-->Select the respective profile and Target System -->Schedule the Background job
Once you schedule the Background job for Client Export/Import then there will be three transport request created.
<SID>KO000<request no> – Cross – Client Data
<SID>KT000<request no> – Client – Specific Data
<SID>KX000<request no> – Client – Specific texts

Login to the Target System with DDIC or sap*-->Execute SCC7-->Import the TR

Notes:
1. Please don’t go with dialog mode while doing the Client Copy.
2. All the client Copies transactions start with SCC*.
SCCL – Local Client Copy
SCC9 – Remote Client Copy
SCC8 – Client Export
SCC7 – Client Import
SCC3 – To check the Client Logs
SCC5 – Client Deletion

How to check the stripes on the AWS HANA Database Server?

Striping the volumes helps to come over the limitations of the IOPS and throughput requirements on an EBS volume. It is always recommended to take advantage of performance improvement with the use of striped.

Pre-Read:-
Disk reads/sec + disk writes/sec = IOPS
Disk read bytes/sec + disk write bytes/sec = throughput

For example, if a single volume(/hana/data or /hana/log) has 250 MiB/s throughput capacity, having a stripe set across four volumes can deliver 250MiB*4 = 1000 MiB/s throughput. This will increase the read and write capacity which siginifcantly increases the performance of the HANA database. 
These four vloumes should be of same size and performance characterstics.

In SAP HANA benchmark testing, the best performance has been achieved using a 256 KB stripe size for data volumes and a 64 KB stripe size for log volumes.

Striping can be checked using the command -> lvs -o+lv_layout,stripes,stripe_size