Slow impact SMP 2.3 system copy

[Former Member]

Hi,

we had a two layer (DEV+PROD) SMP 2.3 system landscape based on Windows/Sybase (SQLAnywhere).

We would perform a CRM system copy (backup+restore) for our backend system to refresh DEV from PROD.

Our AM dept. asked us to align SMP DEV system too.

Is there any smooth safe way to align SMP (DEV from PROD)  data without copying the entire DATABASE tier Windows box (and then act post installation steps).

We would like to mainain all configurations/secutiry parameters and update CDB DATA only.

Another suitable way for us would be to drop the CDB (only data) and then launch an initial download from copied DEV backend.

Many Thanks,

Alessandro Potenziani

[Former Member]

OK.

And how to refresh CacheDB?

Our Rex consultant told us that there is an initial download procedure (to reload data from backend CRM system) but he said that in this way we got duplicates.

[Kevin_SAP]

Copying the Consolidated Database (CDB) between different environments or even different servers in the same environment isn't supported.

Regards,

Kevin

[Former Member]

I read this onto administration guide...

But the point is: what we have to do after a backend system-copy (SAP CRM) to maintain the SMP infrastructure aligned?

BR,

Alessandro

[Kevin_SAP]

Is this DOE or Agentry?

Regards,

Kevin

[Kevin_SAP]

Or REX?

[Former Member]

is a Rex

[Kevin_SAP]

REX is just a JCO connection in SMP.  The concern is when you move an existing connection to a different target, it may be out of sync with the Cache database.

[Former Member]

OK.

And how to refresh CacheDB?

Our Rex consultant told us that there is an initial download procedure (to reload data from backend CRM system) but he said that in this way we got duplicates.

[Kevin_SAP]

You probably would need to delete the REX package in SMP before switching to a different CRM and redeploy REX package also.  Clients would have to reregister or unsubscribe/subscribe.  Something you should test before doing it in production.