Deployment Options Frank Bergmann frank bergmann project-open com

Deployment Options Frank Bergmann frank. bergmann@project-open. com

Contents Saa. S Hosting § § What is Saa. S Hosting? Saa. S Hosting Pros & Cons § Hosting @ Home § § § § Hosting @Home Pros & Cons A Typical Hosting @ Home Configuration How Everything Works Together Backup & Data Security Best Practices Sizing Simplified Network Architecture Software Configuration ã ]project-opem[ 2007, Title / Speaker / 2

A cost efficient option for small and medium companies. No need for IT sophistication. Saa. S Hosting (Software as a Service) ã ]project-opem[ 2007, Title / Speaker / 3

What is Saa. S Hosting? Software as a Service § ]po[ sets up your server together with several other servers in the ]po[ hosting center § ]po[ takes care of backup, security and other system administration tasks § The service is billed monthly Flexible Options § Several hosting options are available with different performance levels § ]po[ provides you with the option to switch to any of the other hosting models ã ]project-opem[ 2007, Title / Speaker / 4

Saa. S Hosting Pros & Cons Advantages § No specific IT skills necessary in your company § Little up-front investment required § Professionally managed backup and security § Service is available even if your internet connectivity is down § Highest availability for external users Disadvantages § File transfer speed is lower then on the local fileserver § Internet failures can disrupt your business ã ]project-opem[ 2007, Title / Speaker / 5

A cost efficient option for companies of all sizes with a certain degree of technology sophistication. Maintenance is handled remotely by a ]po[ administrator. Hosting @Home ã ]project-opem[ 2007, Title / Speaker / 6

Hosting @Home Pros & Cons Advantages § Fastest network connection § Seamless integration with the local file server § Sophisticated backup options available § Easy physical access to the servers § Service is available in the office even if the Internet connection is down § Highest availability for users in the same office Disadvantages § Some IT sophistication in-house is necessary § Higher total cost then Saa. S hosting ã ]project-opem[ 2007, Title / Speaker / 7

A Typical Hosting @ Home Configuration Freelance A Freelance B Se Security Features 1. An a. DSL router provides a cheap Interne connection to the Internet t 2. A backup connection provides connectivity in case of a a. DSL failure Pr 3. A firewall provides controlled access from the Internet im ar 4. A RAID array allow the productive server to survive y the crash of a single hard disk 5. A tape device allows for daily backups of all corporate data. 6. A backup server is ready to take over in case of a failure of the main server. 7. Uninterruptible power Supplies 1 (UPS) protect the system from power failures. 3 ry da n co Hub/Switch a. DSL 2 Firewall 4 PC PC PC RAID Server 6 RAID 5 Backup Server 7 Tape UPS UPS LAN ã ]project-opem[ 2007, Title / Speaker / 8

How Everything Works Together 2. 3. 4. 5. 6. 7. AOLServer is ]po[‘s “Application Server”… …and executes the ]po[ code All data are stored in a Postgre. SQL database The data are copied daily to the backup server The backup server contains an exact copy of the production server, ready to take over in the case of a failure. Documents and files are stored in a normal Windows file server with local backup. The ]po[ servers “mounts” the Windows file server share in order to access the files. The files stay on the Windows server. Linux ]po[ Production Server 1 3 AOL Server Postgre. SQL 2 ]po[ Code 7 Windows File Server Backup 1. 6 File Server 4 7 Linux ]po[ Backup Server 5 AOL Server Postgre. SQL ]po[ Code ã ]project-opem[ 2007, Title / Speaker / 9

Backup & Data Security Best Practices Backup Policies § All server should be equipped with RAID arrays. § We recommend a weekly full-backup of all data on a tape or similar device in order to be able to keep multiple versions. § The backup server should receive daily database backups of the production server in order to speed up the recovery process. 2 1 3 RAID Server RAID Backup Server Tape Backup Scheme 1. Data are stored on a RAID array 2. Daily tape backup 3. Daily backup to backup server for quick recovery ã ]project-opem[ 2007, Title / Speaker / 10

Sizing We recommend two identical servers as “production” and “backup + test” servers “Active users” are those users who are requesting 1 -10 ]po[ pages per minute We recommend Postgre. SQL for all but the largest installations § § § Active Users Computer Memory RAID Server RAID Backup Server Tape Hard Disk 1 -5 Normal desktop computer, even VMware >1 GByte IDE RAID 5 -10 Small Linux server with 1 dual-core processor >2 Gbyte SCSI RAID 10 -20 Linux server with 2 processors with 2 -4 cores each. >4 GByte SCSI RAID 20 -50 Linux server with 4 processors with 2 -4 cores each. >8 GByte SCSI RAID >50 Linux server with >8 processors and Oracle database >16 GByte SCSI RAID plus storage network ã ]project-opem[ 2007, Title / Speaker / 11

Simplified Network Architecture Freelance A Freelance B Interne t For small companies (<10 active users, <30 employees) PC PC PC Hub/Switch Telephone n tio ec nn Co § Two ordinary PCs serve as servers. 2 SATA disks per computer act as RAID § A tape backup is attached to the productive server for daily backups. § A single a. DSL lines provides Internet access § The a. DSL router acts as a minifirewall (packet filter) a. DSL Tape PC PC UPS LAN ã ]project-opem[ 2007, Title / Speaker / 12

Software Configuration § We recommend Linux for the production and backup server (preferably RHEL or Cent. OS, alternatively Open Su. SE 10. x, no Su. SE Enterprise Server!) § Postgre. SQL 8. 2 for < 50 active users § Backup and failover configuration for operating system, database and user data § File storage kept apart from the ]po[ server. § System Monitoring (Big. Brother, Nagios, …) Documentation § Please see the “Operations & Maintenance Guide” for operation procedures ã ]project-opem[ 2007, Title / Speaker / 13

End Frank Bergmann frank. bergmann@project-open. com www. project-open. com ã ]project-opem[ 2007, Title / Speaker / 14