diff --git a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx index 6b2816b78a..1446fccbd6 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx @@ -23,20 +23,20 @@ Access control is handled directly at network-level by Load Balancers, making th Database Instances have settings that allow you to tune the behavior of their database engine to better fit your needs. Available settings depend on the database engine and its version. Each Database Instance setting entry has a default value that the user can override. The deletion of a setting entry restores the setting to the entry's default value. Some default values can be different from the engine's default, as their configuration is optimized to work at full potential with the Scaleway ecosystem. -## Block Storage Legacy - -Block Storage Legacy is a volume type that is decoupled from your compute resources. You can increase your storage space to up to 10 TB without changing your node type. - -## Block Storage Low Latency +## Block Storage -Block Storage Low Latency is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. +Block Storage is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. -Refer to the [Block Storage Low Latency documentation section](/block-storage/concepts/) to learn more about this volume type. +Refer to the [Block Storage documentation section](/block-storage/concepts/) to learn more about this volume type. - Block Low Latency volumes are only available with new-generation node types and in the PAR and AMS regions. + New Block storage volumes are only available with new-generation node types and in the PAR and AMS regions. +## Block Storage Legacy + +Block Storage Legacy is a volume type that is decoupled from your compute resources. You can increase your storage space to up to 10 TB without changing your node type. + ## Clone feature Clone is a feature that allows you to create a full copy of your Database Instance, including users and permissions, at a point in time. This new Instance is fully independent of its parent. @@ -122,10 +122,10 @@ A database type that uses the relational model, which means that it stores and p ## Volume type -This is the type of storage used on your Database Instances. Three types are available: [Local Storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage Low Latency](#block-storage-low-latency). +This is the type of storage used on your Database Instances. Three types are available: [Local Storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage](#block-storage). - Block Low Latency volumes are only available with new-generation node types and only in the PAR and AMS regions. + New Block Storage volumes are only available with new-generation node types and only in the PAR and AMS regions. You can select the volume type upon Database Instance creation, and you can [change the type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) anytime. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx index d86f99e3e3..656382c021 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx @@ -37,7 +37,8 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an The Database Instance goes into the `Initializing` state. - - When switching from a local volume to a block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage. + - When switching from a Local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage. - Disk size cannot be reduced, so when switching from Local to Block, the volume size remains the same by default. - - When switching from a block to a local volume, make sure to select a node with a Local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance. + - When switching from a Block to a Local volume, make sure to select a node with a Local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a Local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance. + - When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/faq/databases-for-postgresql-and-mysql/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx index b1a4aca194..2d1fb011b6 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx @@ -35,9 +35,9 @@ The clone feature allows you to create a new Database Instance from an existing 5. Enter a name for your database or leave the default name suggested by the Scaleway console. 6. Select a node type. You can keep the same node type, or upgrade to a bigger one. - If you have a new-generation Database Instance using a local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

+ If you have a new-generation Database Instance using a Local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). + Similarly, if you have a new-generation Database Instance using a [Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). 7. Click **Clone Database Instance**. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx index 01d587f31d..2c665e9c64 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx @@ -50,7 +50,7 @@ Compared to traditional database management, which requires customers to provide - Choose your storage type and capacity. Two types of storage are available: - **Block Storage Legacy** - With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. - - **Block Storage Low Latency**: This storage type works like the [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. + - **Block Storage**: This storage type works like the [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. - **Local SSD Storage** - Your storage is fixed and tied to your compute resource. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx index ac76145473..2403d35bb4 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx @@ -34,7 +34,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database - **Multi-AZ**: Your Read Replica is hosted in a different AZ, ensuring the resilience of your Replica. We recommend this option for ensuring the availability of your infrastructure, and improving your disaster recovery plan. - [Block Storage Low Latency volumes](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) are currently not available with Multi-AZ Read Replicas. + [Block Storage volumes](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) are currently not available with Multi-AZ Read Replicas. 6. Select the network type. Two types are available: diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx index cb19a6bf6d..51b8f9f5b5 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx @@ -18,7 +18,7 @@ With the autobackup feature, the creation and management of your Database Instan Two types of autobackups are available at Scaleway: [backups](/managed-databases-for-postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot). -Backups are used when your Database Instance's storage option is a local volume. Snapshots are available for Database Instances that use [Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy) and [Low Latency](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) Block Storage volumes. +Backups are used when your Database Instance's storage option is a Local volume. Snapshots are available for Database Instances that use [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy) and [Block Storage](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) volumes. Although they bear the same feature name, automated snapshots and automated backups are different in their design. If you have a Database Instance using Block Storage, it is only possible to use automated snapshots as autobackup. @@ -34,6 +34,8 @@ Backups are used when your Database Instance's storage option is a local volume. The autobackup feature is enabled by default upon the creation of an Instance. Simultaneously, a schedule policy is created. The default autobackup frequency is of 1 per day with a retention period of 7 days. You can change this in the Database Instance information page after Instance creation.
By default, the Database Instance creation date is used as the base timestamp for the automated backups. When you change the schedule configuration, the moment you validated the new configuration becomes the new base timestamp. For example, if at 8 a.m. on a Thursday you update the autobackup frequency to 24h, your next autobackup will be created at 8 a.m. on a Friday. +
+ When autobackup is enabled for your Local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/faq/databases-for-postgresql-and-mysql/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information. 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. @@ -49,4 +51,4 @@ Backups are used when your Database Instance's storage option is a local volume. You can follow our documentation to [restore](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and [export](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-export-backups) your backups. -For snapshots, you can follow the [how to restore snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. \ No newline at end of file +For snapshots, you can follow the [how to restore snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx index 1187957b95..10aa0e21f1 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx @@ -37,9 +37,9 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto ## How to change the node type - If you have a Database Instance that uses a local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

+ If you have a Database Instance that uses a Local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) node type and want to switch to a first-generation node type, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). + Similarly, if you have a new-generation Database Instance using a [Block Storage volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) node type and want to switch to a first-generation node type, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index 175a58205e..ef71083c5d 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -23,7 +23,7 @@ You must upgrade your engine version if your Database Instance uses an End of Li The version upgrade is only available for: - Database Instances using engine versions preceding the most recent version available. - - Database Instances using Block volumes. If your Database Instance uses a local volume, you must first [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to a Block volume and try again. + - Database Instances using Block volumes. If your Database Instance uses a Local volume, you must first [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to a Block volume and try again. diff --git a/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx b/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx index 82884f3fc4..227caedd74 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx @@ -39,7 +39,7 @@ Compared to traditional database management, which requires customers to provide - Choose your storage type and capacity. Two types of storage are available: - **Block Storage Legacy**: With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. - - **Block Storage Low Latency**: This storage type works like Block Storage Legacy, while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. + - **Block Storage**: This storage type works like Block Storage Legacy, while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. - **Local SSD Storage**: Your storage is fixed and tied to your compute resource.