Documente Academic
Documente Profesional
Documente Cultură
1. Overview
1.1 This is just the Outline.
1.1.1Document is not yet complete. Email me if you would like to receive
what I have so far. (ron@eis-corp.com)
2. Objectives
2.1 High Availability, Business Continuity, and Disaster Recovery
2.1.1Websites that NEVER GO DOWN. NO impact when servers crash.
3. Applications
3.1 Standards for Accepting Applications into the Load Balanced (LB)
Environment.
3.3 OS, Web Server, & Software Platforms Load Balanced in multiple data
center locations.
3.3.1Based on the application requirements, which datacenter locations,
services & servers will be LB?
4.2 Load Balancing Server Farms & other network devices using a Server
Load Balancer
4.2.1Different types of servers that will be load balanced
4.3.2Reliability / NO DOWNTIME
4.3.3Enhanced Capacity
4.4.2Frustrated clients
4.4.3Calls to helpdesk
5.1.2Compression
5.1.3SSL Acceleration
6.4 Firewalls
7.4 Is one vendor the best solution for everyone (Not necessarily)?
8. Network Design
8.1 Routing for LB (Load Balanced) Environments.
8.2 IP Addressing
8.2.1Company owned IP address space (x.x.x.x)
9.5.2PTR Record
9.5.3CNAME Record
9.5.4NS Record
10.SSL / HTTPS
10.1 Type of SSL encryption (128 Bit or Key Length 1024)
10.3.5Certificate management
14.4 SSH
15.2 How does GSLB help to provide High Availability for Applications
located in multiple Data Centers?
15.4 What happens when you lose a primary GSLB and/or if you lose a
primary DNS?
15.11.2GSLB Names
15.11.3SERVER LB Names
15.11.5LB Modes
15.12.6DNS TTL
16.2 How does SERVER LB help to provide High Availability for groups
of servers?
16.12 Persistence
16.12.1Why is persistence needed? And why is it important?
16.18.2Administrative IP addresses
20.Application Monitoring
20.1 Who is using what tools.
20.1.1What tools are out there?
21.Appendix
21.1 Network Diagram
21.3 IP addresses