Skip to content

Commit 6137533

Browse files
fix(rdb): summer cleaning (#5405)
* fix(rdb): vacay cleaning * fix(rdb): review jessi Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> * fix(rdb): review hugo estelle * fix(rdb): remove br * fix(rdb): review jessi --------- Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com>
1 parent 9803a7f commit 6137533

34 files changed

+360
-444
lines changed

changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ category: databases
99
product: postgresql-and-mysql
1010
---
1111

12-
Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
12+
Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).

changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ category: databases
99
product: postgresql-and-mysql
1010
---
1111

12-
Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
12+
Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).

changelog/february2025/2025-02-24-mongodb-added-vpc-x-managed-mongodbr-integration.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,5 +9,5 @@ category: databases
99
product: mongodb
1010
---
1111

12-
VPC is now integrated with Managed MongoDB®, allowing you to attach a database instance to a Private Network. Refer to [the dedicated documentation](/managed-mongodb-databases/how-to/connect-database-private-network/) to learn how to set it up.
12+
VPC is now integrated with Managed MongoDB®, allowing you to attach a database instance to a Private Network. Refer to [the dedicated documentation](/managed-mongodb-databases/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/) to learn how to set it up.
1313

changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ product: postgresql-and-mysql
1010
---
1111

1212
The Cross-AZ Read Replica feature ensures your data is replicated in a dedicated read-only node, which is located in another AZ within the same Region as your main node.
13-
14-
For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) documentation page.
13+
14+
For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/) documentation page.
1515

Lines changed: 3 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,17 @@
11
---
2-
title: How to enable autobackup for Databases
3-
description: Instructions for enabling Autobackup for PostgreSQL and MySQL databases.
4-
tags: managed-dabatase autobackup database
5-
dates:
6-
validation: 2025-07-15
7-
posted: 2019-05-11
2+
macro: autobackups
83
---
9-
import Requirements from '@macros/iam/requirements.mdx'
104

115
With the autobackup feature, the creation and management of your Database Instance backups is automated according to your backup schedule configuration.
126

137
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).
148

15-
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.
9+
Backups are used when your Database Instance's storage option is a Local volume. Snapshots are available for Database Instances that use [Block Storage](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) volumes.
1610

1711
<Message type="important">
1812
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.
1913
</Message>
2014

21-
<Requirements />
22-
23-
- A Scaleway account logged into the [console](https://console.scaleway.com)
24-
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
25-
- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
26-
2715
<Message type="note">
2816
- 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.
2917
- 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.
@@ -40,8 +28,4 @@ Backups are used when your Database Instance's storage option is a Local volume.
4028
<Message type="note">
4129
Although autobackup is enabled by default, you can select **Manual** in the **Choose a backup configuration** step of the Database Instance creation wizard to disable the feature before you create the Instance. You can also disable it after the Database Instance is ready.
4230
</Message>
43-
5. Configure the backup frequency and retention, then click <Icon name="validate" /> to confirm.
44-
45-
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.
46-
47-
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.
31+
5. Configure the backup frequency and retention, then click <Icon name="validate" /> to confirm.

menu/navigation.json

Lines changed: 17 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -2134,57 +2134,41 @@
21342134
"label": "Connect to a Database Instance",
21352135
"slug": "connect-database-instance"
21362136
},
2137-
{
2138-
"label": "Connect a Database Instance to a Private Network",
2139-
"slug": "connect-database-private-network"
2140-
},
21412137
{
21422138
"label": "Create a database",
21432139
"slug": "add-a-database"
21442140
},
21452141
{
2146-
"label": "Add users",
2147-
"slug": "add-users"
2148-
},
2149-
{
2150-
"label": "Manage permissions",
2151-
"slug": "manage-permissions"
2152-
},
2153-
{
2154-
"label": "Manage allowed IPs",
2155-
"slug": "manage-allowed-ip-addresses"
2156-
},
2157-
{
2158-
"label": "Monitor Database Instances with Cockpit",
2159-
"slug": "monitor-databases-cockpit"
2142+
"label": "Manage users",
2143+
"slug": "manage-users"
21602144
},
21612145
{
2162-
"label": "Change the volume type",
2163-
"slug": "change-volume-type"
2146+
"label": "Manage volumes",
2147+
"slug": "manage-volumes"
21642148
},
21652149
{
2166-
"label": "Enable Autobackup",
2167-
"slug": "enable-autobackup"
2150+
"label": "Manage nodes",
2151+
"slug": "manage-nodes"
21682152
},
21692153
{
2170-
"label": "Manage manual backups",
2171-
"slug": "manage-manual-backups"
2154+
"label": "Manage backups",
2155+
"slug": "manage-backups"
21722156
},
21732157
{
21742158
"label": "Manage snapshots",
21752159
"slug": "manage-snapshots"
21762160
},
21772161
{
2178-
"label": "Clone a Database Instance",
2179-
"slug": "clone-a-database-instance"
2162+
"label": "Manage Read Replicas",
2163+
"slug": "manage-read-replicas"
21802164
},
21812165
{
2182-
"label": "Create Read Replicas",
2183-
"slug": "create-read-replica"
2166+
"label": "Clone a Database Instance",
2167+
"slug": "clone-a-database-instance"
21842168
},
21852169
{
2186-
"label": "Manage Read Replicas",
2187-
"slug": "manage-read-replica"
2170+
"label": "Manage allowed IPs",
2171+
"slug": "manage-allowed-ip-addresses"
21882172
},
21892173
{
21902174
"label": "Configure advanced settings",
@@ -2195,17 +2179,13 @@
21952179
"slug": "renew-tls-certificate"
21962180
},
21972181
{
2198-
"label": "Upgrade a Database Instance",
2199-
"slug": "upgrade-a-database"
2182+
"label": "Monitor Database Instances with Cockpit",
2183+
"slug": "monitor-databases-cockpit"
22002184
},
22012185
{
2202-
"label": "Upgrade Database Instance engine version",
2186+
"label": "Upgrade Database Instance engine versions",
22032187
"slug": "upgrade-version"
22042188
},
2205-
{
2206-
"label": "Enable High Availability",
2207-
"slug": "enable-high-availability"
2208-
},
22092189
{
22102190
"label": "Apply scheduled maintenance",
22112191
"slug": "apply-maintenance"

pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Yes, they are. Since July 2023, the automatic allocation of IP addresses via IPA
7373

7474
For any new Private Networks you create and attach to Managed Databases after July 2023, your private IP addresses are automatically allocated.
7575

76-
If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old private network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
76+
If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old Private Network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
7777

7878
In the example below, we show you how to do so via the API. We specify the automated configuration of your Private Network via IPAM using `"ipam_config": {},`.
7979

pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ CREATE EXTENSION
3737
To fully use the extension, you must grant read/write rights to the user who will be running the `pg_cron` functions to manage jobs on the database.
3838

3939
<Message type="note">
40-
Refer to the [How to add users to a PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/add-users) documentation for more information.
40+
Refer to the [How to add users to a PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/manage-users) documentation for more information.
4141
</Message>
4242

4343
## Scheduling jobs

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ The HA standby node is linked to the main node, using synchronous replication. S
7676
</Message>
7777

7878
<Message type="note">
79-
HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
79+
HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
8080
</Message>
8181

8282
## Local Storage

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -110,15 +110,15 @@ Database Instances supports IP provisioning using IPAM. With this mode, a privat
110110

111111
No, the second node created when you activate the HA on your Managed Database Instance is a hot standby. This node allows a fast failover in case of issues on the primary node.
112112

113-
You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
113+
You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
114114

115115
## If my main node becomes unavailable, is my Read Replica automatically promoted to the main node?
116116

117117
No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure.
118118

119119
## Why is my number of active backups/snapshots exceeding the quota?
120120

121-
When [autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup), or autosnapshot, is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply.
121+
When [autobackup](/managed-databases-for-postgresql-and-mysql/how-to/manage-backups), or autosnapshot, is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply.
122122

123123
Quotas exist to protect Scaleway from abuse, and to protect your Scaleway resources from the unlikely event of malicious behavior by users in your Organization.
124124

0 commit comments

Comments
 (0)