Shulou(Shulou.com)06/01 Report--

The standard "active and standby switching test and destructive test" (hereinafter referred to as the test) shall prevail on a quarterly / semi-annual basis.

"testing" is the best exercise to verify the safety, effectiveness, maintainability and staffing of the architecture design.

The plan and process of the "test" should involve all the elements in the architecture. Any element that is deliberately avoided indicates that there is a certain risk, and do not try to omit the "test" of the simplest element. Any unexpected situation will always occur in the "test", and we should also know in our hearts that we are happy to see any unexpected situation in the "test" that is not in the plan. This gives us a chance to fix it.

Invite other departments or "laymen" to develop "testing" cases where permissible. When implementing "tests", "saboteurs" and "recovers" are preferably different people.

Question to ask: how does the architecture work when something goes wrong with an element? How does the architecture work when there are problems with two different types of elements? What happens when there are problems with N different types of elements? Is there a hot backup or cold backup for any unit element? What is the backup cycle and how long is the recovery time? If there is a problem that local staff cannot solve, who is the support that can be contacted and how long will it take to be there? Is there an internal operation and maintenance process plan? Wait, wait.

Risk awareness from top to bottom, if all can be reflected in the "test", this is the best thing, software and hardware investment take the "test" effect as one of the considerations.

A short article written in 2011, moved here.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.