This action might not be possible to undo. Are you sure you want to continue?
The goal of this document is to provide technical solutions for the ERP (SAP ECC 6.0) implementations at Maihar Cement. This document would give a brief introduction and suggestion to the build a solution which is robust, scalable and optimized used of resources. The key focus would be to highlight the system sizing requirement, System landscape design, and strategies to ensure business continuity.
Introduction – SAP ERP Central Component (ECC) 6.0
The SAP ERP application has an extensive range of functionality – including personalized information access and tailored reporting – to help you in all areas of your business. With full support to integrate your core business processes – such as customer relationship management, supply chain management, supplier relationship management, and product life-cycle management – SAP ERP provides a foundation for growth, innovation, and end-to-end business process excellence. SAP ERP is a world-class, fully integrated application that fulfills the core business needs of midsize companies and large organizations across all industries and market sectors. It helps enterprises like yours perform financials, human capital management, procurement and logistics, product development and manufacturing, and sales and service, supported by functionality for analytics, corporate services, and end-user service delivery. In addition to increasing efficiency within your organization, SAP ERP also helps you extend end-to-end business processes to your customers, partners, and suppliers. SAP ERP can serve as a business process platform that supports continued growth by providing a foundation for insight, operational excellence, and innovation. SAP ERP is powered by the SAP NetWeaver technology platform, which enables you to build new business solutions rapidly while realizing more business value from your existing IT investments. SAP NetWeaver is also the foundation for enterprise service oriented architecture (enterprise SOA).
Introduction – Netweaver 2004s
The SAP Netweaver technology platform is a comprehensive integration and application platform that helps reduce the total cost of ownership (TCO). It facilitates the integration and alignment of people, information and business processes across organizational and technological boundaries. SAP NetWeaver easily integrates information and applications from virtually any source. It interoperates with and can be extended using the primary market technologies Microsoft .NET, Sun’s J2EE, and IBM WebSphere. SAP NetWeaver is the technical foundation for SAP ECC 6.0 solutions and ensures maximum reliability, security, and scalability, so mission-critical business processes run smoothly. And by providing pre-configured business content, it helps reduce the need for custom integration and lowers TCO.
SAP Netweaver supports installation based on Operating System: Windows, Linux, HP-UX, AIX, Sun-Solaris, OS/400, z/OS, Tru64 Database: SAP DB, ORACLE, DB/2, MS SQL Server
Introduction to SAP Web Application Server
Lets understand WAS in simple context. SAP Web Application Server (WAS) is integral part of SAP Netweaver and ultimately the core engine which has the processing capabilities. There are two types of WAS, ABAP WAS and J2EE WAS which are placed at application layer. SAP ECC 6.0 requires both ABAP WAS and J2EE WAS in order to use full functionality and features. In SAP System Landscape you can have as many as application server you require to support business operation and only one database server.
can’t be altered by any other user session from any application server. After completion of request. Though each WP has dedicated database connection still SAP ECC system can manage multiple active sessions and its not limited to dedicated session as in legacy system. The task of dispatcher is to receive the request from Presentation layer and manage the requests in queues. The task of Message server is to identify application server with best response time. Processing Logic: Login Process: First request would be to establish connection with SAP ECC System.SAP Web Application Server: Each WAS (Application Server) has 2 main components. When user sends request to SAP ECC system. Each Work process establish connection with Database. subsequent request from user will addressed by the allocated server. User context (personalized data. End Users can access the SAP ECC application through SAPGUI (Thick Client) or Browser (Thin Client). Central Instance: Message server + Enqueue server. Request then routed to allocated application server and End user establishes the session with application server after successful login. 7 . process the dynpro logic and also shares common buffer between the work processes.Connection request first addressed by Message server. Authorization) loaded into shared buffer from database. The task of message server is to check the availability of the application server and collect the performance statistic data of each applications server. thus ensured data consistency. Work process loads user context into main memory (roll-in) from shared buffer. request queued into dispatcher and which intern assign to the request to available Work Process (WP) / Server Process (SP). Message Server: The significance of Message server as load balancer is more when there are then one applications server per SAP instance. Once session established. User context also stores the runtime application data of the users. Enqueue server: The task of Enqueue server is to manage the data locking at SAP level. Dispatcher and Work process. Data locked by one user session. WP sends data back to presentation layer and User context rollsout from main memory into shared buffer.
The environment is the system of record and only contains productive customizing and developments. learning. and testing. An isolated and stable environment for testing the customizing. Sandbox system has more importance and it used for destructive testing. just quality assurance tasks. just productive tasks. customizing and data will exist in the system and this environment will be used for unit testing. The environment is representative of the productive environment and contains all product customizing. 1 Quality Assurance system (QAS). In addition new projects’ developments. Sandbox System (SBX) Sandbox system is standalone system and not integrated into Project landscape. developments and in most cases production quality data. In addition this environment will also have newly completed customizing/developments that are in quality testing phase prior to productive release.2 ‘PROMOTE TO PRODUCTION’ LANDSCAPE. The environment should be representative of the productive environment and contain all product production customizing. Since system is standalone it is completely free from risk. These environments should provide: An environment where customizing and development can be performed. No development tasks are performed in this environment. This ‘promote to production’ scenario is recommended when implementing any system based on SAP NetWeaver. This environment may additionally be used for debugging productive issues. developments. and maintenance support changes. No development tasks are performed in this environment. and 1 Development System (DEV). This is typically called a “Three System Landscape” with 1 Production system (PRD). The typical testing that occurs in this environment is regression and integration testing. An isolated and stable production environment. developments and a sampling of production data. Project requirement mapping and building of prototype of solution done in Sandbox. The ideal software landscape to support the implementation is comprised of environments supporting three distinct needs that provide a solid ‘promote to production’ change management and change control process for all configuration and developments. This environment may also be used for replicating and debugging productive issues. This environment is used for as the initial environment for resolution of production issues and routine maintenance support. Development System (DEV) 8 .
This system—containing the company's live data—is where the real business processes are executed. Production System (PRD) A company uses the production system (PRD) for its live. it can be promoted to the production system (PRD). each SAP system landscape requires SAP System where Customizing settings and possibly ABAP Workbench developments can be made. development or changes have been thoroughly tested in this system and signed off by the quality assurance team. 9 . the configuration. management. After all the changes have been unit tested. development or changes undergo further tests and checks to ensure that they do not adversely affect other modules. The other systems in the landscape provide a safe approach to guaranteeing that only correct and tested (that is not defective) new developments and/or customizing configurations get deployed into the productive system. development and production break-fix changes are promoted to the QAS system using the change management system. Therefore the quality of the DEV and QAS system and the implemented change management processes directly impacts the quality of the production system. development and break-fix changes in the development system (DEV). productive work. these changes can be transferred to the quality assurance system (QAS) for further system testing. Here. tracking and audit capabilities thus minimizing risk and human error by eliminating manual repetition of development and customizing work in each system. This ensures consistency.Since each business needs to adapt the SAP software for its own business needs. All system maintenance including break-fixes for productive processes is also performed in the system. the changes are promoted to the quality assurance system (QAS). Quality Assurance System (QAS) After unit testing the customizing. Additionally they ensure that changes to productive developments and configuration by either project enhancements or maintenance do not adversely affect the production environment when deployed. The customizing. When the configuration.
and technical unit within an SAP Instance.2. TEST client (TEST): Developers can use this client to test their Customizing settings and Workbench developments.or clients. which can be considered as the exclusive property of this client. SAP ECC solution can operate with multiple clients if each customer has exclusive access to his or her data in an installation with a shared system platform. organizational. In this client the developers can create test application data for realistic tests. Customizing and Development client (CUDV): Since each business needs to adapt the SAP software for its own business needs. If they discover errors. and central services. SAP's client concept allows you to split an SAP System into multiple logical sub-systems . database. You can isolate these sub-systems and operate them as separate business units. All data in a system with multiple clients is located in a common database. they can remove them in the Customizing 10 . This means that all business data within a client is protected from other clients. before they release their change requests.1 Role of Client in SAP ECC Landscape A client is defined as a self-contained commercial. However. transaction data. each SAP system landscape requires a client where Customizing settings and possibly ABAP Workbench developments can be made. Each client has its own customer data. the SAP System offers a system solution that is implemented for all clients in a central repository and crossclient tables (central data source). business data.
has to be created manually or with Migration script / program or Catt or eCatt. The correctness of the settings can only be guaranteed with extensive testing. The users can use the new functions in this client with specially created application data. Required Master and Transaction data has to be created manually or with Migration script / program. a separate training client can be set up. To prevent conflicts between the prototype client settings and real settings in the Customizing client. Changes to client-specific data are copied from the Customizing client to the TEST client using a special client copy function. and does not transport them from the prototype client. QTST for short. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Any settings that one wants to keep are then entered in the Customizing client. Required Master and Transaction data. A TEST client is always set up in the same SAP System as the Customizing client. One can be sure of this by making appropriate client settings. 11 . This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the TEST client. So that this client can be used without disruption. one cannot make changes to cross-client Customizing data and Repository objects in the prototype client. Production Client (PROD): A separate client is required for productive use of the SAP System. and at worst. The TEST client is set so that one cannot make changes to Customizing data and Repository objects. The client copy function uses the unreleased change requests from the Customizing client to do this.client. This client is set so that no changes to Customizing data and Repository objects can be made. Quality Assurance Client (QTST): Before one can use the Customizing settings and Workbench developments productively. it is essential that no Customizing settings or Workbench developments are made here and also that no tests are carried out. Training client (TRNG): To prepare end users for new functions that are to be transported into the production client. The Change and Transport System (CTS) does not record changes made to client-specific Customizing data. lead to the loss of productive data. The client where these tests are made is the Quality Assurance Client. Prototype (PROT): This client is used to test any client-specific Customizing settings if one is not sure whether one wants to use them in this form. for Unit Testing. Any faulty settings can seriously disrupt productive operations. one needs to test them extensively for errors.
Client is allowed Protection Level No overwriting 1: Allowed Global Settings: Not Modifiable Software Component: Not Modifiable Name Space: Not Modifiable NA Production PROD Production No Changes allowed No Changes to Repository and Cross . For more details about the settings for each client are mentioned in attached file.2 Proposed Client settings for each system Behavior of each depends upon the setting performed in SCC4 and SE06 transaction.Client is allowed Protection Level No overwriting 1: Allowed Quality Assurance TRNG Training Education / No Changes allowed No Changes to Repository and Cross . Changes in SE06 setting will reflect in all the clients existing in the same system. System Client Client Role Sandbox (IDES) SAND Demo Changes and Transports for Client specific Objects Automatic recording of Changes Cross client Changes object Protection: Client copier and Comparision tool Protection Level No overwriting 1: CATT / eCATT Allowed SE06 Settings Changes to Repository and Cross .Client is allowed Protection Level No overwriting 1: Allowed NA Quality Assurance QTST Quality assurance Test No Changes to Repository and Cross . For ABAP Development we are proposing to have separate naming convention “/MAIHAR”.Client is allowed Protection Level No overwriting 1: Allowed Development PROT Demo Changes without Automatic recording. No transports allowed No Changes allowed No Changes to Repository and Cross .3 User and Authorization Strategies for each Client 12 .Client is allowed Global Settings: Modifiable Software Component: Modifiable Name Space: Modifiable Development CUDV Customizing and Development Automatic recording Changes of Changes to Repository and Cross .2.Client is allowed Protection Level 2: No overwriting and no external availability Not Allowed Global Settings: Not Modifiable 2.Client is allowed Protection Level No overwriting 1: Not Allowed Global Settings: Modifiable Software Component: Modifiable Name Space: Modifiable NA Development TEST Test No Changes allowed No Changes to Repository and Cross . As SE06 settings are client independent.
User Types Business Process Owner Functional Consultant Technical Developer Basis Consultant System End User Sandbox (SAND) Prototype (PROT) Customization and Development (CUDV) Test (TEST) Quality Assurance Test (QTST) Training (TRNG) Production (PROD) 3 3 3 3 2 2 3 2 3 2 2 3 3 3 2 2 3 3 3 2 3 3 3 3 2 3 2 2 3 3 3 2 2 3 3 13 .
Sizing and solution architecture suggested is hardware independent.0 and SAP Solution Manager 7. Expressed in GB(GigaByes) / MB(MegaBytes) Cost Factor (Importance in System Sizing): ¾ Backup/recovery depends on size of database ¾ Disk I/O Memory (RAM) Each program execution requires real-time memory to process. 14 . Sizing estimation considered 20 ABAP object development (Objects in customer Name space). It’s very important to have final solution from Hardware vendor based on Hardware technology. 100 SAPS means processing 2000 fully business process line items per hour.0. Extended memory).2 General assumption for Sizing Sizing of SAP ECC 6.7 should be considered. should consult with Infosys / Hardware vendor or section 3. Utilization of production resources is at 60% including buffer of 30%.1 Disk Business transaction and master data are placed in central database. Sizing estimations are calculated to support the SAP operation after 3 years as well. 3. Cost Factor (Importance in System Sizing): Number of servers and/or CPUs require.3 SAP SERVER SIZING Understanding Sizing parameter SAPS Understand CPU processing capacity should be hardware-independent unit as SAP Support many platforms. When data can't be avoided or needs to be moved it will stored in Database. SAP real-time memory structure has many components such as User contexts (Roll area. SAPS describe the performance of a system configuration in the SAP environment and derived from the Sales and Distribution (SD) Benchmark.0 is considered in current phase of the project. Sizing estimation is totally based on input provided by IT team from Maihar Cement ( For ECC attached in Annexure I) and incase of any change/addition in Sizing input. Expressed in GB(GigaByes) / MB(MegaBytes) Cost Factor (Importance in Sizing): physical memory slots. shared buffer memory etc. Heap Area. 3. Required data to complete business transaction are fetched from database and stored in buffer (RAM) till user activity is complete. SAP BI 7.
Thus 144GB / Year and 432GB at end of 3 year. 40GB Memory and 760GB Disk space. 15 . Indicative split-up is shown below. Plus we need to consider additional disk space for database software. 12 GB Disk Space: 400GB Production DB Server With SCS & ASCS Disk Space: 760GB Production Apps Server1 Disk space: 50GB Production System Production Apps Server2 Disk space: 50GB Production Apps Server3 Disk Space: 50GB Disk Space: We have estimated that Database growth will happen at 12GB / Month.3. Quality system is considered to have 50% of production system. Sandbox (IDES) and Development system is considered to have a 25% size of Production environment.e 432 + 100 = 532 GB. Maihar Cement wants maximum disk utilization should be 70% so total Disk storage requirement is around 760GB. Sandbox Server CPU: 3250 SAPS RAM: 6 GB Disk Space: 200GB Development Server CPU: 3250 SAPS RAM: 6 GB Disk space: 200GB Quality Server 6500 SAPS. i. Default storage requirement for ECC software and storing the log files approx. Central services of ABAP (ASCS) and J2EE (SCS) are installed along with Database.3 Sizing for ECC Systems Total Sizing for Production system 13000 SAPS. 100GB.
Though compare to SAP ECC 6.0 actively use application based on ABAP and J2EE instance. Maihar Cement wants maximum disk utilization should be 70% so total Disk storage requirement is around 800GB. i.0. Disk Space: We have estimated that Database growth will happen at 12GB / Month.e 432 + 100 = 532 GB. by default comes with SAP EP 7. 36GB Memory and 800GB Disk space (Indicative). higher resource requirement for data extraction. 100GB. Thus 144GB / Year and 432GB at end of 3 year.0 component.4 Sizing for BI Systems Total Sizing for Production system 10000 SAPS. 12 GB Disk Space: 400GB Production DB Server With SCS & ASCS Disk Space: 800GB Production Apps Server1 Disk space: 50GB Production System Production Apps Server2 Disk space: 50GB Sandbox (IDES) and Development system is designed to have load of 30 Concurrent SAP user / Functional Consultant / Developer. Central services of ABAP (ASCS) and J2EE (SCS) are installed along with Database.3. Plus we need to consider additional disk space for database software. Also SAP BI 7. Default storage requirement for ECC software and storing the log files approx. Sandbox Server CPU: 4000 SAPS RAM: 8 GB Disk Space: 200GB Development Server CPU: 4000 SAPS RAM: 8 GB Disk space: 200GB Quality Server 8000 SAPS. Indicative split-up is shown below. SAP BI 7. 16 .0 system requires more system resources because ideally SAP BI 7.0 System. data loading and reporting.
Following features of Solution manager will be used to support the project. o o o o Project Management ( Document storage ) Central System monitoring Primary SLD ( System Landscape Directory) Maintenance optimizer 17 . SAP Solution Manager 7.3. 8GB RAM and 200GB Disk space.5 Sizing for Solution Manager Solution Manager Server CPU: 4000 SAPS RAM: 8 GB Disk space: 200GB Explanations: Total Sizing of SAP Solution Manager system is 4000 SAPS.0 system is designed to have user load of 30 Concurrent users.
6 System Architecture for Maihar Cement Non-Production Site Solution Manager 4000 SAPS. 8 GB Disk Space: 200GB ECC Sandbox Server 4000 SAPS.3. 8 GB Disk Space: 200GB BI Development Server CPU: 4000 SAPS RAM: 8 GB Disk Space: 200GB BI Quality Server CPU: 8000 SAPS RAM: 12 GB Disk space: 400GB Production Apps Server1 Disk space: 50GB Production Apps Server2 Disk space: 50GB Production Apps Server1 Disk Space: 50GB Production Apps Server2 Disk space: 50GB Production Apps Server3 Disk Space: 50GB ECC Production DB Server with SCS and ASCS Disk space: 760GB Production Site BI Production DB Server With SCS & ASCS Disk Space: 800GB * Network connection between Database and application server should be on high speed network (Minimum 100 mbps). 8 GB Disk Space: 200GB ECC Development Server CPU: 4000 SAPS RAM: 8 GB Disk space: 200GB ECC Quality Server CPU: 8000 SAPS RAM: 12 GB Disk Space: 400GB BI Sandbox Server 4000 SAPS. 18 .
Upgrade sizing: determine additional requirements and add calculated load 3. STAD. or whether you may need to buy new hardware. DB monitor of vendor CPU Analysis: ST06. 2. ST03N. STAD. table growth. Judge whether your current hardware is sufficient.20% of the processes cause 80% of the load. c.Post-Golive Prerequisites: 9 9 9 The System is live The hardware and software scalable Different goals ¾ Only add volume. Analyze 9 9 9 Procedure: 1. b. Different procedures according to goals a. Monitor CPU utilization. Growth rate of 20 largest tables Average and peak CPU load Average and peak memory utilization 19 . httplog As a rule. ST03G User Analysis: ST07. no modified processes ¾ Add different functions ¾ Only upgrade SAP Software Monitor & Analyze: Disk Analysis: DB02. and memory use. STAD.3. GCLOG Front-End Network Load: STAD. Delta sizing: treat like a new sizing and add calculated load. ST03G Memory Analysis: SM04.7 Requirement of Re-sizing . Re-sizing: Add the load coming in through the additional users and projects causing the same load structure. ST03G. ST03N.
4 HIGH AVAILABILITY SOLUTION High Availability – Definitions 4.1 Availability is the capacity to function as expected. SOAP. the use of multiple components that tolerate the failure of individual components – or by cluster and switchover solutions. Switchover Solution . services can be automatically switched from a failed host to a standby host in the event of failure. For a high availability system all single points of failure have to be eliminated. SAP provides a proven. fault-tolerant. ¾ 4. which enable SAP applications using additional software and hardware to achieve high availability. With the SAP NetWeaver Application Server (SAP NetWeaver AS). This is a yes-no concept: a service is available or it is not. The following levels need to be protected against single points of failure: 20 .As the name switchover implies. server.2 Avoiding Single Points of Failure with the SAP NetWeaver AS With SAP NetWeaver Technology. The SAP Java Connector (SAP Jco) enables method calls between Java applications and ABAP applications (Such as SAP ECC. storage. A service is considered available if it can complete its assigned task at the appropriate time. All SAP hardware partners provide their own proven solutions. scalable. HTTPS. ¾ ¾ Virtualization of services is a necessary requirement for an application to be highly available as all SAP HA scenarios require at least one Switchover Solution. SAP enables web applications to be directly supported by the application server for the first time and combines ABAP and J2EE in one infrastructure. allowing continuation of SAP system operation. The individual components can be protected either by horizontal scalability – that is. A switchover solution implies a third party delivered software and/or hardware package that provides such implementation of SAP enabled (configured) application software or other infrastructure elements such as RDBMS. or network. and the Java Communication Services. SMTP. High availability does not include disaster recovery. multi-tier architecture. Availability requiring additional measures. It enables communication between the SAP NetWeaver AS and external partners using Internet standard protocols such as HTTP. The Internet Communication Manager has also been implemented as another new process in the application server framework. SAP BI).
and directory servers) also require to be designed with High Availability Storage Disk storage is particularly important for high availability. in the event of errors. Network To operate SAP applications in networks. This is particularly worthwhile if the applications running on the server are single points of failure. without affecting the servers using them. A Storage Area Network (SAN) is a highspeed network of shared storage systems. routers. they can affect the availability of the business applications and you must therefore protect them. additional components (for example. A Network Attached Storage (NAS) device is a server that has the sole task of providing disk space. These components are provided by partners. However. There has been a trend away from storage units that are connected directly to local computers towards storage systems at network level. NAS devices are intended for file-oriented input and output and are normally accessed from IP networks. load balancers) are required. NAS enables storage systems to be provided and extended flexibly. Partners offer a number of proven solutions for this purpose. e-mail. It stores important data that needs to be called quickly and reliably. 21 . Note especially the following basic measures: ¾ ¾ ¾ ¾ ¾ Provider Connection Router and Firewall Network Load Balancing Redundant Server Networks Other Network Services (DNS. SANs are intended for block-oriented input and output.The layers below the business applications are generally transparent to these applications. domain controllers. They are normally accessed using fiber channels and are suitable for large environments with high performance and scalability requirements. Server You can increase the availability of a server by using multiple components on different servers. switches. firewalls. The most important mechanisms are described briefly below. which can also be single points of failure.
A switchover mechanism ensures that the resources assigned to a node in the cluster are automatically reassigned to another node in the cluster in the event of the first node failing. bus Uninterrupted power supply Error-correcting memory (ECC memory) Mirrored disks Hot-plug compatible components Partitioning of server resources The solutions provided by SAP hardware partners include all these features. takes on the tasks of the failed node. not only do you have to make sure that the database is safeguarded against failure. which appears externally as one unit. multiple layers of hardware can be used with controlling cluster software. space. ¾ Database The database is a central building block in the SAP component. such as boards. 22 . Also. Shared Everything Cluster is a clustering model in which each server can have simultaneous read and write access to all common data. disk storage. There are the following cluster types: ¾ Shared Nothing Cluster is a cluster in which each node has its own tasks but also. SAP supports nearly all important database systems. The affected resources remain available. IP address. in the event of another node failing. except at switchover time. processes) are set up so that applications can continue using them transparently if the underlying hardware fails. power supply. To achieve this. nodes are assigned other server resources. Operating System You should make sure that resources managed by the operating system (for example. in the event of server resources failing.The following features can increase the availability of servers: ¾ ¾ ¾ ¾ ¾ ¾ Redundant resources. hostname. Since the data is crucial. but you also have to regularly save the data itself and check that it can be recovered.
This normally results in a loss of information. And also while sizing the system. 23 .e Host which are used in HA scenario would be used operational during normal operations. Database services and Central services supported from DB server. so that the database host and the central instance then run on this remaining host. If one of the nodes fails. Responsibility to configure High availability other than Database lies with Infrastructure partner.4.3 HA Solution for Maihar For an SAP component. Apps server1 would work in cluster environment with DB server. At same time Apps server1 work as to support Dialog server. for example. Setup of HA: Active . it need to ensure that the remaining host now has to perform both tasks. you can operate the database host and the central instance on two opposite nodes of a cluster. Use of Active – Active clustering. its resources are transferred to the remaining node.Active Scenario – 1: Normal conditions. i.
Scenario . if Application server contribute 30% dialog server load then system would continue to operate with 70% processing capacity. Central services) available.3 : In case of DB failure in cluster environment Normal Business operation will affect temporary as Critical service (Database. if Application server contribute 30% dialog server load which later on transfer to DB server then system would continue to operate with 70% processing capacity. i.Scenario . it is to be note that.1 BI / ECC Production DB Server With SCS & ASCS Disk Space: 760GB BI / ECC Production Apps Server1 Disk space: 50GB Scenario . it is to be note that. Once resources moved from to Apps server1 SAP System continues to support through other application server available in production environment. system would be continue to operate with lesser load. Normal Business operation continues as Critical service (Database.2 : In case of Apps server1 failure in cluster environment. SAP System continues to support through other application server available in production environment. since due to loss of one application server to database server. At the same time.e. system would be continue to operate with lesser load.e. Central services) as resources and services from DB server transferred to Apps Server1. i. 24 . since due to loss of one application server.2 BI / ECC Production DB Server With SCS & ASCS Disk Space: 760GB BI / ECC Production Apps Server1 Disk space: 50GB Scenario . At the same time.
25 . Scenario .1 BI / ECC Production DB Server With SCS & ASCS Disk Space: 760GB BI / ECC Production DB Server Standby Scenario .3 BI / ECC Production DB Server With SCS & ASCS BI / ECC Production Apps Server 1 DB Server With SCS & ASCS Setup of HA: Active .2 : In case of Standby system failure in cluster environment. SAP System continues to support through other application server available in production environment. Database services and Central services supported from one server and its connected to common storage system. Central services) available. Standby server with same configuration of DB server remains available in cluster environment.Passive Scenario – 1: Normal conditions.Scenario . There will not be any loss in SAP System capacity. Normal Business operation continues as Critical service (Database.
System will operate with lesser load. Once resources moved from to Standby server. cost.Scenario .Passive Pros: 1. Lesser hardware 2. Seeing MAIHAR requirement.3 : In case of DB failure in cluster environment Normal Business operation will affect temporary as Critical service (Database.2 BI / ECC Production DB Server With SCS & ASCS Disk Space: 760GB BI / ECC Production DB Standby Server Scenario . Central services) as resources and services from DB server transferred Standby. SAP System will always able to perform at 100%. Cluster setup is easy. Active . SAP System continues to support through other application server available in production environment. Resource remain ideal which can be use for productive use. 2. We suggest to have further discussion with hardware vendor for Active-Active clustering.3 BI / ECC Production DB Server With SCS & ASCS BI / ECC Production Standby Server DB Server With SCS & ASCS Active .Active Pros: 1. Incase of Failover. 26 . Cons: 1. Scenario . Maximum Utilization of resouces. Cons: 1.
so that production can resume quickly at a separate location.5 5. The type and method of implementation depend on the respective database platform. the standby database can be started up using the log files and a consistent status reached. a disaster might have the following causes: 9 Power failure 9 Flood 9 Fire 9 Tornado 9 Earthquake 9 War In this event Maihar Cement might need a disaster recovery site to survive. 27 . For example.1 DISASTER RECOVERY SOLUTION Understanding DR A disaster is a failure that prevents production at an entire location for an extended period. in the event of database failure. the log files can be replicated so that. log-file replication). 5. in the case of asynchronous replication (for example. be aware that the standby database might have an older dataset than the original and that it takes longer to start up the database due to forward recovery. For example.2 DR with Replicated Database Database methods for replicating data are used. However.
backup restore technology can be used for DR synchronization. In order to have characteristic of DR site. All Development. Shutdown the Development and Sandbox system. Development and Sandbox system will be shutdown and the resource allocated to Development and Sandbox system will transfer to DR production system. Non. Dynamic Hardware allocation is required in non-productive environment.5. In case of failure of Production system. DR site can be constructed at Non-productive environment.Production Site in Normal Situation: 1. Non-productive environment need to be at location other than Productive environment. 4. In order to reduce the cost and better utilization of resources. Transfer of resources from Development and Sandbox system to DR CI+DB and DR application servers. 3. BI) are in shutdown mode. DR CI+DB server remains operation with minimal resources which are required to sync the database. 3. 2. Strong network will help to have DR synchronization and DR site would be lagging by few hours to production environment. 28 . Non-production Site in DR Situation (Production Landscape crashed) : 1. Strong network connection is required between Productive and Non-productive environment.3 DR Solution for Maihar We Suggest to Maihar cement to have DR site in their environment. Business approval is required before accepting and activating DR system. Application servers of production system (for ECC. 2. Background to setup DR: 1. Activating Standby database and start the DR production system. Typically DR site operate at 40-60% load of actual production system. 2. If Network is restriction then. 3. Quality and Sandbox system is operated at actual Size.
8 GB Disk Space: 200GB ECC Development Server CPU: 4000 SAPS RAM: 8 GB Disk space: 200GB ECC Quality Server CPU: 8000 SAPS RAM: 12 GB Disk Space: 400GB BI Sandbox Server 4000 SAPS.Normal Situation: Non-Production Site Solution Manager 4000 SAPS. 8 GB Disk Space: 200GB ECC Sandbox Server 4000 SAPS. 8 GB Disk Space: 200GB BI Development Server CPU: 4000 SAPS RAM: 8 GB Disk Space: 200GB BI Quality Server CPU: 8000 SAPS RAM: 12 GB Disk space: 400GB DR BI Production System DB+CI DR BI Production System Application Server1 DR ECC Production System DB+CI DR ECC Production System Application Server Production Site ECC Production DB Server with SCS and ASCS Disk space: 760GB Production Apps Server1 Disk Space: 50GB Production Apps Server2 Disk space: 50GB Production Apps Server3 Disk Space: 50GB BI Production DB Server With SCS & ASCS Disk Space: 800GB Production Apps Server1 Disk space: 50GB Production Apps Server2 Disk space: 50GB 29 .
DR Situation: Non-Production Site Solution Manager 4000 SAPS. 8 GB Disk Space: 200GB ECC Sandbox Server 4000 SAPS. 8 GB Disk Space: 200GB BI Development Server CPU: 4000 SAPS RAM: 8 GB Disk Space: 200GB BI Quality Server CPU: 8000 SAPS RAM: 12 GB Disk space: 400GB Production Apps Server1 Disk space: 50GB Production Apps Server1 Disk Space: 50GB Production Apps Server2 Disk space: 50GB Production Site ECC Production DB Server with SCS and ASCS Disk space: 760GB Production Apps Server3 Disk Space: 50GB BI Production DB Server With SCS & ASCS Disk Space: 800GB Production Apps Server2 Disk space: 50GB DR BI Production System DB+CI DR BI Production System Application Server1 DR ECC Production System DB+CI DR ECC Production System Application Server 30 . 8 GB Disk Space: 200GB ECC Development Server CPU: 4000 SAPS RAM: 8 GB Disk space: 200GB ECC Quality Server CPU: 8000 SAPS RAM: 12 GB Disk Space: 400GB BI Sandbox Server 4000 SAPS.
g. application support scripts. 1. Considering recovery point of view its suggested to go for the 1 method of update log backup. Therefore one has to see for the depending factors which are … Database size Backup device Network interface and network bandwidth between backup device and Server 1. . Size defined for ORAARCH file system is 30 GB.1 1 BACKUP STRATEGY Types of Backup in SAP Environment Database backup Database backup will take care of the backup for RDBMS data. company data. interface files. offline backup once in month or before any major upgrade planned. It is possible to recover system for any given date with online consistent backup and database logs. For e. some of the java level configurations will also be stored in the file system (and not in database).e. It is very important to have regular backup of database to secure the company data. 2 File system backup Some of the application files resides on the operating system like application executable (SAP EXEs).1 Daily online incremental backup: It is suggested to have daily online incremental backup for file system.3 Offline backup: It is suggested to have a complete cold backup i.e. This can be used for single point of recovery for database.1 Online backup: System should have daily on-line backup. Typically this happens during weekends. Before starting schedule of online backup it is necessary to estimate the time required for online backup. It will be good if file system backup taken at the time of daily database backup. Size of Database logs and frequency of backup decide the business data loss in terms of time.2 Offline complete backup: Once in a month complete offline backup needs to be done.If a client have Oracle database running on Solaris. Some of the clients also go for regular database maintenance work before this backup. With Online backup end user continues to work on SAP System with very little performance impact. if you have a copy of Database. 24 GB. In case of J2EE stack system. archive log backup will be triggered when file system reached 80% of st usage i. 2. Thus database backup is critical and also requires security measures. which should run during off office hours. It is also recommended to have an offline backup before any of the major activity in the system like data migration. This will give the time dependant recovery. 31 . All the customization. 2.2 Database log backup: It’s always suggested to have update log file backup once in every 30 to 60 mins to have minimum data loss incase of database crash. transaction data are stored in the Database. This will keep file system in sync with the database. You can rebuild the system. 1. In this case.6 6.
You are also required to take backup of Sandbox. SAP Planning Calendar provide options to protect tapes or disk backup devices from being overwritten during the backup cycle.In most of the locations. Usually tapes are used because they are less expensive and easier to handle. 1 Tape for each system also required to backup the transaction logs on daily basis. You are strongly advised to use 2 tapes per day.3) and offline file system backup (2. In case of data upload or data migration activity only database backup is sufficient. x What type of backup media is to be used. additional tape blank tape should be made available for case of urgency.2) is file system backup gives you single point of recovery for entire system where as with database backup only data will be recovered. How many tapes are needed and their capacity? The number of tapes you need depends on: The number of days in the backup cycle The number of tapes required for the various database and transaction log backups of the day. Now difference between Offline Database backup (1. interface scrip changes one has to go for file system backup. one for the database backup and one for the transaction log backup. full database backups and differential database backups Set the expiration period to 27 days for Online database backup. Development and Quality system on atleast weekly offline backup with database log. for example. We suggest having Tapes as storage for backup media. 6. How long tapes should be saved before they are overwritten? Transaction log. java configuration. disks or tapes? You can choose to backup either to tape or to disk. this means database and application will be brought down and complete file system backup (along with database files) will be done. This will give single point of recovery for entire system. Complete System Backup Use at least two tape sets in rotation so that the last two backups are always available. x x 32 . complete system cold backup will be taken once in a month. In case of change in files like kernel upgrade.2 Backup Solution for Maihar Each company must have backup strategy is well established and backup schedule properly followed to safeguard the business data against any abnormal condition of system crash. It is also recommended to go with this backup before staring the major activities like SPS upgrade. This means the backup cannot be overwritten for 27 days. An essential part of a backup strategy is the management of storage devices. It is also recommended to have one offline backup in backup cycle. Apart from this. Keep the last database backup of each month for a year and the last database backup in the financial year permanently.
Character 1 identifies the database on the tape Single Database: S: Master database backup M: msdb database backup R: SAP database backup O: Other databases backup Multiple Database: C: Combination (SAP database not included) I: Combination (SAP database included) Character 2 identifies the type of backup L: Transaction log backup D: Database backup +: Differential database backup Do not mix transaction log backups and database backups on one tape Characters 3 and 4 indicate the day of the month Character 5 indicates whether it is a parallel or a sequential backup P: S: Parallel backup Sequential backup x How backups that need more than one tape should be organized It is recommends you to test and validate the backup and restore process regularly so that you can restore your database to a correct and consistent state 33 . you can identify the contents of a tape simply by looking at the label.x How tapes should be labeled? If you use the tape naming conventions that SAP recommends. Always make sure that the correct name sticker has been placed on the tape cartridge before you insert it into the tape device.
BI 7.7 ANNEXURE Annexure – 1 Sizing Input Sheet provided by Maihar 7. 34 .0 applications. Attached sheet shows the possible combination of OS and database platform.3 Annexure – 3 SAPGUI Support matrix for OS SAPGUI is client software.2 Annexure – 2 Product Availability Matrix (OS / DB Matrix for SAP Netweaver SR2) SAP ECC 6. Following is matrix which shows available version of SAPGUI supported on OS platform.1 7.0 and Solution manager 7.0.0 .0 and SAP Solution Manager is based on SAP Netweaver SR2. which is required to access ECC 6. on which product can be installed. 7. SAP BI 7.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.