--- title: "Migrating to High Availability - an FSI success story" url: https://daily.dev/posts/migrating-to-high-availability---an-fsi-success-story-ahnsewbyn source_url: https://octopus.com/blog/migrating-to-high-availability-fsi-success-story type: article source: "OctopusDeploy" published: 2026-08-17T11:20:14.875Z updated: 2026-08-17T11:20:38.180Z tags: ["cicd", "active-directory", "octopus-deploy"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Migrating to High Availability - an FSI success story **[OctopusDeploy](https://daily.dev/sources/octopusdeploy)** · 5 min read · 0 upvotes · 0 comments ## Summary A large financial services organization running Octopus Server on an outdated single-instance setup migrated to a High Availability cluster across a different Active Directory domain. The move involved database migration, shared storage relocation, authentication changes, and DNS cutover. By working through the customer's detailed questions and breaking the migration into small, reversible, checkpointed stages, Octopus's customer engineering team helped the cautious enterprise complete the upgrade safely. The customer now follows a regular six-monthly upgrade cadence and rarely needs support. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What steps should I follow to migrate Octopus Server from a single instance to a High Availability cluster with minimal risk? Break the migration into small, reversible stages with checkpoints rather than one cutover. Steps include notifying users in advance, adding new HA nodes as UI-only nodes behind the load balancer, building HA node VMs ahead of time, putting the existing server into maintenance mode and draining tasks, backing up and restoring the database into the new environment, moving shared storage separately, installing Octopus Server on one HA node first to test local authentication and deployments, then repeating for remaining nodes, enabling Active Directory only after basics are proven, and pointing DNS at the load balancer last. _Teams planning a similar high-availability migration can find staged upgrade playbooks like this on daily.dev._ ### Why would a company move Octopus Server to a different Active Directory domain during a High Availability upgrade? A financial services organization needed to relocate its Octopus Server HA cluster into a different Active Directory domain as part of consolidating infrastructure, which affected the database, home directory, shared storage, authentication, and DNS. Testing local Octopus user authentication before enabling Active Directory sign-in reduced the risk of locking out teams during the switch. _Engineers weighing similar domain and authentication migration risks can track real-world examples on daily.dev._ ## Similar posts on daily.dev - [Innovation spotlight: How 3 customers are driving change with migration to Azure SQL](https://daily.dev/posts/innovation-spotlight-how-3-customers-are-driving-change-with-migration-to-azure-sql-0bznr7bjk) · Microsoft Azure · 0 upvotes · 0 comments - [The Hard-Stop Rule: From 3 HCM Monoliths to 120 Domain Microservices](https://daily.dev/posts/the-hard-stop-rule-from-3-hcm-monoliths-to-120-domain-microservices-cwzt7b3br) · InfoQ · 10 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#active-directory](https://daily.dev/tags/active-directory), [#octopus-deploy](https://daily.dev/tags/octopus-deploy) [View this post on daily.dev](https://daily.dev/posts/migrating-to-high-availability---an-fsi-success-story-ahnsewbyn)