Using a UPS to shut down Windows Server, virtualization hosts and NAS in the correct order
UPS shutdown must follow battery runtime, workload dependencies and start order: stop applications and VMs first, then hosts and storage, and prove the sequence in a power-loss drill.

Establish a factual baseline with “UPS communication and battery thresholds” and “application shutdown order”, then move to “virtual-machine shutdown order”. Use backup chain, repository state and recovery results as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking UPS communication and battery thresholds, application shutdown order and virtual-machine shutdown order independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · UPS communication and battery thresholds | Checking UPS communication and battery thresholds helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of UPS communication and battery thresholds. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 02 · application shutdown order | Checking application shutdown order helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of application shutdown order. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 03 · virtual-machine shutdown order | Checking virtual-machine shutdown order helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of virtual-machine shutdown order. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 04 · storage and NAS shutdown last | Checking storage and NAS shutdown last helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of storage and NAS shutdown last. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 05 · power-restoration startup order | Checking power-restoration startup order helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of power-restoration startup order. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
| 06 · scheduled power-failure drills | Checking scheduled power-failure drills helps establish whether the storage or backup state is consistent and can be recovered; compare it with a known-good baseline and the incident timeline. | Record the actual state of scheduled power-failure drills. Record the actual storage, disk, repository or backup state and obtain relevant logs. Validate recovery without changing original data first. |
Investigation and change sequence
- Capture a baseline for UPS communication and battery thresholds and application shutdown order and compare it with a known-good system.
- Correlate evidence from virtual-machine shutdown order and storage and NAS shutdown last to distinguish the direct fault from dependent symptoms.
- Only if evidence points to power-restoration startup order, plan a controlled change with backups, a change window and rollback triggers.
- Finally check scheduled power-failure drills and the real business workflow. Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
Validation and rollback evidence
- Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
- Recheck power-restoration startup order and scheduled power-failure drills against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming UPS communication and battery thresholds is sufficient while overlooking application shutdown order and dependent checks.
- Changing several settings before preserving the original evidence for virtual-machine shutdown order.
- A healthy RAID, snapshot or successful backup job is not proof of a recoverable workload.
Common questions and acceptance criteria
What should be checked first?
Begin with UPS communication and battery thresholds and application shutdown order. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Verify recovered content, application usability and elapsed time against the recovery objective; retain the test evidence.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
