cancel
Showing results for 
Search instead for 
Did you mean: 

TDMS sizing

Former Member
0 Kudos

Hello,

We are planning an implementation of TDMS, and I would like to know your experiences of the sizing of the systems, especially for:

1. The receiver: According to the Master Guide, when you setup the receiver for the first time, you start with a full copy of your production system, where data is being deleted from. Is that correct?

Our production DB is about 4TB, this would mean that we need 4TB free space on our receiver system too to start with.

2. The sender: When the data that's needed for the refresh is being read, it's saved in tables on your sender system. How much disk space should we foresee for that? A certain percentage? Does anyone have an exaple of how much space it took on your machine?

Thanks & Kind regards,

Nicolas

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Nicolas

1.

what will you to a Shell Creation or a TIM ?

He have on our system only 1.5 TB with normal SAP Standard reduction we have for only 1 year data 200 GB. If will start with a Shell Creation you need less of space.

2.

We have 10GB free space on production for us is it enough.

Hope it helps a little bit

cheers

Former Member
0 Kudos

Hi SAPERLE,

Thanks for your reply.

First we'll use TDMS to setup a test system with master data, which means we'll need a TIM.

But I was wondering if it's possible to create a shell first, and then use TDMS to get for example the data from last year out of our production system and load it in the test system.

Or do you need to start from a full copy of production and delete all irrelevant data?

Kind regards,

Nicolas

Former Member
0 Kudos

Hello

The basic requirement of TDMS before running TIM is that the repository on the sender and the receiver system should be identical and to achieve that we have two options -

first one is to copy the sender system to the receiver system and then run TDTIM (this is obsolete method because of the space drawback)

second method is to execute a shell package (TDSHL) between sender and receiver. Shell package is a enhanced form of system copy where only the repository gets copied and the application data is not copies (later on TDTIM is used to copy the application data). This is the modern and highly efficient way to synchronize the repository on the sender and receiver.

Best regards

Pankaj.

Former Member
0 Kudos

Hi Again

1. We start with SCC5 -> Mandant Copy ( with no data ) Copy Profile SAP_UCSV

2. After these we start MDC -> like 1 GB data or TIM 200 GB

Shell Creation like SAP Docu create a "DUMP" ( Image ) -> 600 MB we had never us !?

Cheers

Answers (0)