1. Large Scale Enterprise Systems¶

1.1. System Scenario¶

This document describes exemplary solution implementations for a “Large Scale Enterprise System” scenario. Large scale enterprise systems mainly fall under the categories of “Core Business Systems” and “Finance and Accounting Systems” for internal corporate users, and are applied to systems with the following features.

Normal operation is available for 24 hours of 365 days a year, and is basically performed by one-by-one fall back. (Except in redundant configuration related maintenance where suspension of all servers is required.)
SPOF (i.e., Single Point of Failure） is not allowable. (Requires physical separation will be prescribed for redundant configuration.)
RPO (i.e., Recovery Point Objective) is so implemented at a set goal with 0. (For special failures, such as loss of REDO log space, returns to the time of backup in units of several hours.)
As this is a critical system, requires DR (i.e., Disaster-Recovery) measurements for employees in separate locations to be able to utilize even in disaster.

1.2. System Configuration¶

This system scenario places DR measures to be configured from the two (2) locations which are distant from one another in between the Main Site and DR Site. In the following description, Customers will receive two (2) system configurations: Main Site System Configuration and DR Site System Configuration.

1.2.1. Main Site Configuration¶

The main site accommodates the enterprise system during normal operation times, and configurations similar to the following can be assumed.

Web/AP servers are exclusive virtual environments being configured with Hyper-Visor on Baremetal servers.
DB server is configured through non-virtual Baremetal servers with their high-performance configurations along with Act-Act configurations.
Prepared Production, Testing, and Development environments will be observed. Separating physical machine resources from production and development and then testing, and the production environment is finally dedicated for specialized environments.

Below is a diagram outlining the system configuration.

The main points of the configuration are described in the following sections.

1.2.1.1. Web/AP Server Configuration on Baremetal Server in Hyper-Visor Platform Environments¶

Web/AP Server Configuration on Baremetal Server in Hyper-Visor Platform Environments Baremetal servers.
Customers can allocate Web/AP Server by considering physical arrangement over their independent specialized hardware environments; free architecture is possible through utilizing such Hyper-Visor functions as allocating configurations for multiple Hyper-visor as load-balancing configuration and allocating only one (1) VM utilizing with Hyper-Visor HA Functions.

Following diagram points to the Overviews configuring vShere platform environment for VMware over Baremetal Server.  Provisioning and selecting VMware ESXi for BYOL will let Customers configure ESXi server within a short time period.  Furthermore, Customers can provision Block Storage which is created for data store, mount it at iSCSI from ESXi.  that will complete the Customers’ configuring server platform for VMware Virtual Server.
Moreover, controlling these ESXi Hosts in integrated manner from vCenter Server, Customers can configure their independent vShere platform environments.  By doing so, vShere environment can be introduced much quicker and faster in private cloud environments unlike the past where Customers used to supply servers and storage equipments and configure in their on-premises environments.  Furthermore Customers can divide physical network accommodation equipments within cloud network by allocating ESXi hosts in a different designated group, and further highly efficient fault-tolerance level.
Moreover, controlling these ESXi Hosts in integrated manner from vCenter Server, Customers can configure their independent vShere platform environments.  By doing so, vShere environment can be introduced much quicker and faster in private cloud environments unlike the past where Customers used to supply servers and storage equipments and configure in their on-premises environments.  Furthermore Customers can divide physical network accommodation equipments within cloud network by allocating ESXi hosts in a different designated group, and further highly efficient fault-tolerance level.

When Customers consider protections  of AP servers, they can activate virtual platform’s HA functions (such as vSphere HA) and Live Migration functions (such as vMotion) so that they will improve availability and reliability of systems.  Depending upon importance of systems, host redundancy (such as N+1 configuration, N+2 configuration) and VM-operating host separation can be adjusted at the Customers’ end.  For these configuration exemplars, production dedicates two (2) units of  Baremetal Servers which are operable in scenario.  It depends on the Users to freely determine how to prepare with how many servers for degeneracies so that they can accommodate their own VM.
When Customers consider protections  of AP servers, they can activate virtual platform’s HA functions (such as vSphere HA) and Live Migration functions (such as vMotion) so that they will improve availability and reliability of systems.  Depending upon importance of systems, host redundancy (such as N+1 configuration, N+2 configuration) and VM-operating host separation can be adjusted at the Customers’ end.  For these configuration exemplars, production dedicates two (2) units of  Baremetal Servers which are operable in scenario.  It depends on the Users to freely determine how to prepare with how many servers for degeneracies so that they can accommodate their own VM.
When taking the same configuration for testing environments, even outside of AP server protection such as temporary Clone creation, various functions provided by virtual platforms can be maximally utilized.

1.2.1.2. DB Server Building Through High Performance Baremetal Servers¶

When using Baremetal servers, DB servers can be configured without virtual overhead or influence from other instances. In the configuration diagram above, the testing environment is configured with the same production environment Baremetal servers but when configuring multiple testing environments etc., a portion can be operated on the Virtual platform environment and enable cost reduction. (Able to perform block storage mount from the VM on Hyper-Visor.)

1.2.1.4. DB Server Backup¶

Backup data should be set to a data base within different physical disk equipment from the physical disk equipment which Customers usually utilize in order for Customer to correspond even in the event a cloud equipment failure / error. For this System, DB server utilizes DBMS function for output data to be designated to a different Block Storage to successfully separate physically.

1.2.1.5. Logical Network Configuration¶

This service is not configured with the NW overlay on the Customer-side, but rather provides a cloud function where private IP addresses are utilized and selected for each tenant, and network segments can be created freely. For example, a NW for management purposes can be connected to all servers. Logical networks can be configured with almost no difference to the those configured for on-premise.

1.2.2. DR Site Configuration¶

As with the Solution contents concerning DR site configuration, Customers are advised to refer to the Dr Site item in the Medium Scale Enterprise Systems

Enterprise Cloud 2.0 Solution Guide

2. Medium Scale Enterprise Systems