Accenture Report Documentum 4i on NetApp filers Deployment Guide

Transcription

1 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Documen Purpose This projec was conduced by Accenure o research & develop a Nework Appliance filer and Documenum 4i Deploymen Guide. This documen conains a summary of he findings of he projec. Addiional echnical and execuion deails can be found in he appendix documen. Documen Name: Accenure Repor: Documenum 4i on NeApp filers Deploymen Guide Addiional Relaed Documens: Execuive Summary: Documenum 4i on NeApp filers Deploymen Guide Execuive Summary Documenum 4i on NeApp filers Deploymen Guide Appendix

2 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Conens 1.0 EXECUTIVE SUMMARY DEPLOYMENT GUIDE OVERVIEW DEPLOYMENT GUIDE OBJECTIVES WHO SHOULD USE THIS DEPLOYMENT GUIDE? DESCRIPTION OF KEY ELEMENTS OF DEPLOYMENT GUIDE DEPLOYMENT GUIDE CONFIGURATIONS GENERAL DEPLOYMENT GUIDELINES STANDARD TEST MEASUREMENT DIRECT-ATTACHED STORAGE NETAPP F840 FILER CONFIGURATION NEARSTORE R100 CONFIGURATION DOCUMENTUM 4I BACKUP USING SNAPSHOT DOCUMENTUM 4I DATA RECOVERY USING SNAPRESTORE DOCUMENTUM 4I BACKUP USING CYA HOTBACKUP DOCUMENTUM 4I OBJECT-LEVEL RECOVERY USING CYA HOTBACKUP DOCUMENTUM 4I MIRRORING FOR FAILOVER USING SNAPMIRROR DOCUMENTUM 4I FAILOVER USING CYA VIRTUAL STANDBY DOCUMENTUM 4I MIRRORING FOR FAILOVER USING NEARSTORE AND RSYNC DOCUMENTUM 4I DOCBASE LOAD PERFORMANCE ON NETAPP FILERS 28 Accenure Repor Page 2 of 29 Documenum 4i on NeApp filers Deploymen Guide

3 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Lis of Figures FIGURE 1 DOCUMENTUM 4I BACKUP TIME DAS VS. FILER 5 FIGURE 2 - DOCUMENTUM 4I APPLICATION ARCHITECTURE 9 FIGURE 3 A CYA HOTBACKUP DEPLOYMENT 10 FIGURE 4 DOCUMENTUM 4I BACKUP CONFIGURATION 14 FIGURE 5 - AVERAGE TIME TO COMPLETE A FULL DATABASE AND APPLICATION DATA BACKUP 15 FIGURE 6 DOCUMENTUM 4I SNAPRESTORE CONFIGURATION 16 FIGURE 7 - FULL DATABASE AND APPLICATION DATA RESTORE 18 FIGURE 8 DOCUMENTUM 4I CYA HOTBACKUP CONFIGURATION 18 FIGURE 9 CYA SINGLE OBJECT RESTORE CONFIGURATION 20 FIGURE 10 MIRRORED TEST ENVIRONMENT USING SNAPMIRROR 22 FIGURE 11 MIRRORED TEST ENVIRONMENT WITH CYA VIRTUAL STANDBY 24 FIGURE 12 MIRRORED TEST ENVIRONMENT USING RSYNC 26 FIGURE 13 - NETAPP FILER-BASED DOCUMENTUM 4I ENVIRONMENT 28 FIGURE 14 - NETAPP FILER PERFORMANCE IMPACT ON DOCUMENT LOAD 29 Accenure Repor Page 3 of 29 Documenum 4i on NeApp filers Deploymen Guide

4 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 1.0 Execuive Summary Accenure is he world s leading managemen consuling and echnology services firm wih over 70,000 employees and 120 rained Documenum professionals in he field. An acive Accenure / Documenum Alliance offers soluions o help he Global 2000 manage criical informaion sored in disparae daabases housed in muliple formas such as: documens, ineracive web conen and mulimedia. Accenure has a decade of experience helping cliens across muliple indusries wih documen, web, digial asse, and enerprise conen managemen challenges. Accenure was engaged by Nework Appliance (NeApp) o research Daa Proecion and Business Coninuance sraegies for a Documenum 4i Conen Managemen applicaion inegraed ono a NeApp filer (nework sorage). Documenum Professional Services and CYA Technologies provided on-sie Documenum and CYA produc suppor for he duraion of he projec. This projec examined how NeApp sofware & hardware can be used in daa proecion and business coninuance scenarios. This projec deployed a es environmen ha simulaed he behavior of a large number of concurren users accessing a producion-ready Documenum 4i Conen Managemen applicaion wih NeApp filers hosing he Oracle daabase files and Documenum conen files. In ess run agains his es environmen Accenure was able o successfully inegrae a NeApp filer ino a producion-capaciy Documenum 4i applicaion environmen. Addiional resuls ha were recorded during his esing were: Performance NeApp filers reduced Documenum 4i business process ime by 18% when compared agains direc-aached sorage (DAS) arrays for documen load operaions (in he range of 500-5,000 documens). Scalabiliy In scalabiliy esing he DAS arrays experienced an addiional ime of 2% per ransacion while he filer ime increased by less han 1% when he documen load numbers were increased from 500 o 5,000, hus improving overall applicaion response ime for end users. Availabiliy In applicaion-level failover esing, Documenum 4i deploymens running agains NeApp filers were able o successfully fail over o a fully operaional, sandby environmen wihin as lile as 4 minues. Rapid Daa Backup In es scenarios, Snapsho was used o demonsrae a full 30GB Docbase backup in less han 6 seconds. Recoverabiliy In ess ha simulaed Documenum applicaion failure due o daabase corrupion, he NeApp and SnapMirror filer capabiliies alone faciliaed recovery in less han 4 minues. This included 3.2 seconds o recover he daabase using SnapResore, and 182 seconds for he daabase and Documenum applicaion o recover full hroughpu capaciy. The comparaive direc- aached sorage-based recovery scenario would have aken an esimaed 6 hours o complee. Accenure Repor Page 4 of 29 Documenum 4i on NeApp filers Deploymen Guide

5 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Hours Cold / DAS Cold / filer Ho / DAS Ho / filer Figure 1 Documenum 4i Backup Time DAS vs. Filer Manageabiliy The NeApp filer was insalled, fully inegraed ino he es environmen and serving daa in less han 2.5 hours. The Deploymen Guide projec developed addiional configuraions based on CYA Technologies (CYA) and Open Source uiliies; Daa Proecion Single Objec Resore. Tes resuls validae he use of he NeApp filer as a file server for CYA HOTBackup backup ses in a Documenum 4i deploymen. Business Coninuance CYA Virual SandBy. Tes resuls validae he use of he NeApp filer and SnapMirror in a Disaser Recovery configuraion. SnapMirror was used o replicae CYA HOTBackup ses o an environmen running CYA Virual SandBy. Addiional configuraions validaed he use of SnapMirror alone o replicae daa o a passive backup environmen. Seamless Inegraion Remoe mirroring from DAS o filer using rsync. Tes resuls validae he use of he rsync uiliy o replicae a Docbase from non NeApp sorage (DAS) o NeApp sorage a a remoe locaion for failover and disaser recovery scenarios. Accenure Repor Page 5 of 29 Documenum 4i on NeApp filers Deploymen Guide

6 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 2.0 Deploymen Guide Overview 2.1 Deploymen Guide Objecives The objecive of he Deploymen Guide projec was o define and es muliple configuraions of a NeApp filer in a Documenum 4i producion-capaciy environmen. These configuraions were designed o provide organizaions ha have eiher implemened Documenum 4i or are considering migraing o Documenum 4i wih opions regarding daa sorage and overall applicaion archiecure design. Mos of he resuls of his projec could also be applied o organizaions ha are currenly employing he Documenum Enerprise Documen Managemen Sysem (EDMS) 98 applicaion or who plan o deploy he upcoming Documenum 5.x version. The objecives of he projec were achieved by developing and esing muliple configuraions of he sorage needs of a Documenum 4i Enerprise Conen Managemen (ECM) applicaion wihin a conrolled es environmen. This producion capaciy es environmen was esed wih a user load of up o 150 concurren users. Assuming a ypical 10-o-1 raio of regisered users o concurren users, his load was seleced o represen Documenum insallaions wih approximaely 1,500 regisered users. A subse of configuraions was devised o measure he performance impacs of inegraing a NeApp filer ino a producion-capaciy Documenum 4i deploymen. In order o achieve an objecive overview of he NeApp filer sorage soluion wihin he Documenum 4i applicaion archiecure, a represenaive direc-aached sorage (DAS) configuraion was creaed for hese performance measuremen configuraions. By using a comparaive poin of reference for hese configuraions i was possible o describe he applicaion archiecure differenials beween he sorage ypes. Anoher se of he configuraions was designed o demonsrae he feasibiliy of inegraing NeApp wih complemenary echnology deploymens in a capaciy Documenum 4i environmen. These configuraions esed he deploymen of a NeApp filer or he combinaion of NeApp filer wih complemenary sofware from CYA Technologies or open source resources, o address common Documenum 4i adminisraion issues. 2.2 Who Should Use This Deploymen Guide? The inended audiences for his Deploymen Guide documen are echnical archiecs from organizaions ha fall ino one of he following groups; Organizaions ha are planning on implemening Documenum 4i and need o undersand heir opions for using neworked sorage and/or DAS for differen aspecs of he Documenum 4i archiecure. Organizaions ha are migraing or are planning on migraing from Documenum EDMS 98 (or earlier) o Documenum 4i Organizaions ha have implemened (or are currenly implemening) Documenum 4i and ha need o undersand how o manage daabase files or large numbers of conen files. Organizaions using Documenum 4i ha wish o invesigae ways o reduce heir backup window, recover more quickly from daa corrupion, or explore disaser recovery soluions for Documenum. Sysem Inegraors and Consulans ha archiec or implemen Documenum sysems for cliens and wish o offer cliens sorage, backup, recovery and business coninuance soluions as par of a Documenum implemenaion. Page 6 of 29

7 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Organizaions in hese groups could use he resuls of his sudy o undersand how o implemen NeApp filer echnologies wihin heir curren Documenum applicaion archiecures. This Deploymen Guide documen is no inended o ac as a sizing guide for hardware o be deployed wihin a Documenum applicaion environmen nor is i inended o be an exhausive review of he enire suie of Documenum 4i applicaion funcionaliy. Addiionally, he projec did no develop exensive uning and performance guidelines for he applicaions in he archiecure alhough basic vendor-supplied guidelines were followed. 2.3 Descripion of Key Elemens of Deploymen Guide Nework Appliance Soluion Overview Nework Appliance (NASDAQ: NTAP) is a recognized leader in enerprise sorage and he delivery of daa and conen on demand. NeApp soluions empower enerprises wih susainable compeiive advanage, improved profiabiliy, and faser ime-o-marke by exploiing unapped value in IT infrasrucures. Designed o enable enerprises o creae global daa managemen sraegies oday, NeApp sorage soluions ensure ha cusomers ge informaion where i's needed, when i's needed more efficienly, more effecively, and more reliably han wih any oher soluion available. NeApp soluions esed in his projec include he following: NeApp filers-- A robus, field-proven, highly available sorage soluion (>99.99% daa availabiliy) for consolidaing daa and simplifying daa managemen. NeApp filers are easy o manage appliances, specifically designed for oday's scalable, nework-cenric IT sysem archiecures. Designed for high performance, high availabiliy, and low oal cos of ownership (TCO), NeApp filers include inegraed RAID, a specialized appliance OS (Daa ONTAP ), a paened file sysem (WAFL ), redundan hardware componens, and opional clusering. NeApp filers are designed for soring boh daabase daa and conen files. NeApp NearSore -- NearSore appliances offer cos-effecive, fas-access sorage for online backup and archiving. NearSore is designed o offer secondary sorage for online backup, archiving, documen sorage and disaser recovery. NearSore offers he same OS, file sysem, RAID proecion and ease of managemen as NeApp filers, bu a a significanly lower cos. NeApp Snapsho -- NeApp Snapsho is an inegral par of each filer and NearSore appliance and can make insan, read-only copies of any volume or file sysem in seconds. Snapsho is designed o simplify and speed up daa backup operaions. NeApp SnapResore -- SnapResore allows a filer or NearSore appliance o rever a volume o an earlier poin in ime almos insanly, grealy simplifying and speeding up recovery from daa loss or daa corrupion. NeApp SnapMirror -- SnapMirror allows for simple, robus mirroring of daa from one NeApp appliance o anoher, across any disance and using sandard IP nework connecions. SnapMirror is designed o be used for backup consolidaion, remoe daa sharing and remoe replicaion of criical daa for disaser recovery purposes. Page 7 of 29

8 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide More informaion abou NeApp producs and soluions can be found a hp:// Documenum ECM Soluion Overview Documenum 4i is an Enerprise Conen Managemen (ECM) sysem for powering e-business applicaions, such as corporae porals. Documenum 4i manages conen o allow organizaions o effecively collaborae or share informaion wih cusomers, parners, and employees. Documenum 4i inegraes wih Cusomer Relaionship Managemen (CRM) sysems in he fron office and Enerprise Resource Planning (ERP) sysems in he back office o auomae and sreamline e-business applicaions. Documenum 4i also inegraes wih bes-of-breed commerce and applicaion servers o deliver conen o high-volume and high-inegriy Inerne sies. The Documenum 4i offering consiss of he following componens: Docbase - The Docbase is he underlying reposiory for conen. Muliple reposiories can be linked ogeher across logical and geographic boundaries o form a single, federaed conen reposiory. 4i Server - The server componen of he sysem handles communicaions beween he cliens and he Docbase. The server also manages he processing of scanned inpu, auo rendering, and inegraion poins. Documenum Foundaion Classes (DFC) - This componen is an objec-oriened API layer wrien in Java, which provides inerfaces o a variey of indusry-sandard languages and developer ools, including Java, VB, COM, C, and C++, as well as ASP and JSP echnology. This layer links he various Documenum 4i cliens o he services offered by he Documenum 4i server and enables easy inegraion wih oher sysems. Oher inerfaces, such as Documenum s iteam poral inerface, can also use he DFC o communicae wih he Documenum 4i Server. Developer Sudio - This componen is a GUI environmen used o develop DocApps, which consis of he business rules, workflow, documen lifecycles, and securiy for individual Docbases. The business rules are cenrally sored in a daa dicionary wihin he Documenum 4i server. Once developed, DocApps can be easily migraed beween Docbases, reducing implemenaion imes and lowering cos of ownership. Documenum 4i enables an organizaion s employees, suppliers, parners, and cusomers o collaborae, communicae, and share knowledge. The physical es environmen was consruced using a vanilla insallaion of he Documenum 4i ECM Soluion. No addiional configuraion changes were made o he applicaion and all users accessing he applicaion were Inrane Cliens making requess via RighSie. The overall archiecure of he Documenum 4i applicaion is shown in Figure 2; Page 8 of 29

9 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Con en Con en Con en Con en Con en User Transacions Web Server / RighSie MS IIS Documenum RighSie DCTM 4i econen Server Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa Key = User Transacions Figure 2 - Documenum 4i Applicaion Archiecure The Documenum Enerprise Docbase was pre-populaed using he Documenum Connecion Pooling Benchmark Ki Documen Loader. Samples documens from he Documenum Connecion Pooling Benchmark Ki were used o populae he iniial es environmen Docbase. The Documenum es environmen ha was generaed using a random seeding of he following number of Documenum Objecs;.gif 45kb.hml 8kb.jpg 2kb.pdf 103kb.pp 129kb.x 4kb.doc 79kb.xml 8kb TOTAL DOCUMENTUM OBJECTS 650,000 Page 9 of 29

10 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide CYA Technologies, Inc. CYA HOTBackup, and Virual SandBy CYA Technologies provides applicaion-aware business coninuiy and disaser recovery for Documenum 4i cliens relian on mission-criical conen. CYA HOTBackup, he company's flagship produc, proecs he cross-references beween conen enabling he proecion of e- business processes and he expedied recovery from disaser, corrupion and/or accidenal deleion of informaion. CYA HOTBackup enables businesses in all indusries ha rely on mission-criical conen o mainain he inegriy and availabiliy of informaion criical o produciviy as well as cusomer and parner relaionships. CYA HOTBackup is an available recovery soluion ha allows an organizaion o roll back is reposiory o a specific poin-in-ime and resore eiher single or muliple objecs (even an enire reposiory). Mission-criical conen such as drug submissions, web pages, service agreemens and engineering documenaion is all sored wihin Documenum, and is ofen available on-line. This criical conen - wheher i's shared wih employees, parners, or consumers - needs o be backed up frequenly and in a manner ha enables quick objec-level resoraions of specific pages ha includes conen as well as all of he criical links and relaionships such as auhor, owner, annoaions, PDFs, ec. Figure 3 below shows illusraes a ypical CYA HOTBackup deploymen. Con en Con en Con en Con en Con en User Transacions Web Server / RighSie MS IIS Documenum RighSie CYA Resore GUI (sand-alone compo nen) CYA HOTBackup DCTM 4i econen Server Key Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) = User Transacions Gigabi Eherne sorage nework NeApp F840 Filer DCTM Conen Files Oracle Daabase Files CYA HOTBackup Backup Ses F I L E R V O L U M E Figure 3 A CYA HOTBackup deploymen Page 10 of 29

11 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide CYA Producs include: CYA HOTBackup Enerprise, Sandard & Limied Ediions incremenally backs up conen and relaionships allowing for objec-level, poin-in-ime and bach resoraion in a 24x7 environmen while performing daa inegriy checking. CYA Virual SandBy provides business coninuiy o enerprises by argeing a HOT sie and incremenally sending mission-criical informaion from a primary sever o secondary server a an alernae locaion. In he even of disaser CYA Virual SandBy enables he enerprise o quickly failover simply by changing an IP address. This projec used CYA HOTBackup Enerprise Ediion and Virual Sandby o provide Documenum 4i Daa Proecion and Business Coninuance deploymen scenarios. CYA Technologies offer oher producs for Documenum ha were no esed on his projec. For deails please visi he CYA Technologies websie a: hp:// Page 11 of 29

12 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.0 Deploymen Guide Configuraions 3.1 General Deploymen Guidelines This secion conains an overview of he applicaion archiecures ha were developed for he projec. Prior o he sar of each pair of configuraion ess he es environmen was inspeced o ensure ha he number and size of he daabase and oher files in he DAS and NAS environmens was equivalen. Addiional precauions were aken o ensure ha no addiional exernal facors influenced he oucomes of he es. These included; Monioring nework raffic before, during, and afer he es. Removal of nonessenial processing loads from all es environmen es equipmen. Ho & cold resars of all Microsof Operaing Sysem-dependen es environmen elemens. Free memory checks of all es environmen elemens a he sar of each es run. The objecive of hese configuraions was o esablish a blueprin for he implemenaion of a ypical Documenum 4i applicaion on a NeApp filer in a producion environmen. For he purposes of hese ess only he configuraion of he NeApp filer was capured. The deails of insalling he Documenum 4i applicaion, CYA Technologies sofware, Microsof Windows Load Balancing Sofware (WLBS) and he NeApp filer are conained in separae documenaion available from each respecive vendor (see Appendix for furher informaion on hese vendors). As a baseline comparison he performance measuremen configuraions, he Oracle daabase and Documenum 4i conen files were mouned on a local DAS array. Based on his configuraion, merics were capured ha described how he es environmen performed in boh neworked sorage and also direc-aached sorage (DAS) mode. The failover scenarios leverage he WLBS nework sofware. Nework failover saisics were derived from he benchmarking performed a Microsof on his sofware. For furher deails see: Microsof Library Sandard Tes Measuremen For each configuraion lised in his documen a sandard es measuremen was applied o he applicaion, while he es operaions were being performed, o simulae a live Documenum 4i environmen. The consised of he following iems; Iem Business Processes Users Timescale Descripion Documen Load, Documen Navigae, Documen View, Documen Modify A peak of 150 users was applied in wo ses of 75 users wih a simulaneous, coninual documen load process. The es run duraion varied wih business process and he configuraion. Merics were repored during imes of peak aciviy. Page 12 of 29

13 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Direc-Aached Sorage The ess conduced during he Deploymen Guide projec uilized a direc-aached sorage (DAS) array for comparison purposes. This DAS array comprised he following hardware iems; Sun D240 Media Tray conneced o e x 18GB SCSI Ulra Wide/Fas PCI HD - Hosing Solaris OS and Oracle conrol and execuable files Sun D240 Media Tray conneced o e4800 DDS 4 Tape Drive Back-up and recovery of Oracle daa files, redo logs and index files Sun D1000 conneced o e x 18GB SCSI Ulra Wide/Fas HD - Hosing Oracle daa files Sun D1000 conneced o e x 18GB SCSI Ulra Wide/Fas HD - Hosing Documenum 4i Conen files Sun e x 18 GB FCAL Inernal sorage o he applicaion server for sorage of operaing sysem, Documenum 4i and CYA insallaions. Sun e250-2 x 18 GB SCSI Ulra Wide/Fas HD Inernal sorage o he sandby server for sorage of operaing sysem, Documenum 4i, Oracle, and CYA insallaions NeApp F840 Filer Configuraion Noe: All es configuraions used less han 50% of available sorage space on boh he F840 and NearSore R100. Model NeApp F840c OS Daa ONTAP Disk Shelves 1 x DS-14, 3 x FC9 FCAL(Copper) Disk Drives 35 x 72GB FC NIC Gigabi Eherne FC-AL Disk Adapers NearSore R100 Configuraion Noe: All es configuraions used less han 50% of available sorage space on boh he F840 and NearSore R100. Model R100 OS Daa ONTAP 6.2.R1 P1 Disk Shelves 7 x 12 Disk Drives 84 x 135 GB Maxor ATA NIC Gigabi Eherne (no used) / 100MB Page 13 of 29

14 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.2 Documenum 4i Backup Using Snapsho This series of ess was designed o idenify a NeApp filer configuraion ha could simplify he manageabiliy, and decrease he ime needed for rouine Documenum 4i backup operaions. The applicaion daa idenified for backup were he Daabase meadaa and log files and he Documenum 4i conen files. The basic configuraion of he Documenum 4i applicaion is illusraed below; Conen Conen Conen Conen Conen User Transacions Web Server / RighSie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Gigabi Eherne sorage nework DCTM Conen Files Oracle Daabase Files S N A P S H O T Key = User Transacions Figure 4 Documenum 4i Backup Configuraion Objecive: The ypical scenario for prevening daa loss is defining a daa loss olerance and designing a backup plan ha ensures he daa loss olerance is enforced wih scheduled daa duplicaion. In addiion, he duraion of he backup process can affec how ofen backups are possible. The choice beween ho or cold backup is deermined by he downime olerance of an enerprise. This configuraion explores daa duplicaion in a simulaed Documenum 4i producion environmen wih an applicaion downime olerance allowing backups o be performed while he applicaion is in a quiescen sae and while he applicaion is acive and under load. Cold Backup Approach: Prior o each measuremen, he environmen was rese o a baseline image of a 30GB Docbase. The sandard es load was iniiaed for boh he DAS and NAS mode. The econen server and Daabase processes were quiesced. A cold backup measuremen was aken. Page 14 of 29

15 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide In he NAS configuraion he Oracle daa files, Oracle log files and Documenum conen files were sored on NFS volumes on he NeApp F840 filer. In he DAS configuraion, he Oracle daa files, Oracle log files and Documenum conen files were sored on a direc-aached SUN D1000 sorage array sriped mode, RAID 0 in order o provide he bes performance comparison. Ho Backup Approach: The Oracle daabase was se in Archive Log mode. Prior o each measuremen, he environmen was rese o a baseline image of a 30GB Docbase. The sandard es load was iniiaed for boh he DAS and NAS mode. The Daabase was pu ino ho backup mode and he meadaa, conen and log files were backed up o DAS or a filer. The daabase was hen reurned o a nominal sae. In he NAS configuraion he Oracle daa files, Oracle log files and Documenum conen files were sored on NFS volumes on he NeApp F840 filer. In he DAS configuraion, he Oracle daa files, Oracle log files and Documenum conen files were sored on wo direc-aached SUN D1000 sorage arrays in sriped mode, RAID 0 in order o provide he bes performance comparison. Key Findings: The resuls of his es show ha for ho and cold backup, a 30GB Documenum 4i Docbase on a NeApp filer archiecure using Snapsho experienced a large decrease in overall backup process ime for he Docbase and associaed daabase files when compared o he same Docbase hosed on a DAS array using a disk-o-disk copy. Using informaion provided by NeApp, Snapsho backups of Docbases larger han he 30GB esed would yield resuls wih approximaely he same backup ime as he 30GB Docbase esed, bu his informaion was no validaed during esing on his projec. The graph illusraed below shows he ime o complee a full cold backup of DB and applicaion daa Hours Cold / DAS Cold / filer Ho / DAS Ho / filer Figure 5 - Average Time o Complee a Full Daabase and Applicaion Daa Backup Page 15 of 29

16 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.3 Documenum 4i Daa Recovery Using SnapResore This series of ess was designed o idenify a NeApp filer configuraion ha could increase he performance and manageabiliy of rouine Documenum 4i daa recovery operaions and increase availabiliy by minimizing ime o recovery (TTR). The applicaion daa idenified for he recovery was backed-up daabase meadaa and log files and he Documenum 4i conen files. The basic configuraion of he Documenum 4i applicaion is illusraed below; Conen Conen Conen Conen Conen User Transacions Web Server / RighSie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Gigabi Eherne sorage nework DCTM Conen Files Oracle Daabase Files S N A P R E S T O R E Key = User Transacions Figure 6 Documenum 4i SnapResore Configuraion Objecive: The ypical scenario for prevening daa loss is defining a daa loss olerance and designing a backup plan ha ensures he daa loss olerance is enforced wih scheduled daa duplicaion. The duraion of he backup process can govern he frequency ha he backup process is execued. In he even of unscheduled daa loss, daa resoraion can be addressed wih a variey of echniques. The echnique chosen for he resoraion process depends on he granulariy of he loss and he laency beween he backup and curren image. The Docbase adminisraor wih a large laency olerance may choose o perform periodic backup and rely on daabase recovery mechanisms in he case of daa loss evens. A Docbase adminisraor wih a smaller laency olerance may choose o perform more frequen full-backups and use full daabase resoraions in case of daa loss evens. This configuraion explores daa resoraion in a simulaed Documenum 4i producion environmen wih he demands for daa resoraion a he enire volume level, wih a large and small laency window olerance. Page 16 of 29

17 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide The full filer volume resore ime was measured agains he DAS array, bu no for he incremenal, small laency window recovery. As a baseline comparison for he full volume resoraion configuraion, he Oracle daabase and Documenum 4i conen files were mouned on a local DAS array. Based on his configuraion, merics were capured ha described how he es environmen performed in boh nework sorage and also direc-aached sorage (DAS) mode. Approach: Prior o each es configuraion, he environmen was rese o a baseline Docbase image of 30GB of conen files and 7GB of meadaa. The sandard es load was iniiaed for boh he DAS and NAS mode. The econen server and Daabase processes were quiesced, daa resored from an earlier backup and he ime required for resore was measured. The Oracle daabase was resared and mouned or, in he case of he small laency window ess, he daabase was rolled forward wih off-line log files. In he NAS configuraion he Oracle daa files, Oracle log files and Documenum conen files were sored on NFS volumes on he NeApp F840 filer. In he DAS configuraion, he Oracle daa files, Oracle log files and Documenum conen files were sored on a direc-aached SUN D1000 sorage array sriped mode, RAID 0 in order o provide he bes performance comparison. Key Findings: The resuls of his es show ha for a complee resore wih a large laency window, a 30GB Documenum 4i Docbase on a NeApp filer archiecure experienced a large decrease in overall resore process ime for he Docbase and associaed Daabase files when compared o he same Docbase hosed on a DAS array. In he case of daa loss or corrupion, SnapResore reduced he recovery ime for full volume resores, hus increasing overall applicaion availabiliy. Less ime off-line in he recovery process ranslaed o more availabiliy for user ransacions. Using informaion provided by NeApp, Snapsho backups of Docbases larger han he 30GB esed would yield resuls wih approximaely he same backup ime as he 30GB Docbase esed, bu his informaion was no validaed during esing on his projec. The graph below shows he ime o complee a full resore of he daabase and applicaion daa Hours DAS F840 filer Page 17 of 29

18 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide Figure 7 - Full Daabase and Applicaion Daa Resore 3.4 Documenum 4i Backup Using CYA HOTBackup This series of ess was designed o idenify a NeApp filer configuraion ha, deployed in conjuncion wih CYA HOTBackup, could increase he flexibiliy of rouine Documenum 4i backup operaions. NeApp Snapsho and SnapResore can reduce Documenum backup ime, bu canno resore individual objecs o he Docbase. Using CYA HOTBackup ogeher wih NeApp sorage furher reduces downime by allowing Documenum objec changes o be backed up and individual objecs resored while he Documenum sysem is acive and running. The applicaion daa idenified for backup was he Daabase meadaa and log files and he Documenum 4i conen files. The basic configuraion of he Documenum 4i applicaion is illusraed below; Con en Con en Con en Con en Con en User Transacions Web Server / RighSie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer CYA HOTBackup Docbroker Docbase econen Server EBS Gigabi Eherne sorage nework DCTM Conen Files Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Oracle Daabase Files Key = User Transacions CYA HOTBackup Backup Ses Figure 8 Documenum 4i CYA HOTBackup Configuraion Objecive: The ypical scenario for prevening daa loss is defining a daa loss olerance and designing a backup plan ha ensures he daa loss olerance is enforced wih scheduled daa duplicaion. This configuraion explores daa duplicaion in a simulaed Documenum 4i producion environmen wih an applicaion downime olerance dicaing backups o be performed while he applicaion is acive and under load. This scenario demonsraed objec-level resoraion. Objec-level resoraion provides Page 18 of 29

19 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide he Documenum 4i Adminisraor wih he resoraion conrol down o he single documen level, wihou impacing work in progress. Approach: Prior o each es configuraion, he environmen was rese o a baseline Docbase image of 30GB of conen files and 7GB of meadaa. The sandard es load was iniiaed for NAS mode. The CYA HOTBackup process was iniiaed; soring he CYA HOTBackup backup se files on NFS volumes on he NeApp F840 filer. A daa loss even was simulaed by deleing documens from he Docbase. The deleed objecs were resored using he filer-based CYA HOTBackup backup se. Key Findings: The duraion of he CYA HOTBackup updae process is Docbase-size and conen-change dependen. CYA HOTBackup provides a non inrusive, objec-level backup mechanism ha can resore deleed Documenum objecs wihou incurring any Documenum downime. The resuls of his es show he viabiliy of inegraing CYA HOTBackup and NeApp filer echnologies o deploy a configuraion offering objec-level resoraion capabiliies. Page 19 of 29

20 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.5 Documenum 4i Objec-level Recovery Using CYA HOTBackup This es was designed o idenify a NeApp filer configuraion ha could increase he performance and manageabiliy of rouine Documenum 4i daa recovery operaions and increase availabiliy by minimizing ime o recovery (TTR) using CYA Technologies soluions. The applicaion daa idenified for backup was he Daabase meadaa and log files and he Documenum 4i conen files. The basic configuraion of he Documenum 4i applicaion is illusraed below; Con en Con en Con en Con en Con en User Transacions Web Server / RighSie MS IIS Documenum RighSie CYA Resore GUI (sand-alone compo nen) CYA HOTBackup DCTM 4i econen Server Docbroker Docbase econen Server EBS Gigabi Eherne sorage nework NeApp F840 Filer DCTM Conen Files Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Oracle Daabase Files Key = User Transacions CYA HOTBackup Backup Ses Figure 9 CYA Single Objec Resore Configuraion Objecive: The ypical scenario for prevening daa loss is defining a daa loss olerance and designing a backup plan ha ensures he daa loss olerance is enforced wih scheduled daa duplicaion. This configuraion explores daa resoraion in a simulaed Documenum 4i producion environmen wih he applicaion downime olerance dicaing minimal impac o he acive applicaion. The acive and under load resore also required objec-level resoraion. Objec-level resoraion provides he Documenum 4i Adminisraor wih he resoraion conrol down o he single documen level, wihou impacing work in progress. Approach: Prior o each es configuraion, he environmen was rese o a baseline Docbase image of 30GB of conen files and 7GB of meadaa. The sandard es load was iniiaed for NAS mode. Page 20 of 29

21 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide The CYA HOTBackup process was iniiaed; which sored he backup-se files on NFS volumes on he NeApp F840 filer. A daa loss even was simulaed by deleing documens from he Docbase. The CYA HOTBackup resore capabiliy was used o resore he deleed objec conen file. Key Findings: Objec level resoraion provides documen-specific recovery. Work in progress is uncompromised when objec-level resoraion is used. The resuls of his es show he viabiliy of inegraing CYA HOTBackup and NeApp filer echnologies o deploy a configuraion offering objec-level resoraion capabiliies. Page 21 of 29

22 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.6 Documenum 4i Mirroring for Failover Using SnapMirror Disaser Recovery (DR) Documenum 4i configuraions can be creaed using a variey of echnologies and approaches. This configuraion explores sofware based DR configuraions using a SnapMirror and NeApp filer soluions for sorage. This configuraion uilizes a sraegy incorporaing a mirrored applicaion environmen wih no shared componens. Conen Conen Conen Conen Conen User Transacions Conen Conen Conen Conen Conen Web Server / RighSie Web Server / RighSie MS IIS Documenum Righ Sie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer NeApp NearSore R100 DCTM 4i econen Server Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Gigabi Eherne sorage nework DCTM Conen Files Oracle Daabase Files Remoe 100/10 Mb Eherne Connecion S n A p M i r r o r DCTM Conen Files Oracle Daabase Files 100Mb Eherne Connecion Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Key = User Transacions Figure 10 Mirrored Tes Environmen Using SnapMirror Objecive: The ypical scenario for prevening downime is defining a downime olerance and designing an applicaion archiecure ha ensures he downime olerance is enforced by use of redundancy and failover capabiliies. This configuraion explores failover capabiliies in a simulaed Documenum 4i producion environmen wih he applicaion downime olerance dicaing minimal impac o he acive applicaion. This configuraion explores acive/passive sraegies using SnapMirror o suppor he updae of a passive environmen, which can be failed over o in he even of a caasrophic failure. Some Documenum 4i deploymens may require he abiliy o coninue serving mission-criical conen afer experiencing he loss of a daa cener or oher sie-wide disaser. Such business coninuance scenarios ypically involve mirroring o a remoe, sandby Documenum 4i environmen. Failure can occur a many levels in he archiecure due o; Unplanned nework conneciviy ouages o any or all of he applicaion iers Unplanned power ouages o any or all of he applicaion iers Unplanned failure of he hardware/sofware on any or all of he applicaion iers Unplanned, sie-wide disaser ha desroys he primary daa cener In all of hese cases he applicaion should be resilien enough o coninue processing, wih minimal and in some cases virually no perceived applicaion downime. Approach: Page 22 of 29

23 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide This configuraion deployed a NearSore R100 sorage device as he backup sorage soluion. WLBS was used o provide a Web ier on a virual IP wih failover capabiliy. The Oracle daabase files and Documenum 4i conen was sored on a NeApp F840 filer. The daabase and conen files were mirrored on a one-minue inerval o a filer in he sandby environmen. During execuion of he sandard es suie a failure was simulaed and one of he Web servers was forced ino a quiescen sae. The SnapMirror link was broken and he sandby daabase and applicaion servers sared. The full applicaion load was hen direced o he second e-conen server for verificaion of failover. Key Findings: In ess conduced wih WLBS and SnapMirror, he complee failover ime was under 4 minues. Tes execuion validaed he viabiliy of he WLBS and SnapMirror configuraion. The applicaion performed nominally and ran under a verificaion load following he swich over o he sandby environmen. Mirroring conen and meadaa across machines requires ha he environmen on he machines be idenical in paricular, UNIX password files, daabase configuraion files, pahs, environmenal variables and kernel seings. Noe: Because his es simulaed a Documenum 4i failover scenario requiring only low concurren user load afer failover, boh he econen and daabase server were hosed on he same machine, which was significanly less powerful han he machines used in he primary environmen. Likewise, while he sandby Documenum configuraion sored boh conen and meadaa files on he R100, Nework Appliance does no recommend running Oracle (or any oher daabase) insances direcly from a NearSore R100 appliance. The R100 does no provide he same levels of performance and availabiliy as a sandard Nework Appliance enerprise filer and is no inended o suppor high-ransacion workloads. Failover scenarios ha require he abiliy o suppor higher workloads or run for exended periods of ime may require more powerful Documen 4i econen and/or daabase server hardware, muliple servers or SnapMirror replicaion o a Nework Appliance filer insead of a NearSore. In addiion, he WLBS soluion provides nework-level failover only. The requiremens of some Documenum deploymens migh require a more comprehensive failover soluion. Page 23 of 29

24 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.7 Documenum 4i Failover Using CYA Virual SandBy Disaser Recovery (DR) Documenum 4i configuraions can be creaed using a variey of echnologies and approaches. This configuraion explores sofware based Business Coninuance configuraions using a NeApp filer for sorage and mirroring capabiliy, and CYA Virual SandBy for objec-level mirroring and a virual acive environmen capabiliy. This configuraion sraegy uses wo sand-alone applicaions Conen Conen Conen Conen Conen User Transacions Conen Conen Conen Conen Conen Web Server / RighSie Web Server / RighSie MS IIS Documenum RighSie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer NeApp NearSore R100 DCTM 4i econen Server Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Gigabi Eherne sorage nework DCTM Conen Files Oracle Daabase Files Remoe 100/10 Mb Eherne Connecion S n A p M i r r o r DCTM Conen Files Oracle Daabase Files 100Mb Eherne Connecion Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) CYA HOTBackup Backup Ses Key = User Transacions CYA HOTBackup Backup Ses Figure 11 Mirrored Tes Environmen wih CYA Virual SandBy Objecive: The ypical scenario for prevening downime is defining a downime olerance and designing an applicaion archiecure ha ensures he downime olerance is enforced by use of redundancy and failover capabiliies. This configuraion explores failover capabiliies in a simulaed Documenum 4i producion environmen wih he applicaion down ime olerance dicaing minimal impac o he acive applicaion. This configuraion explores an acive/passive deploymen o demonsrae he feasibiliy of inegraing SnapMirror and CYA Virual SandBy echnologies o provide increased Business Coninuance capabiliies. Failure can occur a many levels in he archiecure due o; Unplanned nework conneciviy ouages o any or all of he applicaion iers Unplanned power ouages o any or all of he applicaion iers Unplanned failure of he hardware/sofware on any or all of he applicaion iers Unplanned, sie-wide disaser ha desroys he primary daa cener In all of hese cases he applicaion should be resilien enough o coninue processing, wih minimal and in some cases virually no perceived applicaion downime. Approach: This configuraion deployed a NearSore R100 sorage device as he backup sorage soluion. Page 24 of 29

25 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide In his es CYA HOTBackup was deployed o capure a ho image of he primary Documenum 4i environmen. SnapMirror was used o mirror he CYA HOTBackup backup se o he failover environmen and he CYA VSB process mainained an up-o-dae and acive sandby environmen. The SnapMirror link was broken and a failover induced via he CYA Virual SandBy GUI. Tes merics were aken from he es environmen o esablish he ime aken o fail over o he new environmen. The full applicaion load was hen direced o he second e-conen server for verificaion of failover. Key Findings: Tes execuion validaed he viabiliy of he WLBS, SnapMirror and CYA VSB configuraion. In ess conduced wih WLBS, SnapMirror and CYA Virual SandBy, he complee failover ime was under 3 minues for an environmen wih a ne change of 20 addiional documens. The applicaion performed nominally and ran under a verificaion load following he swich over o he CYAVSB environmen. I is necessary o synchronize he CYA HOTBackup process and he SnapMirror process o ensure he CYA HOTBackup process is complee before he backup se is mirrored o he Sandby environmen. Noe: Because his es simulaed a Documenum 4i failover scenario requiring only low concurren user load afer failover, boh he econen and daabase server were hosed on he same machine, which was significanly less powerful han he machines used in he primary environmen. Likewise, while he sandby Documenum configuraion sored boh conen and meadaa files on he R100, Nework Appliance does no recommend running Oracle (or any oher daabase) insances direcly from a NearSore R100 appliance. The R100 does no provide he same levels of performance and availabiliy as a sandard Nework Appliance enerprise filer and is no inended o suppor high-ransacion workloads. Failover scenarios ha require he abiliy o suppor higher workloads or run for exended periods of ime may require more powerful Documen 4i econen and/or daabase server hardware, muliple servers or SnapMirror replicaion o a Nework Appliance filer insead of a NearSore appliance. In addiion, he WLBS soluion provides nework-level failover only. The requiremens of some Documenum deploymens migh require a more comprehensive failover soluion. Page 25 of 29

26 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.8 Documenum 4i Mirroring for Failover Using NearSore and Rsync Disaser Recovery (DR) Documenum 4i configuraions can be creaed using a muliude of echnologies and approaches. This configuraion explores open-source, sofware-based DR configuraions using a uiliy called rsync (available a hp://samba.anu.edu.au/rsync/) and a NeApp filer for sorage. This configuraion is mos applicable o environmens wih significan invesmens in non NeApp sorage and can be used o bridge beween non NeApp sorage and NeApp sorage. This configuraion uilizes a sraegy incorporaing a mirrored applicaion environmen, and no shared componens. Conen Conen Conen Conen Conen User Transacions Conen Conen Conen Conen Conen Web Server / RighSie Web Server / RighSie MS IIS Documenum Righ Sie MS IIS Documenum RighSie DCTM 4i econen Server NeApp F840 Filer NeApp NearSore R100 DCTM 4i econen Server Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Gigabi Eherne sorage nework DCTM Conen Files Oracle Daabase Files R S Y N C H Remoe 100/10 Mb Eherne Connecion DCTM Conen Files Oracle Daabase Files 100Mb Eherne Connecion Docbroker Docbase econen Server EBS Daabase Server DCTM Meadaa (Oracle 8 RDBMS) Key = User Transacions Figure 12 Mirrored Tes Environmen Using rsync Objecive: The ypical scenario for prevening downime is defining a downime olerance and designing an applicaion archiecure ha ensures he downime olerance is enforced by use of redundancy and failover capabiliies. This configuraion explores failover capabiliies in a simulaed Documenum 4i producion environmen wih he applicaion downime olerance dicaing minimal impac o he acive applicaion and a heerogeneous sorage environmen. The rsync uiliy can be used o synchronize any wo mounable file sysems. This configuraion explores acive/passive sraegies o demonsrae he feasibiliy of using rsysnc o suppor he updae of a passive environmen using a filer for sorage, which can be failed over o in he even of a caasrophic failure. The NeApp SnapMirror echnology requires ha boh he mirror source and arges be NeApp filers or NearSore producs. Documenum 4i deploymens ha require Docbase mirroring from a non NeApp sorage soluion o a NeApp filer may use he following configuraion. Failure can occur a many levels in he archiecure due o; Unplanned nework conneciviy ouages o any or all of he applicaion iers Unplanned power ouages o any or all of he applicaion iers Unplanned failure of he hardware/sofware on any or all of he applicaion iers Unplanned, sie-wide disaser ha desroys he primary daa cener In all of hese cases he applicaion should be resilien enough o coninue processing, wih minimal and Page 26 of 29

27 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide in some case virually no perceived applicaion downime. Approach: This configuraion deployed a NearSore R100 sorage device as he backup sorage soluion. WLBS was used o provide a Web ier on a virual IP wih failover capabiliy. The Oracle daabase files and Documenum 4i conen were sored on a SUN D1000 sorage array sriped mode, RAID 0 in order o provide he bes performance comparison. The daabase and conen files were mirrored, using rsync, on a one-minue inerval o a filer in he failover environmen. During execuion of he sandard es suie one of he Web servers was forced ino a quiescen sae. The full applicaion load was hen direced o he second e-conen server for verificaion of failover. Key Findings: Tes execuion validaed he viabiliy of he WLBS, rsync configuraion. In ess conduced wih WLBS and rsync he complee failover ime was under 4 minues. The applicaion performed nominally and ran under a verificaion load following he swich over o he Sandby environmen. Using rsync o mirror conen and meadaa across machines requires ha he environmen on he machines be idenical, in paricular, UNIX password files, daabase configuraion files, pahs, environmenal variables and kernel seings. Using rsync o mirror o a filer requires he use of NFS mouns o he arge filer, ha is o say he server funcion of he rsync uiliy, which ransfers daa over sockes, canno be used wih a filer configuraion a his ime. Noe: Because his es simulaed a Documenum 4i failover scenario requiring only low concurren user load afer failover, boh he econen and daabase server were hosed on he same machine, which was significanly less powerful han he machines used in he primary environmen. Likewise, while he sandby Documenum configuraion sored boh conen and meadaa files on he R100, Nework Appliance does no recommend running Oracle (or any oher daabase) insances direcly from a NearSore R100 appliance. The R100 does no provide he same levels of performance and availabiliy as a sandard Nework Appliance enerprise filer and is no inended o suppor high-ransacion workloads. Failover scenarios ha require he abiliy o suppor higher workloads or run for exended periods of ime may require more powerful Documen 4i econen and/or daabase server hardware, muliple servers or SnapMirror replicaion o a Nework Appliance filer insead of a NearSore appliance. In addiion, he WLBS soluion provides nework-level failover only. The requiremens of some Documenum deploymens migh require a more comprehensive failover soluion. Page 27 of 29

28 Accenure Repor Documenum 4i on NeApp filers Deploymen Guide 3.9 Documenum 4i Docbase Load Performance on NeApp Filers As daa requiremens increase a a rapid pace, IT managers look for innovaive ways o leverage scarce resources and provide users wih reliable, high-performance access o informaion. They mus scale infrasrucures worldwide o provide users wih access anyime, anywhere. And hey mus proec he corporaion's daa as a corporae asse. The selecion of sorage soluion for he enerprise is a complex issue. In his configuraion he Documenum 4i applicaion was exercised agains a load process, simulaing a coninuous documen load. Conen Conen Conen Conen Conen User Transacions Web Server / RighSie MS IIS Documenum RighSie Sun D1000 Sorage Array DCTM 4i econen Server NeApp F840 Filer DCTM Conen Files PCI/S CSI Docbroker Docbase econen Server EBS Gigabi Eherne sorage nework DCTM Conen Files Daabase Server Oracle Daabase Files PCI /S CSI DCTM Meadaa (Oracle 8 RDBMS) Oracle Daabase Files Key = User Transacions Figure 13 - NeApp Filer-Based Documenum 4i Environmen Objecive: Slow sorage can have several impacs on applicaion performance; performance of backup operaions, he performance of applicaion response ime and he performance impacs of backup operaions on applicaion response imes. In addiion, slow sorage can miigae he value added by high-end server processors. The ypical scenario for addressing slow sorage is a combinaion of highend sorage soluions and RAID echnologies. This configuraion explores he performance impac of a NeApp filer-based environmen on Documen 4i applicaion performance. Approach: Page 28 of 29