<div>
<p>Have the UPS systems been tested recently for expected runtime post power off?</p>
</div>


Have the UPS systems been tested recently for expected runtime post power off?

kenfcamp

EE Topic Advisor, Independent Technology Professional

Brian B

<div>
<p>No, don't have a template, sorry.</p><p>I'd recommend looking at your DR documentation (and DR testing if yo do it) though as it's likely to have a lot of overlap. could save you some time writing a new document if you could base it on an existing one.</p><p><br></p>
</div>


No, don't have a template, sorry.

I'd recommend looking at your DR documentation (and DR testing if yo do it) though as it's likely to have a lot of overlap. could save you some time writing a new document if you could base it on an existing one.




<div>
<div><p>This is a planed shut down, so DR doesn't apply and they don't have an RTO or RPO defined anyway. (It' on the list of many things they are missing).</p><p>We have lots of battery capacity, but we are still shutting down just in case the outage lasts longer than planned. I will shut off the UPSes as part of the power down.</p></div>
</div>


This is a planed shut down, so DR doesn't apply and they don't have an RTO or RPO defined anyway. (It' on the list of many things they are missing).

We have lots of battery capacity, but we are still shutting down just in case the outage lasts longer than planned. I will shut off the UPSes as part of the power down.

<div>
<p>I disagree. the vast majority of steps for recovering from DR will overlap with powering back on after a planned shutdown. Many of the shutdown steps of a 'DR test' will also align with a planned shutdown.</p><p>It should also identify who to contact to advise of planned (or unplanned) DR events</p><p><br></p><p>A good DR plan should share many elements with the plan you are looking for.</p><p><br></p>
</div>


I disagree. the vast majority of steps for recovering from DR will overlap with powering back on after a planned shutdown. Many of the shutdown steps of a 'DR test' will also align with a planned shutdown.

It should also identify who to contact to advise of planned (or unplanned) DR events




A good DR plan should share many elements with the plan you are looking for.




Senior Technical Architect - HA/Compute/Storage

Philip Elder

<div>
<div class="content wysiwyg-content fr-view">
<p>Have been notified of a power shutdown to the entire building. I'm trying to write up a document with an overview of the IT work required before and after the power outage as well as how it all fits into a timeline relative to the actual event.</p><p>Things like:</p><p>- confirming local access to all servers/hosts</p><p>- confirming backups</p><p>- send notice to affected users</p><p>Just wondering if anyone has a template they could share for a planned server room shutdown?</p><p>Environment is Windows servers and VMware, but doesn't have to be that specific.</p>
</div>
</div>



Have been notified of a power shutdown to the entire building. I'm trying to write up a document with an overview of the IT work required before and after the power outage as well as how it all fits into a timeline relative to the actual event.
Things like:
- confirming local access to all servers/hosts
- confirming backups
- send notice to affected users
Just wondering if anyone has a template they could share for a planned server room shutdown?
Environment is Windows servers and VMware, but doesn't have to be that specific.

Documentation for Server Room Shutdown?

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.

IT Administration

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.