Skip to content

Commit

Permalink
Merge branch 'master' into rc-packaging
Browse files Browse the repository at this point in the history
  • Loading branch information
@cmilesb
cmilesb committed Mar 25, 2024
2 parents 0737dbe + 8f51fa7 commit 52abcca
Show file tree
Hide file tree
Showing 20 changed files with 153 additions and 122 deletions.
6 changes: 5 additions & 1 deletion content/rc/changelog/march-2024.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,8 @@ aliases: []

### Fixed subscriptions through Google Cloud Marketplace

You can now use your [Google Cloud Marketplace]({{<relref "/rc/cloud-integrations/gcp-marketplace/">}}) account to pay for your Fixed subscriptions as well as your Flexible subscriptions.
You can now use your [Google Cloud Marketplace]({{<relref "/rc/cloud-integrations/gcp-marketplace/">}}) account to pay for your Fixed subscriptions as well as your Flexible subscriptions.

### Active-Passive with TLS

[Active-Passive]({{<relref "/rc/databases/migrate-databases#sync-using-active-passive">}}) now supports source databases that require connections over TLS. See [Migrate data]({{<relref "/rc/databases/migrate-databases">}}) for more information.
60 changes: 41 additions & 19 deletions content/rc/databases/migrate-databases.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -52,48 +52,70 @@ To migrate data using Active-Passive syncing, specify the target database as an
{{< note >}}
Before you use Active-Passive, be aware of the following limitations:

- An error will appear when syncing the two databases if the source database has [Transport Layer Security (TLS)]({{< relref "/rc/security/database-security/tls-ssl" >}}) enabled. [Contact support](https://redis.com/company/support/) if you want to migrate a TLS-enabled database using Active-Passive.
- An error will appear when syncing the two databases if the source and target databases are hosted on different Redis Cloud accounts. [Contact support](https://redis.com/company/support/) if you want to migrate a database between accounts using Active-Passive.

- As long as Active-Passive is enabled, data in the target database will not expire and will not be evicted regardless of the set [data eviction policy]({{<relref "rc/databases/configuration/data-eviction-policies.md">}}). We recommend that you turn off Active-Passive after the databases are synced.
{{< /note >}}

### Detailed Active-Passive syncing process

If the databases belong to the same Redis Cloud account, follow these detailed steps to migrate data using Active-Passive syncing:
Follow these detailed steps to migrate data using Active-Passive syncing:

1. Select **Databases** from the [Redis Cloud console](https://app.redislabs.com/) menu and select the target database in the list.

1. Select **Databases** from the [Redis Cloud console](https://app.redislabs.com/) menu and select the source database in the list.
{{<image filename="images/rc/migrate-database-select-source.png" alt="Select the target database from the database list." >}}{{< /image >}}

{{<image filename="images/rc/migrate-database-select-source.png" alt="Select the source database from the database list." >}}{{< /image >}}
4. From the **Configuration** tab of the target database, select **Edit database**.

2. Select the **Copy** button next to the **Public endpoint** details for the source database to copy the endpoint details to the Clipboard.
{{<image filename="images/rc/migrate-data-target-edit.png" alt="Use the **Edit Database** button to change the configuration of the target database." >}}{{< /image >}}

{{<image filename="images/rc/database-public-endpoint-copy.png" alt="The Copy button copies the public endpoint details to the Clipboard." >}}{{< /image >}}
5. In the **Durability** section, enable **Active-Passive Redis** and then select **Add Source**.

3. Use the database list drop-down to select the target database.
{{<image filename="images/rc/migrate-data-active-passive-enable.png" alt="Active-Passive settings are located in the **Durability** section of the database **Configuration** tab." >}}{{< /image >}}

{{<image filename="images/rc/migrate-data-select-target-list.png" alt="Use the database list drop-down to select the target database." width="50%">}}{{< /image >}}
{{<image filename="images/rc/button-database-uri-add.png" alt="Use the **Add Source** button to specify the source of the Active-Passive replica." width="150px">}}{{< /image >}}

4. From the **Configuration** tab of the target database, select **Edit database**.
6. This will open the **Add Active-Passive Redis** screen. Select where the source database is located.

{{<image filename="images/rc/migrate-data-target-edit.png" alt="Use the **Edit Database** button to change the configuration of the target database." >}}{{< /image >}}
{{<image filename="images/rc/migrate-data-add-active-passive.png" alt="The Add Active-Passive Redis screen." >}}{{< /image >}}

5. In the **Durability** section, enable **Active-Passive Redis** and then select **Add URI**.
- Select **Current account** if the source database is located in this Redis Cloud account.

Select the source database from the **Source database** list. You can type in the database's name to find it.

{{<image filename="images/rc/migrate-data-active-passive-enable.png" alt="Active-Passive settings are located in the **Durability** section of the database **Configuration** tab." >}}{{< /image >}}
{{<image filename="images/rc/database-add-account-path-list.png" alt="Select the Source database from the database list." >}}{{< /image >}}

- If the source database is hosted externally, select **External**.

1. In the **Enter the source URI** field, type `redis://` and then paste in the public endpoint details.

{{<image filename="images/rc/migrate-data-specify-source-uri.png" alt="The source URI must be specified using the 'redis://' protocol." >}}{{< /image >}}

1. Select if the source database requires Transport Layer Security (TLS).

- If the source database requires TLS, select **TLS** and enter the public server certificate in the **Server Certificate** field.

{{<image filename="images/rc/migrate-data-tls-server-cert.png" alt="The Server Certificate field." >}}{{< /image >}}

- If the source database requires client authentication, select **Mutual TLS**.

1. Enter the public server certificate in the **Server Certificate** field.

{{<image filename="images/rc/migrate-data-tls-server-cert.png" alt="The Server Certificate field." >}}{{< /image >}}

{{<image filename="images/rc/button-database-uri-add.png" alt="Use the **Add URI** button to specify the source of the Active-Passive replica." >}}{{< /image >}}
1. Select **Download** to download the client certificate.

6. In the text box, type `redis://` and then paste in the public endpoint details.
{{<image filename="images/rc/migrate-data-tls-client-cert.png" alt="The Client Certificate field. Select Download to download the client certificate." >}}{{< /image >}}

{{<image filename="images/rc/migrate-data-specify-source-uri.png" alt="The source URI must be specified using the 'redis://' protocol." >}}{{< /image >}}
1. Configure the source database to accept the client certificate.

Select **Save** to make sure you've specified the source URI correctly.
7. Select **Save Active-Passive** to save your Active-Passive settings.

{{<image filename="images/rc/icon-database-save.png" alt="The **Save** button verifies the Source URI and you can't save until it validates." >}}{{< /image >}}
{{<image filename="images/rc/icon-database-save-active-passive.png" alt="The **Save** button verifies the Source URI and you can't save until it validates." >}}{{< /image >}}

If the endpoint cannot be verified, make sure that you've copied the details directly from the source database and that the value you entered starts with `redis://`.
For an external database, Redis will verify the endpoint at this step. If the endpoint cannot be verified, make sure that you've copied the details directly from the source database and that the value you entered starts with `redis://`.

7. Select **Save Database** to begin updating the database.
8. Select **Save Database** to begin updating the database.

{{<image filename="images/rc/button-database-save.png" alt="Use the **Save Database** button to save your changes, deploy the database, and to start data migration." >}}{{< /image >}}

Expand Down
30 changes: 2 additions & 28 deletions ...ubscriptions/create-fixed-subscription.md → ...tions/create-fixed-subscription/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,41 +18,15 @@ If you're new to Redis Cloud, the [quick start]({{<relref "/rc/rc-quickstart.md"

## Fixed plans

Fixed plan [pricing](https://redis.com/cloud/pricing/) scales according to the memory size of the database defined in the subscription. Additional limits also apply, as shown in the tables below (updated February 2024).
Fixed plan [pricing](https://redis.com/cloud/pricing/) scales according to the memory size of the database defined in the subscription. Additional limits also apply, as shown in [Fixed plan details]({{<relref "rc/subscriptions/create-fixed-subscription/fixed-plan-details">}}).

The 30 MB Fixed plan is free; it's designed for learning and building test projects. It gives you enough space to learn Redis concepts and develop application prototypes.

Our paid plans start at 250 MB and offer extra features, like high availability and backups (both daily and instant). They are great for bigger projects or production environments that require increased storage, reliability, and other features to support your operational needs.

If you need additional resources, you can [upgrade your subscription]({{<relref "/rc/subscriptions/view-fixed-subscription#upgrade-subscription-plan">}}) at any time.

There are some differences between plans for the different high availability options. See the tables for [No replication and single-zone replication](#cache-standard) and [Multi-zone replication](#multi-az) for more details.

### No replication and single-zone replication {#cache-standard}

| **DB&nbsp;size**<sup>[1](#table-note-1-cache-standard)</sup> | **30&nbsp;MB&nbsp;(Free)** | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** |
|---|---|---|---|---|---|---|
| **Concurrent<br/>connections<br/>per database** | 30 | 256 | 1024 | 2500 | 5000 | 10000 |
| **CIDR<br/> allow rules** | 1 | 4 | 4-8 | 4-8 | 4-16 | 4-32 |
| **Monthly<br/> total network<br/> bandwidth** | 5&nbsp;GB | 100&nbsp;GB | 200&nbsp;GB | 400&nbsp;GB | 800&nbsp;GB | 2000&nbsp;GB |
| **Maximum<br/> throughput<sup>[2](#table-note-2-cache-standard)</sup>** | 100&nbsp;ops/sec | 1000&nbsp;ops/sec | 2000&nbsp;ops/sec | 4000&nbsp;ops/sec | 8000&nbsp;ops/sec | 16000&nbsp;ops/sec |

1. <a name="table-note-1-cache-standard" style="display: block; height: 80px; margin-top: -80px;"></a> Database size includes replication where applicable. See [High availability cost impact]({{<relref "rc/databases/configuration/high-availability#performance-and-cost-impact">}}) for more information.

2. <a name="table-note-2-cache-standard" style="display: block; height: 80px; margin-top: -80px;"></a> Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024.

### Multi-zone replication {#multi-az}

| **DB&nbsp;size&nbsp;**<sup>[1](#table-note-1-multi-az)</sup> | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** |
|---|---|---|---|---|---|
| **Concurrent<br/>connections<br/>per database** | 256 | 1024 | 2500 | 5000 | 10000 |
| **CIDR<br/> allow rules** | 4 | 8 | 8 | 16 | 32 |
| **Monthly<br/> total network<br/> bandwidth** | 64&nbsp;GB | 200 GB | 400 GB | 800 GB | 2000 GB |
| **Maximum<br/> throughput<sup>[2](#table-note-2-multi-az)</sup>** | 1000 ops/sec | 2000 ops/sec | 4000 ops/sec | 8000 ops/sec | 16000 ops/sec |

1. <a name="table-note-1-multi-az" style="display: block; height: 80px; margin-top: -80px;"></a> Database size includes replication. See [High availability cost impact]({{<relref "rc/databases/configuration/high-availability#performance-and-cost-impact">}}) for more information.

2. <a name="table-note-2-multi-az" style="display: block; height: 80px; margin-top: -80px;"></a> Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024.
There are some differences between plans for the various high availability options. See [Fixed plan details]({{<relref "/rc/subscriptions/create-fixed-subscription/fixed-plan-details">}}) for more information.

## Create a Fixed subscription

Expand Down
38 changes: 38 additions & 0 deletions content/rc/subscriptions/create-fixed-subscription/fixed-plan-details.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
Title: Fixed plan details
description: Provides detailed information on Fixed plans
weight: $weight
alwaysopen: false
categories: ["RC"]
---

## Current Fixed plans

These plans are currently offered for all new and upgraded Fixed subscriptions (updated March 2024).

| **DB&nbsp;size**<sup>[1](#table-note-1)</sup> | **30&nbsp;MB&nbsp;(Free)** | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** |
|---|---|---|---|---|---|---|
| **Concurrent<br/>connections<br/>per database** | 30 | 256 | 1024 | 2500 | 5000 | 10000 |
| **CIDR<br/> allow rules** | 1 | 4 | 4-8 | 4-8 | 4-16 | 4-32 |
| **Monthly<br/> total network<br/> bandwidth** | 5&nbsp;GB | 100&nbsp;GB | 200&nbsp;GB | 400&nbsp;GB | 800&nbsp;GB | 2000&nbsp;GB |
| **Maximum<br/> throughput<sup>[2](#table-note-2)</sup>** | 100&nbsp;ops/sec | 1000&nbsp;ops/sec | 2000&nbsp;ops/sec | 4000&nbsp;ops/sec | 8000&nbsp;ops/sec | 16000&nbsp;ops/sec |

1. <a name="table-note-1" style="display: block; height: 80px; margin-top: -80px;"></a> Database size includes replication where applicable. See [High availability cost impact]({{<relref "rc/databases/configuration/high-availability#performance-and-cost-impact">}}) for more information.

2. <a name="table-note-2" style="display: block; height: 80px; margin-top: -80px;"></a> Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024.

## Previous plans {#legacy}

These plans were available before November 2023.

{{<table-scrollable>}}
| **Max&nbsp;DB&nbsp;size&nbsp;**<sup>[1](#table-note-1-legacy)</sup> | **30 MB** | **100 MB** | **250 MB** | **500 MB** | **1 GB** | **2.5 GB** | **5 GB** | **10 GB** |
|-----------------------------------------------------------------------------------|------------------|------------------|-------------------|-------------------|-------------------|-------------------|-------------------|--------------------|
| **Concurrent<br/>connections<br/>per database** | 30 | 256 | 256 | 512 | 1024 | 2500 | 5000 | 10000 |
| **Monthly<br/> total network<br/> bandwidth**<sup>[2](#table-note-2-legacy)</sup> | 5&nbsp;GB | 50&nbsp;GB | 100&nbsp;GB | 150&nbsp;GB | 200&nbsp;GB | 400&nbsp;GB | 800&nbsp;GB | 2000&nbsp;GB |
| **Maximum<br/> throughput** | 100&nbsp;ops/sec | 500&nbsp;ops/sec | 1000&nbsp;ops/sec | 1500&nbsp;ops/sec | 2000&nbsp;ops/sec | 4000&nbsp;ops/sec | 8000&nbsp;ops/sec | 16000&nbsp;ops/sec |
{{</table-scrollable>}}

1. <a name="table-note-1-legacy" style="display: block; height: 80px; margin-top: -80px;"></a> Database size includes replication. See [High availability cost impact]({{<relref "rc/databases/configuration/high-availability#performance-and-cost-impact">}}) for more information.

2. <a name="table-note-2-legacy" style="display: block; height: 80px; margin-top: -80px;"></a> Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024.
31 changes: 25 additions & 6 deletions content/rc/subscriptions/maintenance/_index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ categories: []
aliases:
---

Redis will maintain your Redis Cloud subscriptions and databases as needed to ensure your databases are running the most stable and up-to-date version of Redis. During maintenance, you may notice some latency when connecting to your databases.
Redis will maintain your Redis Cloud subscriptions and databases as needed to ensure your databases are running the most stable and up-to-date version of Redis.

Redis will attempt to perform maintenance during low-traffic hours when possible, based on the region where your subscription is located. If you want to control when Redis can perform maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows]({{<relref "/rc/subscriptions/maintenance/set-maintenance-windows">}}).
By default, Redis will perform maintenance automatically while limiting service disruption as much as possible. If you want to control when Redis can perform maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows]({{<relref "/rc/subscriptions/maintenance/set-maintenance-windows">}}).

## Maintenance activities

Expand All @@ -26,15 +26,34 @@ This includes, but is not limited to:
- Adding more memory to a node
- Applying security patches

Redis will notify users by email when maintenance starts and ends. If Redis needs an action from a user to start maintenance, Redis will notify users with a reasonable amount of time before planned maintenance.
Redis will notify users by email when maintenance starts and ends. For more details, see [Notifications](#notifications).

For major upgrades or upgrades that might include breaking changes, users will receive an advance notification with sufficient time to prepare before the upgrade.
During maintenance, your database will be operational, but you may notice some latency when connecting to your databases.

If you want to receive notifications by email, make sure **Operational emails** are activated in your user settings in [Access Management]({{<relref "/rc/security/access-control/access-management">}}).
Your application may also disconnect from your database for a few seconds. Most Redis clients are set to refresh their DNS address when they reconnect to the database, and you will not be required to perform any further action. If you encounter connectivity problems for more than a minute during maintenance, please refresh your DNS entries.

### Urgent maintenance

Urgent maintenance refers to any activity that could affect service and cannot wait for scheduling. This includes applying urgent security patches.

Redis can perform urgent maintenance at any time, even if you have set a manual maintenance window or have temporarily skipped maintenance. Redis will notify users by email when urgent maintenance starts and ends.
Redis can perform urgent maintenance at any time, even if you have set a manual maintenance window or have temporarily [skipped maintenance]({{<relref "/rc/subscriptions/maintenance/set-maintenance-windows#skip-maintenance-temporarily">}}). Redis will notify you by email when urgent maintenance starts and ends.

## Notifications

Redis will notify you by email when maintenance starts and ends. If Redis needs an action from you to start maintenance, Redis will notify you with a reasonable amount of time before planned maintenance.

For major upgrades or upgrades that might include breaking changes, you will receive an advance notification with sufficient time to prepare before the upgrade.

If you want to receive maintenance notifications by email:

1. Go to [Access Management]({{<relref "/rc/security/access-control/access-management">}}) and select your account in the list.

1. Select the Edit button.

{{<image filename="images/rc/icon-access-management-edit-user.png" width="30px" alt="Use the Edit button change details for a team member." >}}{{< /image >}}

1. Select **Operational emails** if it is not already turned on.

{{<image filename="images/rc/access-mgmt-edit-user-dialog.png" width="50%" alt="Use the Edit User dialog to change the details for a user" >}}{{< /image >}}

1. Select **Save user** to save your changes.
Loading

0 comments on commit 52abcca

Please sign in to comment.