Refreshing our Development System Question!

[Former Member]

Hi All

I am looking to refresh our DEV ECC System with about 3 months worth of data, at their request. However they are concerned with the ammount of potential downtime there will be, if any.

However, my plan is to do the following, which should remove the possibility of any downtime:

Current DEV Client is 500, so I plan to transfer data into a new client 501 and once this is complete then they can use the new client rather than the older 500 client. So also as any changes they make are not client dependant, this should be ok for them.

Does this sound right?

Thanks in advance

Phil

[Former Member · Accepted solution]

Your approach sound fine but in this approach too you will need a receiver system downtime. Before actual data transfer TDMS will temporarily cleanup data of all the clients in the receiver system and then restore the data of all the clients expect the one to which the data transfer will happen. So during receiver deletion steps you will need a downtime on the receiver system.

Other little better approach (from receiver downtime perspective) could be create a new SAP system all together (may be in the same box install a new instance) by using TDMS Shell and then time based data transfer. This way your team may keep using the current dev system and once the new system is set up they may move on to it. This is just a suggestion and i dont know if this is really an option for you or not.

I hope this info helps.

[Former Member · Accepted solution]

Thanks for the help.

However I do have one question, when you say: "Before actual data transfer TDMS will temporarily cleanup data of all the clients in the receiver system" I am assuming that this will have not effect on development changes and is purely the data only?

Thanks again Pankaj

[Former Member · Accepted solution]

Yes you are right only data, no repository objects are affected.