Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Arbutus Migration Guide: Difference between revisions
internal links to three scenarios
(standardize formatting, simplify some language) |
(internal links to three scenarios) |
||
| Line 44: | Line 44: | ||
# Plan an outage window. Generally, shutting down services and the instance(s) is the best way to avoid corrupt or inconsistent data after the migration. Smaller volumes should copy over fairly quickly i.e. within minutes, but larger volumes will take longer. Plan accordingly for this. Additionally, floating IP addresses will change, so ensure the TTL of your DNS records is set to a small value so that the changes propagate as quickly as possible. | # Plan an outage window. Generally, shutting down services and the instance(s) is the best way to avoid corrupt or inconsistent data after the migration. Smaller volumes should copy over fairly quickly i.e. within minutes, but larger volumes will take longer. Plan accordingly for this. Additionally, floating IP addresses will change, so ensure the TTL of your DNS records is set to a small value so that the changes propagate as quickly as possible. | ||
There are three general migration scenarios to consider. Depending on your | There are three general migration scenarios to consider. | ||
* [[#Manual or orchestrated migration|Manual or orchestrated migration]] | |||
* [[#Migrating volume-backed instances|Migrating volume-backed instances]] | |||
* [[#Migrating ephemeral instances|Migrating ephemeral instances]] | |||
Depending on your current setup, you may use any or all of these scenarios to migrate from the West Cloud to the Arbutus Cloud. | |||
== Manual or orchestrated migration == | == Manual or orchestrated migration == | ||