> For the complete documentation index, see [llms.txt](https://community.peerplays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.peerplays.com/risk-register/introduction/bunker-issue/power-and-backup-failure.md). # Power and Backup Failure ## Description Power is the key factor to run any server. There are situation where the power and backup can fail to switch back which halt the servers to come up. It can be any disaster, natural calamities, accidents, etc., In order to overcome this situation, the following ideas and plans were proposed by the SMEs. This can help the user to understand the possibilities and person to help in retrieve the situation to normal. ## Mitigation Ideas 1. Providing a backup to backups. 2. Plan Tier-3 availability. 3. Generators for critical operations with auto-on features over power failure. 4. Key actors need to have clear communication among themselves 5. The mirrored servers can be Off-premises 6. Maintenance Team with 24/7 availability ## Response Plan 1. Re-deploy the services such as AWS, Linode, etc., whenever in need 2. Pre-written redeploy plans for critical services 3. Start the Generator ## Responder Team In order to find the solution/ to know in details about the risk that has happened, responder team is one to be communicated first. ### First Responder Team **Point of Contact:** Jonathan / Maintenance Team ### Second Responder Team **Point of Contact:** Kyle and Riley respectively --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://community.peerplays.com/risk-register/introduction/bunker-issue/power-and-backup-failure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.