DBaaS update [correct] #7141
Open
DBaaS update [correct] #7141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open
✅ Deploy Preview for nostalgic-ptolemy-b01ab8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
jddocs
approved these changes
Nov 12, 2024
| With the re-introduction of this new service, the resources currently available will be retired. Please study the guides below about how to create new databases, migrate existing databases to the new infrastructure, and how the pricing changes. | ||
|
|
||
| ## New database creation | ||
| Starting November 14th, 2024, you can set up new database instances through the Linode API and in Cloud Manager. These locations might be different from where customers currently have running databases. |
There was a problem hiding this comment.
Should "customers" be customer-facing here?
| ## Migration of existing databases | ||
| We highly recommend migrating data from the old database infrastructure as soon as possible because, from November 14th, 2024, the old database infrastructure won’t receive updates anymore. | ||
|
|
||
| All customers will be offered the ability to select the final migration schedule window. There will be an option to choose one or more database instances for each migration process. **If a customer does not initiate the migration after two reminders, we will initiate the migration from the backend during off-business hours.** |
There was a problem hiding this comment.
Same note for the second sentence here - wonder if it should read "If you do not initiate the migration..."
|
|
||
| All customers will be offered the ability to select the final migration schedule window. There will be an option to choose one or more database instances for each migration process. **If a customer does not initiate the migration after two reminders, we will initiate the migration from the backend during off-business hours.** | ||
|
|
||
| At the start of migration, customers will be presented with the following information: |
There was a problem hiding this comment.
And the use of "customers" here
|
|
||
| ## Additional notes | ||
|
|
||
| Restore works differently in the new platform! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.