Add resilient emergency restore for partial BizTalk operations

2026-08-19 17:45:20 +02:00
parent 08626197be
commit 9ce7e8d45a
19 changed files with 1221 additions and 120 deletions
@@ -1,6 +1,25 @@

 # Changelog

+## [2.2.0] - 2026-08-19
+### Added
+- State-aware **Emergency Restore** from an existing `before.json` without overwriting the recovery source.
+- Enterprise Single Sign-On (`ENTSSO`) startup as the first emergency-recovery prerequisite.
+- Durable per-step `shutdown-result.json`, `restore-result.json` and timestamped emergency result reports.
+- Regression coverage for the ACC `Microsoft.BizTalk.Scheduler` failure, best-effort continuation, already-satisfied states, emergency ordering and global cross-application ordering.
+
+### Changed
+- Shutdown and restore continue with remaining independent steps after an isolated WMI or adapter failure and finish with an explicit operator-review result.
+- Runtime operations skip artifacts that already match the requested target state, making recovery from partial shutdowns idempotent.
+- Post-operation snapshots are attempted and diagnosed independently after partial execution failures.
+- Shutdown order is now global across all applications: receive locations, orchestrations, send ports, then host instances.
+- Restore order is now global across all applications: host instances, send ports, orchestrations, then receive locations.
+
+### Fixed
+- An ACC shutdown no longer aborts every later step when `RV_PMP_Trigger_Schedule` fails validation because `Microsoft.BizTalk.Scheduler` or a dependency cannot be loaded.
+- A partial shutdown no longer prevents recovery evidence from being written after the first failed step.
+- Host-instance steps no longer treat the short name and FQDN of the same target server as different machines.
+
 ## [2.1.3] - 2026-08-11
 ### Added
 - Bounded retry/backoff diagnostics for transient `Directory.Move` locks caused by the Windows loader, antivirus or endpoint protection.