Subversion Fire Drill
You operate a Subversion server installation and have never had problems with stability, reliability or data integrity? Not at all unusual - Subversion is known for its solid performance in production environments. It just works.
Despite Subversion's well-earned reputation as a robust and mature software product, it is by no means immune to data loss or corruption. Hardware defects, unexpected power failures or other unforeseen incidents can leave repository data in an inconsistent state.
Silent data corruption is particularly treacherous, as the damage first becomes apparent when attempting to check out older revisions. Similarly difficult to detect are problems with redundancy automation or flaws in untested backup/restore and disaster-recovery schemes.
In accordance with Murphy's Law, the appearance of these problems tends to coincide with critical release deadlines, laming the development process and necessitating costly firefighting measures. To help identify and eliminate problems before they become acute, we are offering a „fire-drill“ package to address the following threat scenarios:
- Unnoticed repository corruption
- Server failure and data recovery
- Unusable Backups, restore impossible or flawed
- Faulty redundancy automation (failover)
Following a thorough preparation, these scenarios will be tested on your production system. The results of the fire-drill exercise will be recorded and analyzed so that appropriate corrective measures can be taken.
Skeptical? Concerned that something might go terribly wrong? Don't worry, the exercises will be carefully prepared and tailored to your infrastructure – your data will be safe. Contact us.
The fire-drill consists of two separate (non-consecutive) days on site, plus an additional day for analysis and documentation.
Day 1: Preparation
- Infrastructure survey, information-gathering
- Scenario and execution planning
Day 2: Execution
- Fire-drill exercise
Day 3: Wrap-up
- Evaluation and report