Ansicht
Dokumentation
09933 - Refresh of TST SID's with Production over 400gb
ROGBILLS - Synchronize billing plans CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Refresh of TST SID's with Production over 400gb
Hi Doreen,I did some investigating on this myself. Our database just crossed
the 600 gig mark so it's getting expensive to do copies. I had
located a product to do master data only copies using only the
transport system. I figured this would allow us to do a full
export/import refresh of all our master data in about 5-8 hours
including export time from PRD (and use 10-15% of the space). That
was a projection based on a test using 875,000 customers and 275,000
material masters.
However, when it was presented to the team(s) they decided that the
traditional full database copy was the way we should go. It seemed
every group had at least one compelling reason that they wanted
all/part of the transactional data available. The ABAP team liked the
fact that the full copy re-syncs the programs and structures. The
functional teams like all the transactional data. The only team that
really would be OK with the master data only was the Variant Config
guy. The only benefit to the Basis team is that we will get a lot of
test data for archiving. 🙂
So we will continue using the full database copy. The next chance to
reconsider will be when we do the codepage conversion. That will
increase the disk cost by 60-70% for the database portion.
Our last database copy took about 8 hours to just restore the
database (including deleting the R3PRDDATA lib) and then a day or
two (part-time) running BDLS, redoing the transport system, cleaning
up the connections to BW and EBP, changing the outputs, stopping
faxing, stopping jobs, etc.
Craig.
--- In DoNotReply@consolut.eu, "Anderson, Doreen"
<dandersoZb...> wrote:
> 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]
Durban Tours - Südafrika Safari
ABAP Short Reference BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 3283 Date: 20240419 Time: 022430 sap01-206 ( 3 ms )
