on 05-27-2008 5:29 AM
Hi,
We are setting up a DR Site, for our Production SAP system.
At present the curren setup for Production SAP system are as follows.
SAP ERP 2005 (SAP ECC 6.), ABAP+JAVA on Windows with MS SQL Server
2005.
Data are stored on SAN and SAP installed on MSCS Cluster enviornment.
For Setting up the DR site, we are setting up Central System
installation and replication will be configured between SAP
Production/Primary system and DR site.
We are shoadwing at our test setup and facing below replication issues
while setting up transactional replication in MS SQL server 2005.
1. At present 78716 articles are available on Production Database, and
SQL fails the replication publication after 59000 articles.
We open the ticket with Microsoft and below are the suggestion provided
by them.
1. Microsfot suggest to prepare 2\3 publications for total number of
tables, 1 publication for all Views and 1 publication for SPs,
Functions and Data types with single Distributor Agent. Distribution Agent will
take care of propagating changes in the tables across the publications.
2. All related tables (Parent child relationship) to be published on
one publication.
3. It would recommend to create 4 publications: 2 for the tables, 1 for
the views and the other for the stored procedures. This would ensure
better manageability.
The main concerns here is about splitting the tables into two different
sets with about 30,000 in one of the publications and the rest in the
second publication.
You will have to make sure that all the dependant tables are included
in the same publication. Since this database is a SAP database, requesting to provide information as follows.
1. Identify and split the entire set of table into two/three groups.
2. How to publish dynamic tables (The tables which get created post
publication process).
Regards,
JP
Dear Expert
there is any best practise for create DRC system using MSSQL 2005 ???
because we plan to create DRC system for :
1. SRM 6.0
2. R3
3. SEM
4. BI
5. Portal
thanks for your help
rgds
echo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Replication is not recommended in an SAP environment. It was never tested and has some backlogs, as you already found out.
As you are on SQL Server 2005 i would recommend to use Database Mirroring, as this is fully supported and tested by SAP. Or you can use Logshipping, if you need a security time window for your DR site.
Regards
Clas Hortien
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Clas Hortien,
Thanks for reply, it is very helpful for planning about the replication.
While discussing about the mirroring and log shipping we have few queries, and it would be very grateful if you provide some guidence on it.
Our Primary site is in Mumbai and DR site is in UK, we will connect through Internet bandwidth and the RTD is 220.
For Mirroring
Will it be feasible to configure Mirroring on Internet bandwidth?
Since the mirroring is tested if you have any notes to refer then please provide.
For Log shipping.
Generally in log shipping the primary site will be on Active mode and DR will be on passive mode. while doing a log shipping how do we verify the data?
Once again thanking you for your reply and awaiting for your further guidence.
Regards,
JP
Hi,
for database mirroring and log shipping there a several very good whitepapers and other documents out there:
[http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/SAP_SQL2005_Best%20Practices.doc]
[http://blogs.msdn.com/saponsqlserver/archive/2007/09/26/what-did-we-learn-using-database-mirroring-over-the-last-two-years-in-our-sap-erp-system-second-revision.aspx]
[http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032297524&EventCategory=5&culture=en-US&CountryCode=US]
[http://sqlcat.com/whitepapers/archive/2007/11/19/database-mirroring-best-practices-and-performance-considerations.aspx]
Furthermore see note 965908 for this.
The needed bandwidth depends on the amount of log you create in a given timeframe. Internet bandwidth can be suffient, if you don't generate much log (btw, i don't understand the term RTD is 220).
In the log shipping scenario you can run the DR site in standby mode, then a readonly access (as DBCC etc.) is possible.
Regards
Clas Hortien
hi guys .
i need you advice
if we wan to create DRC System .. in windows base " can we use VMware Site Recovery Manager " ???
because i check the web site vmware already certificate SAP,
http://www.vmware.com/partners/alliances/technology/sap.html
rgds
echo
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.