We’re excited to announce a Shorter Migration Downtimes is now generally available. This feature is designed to minimise downtime during realm migrations, making the process more efficient and less disruptive for our enterprise customers.
Why Shorter Migration Downtimes?
Planning for a 24-hour migration downtime can be challenging for customers, especially when this needs to be scheduled multiple times as apps begin supporting migrations. Our data shows that over 99% of app migrations are completed within 2 hours. This insight, along with feedback from customers and partners led us to rethink and optimise the migration process.
Shorter Default Downtimes
Based on our observations, the majority of migrations are completed within 2 hours. We have reduced the default downtime for realm migrations from 24 hours to 2 hours. This change will streamline the migration process, reducing interruptions for our customers and aligning more closely with actual migration times.
FAQ
Can app partners alter this default downtime?
With the introduction of Shorter Migration Windows preview, Connect developers can specify the expected duration of a realm migration for their customers. To implement this change, update the app descriptor to include the maxMigrationDurationHours parameter. This parameter will set the estimated migration duration, ranging from 0.5 to 24 hours. The example below demonstrates how to configure this setting:
"dataResidency": {
"maxMigrationDurationHours": 4 // default is 2 hours, maximum is 24 hours
}
What happens if a migration takes longer than the defined period?
- Like it does currently, if a migration takes longer than the defined maxMigrationDuration, the migration will timeout and fail.
What happens if a migration takes less time than the defined period?
- In the event a migration takes less time than the defined maxMigrationDuration, if all migrations for that customer are finished, they will be brought back online earlier.
Customer Experience
Customers will benefit from greater transparency and predictability in the migration process. They will be able to view the expected downtime for their apps as they migrate.
Note: The migration downtime for a customer is the highest maxMigrationDuration provided among Apps in the migration.
You can read more in our documentation
As always, your insights are incredibly valuable to us, so please don’t hesitate to ask questions, share feedback, or throw out ideas.