This page details production environment issues.
Failure Scenarios
- hard drive failures
- data center is physically destroyed
- data center connectivity is lost
- database is corrupted
Risks
- DOS attacks
- SQL injection attacks
- account and password security
- virus scans
Environments
Changes of any sort are first tested in the development environment.
If the tests pass, we apply the changes to QA where business users conduct testing.
Only after the business users approve the changes do we release any changes to PROD.
This includes everything from OS upgrades through to our own application code, minor and major
what is our Recovery Time Objective? (how soon to be back up and running)
http://en.wikipedia.org/wiki/Recovery_Time_Objective
access to the database is more important than access to the cached map data
upon a DC failover, we will have to reseed chache
Can we assume that we are not going to use replication?
If no replication, how much work can we loose? (1 day, 4 hours?, 2 hours?)
Recovery Point Objective (acceptable amount of data loss measured in time)
http://en.wikipedia.org/wiki/Recovery_point_objective
monitor disk space
Add Comment