Ansicht
Dokumentation
09811 - Refresh of TST SID's with Production over 400gb
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up CPI1466 during BackupThis documentation is copyright by SAP AG.
Refresh of TST SID's with Production over 400gb
Our team has not embraced the use of Infoshuttle from the perspective ofrebuilding an ENTIRE CLIENT.
One of our ABAP team members did rebuild a full client in DEV via data
back from Production using Infoshuttle - but he had to babysit the
process for 2 weeks and our project Manager can't afford to loose him as
a resource for that long of a period.
So, I'm probably going to try to take the Infoshuttle ball, seems like
noone minds Basis spending that kind of time.
Doreen
-----Original Message-----
From: stanley.mcpartlandZbently.com
[mailto:stanley.mcpartlandZbently.com]
Sent: Wednesday, April 09, 2003 9:41 AM
To: DoNotReply@consolut.eu
Subject: RE: Refresh of TST SID's with Production over
400gb
Hi Doreen,
Don't you have InfoShuttle? We getting ready to take another look at it
as
we start to roll R/3 out to other sites. We are a bit under 400GB now,
but
that may triple or more in the next couple of years. I concerned not
just
with DASD, but also with processor and memory as the database grows. I
expect that we will have to upgrade all 3 to maintain adequate
performance
during a system test. We are adding more DASD in the short term. If
you do
have InfoShuttle, what is preventing you from using it to refresh TST?
If anyone else has experience with InfoShuttle, I'd like to hear how you
are
using it.
Regards,
Stan
-----Original Message-----
From: Anderson, Doreen [mailto:dandersoZballhort.com]
Sent: Wednesday, 09 April, 2003 7:08 AM
To: DoNotReply@consolut.eu
Subject: Refresh of TST SID's with Production over 400gb
For those account whose Production Data library size is 400gb or
over......
Are you still supporting your teams by continuing to perform refreshes
of your TST SID via homogenous system copies back to TST?
We are just trying to see what others are doing to get more current data
into their TST systems.
Currently our Production DB library is 450gb and expectations are that
it will be 707gb by August of 2004 due to bringing additional European
sites up on SAP. The team is wanting a TST refresh in August 2004. At
what point are you saying that the disk needed to support this continued
effort is just too costly?
Any feedback is greatly appreciated
Doreen
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to
http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to
http://www.consolut.net
Durban Tours - Südafrika Safari
BAL Application Log Documentation rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4423 Date: 20240427 Time: 023239 sap01-206 ( 3 ms )
