Attachment 152345 Details for Bug 126041 – HTML file that makes the export crash

HTML file that makes the export crash

export_input.html (text/html), 42.65 KB, created by Simon Urli on 2019-06-21 14:10:56 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon Urli

Created: 2019-06-21 14:10:56 UTC

Size: 42.65 KB

patch

obsolete

><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
><html xmlns="http://www.w3.org/1999/xhtml"><head>
><title>
>  fdg - Reference architecture overview
></title>
><meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
><meta content="en" name="language" />
>
></head><body class="exportbody" pdfcover="1" pdftoc="1">
>
>  <div class="pdfheader">
>                      Reference architecture overview
><hr style="border-width: 0.25pt" />
>
>    </div>
>  <div class="pdffooter">
>        <hr style="border-width: 0.25pt" />
>Page <span class="page-number" /> / <span class="page-total" /> - last modified by Administrator on 2019/06/21 15:34
>
>    </div>
>  <div class="pdfcover">
>        <div style="width: 100%;">
><hr style="border-width: 0.25pt" />
><h1 style="text-align: left;">
>  Reference architecture overview
></h1>
><div>
>  <p class="author" style="text-align: left;">last modified by Administrator</p>
></div>
><div>
>  <p class="date" style="text-align: left;">on 2019/06/21 15:34</p>
></div>
><br />
><hr style="border-width: 0.25pt" />
></div>
>
>    </div>
>  <p style="page-break-before: always" /><div class="pdftoc">
>        <h1>Table of Contents</h1>
>
>    </div>
><p style="page-break-before: always" /><div id="xwikimaincontainer">
><div id="xwikimaincontainerinner">
>
><div id="xwikicontent">
>      <h4 class="wikigeneratedid" id="HReferencearchitectureoverview"><span><span id="_Ref241379932" />Reference architecture overview</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDocumentpurpose"><span>Document purpose</span></h5></div></td><td><div><p>This Reference Architecture provides an overview of the architecture of a virtualized&nbsp;business continuity&nbsp;solution that uses the EMC Celerra unified storage platform and Oracle Database 11g on Linux using DNFS and NFS. Key elements, migration details, and hardware and software resources are among the topics discussed.</p><p>Information in this document can be used:</p><ul><li>As the basis for a solution build, white paper, best practices document, or training.</li><li>By other EMC organizations (for example, the technical services or sales organization) as the basis for producing documentation for a technical services or sales kit.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutionpurpose"><span>Solution purpose</span></h5></div></td><td>The purposes of this solution are to:<div><ul><li>Demonstrate the functional, performance, resiliency, and scalability capabilities of an Oracle software stack that:</li><li>Is booted on virtualized hardware and incorporates a four-node VMware High Availability (HA) cluster.</li><li>Uses either the Oracle Direct NFS (DNFS) protocol (Oracle 11<em>g</em>) or the kernel NFS (KNFS) protocol (Oracle 10<em>g</em>) to access the storage elements for the Oracle Database.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HThebusinesschallenge"><span>The business challenge</span></h5></div></td><td><div><p>Midsize enterprises face the same challenges as their larger counterparts when it comes to managing database environments. These challenges include:</p><ul><li>Rising costs</li><li>Control over resource utilization and scaling</li><li>Lack of sufficient IT resources to deploy, manage, and maintain complex environments at the departmental level</li><li>The need to reduce power, cooling, and space requirements</li></ul><p>Unlike large enterprises, midsize enterprises are constrained by smaller budgets and cannot afford a custom, one-off solution. This makes the process of creating a database solution for midsize enterprises even more challenging than for large enterprises.</p><p>Traditional database deployments have relied on utilizing fiber channel protocol storage infrastructure in a physically managed environment.</p><p>Through significant technology innovations and close collaboration with both Oracle and VMware, EMC is able to offer new advanced solutions, incorporating flexible, tiered storage functionality and multiple protocols, as well as optimized use of virtualization.</p><p>Customers&rsquo; choice to leverage different storage protocols, functionality, and virtualization should be based on their individual application requirements for utilization, performance, flexibility, and cost.</p><p>EMC designed, tested, and documented this solution to specifically address the following challenges:</p><ul><li>Rising costs</li></ul><p>Focus on deploying Oracle over lower-cost NFS protocol environments to reduce cost and improve efficiency of networked storage</p><ul><li>Resource utilization</li></ul><p>Align the technology strengths of networked storage with virtualization software to increase database server and storage utilization, with higher leverage at scale</p><ul><li>Resource efficiency</li></ul><p>Simplify database resource and infrastructure administration utilizing NFS and virtualization. Empower DBAs with enhanced solutions for backup, data movement, and data protection.</p><p>This solution documents implementation procedures and best practices for deploying a single platform solution to quickly and effectively to achieve these benefits.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HThetechnologysolution"><span>The technology solution</span></h5></div></td><td>This solution demonstrates how organizations can:<div><ul><li>Maximize the use of the database-server CPU, memory, and I/O channels by offloading the performance impacts of backup, restore, and recovery operations from the production server.</li><li>Use virtualization to reduce costs by reducing the number of servers and related IT hardware in the data center.</li><li>Implement a high-availability solution using a VMware HA cluster.</li><li>Get the most out of hardware by using VMware DRS to automatically reallocate virtual machines, according to need, across servers.</li><li>Use DNFS to:</li></ul><ul><li>Simplify network setup and management by taking advantage of DNFS automated management of tasks, such as load balancing across network connections and tuning of Linux NFS parameters.</li><li>Increase the capacity and throughput of their existing infrastructure. Transactions per second and user load are both higher with DNFS than with KNFS, enabling more output from the same infrastructure.</li></ul><ul><li>Use EMC Replication Manager for NFS with EMC SnapSure to free up the database server&rsquo;s CPU, memory, and I/O channels from the effects of operations relating to backup, restore, and recovery. EMC Replication Manager for NFS with EMC SnapSure writeable checkpoints also helps in creating test/development systems without any impact on the production environment.</li><li>Ensure business continuity by using Celerra and Oracle Data Guard to provide disaster recovery capability.</li></ul></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HSolutioncomponents"><span><span id="_Ref241380063" />Solution components</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction"><span>Introduction</span></h5></div></td><td>This section describes the components of the solution, and explains some of the key terminology and concepts that are used in this document.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HKeytermsdefined"><span>Key terms defined</span></h5></div></td><td>The following table describes several terms used in this document:<div><table><tbody><tr><td><strong>Term</strong></td><td><strong>Description</strong></td></tr><tr><td>Solution</td><td>A solution is a complete stack of hardware and software upon which a customer would choose to run their entire business or business function.</td></tr><tr><td>Solution attribute</td><td>A solution attribute addresses the entire solution stack, but does so in a way relating to a discrete area of testing. For example, performance testing is a solution attribute.</td></tr><tr><td>Solution component</td><td><div><p>A solution component addresses a subset of the solution stack that consists of a discrete set of hardware or software, and focuses on a single IT function. For example, backup and recovery, and disaster recovery are solution components.</p><p>A solution component can be either &ldquo;basic&rdquo; or &ldquo;advanced.&rdquo;</p></div></td></tr><tr><td>Basic solution component</td><td>A basic solution component uses only the features and functionality provided by the Oracle stack. Examples are RMAN for backup and recovery, and Data Guard for disaster recovery.</td></tr><tr><td>Advanced solution component</td><td>An advanced solution component uses the features and functionality of EMC hardware or software. Examples are EMC SnapView&trade; for backup and recovery, and EMC MirrorView&trade; for disaster recovery.</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutionattributes"><span>Solution attributes</span></h5></div></td><td>The following table describes the solution attributes that are included in this solution:<div><table><tbody><tr><td><strong>Attribute</strong></td><td><strong>Description</strong></td></tr><tr><td>Scale-out OLTP</td><td>This is the baseline performance test presently used for virtualized solutions. It consists of an industry-standard TPC-C workload running on a cluster of VMware ESX servers. Multiple database images are used for the workload, emulating a software-as-a-service (SaaS) customer. This is a scale-out, because all users in the database are not able to access all rows in the combined databases but can only see the data in the database to which it is connected. Thus, the database is federated.</td></tr><tr><td>Resiliency</td><td>The purpose of resiliency testing is to validate the fault-tolerance and high-availability features of the hardware and software stack. Faults are inserted into the configuration at various layers in the solutions stack. Some of the layers where fault tolerance is tested include:<div><ul><li>VMware HA cluster interconnect port</li><li>Storage processor</li><li>Data Mover</li></ul></div></td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutioncomponents-1"><span>Solution components</span></h5></div></td><td>The following table describes the solution components that are included in this solution:<div><table><tbody><tr><td><strong>Component</strong></td><td><strong>Description</strong></td></tr><tr><td>Basic Backup</td><td>This is backup and recovery using Oracle RMAN, the built-in backup and recovery tool provided by Oracle.</td></tr><tr><td>Advanced Backup</td><td><div><p>This is backup and recovery using EMC value-added software or hardware.</p><p>In this solution EMC SnapSure is used to provide Advanced Backup functionality.</p></div></td></tr><tr><td>Basic Protect</td><td>This is disaster recovery using Oracle Data Guard, Oracle&rsquo;s built-in remote replication tool.</td></tr><tr><td>Test/Dev</td><td>A running production OLTP database is cloned with minimal, if any, performance impact on the production server, as well as no downtime. The resulting dataset is provisioned on another server for use for testing and development.</td></tr><tr><td>Migration</td><td>The ability to migrate a running production Oracle database from one storage protocol to another (FCP/ASM to DNFS or KNFS, or vice versa) is a frequent customer request. This can include full production database cut-over, or the creation of a clone on another storage protocol for backup, test/dev, or other purposes.</td></tr></tbody></table></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HTechnologysolution"><span>Technology solution</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOverview"><span>Overview</span></h5></div></td><td><div><p>All database objects are stored on an NFS mount. In the case of Oracle Database 11<em>g</em>, datafiles, tempfiles, controlfiles, online redo logfiles, and archive logfiles are accessed using the DNFS protocol.</p><p>The Oracle software stack is booted on virtualized hardware and incorporates a four-node VMware High Availability (HA) cluster. For the purpose of high availability, VMotion is used to migrate a virtual machine running the production database from one ESX server to another without any downtime. Each ESX server is connected to the production storage using a dedicated storage network; a separate set of dedicated TCP/IP networks is used for the cluster interconnect. Then based on the need, VMware DRS is used to automatically allocate resources to multiple virtual machines for load-balancing purposes.</p><p>Two sites connected by a WAN are used in the solution, one site is used for production and the other site is used as a disaster recovery target. Oracle 11<em>g</em> or 10<em>g</em> for x86-64 is run on Red Hat Enterprise Linux or on Oracle Enterprise Linux on virtual machines.</p><p>The solution also includes virtualized servers for use as test/dev and basic protect targets. Virtualization of the test/dev and disaster recovery (DR) target servers is supported using VMware ESX. The Replication Manager server is also virtualized.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HProductionsite"><span>Production site</span></h5></div></td><td>The production site consists of:<div><ul><li>A Celerra connected to the four-node VMware HA cluster through the production storage network. EMC SnapSure is used to provide an advanced backup solution. SnapSure writeable checkpoints are used to create a test/dev target database.</li><li>Virtualized Oracle Database 11<em>g</em> or 10<em>g</em> scale-out servers are running on virtual machines hosted on a four-node VMware HA cluster.</li><li>The virtualized single-instance server is connected to the client, WAN, and target storage networks through virtualized connections on the virtualization server.</li><li>The Oracle Database 11<em>g</em> or 10<em>g</em> scale-out servers are connected to the client, HA cluster interconnect, WAN, and production storage networks through virtualized connections on the VMware ESX servers.</li><li>The Replication Manager agent is installed on all production database servers and the mount host where the test/dev target database will be started.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDisasterrecoverytargetsite"><span>Disaster recovery target site</span></h5></div></td><td>The disaster recovery target site consists of:<div><ul><li>A virtualized single-instance Oracle Database 11<em>g</em> or 10<em>g</em> server that is used as:</li></ul><ul><li>The disaster recovery target for Basic Protect</li><li>The target for Test/Dev</li></ul><ul><li>A Celerra connected to the VMware ESX through the disaster recovery storage network. The Oracle Database 11<em>g</em>/10<em>g</em> single-instance target server accesses this network through a virtualized switch on the ESX server.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HStoragelayout"><span>Storage layout</span></h5></div></td><td><div><p>The following table describes how each Oracle file type and database object is stored for this solution:</p><table><tbody><tr><td><strong>What</strong></td><td><strong>Where</strong></td><td><strong>File-system type</strong></td></tr><tr><td>Oracle datafiles</td><td rowspan="5">FC disks</td><td rowspan="8">RAID-protected NFS file system</td></tr><tr><td>Oracle tempfiles</td></tr><tr><td>Oracle online redo logfiles</td></tr><tr><td>Oracle controlfiles</td></tr><tr><td>VMDK pointer files</td></tr><tr><td>Archived logfiles</td><td rowspan="3">SATA II</td></tr><tr><td>Flashback recovery area</td></tr><tr><td>Backup target</td></tr></tbody></table><p>For implementations using Oracle Database 11<em>g</em>, all files are accessed using DNFS. For implementations using Oracle Database 10<em>g</em>, all files are accessed using KNFS.</p><ul><li>RAID-protected NFS file systems are designed to satisfy the I/O demands of particular database objects. For example, RAID 5 is sometimes used for the datafiles and tempfiles, but RAID 1 is always used for the online redo logfiles. Two separate RAID configurations are supported. For more information refer to <em>EMC Solutions for Oracle Database 10g/11g for Midsize Enterprises Physically Booted Solutions with EMC Celerra NS40 Unified Storage Platform - Reference Architecture</em>.</li><li>Oracle datafiles and online redo logfiles reside on their own NFS file system. Online redo logfiles are mirrored across two different file systems using Oracle software multiplexing. Three NFS file systems are used - one file system for datafiles and tempfiles, and two file systems for online redo logfiles.</li><li>Oracle controlfiles are mirrored across the online redo logfile NFS file systems.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNetworkarchitecture"><span>Network architecture</span></h5></div></td><td>The design implements the following physical connections:<div><ul><li>TCP/IP provides network connectivity.</li><li>DNFS provides file system semantics for Oracle Database 11<em>g</em>. KNFS provides file system semantics for NFS file systems on Oracle Database 10<em>g</em>.</li><li>Client virtual machines run on a VMware ESX. They are connected to a client network.</li><li>Client and VMware HA cluster interconnect and redundant TCP/IP storage networks consist of dedicated network switches and virtual local area networks (VLANs).</li><li>The VMware HA cluster interconnect and storage networks consist of trunked and virtualized IP connections to balance and distribute network I/O. Jumbo frames are enabled on these networks.</li></ul></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HMigration"><span>Migration</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction-1"><span>Introduction</span></h5></div></td><td><div><p>Customers often request the ability to migrate a virtualized Oracle Database across storage protocols. In response to this, the Oracle Consulting (CSV) group has validated that customers who have an Oracle Database operating in a virtualized environment can migrate data from:</p><ul><li>An FCP/ASM to an NFS-mounted file system</li><li>An NFS-mounted file system to an FCP/ASM</li></ul><p>Customers might be interested in cross-protocol migration because testing and development activities can be supported on less expensive, simpler NFS storage, while production can be carried out on higher-performing ASM/FCP storage.</p><p>Customers may also want to use the storage replication technologies available on a different protocol from the production database.&nbsp; For example, customers may wish to use RecoverPoint to support remote replication but have production on NFS.</p><p>The migrations were performed with minimal performance impact and no downtime on the virtualized production database.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSANtoNASmigrationdiagram"><span>SAN to NAS migration diagram</span></h5></div></td><td>The following diagram is a high-level view of the migration component:</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_4ecd98f6dd410c9a.png" height="481" src="pdf2802290551349436541.tmp" width="622" /></p><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HMigratinganonlineOracleDatabasefromSANtoNAS"><span>Migrating an online Oracle Database from SAN to NAS</span></h5></div></td><td>These steps were followed to perform the SAN to NAS migration operation:<div><table><tbody><tr><td><strong>Step</strong></td><td><strong>Action</strong></td></tr><tr><td>1</td><td>Using EMC Replication Manager, a consistent backup of the running virtualized production database is performed on the EMC CLARiiON<sup>&reg;</sup> using SnapView snapshot.</td></tr><tr><td>2</td><td>This backup is mounted (but not opened) on the migration server in this case a VMware virtual machine (a physically booted server would also work). The NFS target array is also mounted on the migration server.</td></tr><tr><td>3</td><td>Using Oracle Recovery Manager (RMAN), a backup of this database is taken onto the target location. This backup is performed as a database image, so that the datafiles are written directly to the target NFS mount.</td></tr><tr><td>4</td><td>The migration server is then switched to the new database, which has been copied by RMAN to the NFS mount.</td></tr><tr><td>5</td><td>The target database is set in Data Guard continuous recovery mode, and Data Guard log ship/log apply is used to catch the virtualized target database up to the virtualized production version.</td></tr><tr><td>6</td><td>Once the virtualized target database is caught up to production, Data Guard failover can be used to retarget to the virtualized target database. If appropriate networking configuration is performed, clients will see no downtime when this operation occurs.</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="H"><span /></h5></div></td><td>The result, as stated above, is that the virtualized production FCP-mounted database can be migrated to NFS with minimal performance impact and no downtime.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNAStoSANmigrationdiagram"><span>NAS to SAN migration diagram</span></h5></div></td><td>The following diagram is a high-level view of the NAS to SAN migration component.</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_856356489430d5b5.png" height="464" src="pdf7421571461880137549.tmp" width="626" /></p><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HMigratinganonlineOracleDatabasefromNAStoSAN"><span>Migrating an online Oracle Database from NAS to SAN</span></h5></div></td><td>These steps were followed to perform the NAS to SAN migration operation:<div><table><tbody><tr><td><strong>Step</strong></td><td><strong>Action</strong></td></tr><tr><td>1</td><td>Using EMC Replication Manager, a consistent backup of the running virtualized production database is performed on the EMC Celerra<sup>&reg;</sup> using a SnapSure checkpoint snapshot.</td></tr><tr><td>2</td><td>This backup is mounted (but not opened) on the migration server, in this case a VMware virtual machine (a physically booted server would also work). The FCP/ASM target LUNs are also mounted on the migration server.</td></tr><tr><td>3</td><td>Using Oracle Recovery Manager (RMAN), a backup of this database is taken onto the target location. This backup is performed as a database image, so that the datafiles are written directly to the target FCP/ASM LUNs.</td></tr><tr><td>4</td><td>The migration server is then switched to the new database that has been copied by RMAN to the FCP/ASM LUNs.</td></tr><tr><td>5</td><td>The virtualized target database is set in Data Guard continuous recovery mode, and Data Guard log ship/log apply is used to catch the virtualized target database up to the production version.</td></tr><tr><td>6</td><td>Once the virtualized target database is copied to production, Data Guard failover can be used to retarget to the virtualized target database. If appropriate networking configuration is performed, clients will not see any downtime when this operation occurs.</td></tr></tbody></table></div></td></tr></tbody></table><p>The result, as stated above, is that the virtualized production NFS-mounted database can be migrated to FCP/ASM with minimal performance impact and no downtime.</p><h4 class="wikigeneratedid" id="HKeyelements"><span>Key elements</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction-2"><span>Introduction</span></h5></div></td><td>This section provides an overview of the technologies that are used in this solution.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCCelerraunifiedstorageplatform"><span>EMC Celerra unified storage platform</span></h5></div></td><td><div><p>The Celerra is a remarkably versatile device. Celerra includes a world-class network-attached storage (NAS) array combined with the functionality and performance of the leading midrange storage area network (SAN) array. Celerra provides both NAS and SAN functionality and performance without compromise.</p><p>The key features provided by the Celerra are described in the following table:</p><table><tbody><tr><td><strong>Feature</strong></td><td><strong>Provided by</strong></td></tr><tr><td>NAS</td><td><div><p>Network File System (NFS) and</p><p>Common Internet File System (CIFS) protocols</p></div></td></tr><tr><td>iSCSI storage</td><td>Celerra&rsquo;s Data Movers</td></tr><tr><td>SAN storage</td><td>Fibre Channel Protocol (FCP) through the back-end EMC CLARiiON CX4</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCReplicationManager"><span>EMC Replication Manager</span></h5></div></td><td><div><p>EMC Replication Manager manages EMC point-in-time replication technologies through a centralized management console. Replication Manager coordinates the entire data replication process &ndash; from discovery and configuration to the management of multiple application consistent disk-based replicas. Replication Manager can auto-discover your replication environment and enable streamlined management by scheduling, recording, and cataloging replica information including auto-expiration.</p><p>Replication Manager integrates with the Oracle Database server and provides an easy interface to create and manage Oracle replicas.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCCelerraSnapSure"><span>EMC Celerra SnapSure</span></h5></div></td><td><div><p>SnapSure creates a logical point-in-time image (checkpoint) of a production file system (PFS) that reflects the state of the PFS at the point in time when the checkpoint is created. SnapSure can maintain up to 96 PFS checkpoints while allowing PFS applications continued access to the real-time data.</p><h6 class="wikigeneratedid" id="HHowSnapSureworks"><span>How SnapSure works</span></h6><p>The principle of SnapSure is &ldquo;copy on first write&rdquo; (COFW). When a block within the PFS is modified, a copy containing the block&rsquo;s original content is saved to a separate volume called the SavVol. Subsequent changes made to the same block in the PFS are not copied into the SavVol. The original blocks from the PFS (in the SavVol) and the unchanged PFS blocks (remaining in the PFS) are read by SnapSure according to a bitmap and blockmap data-tracking structure. These blocks combine to provide a complete point-in-time file system image called a checkpoint.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVMwareESX"><span>VMware ESX</span></h5></div></td><td>VMware ESX is the flagship virtualization server product from VMware and is the market leader in server virtualization. VMware ESX provides a high-performance, robust, fault-tolerant and high-availability virtualization solution.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOraclesoftwarestack"><span>Oracle software stack</span></h5></div></td><td>The Oracle software stack covered by this solution consists of:<div><ul><li>Oracle Database 11<em>g</em> and 10<em>g</em></li><li>Oracle DNFS (11<em>g</em> only; KNFS used on 10<em>g</em>)</li><li>Oracle Enterprise Linux</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOracleDNFS"><span>Oracle DNFS</span></h5></div></td><td><div><p>DNFS is a new feature introduced in Oracle Database 11<em>g</em>; it integrates the NFS client directly inside the database kernel instead of the operating system kernel. DNFS provides significant performance, manageability, and efficiency benefits over KNFS.</p><h6 class="wikigeneratedid" id="HBetterperformance"><span>Better performance</span></h6><p>Transactions per second and user load are both higher with DNFS than with KNFS, and this enables organizations to gain more output from the same infrastructure. CPU costs on both the database server and the file server are lower. In addition, port scaling with DNFS is much better, enabling higher bandwidth and thus higher scaling.</p><h6 class="wikigeneratedid" id="HHighavailability"><span>High availability</span></h6><p>Load balancing and high availability (HA) are managed internally within the DNFS client.</p><h6 class="wikigeneratedid" id="HConcurrentI2FO"><span>Concurrent I/O</span></h6><p>The DNFS client performs concurrent I/O by bypassing the operating system. The benefits of this are:</p><ul><li>Better performance due to the reduction of memory consumption and CPU utilization</li><li>Consistent NFS performance, which is observed across all operating systems.</li></ul><h6 class="wikigeneratedid" id="HOptimizedfordatabaseworkloads"><span>Optimized for database workloads</span></h6><p>DNFS is optimized for database workloads and supports asynchronous I/O, which is suitable for most databases. It delivers optimized performance by automatically load balancing across the available paths. Load balancing in DFNS is almost invariably superior to the conventional Linux kernel NFS (KNFS).</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVMwareDistributedResourceScheduler"><span>VMware Distributed Resource Scheduler</span></h5></div></td><td>VMware Distributed Resource Scheduler (DRS) is a cluster feature of VMware vCenter Server; it provides dynamic load balancing and resource sharing for multiple virtual machines across ESX servers. DRS uses VMotion as the underlying transport feature to move virtual machines from one ESX server to another.</td></tr></tbody></table><h4 class="wikigeneratedid" id="HPhysicalarchitecture"><span>Physical architecture</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HReferencearchitecturediagram"><span>Reference architecture diagram</span></h5></div></td><td>The following diagram depicts the overall physical architecture of the solution.</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_dc59c2f02504ebed.png" height="515" src="pdf1052853033950301652.tmp" width="651" /></p><h4 class="wikigeneratedid" id="HValidatedenvironmentprofile"><span>Validated environment profile</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HProfilecharacteristics"><span>Profile characteristics</span></h5></div></td><td>For information on the validated environment profile and performance results, refer to the Proven Solution Guide for this solution. This information can be accessed on EMC Powerlink<sup>&reg;</sup>, EMC.com, and the EMC|KB.WIKI.</td></tr></tbody></table><h4 class="wikigeneratedid" id="HHardwareandsoftwareresources"><span><span id="_Ref223689231" /><span id="_Ref223689206" />Hardware and software resources</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HHardware"><span>Hardware</span></h5></div></td><td>The hardware used to validate the solution is listed below.</td></tr></tbody></table><table><tbody><tr><td><strong>Equipment</strong></td><td><strong>Quantity</strong></td><td><strong>Configuration</strong></td></tr><tr><td>EMC Celerra unified storage platforms (included an EMC CLARiiON CX4 back-end storage array)</td><td>2</td><td><div><ul><li>2 Data Movers</li><li>4 GbE network connections per Data Mover</li><li>2 or 3 FC shelves</li><li>1 SATA shelf</li><li>30 or 45 73 GB FC disks (depending on configuration)</li><li>15 1 TB SATA disks</li><li>1 Control Station</li><li>2 storage processors</li><li>DART version 5.6.44-4</li></ul></div></td></tr><tr><td>Gigabit Ethernet switches</td><td>5</td><td>24 ports per switch</td></tr><tr><td>VMware ESX HA cluster servers</td><td>4</td><td><div><ul><li>2 2.66 GHz Intel Pentium 4 quad-core processors</li><li>24 GB of RAM</li><li>2 146 GB 15k internal SCSI disks</li><li>2 onboard GbE Ethernet NICs</li><li>2 additional Intel PRO/1000 PT quad-port GbE Ethernet NICs</li><li>2 SANblade QLE2462-E-SP 4 Gb/s dual-port FC HBAs (4 ports in total)</li></ul></div></td></tr><tr><td>Virtualization server (VMware ESX)</td><td>1</td><td><div><ul><li>4 2.86 GHz AMD Opteron quad-core processors</li><li>32 GB of RAM</li><li>2 146 GB 15k internal SCSI disks</li><li>2 onboard GbE Ethernet NICs</li><li>3 additional Intel PRO/1000 PT quad-port GbE Ethernet NICs</li><li>2 SANblade QLE2462-E-SP 4 Gb/s dual-port FC HBAs (4 ports in total)</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSoftware"><span>Software</span></h5></div></td><td>The software used to validate the solution is listed below.</td></tr></tbody></table><table><tbody><tr><td><strong>Software</strong></td><td><strong>Version</strong></td></tr><tr><td>Oracle Enterprise Linux</td><td>5.2</td></tr><tr><td>VMware ESX Server/vSphere</td><td>4.0</td></tr><tr><td>Microsoft Windows Server 2003 Standard Edition</td><td>2003</td></tr><tr><td>Oracle Database Standard Edition</td><td>11<em>g</em> (11<em>g</em> Ver. 11.1.0.7.0) or 10<em>g</em></td></tr><tr><td>Quest Benchmark Factory for Databases</td><td>5.8.1</td></tr><tr><td>EMC Celerra Manager Advanced Edition</td><td>5.6</td></tr><tr><td>EMC Navisphere<sup>&reg;</sup> Agent</td><td>6.26.0.2.24</td></tr><tr><td>EMC Replication Manager</td><td>5.2.2.0</td></tr><tr><td>EMC FLARE<sup>&reg;</sup></td><td>04.28.000.5.504</td></tr><tr><td>EMC DART</td><td>5.6.44-4</td></tr><tr><td>EMC Navisphere Management</td><td>6.28</td></tr></tbody></table><h4 class="wikigeneratedid" id="HConclusion"><span>Conclusion</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSummary"><span>Summary</span></h5></div></td><td>This section provides a summary of the solution and of the business challenges that it addresses.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HReducedtotalcostofownership"><span>Reduced total cost of ownership</span></h5></div></td><td><div><p>In any reasonable configuration, the database server's CPU is the most precious component of the entire architecture. Therefore, the over-arching principle of EMC's Oracle Database 11<em>g</em> and 10<em>g</em> solutions for midsize enterprises is to free up the database server's CPU (as well as memory and I/O channels) from utility operations such as backup and recovery, disaster recovery staging, test/dev, and cloning. The highest and best use of the database server&rsquo;s CPUs is to parse and execute the SQL statements that are required by the application user.</p><h6 class="wikigeneratedid" id="HCPUusage"><span>CPU usage</span></h6><p>This solution reduces the load on the database server CPU by using:</p><ul><li>EMC Replication Manager for NFS with EMC SnapSure to carry out a physical backup of an Oracle 11<em>g</em> or 10<em>g</em> production database while offloading all performance impacts of the backup operation from the production server</li><li>DNFS to achieve better performance due to the reduction of memory consumption and CPU utilization</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVirtualization"><span>Virtualization</span></h5></div></td><td><div><p>The use of virtualization for the production database server provides manageability and ease-of-use advantages. In a scale-out context, virtualization can provide superior performance and scalability compared to physically booted configurations - even when using hardware identical to that used in the physically booted configuration.</p><p>Utility servers, such as a test/dev target and basic protect target, are more easily and conveniently managed as virtual machines than as physically booted Oracle Database servers. The advantages of consolidation, flexible migration and so on, which are the mainstays of virtualization, apply to these servers as well.</p><h6 class="wikigeneratedid" id="HReducedcosts"><span>Reduced costs</span></h6><p>One of the main challenges faced by the customer is to reduce cost by utilizing infrastructure effectively. Virtualization enables reduction in the number of servers and related IT hardware in the data center. The other main feature is the ability to move a running virtual machine production database from one physical sever to another physical server without any downtime.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDistributedresourcescheduling"><span>Distributed resource scheduling</span></h5></div></td><td><div><p>VMware DRS provides the ability to distribute workload across multiple ESX servers by migrating virtual machines according to resource consumption and demand. VMware DRS dynamically manages pooled resources from multiple ESX servers. VMware DRS aggregates and centrally manages the resources of multiple hosts as resource pools. Different sets of rules and priorities can be defined for individual Oracle virtual machines based on the criticality.</p><div class="wikimodel-emptyline" /><p>When an Oracle Database server virtual machine operating within a resource pool experiences increased utilization of resources, DRS will try to allocate the resources from the centralized pool based on the rules and priorities.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HHighavailability-1"><span>High availability</span></h5></div></td><td><div><p><strong>VMotion</strong></p><p>The use of VMware VMotion to migrate an Oracle Database instance from one piece of hardware to another was achieved in our tests with virtually no performance impact and no downtime on the running Oracle Database instance. This provides a very high level of manageability and downtime reduction for tasks such as software and hardware upgrades.</p><h6 class="wikigeneratedid" id="HVMwareHAcluster"><span>VMware HA cluster</span></h6><p>The use of a VMware HA cluster provides further high-availability advantages to the virtualized solution. EMC has validated the use of a VMware HA cluster with Oracle Database 11<em>g</em> and 10<em>g</em> in a single-instance scale-out environment. In addition, a VMware HA cluster can be used to automate failover in the event of a hardware or software failure.</p><h6 class="wikigeneratedid" id="HFaultTolerance"><span>Fault Tolerance</span></h6><p>The use of VMware Fault Tolerance provides true zero downtime for Oracle VMware-based database servers. This means that a database server running on VMware can be protected from unplanned downtime. This is a significant improvement over the previous version of VMware and is provided on the HA cluster. The use of Fault Tolerance is presently limited to one vCPU, making Fault Tolerance only applicable to smaller Oracle Database servers.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HImprovedperformance"><span>Improved performance</span></h5></div></td><td>The Direct NFS (DNFS) client performs concurrent I/O by bypassing the operating system. The benefits of this are:<div><ul><li>Consistent NFS performance is observed across all operating systems.</li><li>DNFS is optimized for database workloads and supports asynchronous I/O, which is suitable for most databases. It delivers optimized performance by automatically load balancing across the available paths. Load balancing in DNFS is frequently superior to the conventional Linux kernel NFS (KNFS).</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEaseofuse"><span>Ease of use</span></h5></div></td><td><div><p>The use of DNFS simplifies network setup and management by eliminating administration tasks such as:</p><ul><li>Setting up network subnets</li><li>LACP bonding</li><li>Tuning of Linux NFS parameters</li></ul><p>Load balancing and high availability (HA) are managed internally within the DNFS client.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HBusinesscontinuity"><span>Business continuity</span></h5></div></td><td><div><p><strong>Advanced backup and recovery</strong></p><p>EMC Replication Manager is a comprehensive graphical application that provides Oracle storage replication using EMC storage technology. This eliminates the requirement for the customer to write scripts or to manually perform replication tasks. These tasks can now be fully automated and managed by Replication Manager.</p><p>One of the solution components using Replication Manager in the solution presented in this reference architecture included Advanced Backup and Recovery using EMC SnapSure checkpoints.</p><h6 class="wikigeneratedid" id="HTest2Fdev"><span>Test/dev</span></h6><p>The ability to deploy a writeable copy of the production database is required by many customers. The process of provisioning this writeable copy must create minimal, if any, performance impact on the production database server. Also, absolutely no downtime can be tolerated. The Test/Dev solution component documented here provides this using EMC Replication Manager for NFS with EMC SnapSure writeable checkpoint.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HRobustperformanceandscaling"><span>Robust performance and scaling</span></h5></div></td><td><div><p>The resiliency testing carried out by EMC ensures that the database configuration is reliable. High availability is used at every major layer of the solution, including the database server, NAS file server, and back-end CLARiiON CX4. By testing the fault tolerance of all of these layers, the ability of the application to withstand hardware failures with no downtime is assured.</p><p>The performance testing carried out by EMC utilizes an industry-standard OLTP benchmark but does so without exotic tunings that are not compliant with best practices. In addition, real-world configurations that the customer is likely to deploy are used. This enables the customer to be reasonably assured that the configuration that they choose to run their application will do so predictably and reliably.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNextsteps"><span>Next steps</span></h5></div></td><td><div><p>EMC can help accelerate assessment, design, implementation, and management while lowering the implementation risks and costs of an end-to- end solution for an Oracle Database 11<em>g</em> or 10<em>g</em> environment.</p><p>To learn more about this and other solutions contact an EMC representative or visit <span style="text-decoration:underline"><span class="wikiexternallink"><a href="http://www.emc.com/solutions/application-environment/oracle/solutions-for-oracle-database.htm">http://www.emc.com/solutions/application-environment/oracle/solutions-for-oracle-database.htm</a></span></span></p></div></td></tr></tbody></table><div id="_PictureBullets" />
>          </div>
></div>
></div>
>
></body></html>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<title>
  fdg - Reference architecture overview
</title>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
<meta content="en" name="language" />

</head><body class="exportbody" pdfcover="1" pdftoc="1">

  <div class="pdfheader">
                      Reference architecture overview
<hr style="border-width: 0.25pt" />

    </div>
  <div class="pdffooter">
        <hr style="border-width: 0.25pt" />
Page <span class="page-number" /> / <span class="page-total" /> - last modified by Administrator on 2019/06/21 15:34

    </div>
  <div class="pdfcover">
        <div style="width: 100%;">
<hr style="border-width: 0.25pt" />
<h1 style="text-align: left;">
  Reference architecture overview
</h1>
<div>
  <p class="author" style="text-align: left;">last modified by Administrator</p>
</div>
<div>
  <p class="date" style="text-align: left;">on 2019/06/21 15:34</p>
</div>
<br />
<hr style="border-width: 0.25pt" />
</div>

    </div>
  <p style="page-break-before: always" /><div class="pdftoc">
        <h1>Table of Contents</h1>

    </div>
<p style="page-break-before: always" /><div id="xwikimaincontainer">
<div id="xwikimaincontainerinner">

<div id="xwikicontent">
      <h4 class="wikigeneratedid" id="HReferencearchitectureoverview"><span><span id="_Ref241379932" />Reference architecture overview</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDocumentpurpose"><span>Document purpose</span></h5></div></td><td><div><p>This Reference Architecture provides an overview of the architecture of a virtualized&nbsp;business continuity&nbsp;solution that uses the EMC Celerra unified storage platform and Oracle Database 11g on Linux using DNFS and NFS. Key elements, migration details, and hardware and software resources are among the topics discussed.</p><p>Information in this document can be used:</p><ul><li>As the basis for a solution build, white paper, best practices document, or training.</li><li>By other EMC organizations (for example, the technical services or sales organization) as the basis for producing documentation for a technical services or sales kit.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutionpurpose"><span>Solution purpose</span></h5></div></td><td>The purposes of this solution are to:<div><ul><li>Demonstrate the functional, performance, resiliency, and scalability capabilities of an Oracle software stack that:</li><li>Is booted on virtualized hardware and incorporates a four-node VMware High Availability (HA) cluster.</li><li>Uses either the Oracle Direct NFS (DNFS) protocol (Oracle 11<em>g</em>) or the kernel NFS (KNFS) protocol (Oracle 10<em>g</em>) to access the storage elements for the Oracle Database.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HThebusinesschallenge"><span>The business challenge</span></h5></div></td><td><div><p>Midsize enterprises face the same challenges as their larger counterparts when it comes to managing database environments. These challenges include:</p><ul><li>Rising costs</li><li>Control over resource utilization and scaling</li><li>Lack of sufficient IT resources to deploy, manage, and maintain complex environments at the departmental level</li><li>The need to reduce power, cooling, and space requirements</li></ul><p>Unlike large enterprises, midsize enterprises are constrained by smaller budgets and cannot afford a custom, one-off solution. This makes the process of creating a database solution for midsize enterprises even more challenging than for large enterprises.</p><p>Traditional database deployments have relied on utilizing fiber channel protocol storage infrastructure in a physically managed environment.</p><p>Through significant technology innovations and close collaboration with both Oracle and VMware, EMC is able to offer new advanced solutions, incorporating flexible, tiered storage functionality and multiple protocols, as well as optimized use of virtualization.</p><p>Customers&rsquo; choice to leverage different storage protocols, functionality, and virtualization should be based on their individual application requirements for utilization, performance, flexibility, and cost.</p><p>EMC designed, tested, and documented this solution to specifically address the following challenges:</p><ul><li>Rising costs</li></ul><p>Focus on deploying Oracle over lower-cost NFS protocol environments to reduce cost and improve efficiency of networked storage</p><ul><li>Resource utilization</li></ul><p>Align the technology strengths of networked storage with virtualization software to increase database server and storage utilization, with higher leverage at scale</p><ul><li>Resource efficiency</li></ul><p>Simplify database resource and infrastructure administration utilizing NFS and virtualization. Empower DBAs with enhanced solutions for backup, data movement, and data protection.</p><p>This solution documents implementation procedures and best practices for deploying a single platform solution to quickly and effectively to achieve these benefits.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HThetechnologysolution"><span>The technology solution</span></h5></div></td><td>This solution demonstrates how organizations can:<div><ul><li>Maximize the use of the database-server CPU, memory, and I/O channels by offloading the performance impacts of backup, restore, and recovery operations from the production server.</li><li>Use virtualization to reduce costs by reducing the number of servers and related IT hardware in the data center.</li><li>Implement a high-availability solution using a VMware HA cluster.</li><li>Get the most out of hardware by using VMware DRS to automatically reallocate virtual machines, according to need, across servers.</li><li>Use DNFS to:</li></ul><ul><li>Simplify network setup and management by taking advantage of DNFS automated management of tasks, such as load balancing across network connections and tuning of Linux NFS parameters.</li><li>Increase the capacity and throughput of their existing infrastructure. Transactions per second and user load are both higher with DNFS than with KNFS, enabling more output from the same infrastructure.</li></ul><ul><li>Use EMC Replication Manager for NFS with EMC SnapSure to free up the database server&rsquo;s CPU, memory, and I/O channels from the effects of operations relating to backup, restore, and recovery. EMC Replication Manager for NFS with EMC SnapSure writeable checkpoints also helps in creating test/development systems without any impact on the production environment.</li><li>Ensure business continuity by using Celerra and Oracle Data Guard to provide disaster recovery capability.</li></ul></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HSolutioncomponents"><span><span id="_Ref241380063" />Solution components</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction"><span>Introduction</span></h5></div></td><td>This section describes the components of the solution, and explains some of the key terminology and concepts that are used in this document.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HKeytermsdefined"><span>Key terms defined</span></h5></div></td><td>The following table describes several terms used in this document:<div><table><tbody><tr><td><strong>Term</strong></td><td><strong>Description</strong></td></tr><tr><td>Solution</td><td>A solution is a complete stack of hardware and software upon which a customer would choose to run their entire business or business function.</td></tr><tr><td>Solution attribute</td><td>A solution attribute addresses the entire solution stack, but does so in a way relating to a discrete area of testing. For example, performance testing is a solution attribute.</td></tr><tr><td>Solution component</td><td><div><p>A solution component addresses a subset of the solution stack that consists of a discrete set of hardware or software, and focuses on a single IT function. For example, backup and recovery, and disaster recovery are solution components.</p><p>A solution component can be either &ldquo;basic&rdquo; or &ldquo;advanced.&rdquo;</p></div></td></tr><tr><td>Basic solution component</td><td>A basic solution component uses only the features and functionality provided by the Oracle stack. Examples are RMAN for backup and recovery, and Data Guard for disaster recovery.</td></tr><tr><td>Advanced solution component</td><td>An advanced solution component uses the features and functionality of EMC hardware or software. Examples are EMC SnapView&trade; for backup and recovery, and EMC MirrorView&trade; for disaster recovery.</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutionattributes"><span>Solution attributes</span></h5></div></td><td>The following table describes the solution attributes that are included in this solution:<div><table><tbody><tr><td><strong>Attribute</strong></td><td><strong>Description</strong></td></tr><tr><td>Scale-out OLTP</td><td>This is the baseline performance test presently used for virtualized solutions. It consists of an industry-standard TPC-C workload running on a cluster of VMware ESX servers. Multiple database images are used for the workload, emulating a software-as-a-service (SaaS) customer. This is a scale-out, because all users in the database are not able to access all rows in the combined databases but can only see the data in the database to which it is connected. Thus, the database is federated.</td></tr><tr><td>Resiliency</td><td>The purpose of resiliency testing is to validate the fault-tolerance and high-availability features of the hardware and software stack. Faults are inserted into the configuration at various layers in the solutions stack. Some of the layers where fault tolerance is tested include:<div><ul><li>VMware HA cluster interconnect port</li><li>Storage processor</li><li>Data Mover</li></ul></div></td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSolutioncomponents-1"><span>Solution components</span></h5></div></td><td>The following table describes the solution components that are included in this solution:<div><table><tbody><tr><td><strong>Component</strong></td><td><strong>Description</strong></td></tr><tr><td>Basic Backup</td><td>This is backup and recovery using Oracle RMAN, the built-in backup and recovery tool provided by Oracle.</td></tr><tr><td>Advanced Backup</td><td><div><p>This is backup and recovery using EMC value-added software or hardware.</p><p>In this solution EMC SnapSure is used to provide Advanced Backup functionality.</p></div></td></tr><tr><td>Basic Protect</td><td>This is disaster recovery using Oracle Data Guard, Oracle&rsquo;s built-in remote replication tool.</td></tr><tr><td>Test/Dev</td><td>A running production OLTP database is cloned with minimal, if any, performance impact on the production server, as well as no downtime. The resulting dataset is provisioned on another server for use for testing and development.</td></tr><tr><td>Migration</td><td>The ability to migrate a running production Oracle database from one storage protocol to another (FCP/ASM to DNFS or KNFS, or vice versa) is a frequent customer request. This can include full production database cut-over, or the creation of a clone on another storage protocol for backup, test/dev, or other purposes.</td></tr></tbody></table></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HTechnologysolution"><span>Technology solution</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOverview"><span>Overview</span></h5></div></td><td><div><p>All database objects are stored on an NFS mount. In the case of Oracle Database 11<em>g</em>, datafiles, tempfiles, controlfiles, online redo logfiles, and archive logfiles are accessed using the DNFS protocol.</p><p>The Oracle software stack is booted on virtualized hardware and incorporates a four-node VMware High Availability (HA) cluster. For the purpose of high availability, VMotion is used to migrate a virtual machine running the production database from one ESX server to another without any downtime. Each ESX server is connected to the production storage using a dedicated storage network; a separate set of dedicated TCP/IP networks is used for the cluster interconnect. Then based on the need, VMware DRS is used to automatically allocate resources to multiple virtual machines for load-balancing purposes.</p><p>Two sites connected by a WAN are used in the solution, one site is used for production and the other site is used as a disaster recovery target. Oracle 11<em>g</em> or 10<em>g</em> for x86-64 is run on Red Hat Enterprise Linux or on Oracle Enterprise Linux on virtual machines.</p><p>The solution also includes virtualized servers for use as test/dev and basic protect targets. Virtualization of the test/dev and disaster recovery (DR) target servers is supported using VMware ESX. The Replication Manager server is also virtualized.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HProductionsite"><span>Production site</span></h5></div></td><td>The production site consists of:<div><ul><li>A Celerra connected to the four-node VMware HA cluster through the production storage network. EMC SnapSure is used to provide an advanced backup solution. SnapSure writeable checkpoints are used to create a test/dev target database.</li><li>Virtualized Oracle Database 11<em>g</em> or 10<em>g</em> scale-out servers are running on virtual machines hosted on a four-node VMware HA cluster.</li><li>The virtualized single-instance server is connected to the client, WAN, and target storage networks through virtualized connections on the virtualization server.</li><li>The Oracle Database 11<em>g</em> or 10<em>g</em> scale-out servers are connected to the client, HA cluster interconnect, WAN, and production storage networks through virtualized connections on the VMware ESX servers.</li><li>The Replication Manager agent is installed on all production database servers and the mount host where the test/dev target database will be started.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDisasterrecoverytargetsite"><span>Disaster recovery target site</span></h5></div></td><td>The disaster recovery target site consists of:<div><ul><li>A virtualized single-instance Oracle Database 11<em>g</em> or 10<em>g</em> server that is used as:</li></ul><ul><li>The disaster recovery target for Basic Protect</li><li>The target for Test/Dev</li></ul><ul><li>A Celerra connected to the VMware ESX through the disaster recovery storage network. The Oracle Database 11<em>g</em>/10<em>g</em> single-instance target server accesses this network through a virtualized switch on the ESX server.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HStoragelayout"><span>Storage layout</span></h5></div></td><td><div><p>The following table describes how each Oracle file type and database object is stored for this solution:</p><table><tbody><tr><td><strong>What</strong></td><td><strong>Where</strong></td><td><strong>File-system type</strong></td></tr><tr><td>Oracle datafiles</td><td rowspan="5">FC disks</td><td rowspan="8">RAID-protected NFS file system</td></tr><tr><td>Oracle tempfiles</td></tr><tr><td>Oracle online redo logfiles</td></tr><tr><td>Oracle controlfiles</td></tr><tr><td>VMDK pointer files</td></tr><tr><td>Archived logfiles</td><td rowspan="3">SATA II</td></tr><tr><td>Flashback recovery area</td></tr><tr><td>Backup target</td></tr></tbody></table><p>For implementations using Oracle Database 11<em>g</em>, all files are accessed using DNFS. For implementations using Oracle Database 10<em>g</em>, all files are accessed using KNFS.</p><ul><li>RAID-protected NFS file systems are designed to satisfy the I/O demands of particular database objects. For example, RAID 5 is sometimes used for the datafiles and tempfiles, but RAID 1 is always used for the online redo logfiles. Two separate RAID configurations are supported. For more information refer to <em>EMC Solutions for Oracle Database 10g/11g for Midsize Enterprises Physically Booted Solutions with EMC Celerra NS40 Unified Storage Platform - Reference Architecture</em>.</li><li>Oracle datafiles and online redo logfiles reside on their own NFS file system. Online redo logfiles are mirrored across two different file systems using Oracle software multiplexing. Three NFS file systems are used - one file system for datafiles and tempfiles, and two file systems for online redo logfiles.</li><li>Oracle controlfiles are mirrored across the online redo logfile NFS file systems.</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNetworkarchitecture"><span>Network architecture</span></h5></div></td><td>The design implements the following physical connections:<div><ul><li>TCP/IP provides network connectivity.</li><li>DNFS provides file system semantics for Oracle Database 11<em>g</em>. KNFS provides file system semantics for NFS file systems on Oracle Database 10<em>g</em>.</li><li>Client virtual machines run on a VMware ESX. They are connected to a client network.</li><li>Client and VMware HA cluster interconnect and redundant TCP/IP storage networks consist of dedicated network switches and virtual local area networks (VLANs).</li><li>The VMware HA cluster interconnect and storage networks consist of trunked and virtualized IP connections to balance and distribute network I/O. Jumbo frames are enabled on these networks.</li></ul></div></td></tr></tbody></table><h4 class="wikigeneratedid" id="HMigration"><span>Migration</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction-1"><span>Introduction</span></h5></div></td><td><div><p>Customers often request the ability to migrate a virtualized Oracle Database across storage protocols. In response to this, the Oracle Consulting (CSV) group has validated that customers who have an Oracle Database operating in a virtualized environment can migrate data from:</p><ul><li>An FCP/ASM to an NFS-mounted file system</li><li>An NFS-mounted file system to an FCP/ASM</li></ul><p>Customers might be interested in cross-protocol migration because testing and development activities can be supported on less expensive, simpler NFS storage, while production can be carried out on higher-performing ASM/FCP storage.</p><p>Customers may also want to use the storage replication technologies available on a different protocol from the production database.&nbsp; For example, customers may wish to use RecoverPoint to support remote replication but have production on NFS.</p><p>The migrations were performed with minimal performance impact and no downtime on the virtualized production database.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSANtoNASmigrationdiagram"><span>SAN to NAS migration diagram</span></h5></div></td><td>The following diagram is a high-level view of the migration component:</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_4ecd98f6dd410c9a.png" height="481" src="pdf2802290551349436541.tmp" width="622" /></p><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HMigratinganonlineOracleDatabasefromSANtoNAS"><span>Migrating an online Oracle Database from SAN to NAS</span></h5></div></td><td>These steps were followed to perform the SAN to NAS migration operation:<div><table><tbody><tr><td><strong>Step</strong></td><td><strong>Action</strong></td></tr><tr><td>1</td><td>Using EMC Replication Manager, a consistent backup of the running virtualized production database is performed on the EMC CLARiiON<sup>&reg;</sup> using SnapView snapshot.</td></tr><tr><td>2</td><td>This backup is mounted (but not opened) on the migration server in this case a VMware virtual machine (a physically booted server would also work). The NFS target array is also mounted on the migration server.</td></tr><tr><td>3</td><td>Using Oracle Recovery Manager (RMAN), a backup of this database is taken onto the target location. This backup is performed as a database image, so that the datafiles are written directly to the target NFS mount.</td></tr><tr><td>4</td><td>The migration server is then switched to the new database, which has been copied by RMAN to the NFS mount.</td></tr><tr><td>5</td><td>The target database is set in Data Guard continuous recovery mode, and Data Guard log ship/log apply is used to catch the virtualized target database up to the virtualized production version.</td></tr><tr><td>6</td><td>Once the virtualized target database is caught up to production, Data Guard failover can be used to retarget to the virtualized target database. If appropriate networking configuration is performed, clients will see no downtime when this operation occurs.</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="H"><span /></h5></div></td><td>The result, as stated above, is that the virtualized production FCP-mounted database can be migrated to NFS with minimal performance impact and no downtime.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNAStoSANmigrationdiagram"><span>NAS to SAN migration diagram</span></h5></div></td><td>The following diagram is a high-level view of the NAS to SAN migration component.</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_856356489430d5b5.png" height="464" src="pdf7421571461880137549.tmp" width="626" /></p><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HMigratinganonlineOracleDatabasefromNAStoSAN"><span>Migrating an online Oracle Database from NAS to SAN</span></h5></div></td><td>These steps were followed to perform the NAS to SAN migration operation:<div><table><tbody><tr><td><strong>Step</strong></td><td><strong>Action</strong></td></tr><tr><td>1</td><td>Using EMC Replication Manager, a consistent backup of the running virtualized production database is performed on the EMC Celerra<sup>&reg;</sup> using a SnapSure checkpoint snapshot.</td></tr><tr><td>2</td><td>This backup is mounted (but not opened) on the migration server, in this case a VMware virtual machine (a physically booted server would also work). The FCP/ASM target LUNs are also mounted on the migration server.</td></tr><tr><td>3</td><td>Using Oracle Recovery Manager (RMAN), a backup of this database is taken onto the target location. This backup is performed as a database image, so that the datafiles are written directly to the target FCP/ASM LUNs.</td></tr><tr><td>4</td><td>The migration server is then switched to the new database that has been copied by RMAN to the FCP/ASM LUNs.</td></tr><tr><td>5</td><td>The virtualized target database is set in Data Guard continuous recovery mode, and Data Guard log ship/log apply is used to catch the virtualized target database up to the production version.</td></tr><tr><td>6</td><td>Once the virtualized target database is copied to production, Data Guard failover can be used to retarget to the virtualized target database. If appropriate networking configuration is performed, clients will not see any downtime when this operation occurs.</td></tr></tbody></table></div></td></tr></tbody></table><p>The result, as stated above, is that the virtualized production NFS-mounted database can be migrated to FCP/ASM with minimal performance impact and no downtime.</p><h4 class="wikigeneratedid" id="HKeyelements"><span>Key elements</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HIntroduction-2"><span>Introduction</span></h5></div></td><td>This section provides an overview of the technologies that are used in this solution.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCCelerraunifiedstorageplatform"><span>EMC Celerra unified storage platform</span></h5></div></td><td><div><p>The Celerra is a remarkably versatile device. Celerra includes a world-class network-attached storage (NAS) array combined with the functionality and performance of the leading midrange storage area network (SAN) array. Celerra provides both NAS and SAN functionality and performance without compromise.</p><p>The key features provided by the Celerra are described in the following table:</p><table><tbody><tr><td><strong>Feature</strong></td><td><strong>Provided by</strong></td></tr><tr><td>NAS</td><td><div><p>Network File System (NFS) and</p><p>Common Internet File System (CIFS) protocols</p></div></td></tr><tr><td>iSCSI storage</td><td>Celerra&rsquo;s Data Movers</td></tr><tr><td>SAN storage</td><td>Fibre Channel Protocol (FCP) through the back-end EMC CLARiiON CX4</td></tr></tbody></table></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCReplicationManager"><span>EMC Replication Manager</span></h5></div></td><td><div><p>EMC Replication Manager manages EMC point-in-time replication technologies through a centralized management console. Replication Manager coordinates the entire data replication process &ndash; from discovery and configuration to the management of multiple application consistent disk-based replicas. Replication Manager can auto-discover your replication environment and enable streamlined management by scheduling, recording, and cataloging replica information including auto-expiration.</p><p>Replication Manager integrates with the Oracle Database server and provides an easy interface to create and manage Oracle replicas.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEMCCelerraSnapSure"><span>EMC Celerra SnapSure</span></h5></div></td><td><div><p>SnapSure creates a logical point-in-time image (checkpoint) of a production file system (PFS) that reflects the state of the PFS at the point in time when the checkpoint is created. SnapSure can maintain up to 96 PFS checkpoints while allowing PFS applications continued access to the real-time data.</p><h6 class="wikigeneratedid" id="HHowSnapSureworks"><span>How SnapSure works</span></h6><p>The principle of SnapSure is &ldquo;copy on first write&rdquo; (COFW). When a block within the PFS is modified, a copy containing the block&rsquo;s original content is saved to a separate volume called the SavVol. Subsequent changes made to the same block in the PFS are not copied into the SavVol. The original blocks from the PFS (in the SavVol) and the unchanged PFS blocks (remaining in the PFS) are read by SnapSure according to a bitmap and blockmap data-tracking structure. These blocks combine to provide a complete point-in-time file system image called a checkpoint.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVMwareESX"><span>VMware ESX</span></h5></div></td><td>VMware ESX is the flagship virtualization server product from VMware and is the market leader in server virtualization. VMware ESX provides a high-performance, robust, fault-tolerant and high-availability virtualization solution.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOraclesoftwarestack"><span>Oracle software stack</span></h5></div></td><td>The Oracle software stack covered by this solution consists of:<div><ul><li>Oracle Database 11<em>g</em> and 10<em>g</em></li><li>Oracle DNFS (11<em>g</em> only; KNFS used on 10<em>g</em>)</li><li>Oracle Enterprise Linux</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HOracleDNFS"><span>Oracle DNFS</span></h5></div></td><td><div><p>DNFS is a new feature introduced in Oracle Database 11<em>g</em>; it integrates the NFS client directly inside the database kernel instead of the operating system kernel. DNFS provides significant performance, manageability, and efficiency benefits over KNFS.</p><h6 class="wikigeneratedid" id="HBetterperformance"><span>Better performance</span></h6><p>Transactions per second and user load are both higher with DNFS than with KNFS, and this enables organizations to gain more output from the same infrastructure. CPU costs on both the database server and the file server are lower. In addition, port scaling with DNFS is much better, enabling higher bandwidth and thus higher scaling.</p><h6 class="wikigeneratedid" id="HHighavailability"><span>High availability</span></h6><p>Load balancing and high availability (HA) are managed internally within the DNFS client.</p><h6 class="wikigeneratedid" id="HConcurrentI2FO"><span>Concurrent I/O</span></h6><p>The DNFS client performs concurrent I/O by bypassing the operating system. The benefits of this are:</p><ul><li>Better performance due to the reduction of memory consumption and CPU utilization</li><li>Consistent NFS performance, which is observed across all operating systems.</li></ul><h6 class="wikigeneratedid" id="HOptimizedfordatabaseworkloads"><span>Optimized for database workloads</span></h6><p>DNFS is optimized for database workloads and supports asynchronous I/O, which is suitable for most databases. It delivers optimized performance by automatically load balancing across the available paths. Load balancing in DFNS is almost invariably superior to the conventional Linux kernel NFS (KNFS).</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVMwareDistributedResourceScheduler"><span>VMware Distributed Resource Scheduler</span></h5></div></td><td>VMware Distributed Resource Scheduler (DRS) is a cluster feature of VMware vCenter Server; it provides dynamic load balancing and resource sharing for multiple virtual machines across ESX servers. DRS uses VMotion as the underlying transport feature to move virtual machines from one ESX server to another.</td></tr></tbody></table><h4 class="wikigeneratedid" id="HPhysicalarchitecture"><span>Physical architecture</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HReferencearchitecturediagram"><span>Reference architecture diagram</span></h5></div></td><td>The following diagram depicts the overall physical architecture of the solution.</td></tr></tbody></table><p><img alt="010-[EMC]-Bullets-Tables-English-22Pages-DOC_html_dc59c2f02504ebed.png" height="515" src="pdf1052853033950301652.tmp" width="651" /></p><h4 class="wikigeneratedid" id="HValidatedenvironmentprofile"><span>Validated environment profile</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HProfilecharacteristics"><span>Profile characteristics</span></h5></div></td><td>For information on the validated environment profile and performance results, refer to the Proven Solution Guide for this solution. This information can be accessed on EMC Powerlink<sup>&reg;</sup>, EMC.com, and the EMC|KB.WIKI.</td></tr></tbody></table><h4 class="wikigeneratedid" id="HHardwareandsoftwareresources"><span><span id="_Ref223689231" /><span id="_Ref223689206" />Hardware and software resources</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HHardware"><span>Hardware</span></h5></div></td><td>The hardware used to validate the solution is listed below.</td></tr></tbody></table><table><tbody><tr><td><strong>Equipment</strong></td><td><strong>Quantity</strong></td><td><strong>Configuration</strong></td></tr><tr><td>EMC Celerra unified storage platforms (included an EMC CLARiiON CX4 back-end storage array)</td><td>2</td><td><div><ul><li>2 Data Movers</li><li>4 GbE network connections per Data Mover</li><li>2 or 3 FC shelves</li><li>1 SATA shelf</li><li>30 or 45 73 GB FC disks (depending on configuration)</li><li>15 1 TB SATA disks</li><li>1 Control Station</li><li>2 storage processors</li><li>DART version 5.6.44-4</li></ul></div></td></tr><tr><td>Gigabit Ethernet switches</td><td>5</td><td>24 ports per switch</td></tr><tr><td>VMware ESX HA cluster servers</td><td>4</td><td><div><ul><li>2 2.66 GHz Intel Pentium 4 quad-core processors</li><li>24 GB of RAM</li><li>2 146 GB 15k internal SCSI disks</li><li>2 onboard GbE Ethernet NICs</li><li>2 additional Intel PRO/1000 PT quad-port GbE Ethernet NICs</li><li>2 SANblade QLE2462-E-SP 4 Gb/s dual-port FC HBAs (4 ports in total)</li></ul></div></td></tr><tr><td>Virtualization server (VMware ESX)</td><td>1</td><td><div><ul><li>4 2.86 GHz AMD Opteron quad-core processors</li><li>32 GB of RAM</li><li>2 146 GB 15k internal SCSI disks</li><li>2 onboard GbE Ethernet NICs</li><li>3 additional Intel PRO/1000 PT quad-port GbE Ethernet NICs</li><li>2 SANblade QLE2462-E-SP 4 Gb/s dual-port FC HBAs (4 ports in total)</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSoftware"><span>Software</span></h5></div></td><td>The software used to validate the solution is listed below.</td></tr></tbody></table><table><tbody><tr><td><strong>Software</strong></td><td><strong>Version</strong></td></tr><tr><td>Oracle Enterprise Linux</td><td>5.2</td></tr><tr><td>VMware ESX Server/vSphere</td><td>4.0</td></tr><tr><td>Microsoft Windows Server 2003 Standard Edition</td><td>2003</td></tr><tr><td>Oracle Database Standard Edition</td><td>11<em>g</em> (11<em>g</em> Ver. 11.1.0.7.0) or 10<em>g</em></td></tr><tr><td>Quest Benchmark Factory for Databases</td><td>5.8.1</td></tr><tr><td>EMC Celerra Manager Advanced Edition</td><td>5.6</td></tr><tr><td>EMC Navisphere<sup>&reg;</sup> Agent</td><td>6.26.0.2.24</td></tr><tr><td>EMC Replication Manager</td><td>5.2.2.0</td></tr><tr><td>EMC FLARE<sup>&reg;</sup></td><td>04.28.000.5.504</td></tr><tr><td>EMC DART</td><td>5.6.44-4</td></tr><tr><td>EMC Navisphere Management</td><td>6.28</td></tr></tbody></table><h4 class="wikigeneratedid" id="HConclusion"><span>Conclusion</span></h4><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HSummary"><span>Summary</span></h5></div></td><td>This section provides a summary of the solution and of the business challenges that it addresses.</td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HReducedtotalcostofownership"><span>Reduced total cost of ownership</span></h5></div></td><td><div><p>In any reasonable configuration, the database server's CPU is the most precious component of the entire architecture. Therefore, the over-arching principle of EMC's Oracle Database 11<em>g</em> and 10<em>g</em> solutions for midsize enterprises is to free up the database server's CPU (as well as memory and I/O channels) from utility operations such as backup and recovery, disaster recovery staging, test/dev, and cloning. The highest and best use of the database server&rsquo;s CPUs is to parse and execute the SQL statements that are required by the application user.</p><h6 class="wikigeneratedid" id="HCPUusage"><span>CPU usage</span></h6><p>This solution reduces the load on the database server CPU by using:</p><ul><li>EMC Replication Manager for NFS with EMC SnapSure to carry out a physical backup of an Oracle 11<em>g</em> or 10<em>g</em> production database while offloading all performance impacts of the backup operation from the production server</li><li>DNFS to achieve better performance due to the reduction of memory consumption and CPU utilization</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HVirtualization"><span>Virtualization</span></h5></div></td><td><div><p>The use of virtualization for the production database server provides manageability and ease-of-use advantages. In a scale-out context, virtualization can provide superior performance and scalability compared to physically booted configurations - even when using hardware identical to that used in the physically booted configuration.</p><p>Utility servers, such as a test/dev target and basic protect target, are more easily and conveniently managed as virtual machines than as physically booted Oracle Database servers. The advantages of consolidation, flexible migration and so on, which are the mainstays of virtualization, apply to these servers as well.</p><h6 class="wikigeneratedid" id="HReducedcosts"><span>Reduced costs</span></h6><p>One of the main challenges faced by the customer is to reduce cost by utilizing infrastructure effectively. Virtualization enables reduction in the number of servers and related IT hardware in the data center. The other main feature is the ability to move a running virtual machine production database from one physical sever to another physical server without any downtime.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HDistributedresourcescheduling"><span>Distributed resource scheduling</span></h5></div></td><td><div><p>VMware DRS provides the ability to distribute workload across multiple ESX servers by migrating virtual machines according to resource consumption and demand. VMware DRS dynamically manages pooled resources from multiple ESX servers. VMware DRS aggregates and centrally manages the resources of multiple hosts as resource pools. Different sets of rules and priorities can be defined for individual Oracle virtual machines based on the criticality.</p><div class="wikimodel-emptyline" /><p>When an Oracle Database server virtual machine operating within a resource pool experiences increased utilization of resources, DRS will try to allocate the resources from the centralized pool based on the rules and priorities.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HHighavailability-1"><span>High availability</span></h5></div></td><td><div><p><strong>VMotion</strong></p><p>The use of VMware VMotion to migrate an Oracle Database instance from one piece of hardware to another was achieved in our tests with virtually no performance impact and no downtime on the running Oracle Database instance. This provides a very high level of manageability and downtime reduction for tasks such as software and hardware upgrades.</p><h6 class="wikigeneratedid" id="HVMwareHAcluster"><span>VMware HA cluster</span></h6><p>The use of a VMware HA cluster provides further high-availability advantages to the virtualized solution. EMC has validated the use of a VMware HA cluster with Oracle Database 11<em>g</em> and 10<em>g</em> in a single-instance scale-out environment. In addition, a VMware HA cluster can be used to automate failover in the event of a hardware or software failure.</p><h6 class="wikigeneratedid" id="HFaultTolerance"><span>Fault Tolerance</span></h6><p>The use of VMware Fault Tolerance provides true zero downtime for Oracle VMware-based database servers. This means that a database server running on VMware can be protected from unplanned downtime. This is a significant improvement over the previous version of VMware and is provided on the HA cluster. The use of Fault Tolerance is presently limited to one vCPU, making Fault Tolerance only applicable to smaller Oracle Database servers.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HImprovedperformance"><span>Improved performance</span></h5></div></td><td>The Direct NFS (DNFS) client performs concurrent I/O by bypassing the operating system. The benefits of this are:<div><ul><li>Consistent NFS performance is observed across all operating systems.</li><li>DNFS is optimized for database workloads and supports asynchronous I/O, which is suitable for most databases. It delivers optimized performance by automatically load balancing across the available paths. Load balancing in DNFS is frequently superior to the conventional Linux kernel NFS (KNFS).</li></ul></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HEaseofuse"><span>Ease of use</span></h5></div></td><td><div><p>The use of DNFS simplifies network setup and management by eliminating administration tasks such as:</p><ul><li>Setting up network subnets</li><li>LACP bonding</li><li>Tuning of Linux NFS parameters</li></ul><p>Load balancing and high availability (HA) are managed internally within the DNFS client.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HBusinesscontinuity"><span>Business continuity</span></h5></div></td><td><div><p><strong>Advanced backup and recovery</strong></p><p>EMC Replication Manager is a comprehensive graphical application that provides Oracle storage replication using EMC storage technology. This eliminates the requirement for the customer to write scripts or to manually perform replication tasks. These tasks can now be fully automated and managed by Replication Manager.</p><p>One of the solution components using Replication Manager in the solution presented in this reference architecture included Advanced Backup and Recovery using EMC SnapSure checkpoints.</p><h6 class="wikigeneratedid" id="HTest2Fdev"><span>Test/dev</span></h6><p>The ability to deploy a writeable copy of the production database is required by many customers. The process of provisioning this writeable copy must create minimal, if any, performance impact on the production database server. Also, absolutely no downtime can be tolerated. The Test/Dev solution component documented here provides this using EMC Replication Manager for NFS with EMC SnapSure writeable checkpoint.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HRobustperformanceandscaling"><span>Robust performance and scaling</span></h5></div></td><td><div><p>The resiliency testing carried out by EMC ensures that the database configuration is reliable. High availability is used at every major layer of the solution, including the database server, NAS file server, and back-end CLARiiON CX4. By testing the fault tolerance of all of these layers, the ability of the application to withstand hardware failures with no downtime is assured.</p><p>The performance testing carried out by EMC utilizes an industry-standard OLTP benchmark but does so without exotic tunings that are not compliant with best practices. In addition, real-world configurations that the customer is likely to deploy are used. This enables the customer to be reasonably assured that the configuration that they choose to run their application will do so predictably and reliably.</p></div></td></tr></tbody></table><table><tbody><tr><td><div><h5 class="wikigeneratedid" id="HNextsteps"><span>Next steps</span></h5></div></td><td><div><p>EMC can help accelerate assessment, design, implementation, and management while lowering the implementation risks and costs of an end-to- end solution for an Oracle Database 11<em>g</em> or 10<em>g</em> environment.</p><p>To learn more about this and other solutions contact an EMC representative or visit <span style="text-decoration:underline"><span class="wikiexternallink"><a href="http://www.emc.com/solutions/application-environment/oracle/solutions-for-oracle-database.htm">http://www.emc.com/solutions/application-environment/oracle/solutions-for-oracle-database.htm</a></span></span></p></div></td></tr></tbody></table><div id="_PictureBullets" />
          </div>
</div>
</div>

</body></html>

Actions: View

Attachments on bug 126041: 152345 | 152346