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

2.  ]project-opem[ 2007, Title / Speaker / 2 SaaS Hosting  What is SaaS Hosting?  SaaS 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 Contents

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

4.  ]project-opem[ 2007, Title / Speaker / 4 What is SaaS 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

5.  ]project-opem[ 2007, Title / Speaker / 5 SaaS 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

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

7.  ]project-opem[ 2007, Title / Speaker / 7 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 SaaS hosting

8.  ]project-opem[ 2007, Title / Speaker / 8 Security Features 1.An aDSL router provides a cheap connection to the Internet 2.A backup connection provides connectivity in case of a aDSL failure 3.A firewall provides controlled access from the Internet 4.A RAID array allow the productive server to survive 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 (UPS) protect the system from power failures. A Typical Hosting @ Home Configuration UPS Interne t Backup Server Server Firewall aDSL Hub/Switch Tape PC Freelance A Freelance B RAID LAN Secondary Primary 3 4 6 5 12 7

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

10.  ]project-opem[ 2007, Title / Speaker / 10 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. Backup Server Server Tape RAID 1 2 Backup Scheme 1.Data are stored on a RAID array 2.Daily tape backup 3.Daily backup to backup server for quick recovery 3 Backup & Data Security Best Practices

11.  ]project-opem[ 2007, Title / Speaker / 11  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 PostgreSQL for all but the largest installations Backup Server Server Tape RAID Active UsersComputerMemoryHard Disk 1-5Normal desktop computer, even VMware>1 GByteIDE RAID 5-10Small Linux server with 1 dual-core processor >2 GbyteSCSI RAID 10-20Linux server with 2 processors with 2-4 cores each. >4 GByteSCSI RAID 20-50Linux server with 4 processors with 2-4 cores each. >8 GByteSCSI RAID >50Linux server with >8 processors and Oracle database >16 GByteSCSI RAID plus storage network Sizing

12.  ]project-opem[ 2007, Title / Speaker / 12 For small companies (<10 active users, <30 employees)  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 aDSL lines provides Internet access  The aDSL router acts as a mini-firewall (packet filter) Interne t Freelance A Freelance B Telephone UPS aDSL Hub/Switch PC LAN Connection PC Tape Simplified Network Architecture

13.  ]project-opem[ 2007, Title / Speaker / 13 Configuration  We recommend Linux for the production and backup server (preferably RHEL or CentOS, alternatively Open SuSE 10.x, no SuSE Enterprise Server!)  PostgreSQL 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 (BigBrother, Nagios, …) Documentation  Please see the “Operations & Maintenance Guide” for operation procedures Software Configuration

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