Skip to content

Commit 456e185

Browse files
fix(rdb): block changes (#4331)
1 parent db37add commit 456e185

File tree

9 files changed

+25
-22
lines changed

9 files changed

+25
-22
lines changed

pages/managed-databases-for-postgresql-and-mysql/concepts.mdx

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,20 +23,20 @@ Access control is handled directly at network-level by Load Balancers, making th
2323

2424
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.
2525

26-
## Block Storage Legacy
27-
28-
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.
29-
30-
## Block Storage Low Latency
26+
## Block Storage
3127

32-
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.
28+
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.
3329

34-
Refer to the [Block Storage Low Latency documentation section](/block-storage/concepts/) to learn more about this volume type.
30+
Refer to the [Block Storage documentation section](/block-storage/concepts/) to learn more about this volume type.
3531

3632
<Message type="note">
37-
Block Low Latency volumes are only available with new-generation node types and in the PAR and AMS regions.
33+
New Block storage volumes are only available with new-generation node types and in the PAR and AMS regions.
3834
</Message>
3935

36+
## Block Storage Legacy
37+
38+
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.
39+
4040
## Clone feature
4141

4242
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
122122

123123
## Volume type
124124

125-
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).
125+
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).
126126

127127
<Message type="note">
128-
Block Low Latency volumes are only available with new-generation node types and only in the PAR and AMS regions.
128+
New Block Storage volumes are only available with new-generation node types and only in the PAR and AMS regions.
129129
</Message>
130130

131131
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.

pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,8 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
3737
The Database Instance goes into the `Initializing` state.
3838

3939
<Message type="important">
40-
- 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.
40+
- 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.
4141
- Disk size cannot be reduced, so when switching from Local to Block, the volume size remains the same by default.
42-
- 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.
42+
- 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.
43+
- 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.
4344
</Message>

pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ The clone feature allows you to create a new Database Instance from an existing
3535
5. Enter a name for your database or leave the default name suggested by the Scaleway console.
3636
6. Select a node type. You can keep the same node type, or upgrade to a bigger one.
3737
<Message type="important">
38-
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. <br /><br />
38+
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. <br /><br />
3939

40-
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).
40+
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).
4141
</Message>
4242
7. Click **Clone Database Instance**.
4343

pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Compared to traditional database management, which requires customers to provide
5050
- Choose your storage type and capacity. Two types of storage are available:
5151
- **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.
5252

53-
- **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.
53+
- **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.
5454

5555
- **Local SSD Storage** - Your storage is fixed and tied to your compute resource.
5656
<Message type="note">

pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database
3434
- **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.
3535

3636
<Message type="important">
37-
[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.
37+
[Block Storage volumes](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) are currently not available with Multi-AZ Read Replicas.
3838
</Message>
3939

4040
6. Select the network type. Two types are available:

pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ With the autobackup feature, the creation and management of your Database Instan
1818

1919
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).
2020

21-
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.
21+
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.
2222

2323
<Message type="important">
2424
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.
3434
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.
3535
<br />
3636
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.
37+
<br />
38+
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.
3739
</Message>
3840

3941
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.
4951

5052
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.
5153

52-
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.
54+
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.

pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto
3737
## How to change the node type
3838

3939
<Message type="important">
40-
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. <br /><br />
40+
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. <br /><br />
4141

42-
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).
42+
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).
4343
</Message>
4444

4545
1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays.

pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You must upgrade your engine version if your Database Instance uses an End of Li
2323
<Message type="important">
2424
The version upgrade is only available for:
2525
- Database Instances using engine versions preceding the most recent version available.
26-
- 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.
26+
- 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.
2727
</Message>
2828

2929
<Macro id="requirements" />

pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Compared to traditional database management, which requires customers to provide
3939
- Choose your storage type and capacity. Two types of storage are available:
4040
- **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.
4141

42-
- **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.
42+
- **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.
4343

4444
- **Local SSD Storage**: Your storage is fixed and tied to your compute resource.
4545
<Message type="note">

0 commit comments

Comments
 (0)