Re: [sap-basis] client export from prd to dev
Posted by
Admin at
Share this post:
|
0 Comments
Posted by Jerry Berry (SAP Basis/Security/Archiving/Database Administrator) on Apr 29 at 10:14 AM | Mark as helpful |
What I would do is this. Create a QAS System as a System Copy of Production. Then put it in your landscape between your DEV and PRD boxes. THEN, you can test with Production data in your QAS System without disturbing development in DEV and leaving Production alone. This the according to "Best Practices" for SAP.
Good Luck
From: D. Caddick via sap-basis <sap-basis@Groups.ITtoolbox.com>
To: Jerry Berry <gdb758@yahoo.com>
Sent: Thu, April 29, 2010 7:10:07 AM
Subject: RE: [sap-basis] client export from prd to dev
Posted by D. Caddick (SAP NetWeaver/BASIS Consultant)
on Apr 29 at 7:08 AM Mark as helpful
Hi Shashi,
This is terrible, You should NEVER allow direct update in PRD. The changes
should always take place in the DEV system. Your Development team should be
creating their own test data, it is still not a good idea to copy PRD into a
Development client.
Regards
From: shashi via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
Sent: 29 April 2010 08:58
To: D. Caddick
Subject: Re: [sap-basis] client export from prd to dev
Posted by shashi (Basis Admin)
on Apr 29 at 3:59 AM
<http://it.toolbox.com/api/ContentVote/3470849/1/1/> Mark this reply as
helpfulMark as helpful
Hi Caddick,
We have 2 system landscape.
what i mean is
Many of the changes done directly in production . If some one want to test
in development that data is not available.
so i am planing this client export
Regards
Shashi
On Thu, Apr 29, 2010 at 12:31 PM, D. Caddick via sap-basis <
sap-basis@groups.ittoolbox.com> wrote:
> Posted by D. Caddick(SAP NetWeaver/BASIS Consultant)
> on Apr 29 at 3:34 AM
> Hi Shashi,
>
>
>
> You are correct. It is not considered a "Best Practice" to copy Production
> data to Development.
>
> 1. Data Protection/Security issues.
>
> 2. Too much data in Dev for development testing
>
>
>
> What do you mean by "Here development is not maintaining."?
>
>
>
> However you explanation of the Export is correct.
>
>
>
> Regards
>
>
>
> From: shashi via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
> Sent: 29 April 2010 06:53
> To: D. Caddick
> Subject: [sap-basis] client export from prd to dev
>
>
>
>
>
>
>
>
> Posted by shashi (Basis Admin)
> on Apr 29 at 2:02 AM
>
>
>
> Dear all,
> As i am new to this project here i am facing different issues. Here
> development is not maintaining. Every time our abapers asking to transport
> program from dev to prod for testing purpose.
> As i need to set this process. i am planning to create new client in dev
> and
> export full client data from prod to dev.
> So by exporting in scc8 ... sap_all profile will it copy full client?
> My full data base size in production system is 80 gb..
> So before doing client export i need to suspend all jobs using BTCTRNS1.
> After client export using BTCTRNS2 I can unsuspend all jobs
> Is this procedure right is any thing else there i have to look
> In some of the threads i read that it is not recommended to client export
> from prod to dev... But i have no option
> Please suggest me
>
> Regards
> Shashi
__.____._ Good Luck
From: D. Caddick via sap-basis <sap-basis@Groups.ITtoolbox.com>
To: Jerry Berry <gdb758@yahoo.com>
Sent: Thu, April 29, 2010 7:10:07 AM
Subject: RE: [sap-basis] client export from prd to dev
Posted by D. Caddick (SAP NetWeaver/BASIS Consultant)
on Apr 29 at 7:08 AM Mark as helpful
Hi Shashi,
This is terrible, You should NEVER allow direct update in PRD. The changes
should always take place in the DEV system. Your Development team should be
creating their own test data, it is still not a good idea to copy PRD into a
Development client.
Regards
From: shashi via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
Sent: 29 April 2010 08:58
To: D. Caddick
Subject: Re: [sap-basis] client export from prd to dev
Posted by shashi (Basis Admin)
on Apr 29 at 3:59 AM
<http://it.toolbox.com/api/ContentVote/3470849/1/1/> Mark this reply as
helpfulMark as helpful
Hi Caddick,
We have 2 system landscape.
what i mean is
Many of the changes done directly in production . If some one want to test
in development that data is not available.
so i am planing this client export
Regards
Shashi
On Thu, Apr 29, 2010 at 12:31 PM, D. Caddick via sap-basis <
sap-basis@groups.ittoolbox.com> wrote:
> Posted by D. Caddick(SAP NetWeaver/BASIS Consultant)
> on Apr 29 at 3:34 AM
> Hi Shashi,
>
>
>
> You are correct. It is not considered a "Best Practice" to copy Production
> data to Development.
>
> 1. Data Protection/Security issues.
>
> 2. Too much data in Dev for development testing
>
>
>
> What do you mean by "Here development is not maintaining."?
>
>
>
> However you explanation of the Export is correct.
>
>
>
> Regards
>
>
>
> From: shashi via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
> Sent: 29 April 2010 06:53
> To: D. Caddick
> Subject: [sap-basis] client export from prd to dev
>
>
>
>
>
>
>
>
> Posted by shashi (Basis Admin)
> on Apr 29 at 2:02 AM
>
>
>
> Dear all,
> As i am new to this project here i am facing different issues. Here
> development is not maintaining. Every time our abapers asking to transport
> program from dev to prod for testing purpose.
> As i need to set this process. i am planning to create new client in dev
> and
> export full client data from prod to dev.
> So by exporting in scc8 ... sap_all profile will it copy full client?
> My full data base size in production system is 80 gb..
> So before doing client export i need to suspend all jobs using BTCTRNS1.
> After client export using BTCTRNS2 I can unsuspend all jobs
> Is this procedure right is any thing else there i have to look
> In some of the threads i read that it is not recommended to client export
> from prod to dev... But i have no option
> Please suggest me
>
> Regards
> Shashi
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
In the Spotlight
_.____.__ Your SAP Security is at Risk...Learn How to Stay Protected. Read the free white paper from SenSage