<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Uprite Services</title>
    <description>The latest articles on DEV Community by Uprite Services (@upriteservices).</description>
    <link>https://dev.to/upriteservices</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4185123%2F4384fd8c-6bec-45d8-b77c-30bf5e6f748d.png</url>
      <title>DEV Community: Uprite Services</title>
      <link>https://dev.to/upriteservices</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/upriteservices"/>
    <language>en</language>
    <item>
      <title>Clean Shutdown and Restart Order for a Small Office in a Texas Grid Emergency</title>
      <dc:creator>Uprite Services</dc:creator>
      <pubDate>Wed, 14 Oct 2026 18:26:27 +0000</pubDate>
      <link>https://dev.to/upriteservices/clean-shutdown-and-restart-order-for-a-small-office-in-a-texas-grid-emergency-edc</link>
      <guid>https://dev.to/upriteservices/clean-shutdown-and-restart-order-for-a-small-office-in-a-texas-grid-emergency-edc</guid>
      <description>&lt;p&gt;A small office survives a Texas grid emergency by shutting down cleanly before the power drops and restarting in dependency order after it returns. The UPS only buys the minutes needed for a clean shutdown. Everything else, from when to act to what comes back first, has to be decided in advance and written down.&lt;/p&gt;

&lt;p&gt;I'm the CTO at a managed IT company in Dallas, and this is the mechanical part of storm planning that's easiest to skip. Not the policy. The wiring.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The problem&lt;/strong&gt;&lt;br&gt;
A UPS is not a runtime plan. It's a shutdown plan.&lt;/p&gt;

&lt;p&gt;The outages that actually hit DFW offices aren't short. After the windstorm on May 28, 2024, Oncor counted more than 650,000 customer outages, and the hardest-hit areas waited days. During Winter Storm Uri in February 2021, ERCOT's firm load shed ran nearly 3 consecutive days. No battery in a server closet covers that.&lt;/p&gt;

&lt;p&gt;So the goal during an outage is simple. Get every server down cleanly while the battery still has charge, then bring things back in the right order once power is stable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 1: make the UPS actually trigger the shutdown&lt;/strong&gt;&lt;br&gt;
A UPS that beeps during its self-test proves the battery works. It doesn't prove the server will shut down. Those are separate paths, and the second one is where plans fail.&lt;/p&gt;

&lt;p&gt;The UPS needs a way to tell the server that the battery is low. There are 3 common paths:&lt;/p&gt;

&lt;p&gt;A USB cable from the UPS to a single server&lt;br&gt;
A network management card in the UPS that signals hosts over the LAN&lt;br&gt;
A shutdown agent on the hypervisor, which can take down the guests before the host&lt;br&gt;
Pick the one that fits your setup, set servers to shut down on low battery, and then test it the boring way. Pull the plug on a quiet afternoon and watch. Until you've seen it happen, assume it doesn't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2: tie shutdown actions to alerts, not to the outage&lt;/strong&gt;&lt;br&gt;
Waiting for the lights to flicker is too late. ERCOT publishes a notification ladder (called TXANS), and the useful trick is to attach an IT action to each rung.&lt;/p&gt;

&lt;p&gt;ERCOT alert IT action&lt;br&gt;
Weather Watch (about 3 to 5 days out)   Confirm last night's backup finished, run a UPS self-test, check that remote logins work&lt;br&gt;
Conservation Appeal Turn off nonessential gear, move scheduled reboots out of the appeal window, confirm low-battery shutdown is set&lt;br&gt;
Energy Emergency Alert Level 1 or 2 Name who shuts down which system, then stand by&lt;br&gt;
Energy Emergency Alert Level 3  Shut down noncritical servers cleanly before the power goes, keep the firewall and core switch on UPS, post a status note for staff&lt;br&gt;
EEA Level 3 is the only rung where ERCOT says controlled outages are possible, and ERCOT is clear they'd hit every customer class, commercial included.&lt;/p&gt;

&lt;p&gt;Keeping the firewall and core switch on UPS is deliberate. They're what lets the status note, and anyone working remotely, still reach the network.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3: restart in dependency order&lt;/strong&gt;&lt;br&gt;
When power comes back, don't power everything on at once. Ignore the first flicker, give the power a little while to hold, and then bring systems up in the order they depend on each other.&lt;/p&gt;

&lt;p&gt;Internet service and the firewall. Everything else needs somewhere to go.&lt;br&gt;
Core switches and Wi-Fi.&lt;br&gt;
Storage, NAS or SAN. Let it finish its own checks before anything leans on it.&lt;br&gt;
Domain controllers, or whatever handles sign-in.&lt;br&gt;
Application servers and line-of-business software.&lt;br&gt;
Backups. Confirm the next scheduled job actually runs and finishes.&lt;br&gt;
The logic is plain. Storage comes before servers because the servers lean on it. Sign-in comes before applications because the apps need something to authenticate against.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 4: post-boot checks&lt;/strong&gt;&lt;br&gt;
Anything that rebooted on its own deserves a look for 3 things:&lt;/p&gt;

&lt;p&gt;The right IP address&lt;br&gt;
The right clock time&lt;br&gt;
The services it's supposed to be running&lt;br&gt;
Then check the UPS units. They're probably drained. A second outage an hour later will find them empty and take everything down hard, which is the exact scenario you spent all that effort avoiding.&lt;/p&gt;

</description>
      <category>sysadmin</category>
      <category>networking</category>
      <category>infrastructure</category>
      <category>backup</category>
    </item>
  </channel>
</rss>
