Our countdown, brought to you by SearchStorage.com high availability expert Evan Marcus, includes some common sense tips for the everyday storage admin to follow.
#10: Separate environments
Separate production and development networks
Don't let developers access production systems
- Unless there is an emergency...and then only briefly to diagnose a problem
Keep QA off of production hardware, too
Production hardware is for production only!
You'll never achieve resiliency without separate environments
- Change control cannot be enforced
You may need six environments:
1. Production: Everything works and doesn't change
2. Production mirror: If a prod change goes badly
3. Disaster recovery: Survive after catastrophe hits
4. QA: Change is controlled and tested
5. Development: Works in progress
6. Lab: Playground; preliminary test bed for new hardware and third party software
Could combine prod mirror and disaster recovery
- Definitely better not to, though...
Looking for more great Evan Marcus information?
Check out the Evan Marcus availability tips section of SearchStorage.com.
Also, visit our bookstore for Evan's book: Blueprints for high availability: Designing resilient distributed systems.
Have your own tips for the everyday admin? Submit them here.
This material is copyright 1997-2002 by Evan Marcus and Hal L. Stern. It may not be used in whole or part for commercial purposes without the express permission of both authors.