From 93949730aa55e32bf090e6a6c4c6821458ff5f91 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Fri, 25 Sep 2026 11:06:42 +0100 Subject: [PATCH] DOC-7118 unit 3: convert rc databases/ to render hooks Migrate relref shortcode links and note/warning/tip/info callout shortcodes to plain Markdown links and > [!NOTE] blockquotes across content/operate/rc/databases/ (30 of 31 listed files changed; the 31st, configuration/_index.md, had nothing to convert). Hand-fixed 8 callout instances nested inside list items where the converter dropped the continuation-line indent and left a spurious trailing '>' artifact at the old closing-tag position, matching the established rs/ convention (4/8-space indent on every blockquote line, terminating ' >' line). Co-Authored-By: Claude Sonnet 5 --- content/operate/rc/databases/_index.md | 42 +++++----- .../rc/databases/active-active/_index.md | 30 ++++--- .../create-active-active-database.md | 52 ++++++------ .../databases/active-active/develop/_index.md | 4 +- .../databases/active-active/manage-regions.md | 4 +- content/operate/rc/databases/back-up-data.md | 20 +++-- .../configuration/advanced-capabilities.md | 16 ++-- .../rc/databases/configuration/clustering.md | 52 ++++++------ .../configuration/data-eviction-policies.md | 8 +- .../configuration/data-persistence.md | 7 +- .../configuration/high-availability.md | 21 +++-- .../rc/databases/configuration/sizing.md | 20 ++--- .../operate/rc/databases/connect/_index.md | 71 ++++++++-------- .../rc/databases/connect/insight-cloud.md | 17 ++-- .../rc/databases/create-database/_index.md | 14 ++-- .../create-essentials-database.md | 26 +++--- .../create-database/create-flex-database.md | 20 ++--- .../create-database/create-free-database.md | 11 ++- .../create-pro-database-existing.md | 49 ++++++------ .../create-pro-database-new.md | 60 +++++++------- .../operate/rc/databases/delete-database.md | 7 +- content/operate/rc/databases/flush-data.md | 17 ++-- content/operate/rc/databases/import-data.md | 28 +++---- .../operate/rc/databases/migrate-databases.md | 32 ++++---- .../rc/databases/monitor-performance.md | 34 ++++---- .../rc/databases/redirect-endpoints.md | 28 +++---- content/operate/rc/databases/tag-database.md | 4 +- .../rc/databases/version-management/_index.md | 22 +++-- .../version-management/upgrade-version.md | 49 ++++++------ .../rc/databases/view-edit-database.md | 80 +++++++++---------- 30 files changed, 409 insertions(+), 436 deletions(-) diff --git a/content/operate/rc/databases/_index.md b/content/operate/rc/databases/_index.md index f98e4c9b2d..c52723fa73 100644 --- a/content/operate/rc/databases/_index.md +++ b/content/operate/rc/databases/_index.md @@ -17,51 +17,51 @@ Here's how to perform a variety of tasks: ## Common database tasks -- [Create a database]({{< relref "/operate/rc/databases/create-database" >}}) +- [Create a database](/content/operate/rc/databases/create-database/_index.md) - - [Create an Essentials database]({{< relref "/operate/rc/databases/create-database/create-essentials-database" >}}) - - [Create a Pro database with a new subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) - - [Create a Pro database in an existing subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) - - [Create an Active-Active database]({{< relref "/operate/rc/databases/active-active/create-active-active-database" >}}) + - [Create an Essentials database](/content/operate/rc/databases/create-database/create-essentials-database.md) + - [Create a Pro database with a new subscription](/content/operate/rc/databases/create-database/create-pro-database-new.md) + - [Create a Pro database in an existing subscription](/content/operate/rc/databases/create-database/create-pro-database-existing.md) + - [Create an Active-Active database](/content/operate/rc/databases/active-active/create-active-active-database.md) -- [View and edit databases]({{< relref "/operate/rc/databases/view-edit-database" >}}) +- [View and edit databases](/content/operate/rc/databases/view-edit-database.md) -- [Delete database]({{< relref "/operate/rc/databases/delete-database" >}}) +- [Delete database](/content/operate/rc/databases/delete-database.md) -If you're new to Redis Cloud, see the [Quick Start]({{< relref "/operate/rc/rc-quickstart" >}}). +If you're new to Redis Cloud, see the [Quick Start](/content/operate/rc/rc-quickstart.md). ## Additional tasks -- [Monitor database performance]({{< relref "/operate/rc/databases/monitor-performance" >}}) +- [Monitor database performance](/content/operate/rc/databases/monitor-performance.md) -- [Import data into databases]({{< relref "/operate/rc/databases/import-data" >}}) +- [Import data into databases](/content/operate/rc/databases/import-data.md) -- [Back up databases]({{< relref "/operate/rc/databases/back-up-data" >}}) +- [Back up databases](/content/operate/rc/databases/back-up-data.md) -- [Secure database access]({{< relref "/operate/rc/security/database-security/" >}}) +- [Secure database access](/content/operate/rc/security/database-security/_index.md) ## Configuration details These topics provide background details that can help you tailor your databases to better fit your needs. -- [Clustering Redis databases]({{< relref "/operate/rc/databases/configuration/clustering" >}}): Redis Cloud uses clustering to manage very large databases (25 GB and larger). Learn how to manage clustering and how to use hashing policies to manage the process. +- [Clustering Redis databases](/content/operate/rc/databases/configuration/clustering.md): Redis Cloud uses clustering to manage very large databases (25 GB and larger). Learn how to manage clustering and how to use hashing policies to manage the process. -- [Data eviction policies]({{< relref "/operate/rc/databases/configuration/data-eviction-policies" >}}): Data eviction policies control what happens when new data exceeds the memory limits of a database. Learn the available policies and how to control them. +- [Data eviction policies](/content/operate/rc/databases/configuration/data-eviction-policies.md): Data eviction policies control what happens when new data exceeds the memory limits of a database. Learn the available policies and how to control them. -- [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}): Data persistence enables recovery in the event of memory loss or other catastrophic failure. Learn which options are available and how to apply specific settings to individual databases. +- [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md): Data persistence enables recovery in the event of memory loss or other catastrophic failure. Learn which options are available and how to apply specific settings to individual databases. -- [High availability and replication]({{< relref "/operate/rc/databases/configuration/high-availability" >}}): Replication allows for automatic failover and greater fault tolerance. It can prevent data loss in the event of a hardware or zone failure. Learn which options are available for Redis Cloud subscriptions. +- [High availability and replication](/content/operate/rc/databases/configuration/high-availability.md): Replication allows for automatic failover and greater fault tolerance. It can prevent data loss in the event of a hardware or zone failure. Learn which options are available for Redis Cloud subscriptions. -- [Advanced Capabilities]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}): Advanced capabilities extend Redis database functionality by adding new data types and options. Learn about the advanced capability options that are available for your database. +- [Advanced Capabilities](/content/operate/rc/databases/configuration/advanced-capabilities.md): Advanced capabilities extend Redis database functionality by adding new data types and options. Learn about the advanced capability options that are available for your database. ## Compatibility -Redis Cloud does not support certain commands. Instead of using these commands, Redis Cloud automatically handles features like replication and lets you [manage your database]({{< relref "/operate/rc/databases" >}}) from the [Redis Cloud console](https://cloud.redis.io/) or [Redis Cloud REST API]({{< relref "/operate/rc/api" >}}). +Redis Cloud does not support certain commands. Instead of using these commands, Redis Cloud automatically handles features like replication and lets you [manage your database](/content/operate/rc/databases/_index.md) from the [Redis Cloud console](https://cloud.redis.io/) or [Redis Cloud REST API](/content/operate/rc/api/_index.md). For more details, see: -- [Redis Cloud compatibility]({{< relref "/operate/rc/compatibility" >}}) +- [Redis Cloud compatibility](/content/operate/rc/compatibility.md) -- [Command compatibility]({{< relref "/operate/rs/references/compatibility/commands" >}}) +- [Command compatibility](/content/operate/rs/references/compatibility/commands/_index.md) -- [Configuration compatibility]({{< relref "/operate/rs/references/compatibility/config-settings" >}}) +- [Configuration compatibility](/content/operate/rs/references/compatibility/config-settings.md) diff --git a/content/operate/rc/databases/active-active/_index.md b/content/operate/rc/databases/active-active/_index.md index 312ee5032d..bc9a94f0a2 100644 --- a/content/operate/rc/databases/active-active/_index.md +++ b/content/operate/rc/databases/active-active/_index.md @@ -15,19 +15,18 @@ aliases: Active-Active databases store data across multiple regions and availability zones. This improves scalability, performance, and availability, especially when compared to standalone databases. -To create Active-Active databases, you need a Redis Cloud Pro subscription that enables Active-Active Redis and defines the regions for each copy of your databases. See [Create an Active-Active database]({{< relref "/operate/rc/databases/active-active/create-active-active-database" >}}) for instructions. +To create Active-Active databases, you need a Redis Cloud Pro subscription that enables Active-Active Redis and defines the regions for each copy of your databases. See [Create an Active-Active database](/content/operate/rc/databases/active-active/create-active-active-database.md) for instructions. Active-Active databases are distributed across multiple regions (geo-distribution). This improves performance by reducing latency for nearby users and improves availability by protecting against data loss in case of network or resource failure. -Active-Active databases allow read and write operations in each copy. Each copy eventually reflects changes made in other copies ([eventual consistency]({{< relref "/glossary#eventual-consistency" >}})). Conflict-free replicated data types (CRDTs) synchronize read and write operations between copies. CRDTs ensure consistency and resolve conflicts. +Active-Active databases allow read and write operations in each copy. Each copy eventually reflects changes made in other copies ([eventual consistency](/content/glossary/_index.md#eventual-consistency)). Conflict-free replicated data types (CRDTs) synchronize read and write operations between copies. CRDTs ensure consistency and resolve conflicts. -Active-Active databases use TLS to synchronize data between regions. You can also use TLS to encrypt client connections. See [Transport Layer Security (TLS)]({{< relref "/operate/rc/security/database-security/tls-ssl.md" >}}) for more information. +Active-Active databases use TLS to synchronize data between regions. You can also use TLS to encrypt client connections. See [Transport Layer Security (TLS)](/content/operate/rc/security/database-security/tls-ssl.md) for more information. -When developing for Active-Active databases, you need to consider some important differences. See [Develop applications with Active-Active databases]({{< relref "/operate/rc/databases/active-active/develop/_index.md" >}}) for related information. +When developing for Active-Active databases, you need to consider some important differences. See [Develop applications with Active-Active databases](/content/operate/rc/databases/active-active/develop/_index.md) for related information. -{{< note >}} -Active-Active subscriptions on Redis Cloud are limited to a maximum of 10 regions and 10 databases. -{{< /note >}} +> [!NOTE] +> Active-Active subscriptions on Redis Cloud are limited to a maximum of 10 regions and 10 databases. ## Active-Active geo-distributed replication highlights @@ -42,9 +41,8 @@ The availability of each region depends on the number of availability zones it p An Active-Active database can combine regions with different availability zone counts. When it does, the availability of the entire deployment is determined by the least resilient region. For example, an Active-Active database that spans a region with three availability zones and a region with fewer than three availability zones provides 99.99% (four-nines) availability overall. -{{< note >}} -Regions with fewer than three availability zones are not available when you create an Active-Active database in the Redis Cloud console. To create an Active-Active database that includes one of these regions, use the [Redis Cloud REST API]({{< relref "/operate/rc/api" >}}). You'll be able to manage these databases using the Redis Cloud console after they're created. -{{< /note >}} +> [!NOTE] +> Regions with fewer than three availability zones are not available when you create an Active-Active database in the Redis Cloud console. To create an Active-Active database that includes one of these regions, use the [Redis Cloud REST API](/content/operate/rc/api/_index.md). You'll be able to manage these databases using the Redis Cloud console after they're created. ### Local latency with unique endpoints @@ -60,15 +58,15 @@ After a failure at the process, node, or zone level, Active-Active databases aut However, Active-Active databases do not have a built-in [failover](https://en.wikipedia.org/wiki/Failover) or failback mechanism for application connections. To handle cluster-level failures, you should implement one of the following disaster recovery strategies to redirect traffic between regions: -- [Network-based]({{}}): Global traffic managers and load balancers for routing. +- [Network-based](/content/operate/rs/databases/active-active/disaster-recovery/network-based.md): Global traffic managers and load balancers for routing. -- [Proxy-based]({{}}): Software proxies handle detection and routing logic. +- [Proxy-based](/content/operate/rs/databases/active-active/disaster-recovery/proxy-based.md): Software proxies handle detection and routing logic. -- [Client library-based]({{}}): Database client libraries with built-in failover logic. +- [Client library-based](/content/operate/rs/databases/active-active/disaster-recovery/client-library-based.md): Database client libraries with built-in failover logic. -- [Application-based]({{}}): Custom application-level monitoring and connectivity management. +- [Application-based](/operate/rc/databases/active-active/develop/app-failover-active-active): Custom application-level monitoring and connectivity management. -For more information and guidance on which disaster recovery strategy to implement, see [Disaster recovery strategies for Active-Active databases]({{< relref "/operate/rs/databases/active-active/disaster-recovery" >}}). +For more information and guidance on which disaster recovery strategy to implement, see [Disaster recovery strategies for Active-Active databases](/content/operate/rs/databases/active-active/disaster-recovery/_index.md). Data automatically syncs to a recovered cluster when it returns to a healthy state. @@ -78,4 +76,4 @@ Active-Active databases consume more memory than standalone databases. Because A Active-Active databases also begin evicting keys earlier than standalone databases, at 80% of an instance's memory limit, and reserve additional memory for replication backlogs. Account for these factors when you size your database. -For more information, see [Memory limits and sizing]({{< relref "/operate/rc/databases/configuration/sizing#dataset-size" >}}). +For more information, see [Memory limits and sizing](/content/operate/rc/databases/configuration/sizing.md#dataset-size). diff --git a/content/operate/rc/databases/active-active/create-active-active-database.md b/content/operate/rc/databases/active-active/create-active-active-database.md index c1462c8386..bb9699b61c 100644 --- a/content/operate/rc/databases/active-active/create-active-active-database.md +++ b/content/operate/rc/databases/active-active/create-active-active-database.md @@ -13,7 +13,7 @@ aliases: - /operate/rc/databases/create-database/create-active-active-database --- -Active-Active databases store data across multiple regions and availability zones. This improves scalability, performance, and availability, especially when compared to standalone databases. See [Active-Active Redis]({{< relref "/operate/rc/databases/active-active" >}}) for more information. +Active-Active databases store data across multiple regions and availability zones. This improves scalability, performance, and availability, especially when compared to standalone databases. See [Active-Active Redis](/content/operate/rc/databases/active-active/_index.md) for more information. To deploy Active-Active databases in Redis Cloud, you need a Redis Cloud Pro plan that enables Active-Active Redis and defines the regions for each copy of your databases. @@ -27,13 +27,13 @@ Redis Cloud maintains consistency among instances in the background; that is, ea {{< embed-md "rc-create-db-first-steps.md" >}} -3. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Pro**. +3. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Pro**. {{The Subscription selection panel with Pro selected.}} - {{< note >}} -This guide shows how to create an Active-Active database with a new Pro subscription. If you already have an Active-Active subscription and want to add a database to it, see [Create a Pro database in an existing subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}). Active-Active subscriptions can host a maximum of 10 databases. - {{< /note >}} + > [!NOTE] + > This guide shows how to create an Active-Active database with a new Pro subscription. If you already have an Active-Active subscription and want to add a database to it, see [Create a Pro database in an existing subscription](/content/operate/rc/databases/create-database/create-pro-database-existing.md). Active-Active subscriptions can host a maximum of 10 databases. + > After you select **Pro**, the **Database settings** section will appear. @@ -71,9 +71,8 @@ When you enable Active-Active Redis, two regions are selected by default. Select {{Use the Region drop-down to select the regions for your Active-Active database.}} -{{< note >}} -Active-Active subscriptions on Redis Cloud are limited to a maximum of 10 regions. -{{< /note >}} +> [!NOTE] +> Active-Active subscriptions on Redis Cloud are limited to a maximum of 10 regions. Use the checkboxes in the list to select or remove regions. The Search box lets you locate specific regions. @@ -87,21 +86,20 @@ You can use a region's Remove button to remove it from the list. In the **Advanced options** section, you can: -- Choose to deploy your Active-Active database to an existing Cloud Account, if [Redis Cloud Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) is enabled. +- Choose to deploy your Active-Active database to an existing Cloud Account, if [Redis Cloud Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) is enabled. - Define CIDR addresses for each region in the **VPC configuration** section. {{< embed-md "rc-aa-cidr.md" >}} - If you chose to deploy your Active-Active database to an existing [Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) account, you can also define the VPC ID for each region. Select **In existing VPC** and the set the VPC ID for each selected region. + If you chose to deploy your Active-Active database to an existing [Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) account, you can also define the VPC ID for each region. Select **In existing VPC** and the set the VPC ID for each selected region. -- Set your [maintenance]({{< relref "/operate/rc/subscriptions/maintenance" >}}) settings in the **Maintenance windows** section. Select **Manual** if you want to set [manual maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). +- Set your [maintenance](/content/operate/rc/subscriptions/maintenance/_index.md) settings in the **Maintenance windows** section. Select **Manual** if you want to set [manual maintenance windows](/content/operate/rc/subscriptions/maintenance/set-maintenance-windows.md). -{{< note >}} -Multi-AZ replication is required for all Active-Active databases. - -Regions with fewer than three availability zones are not available in the Redis Cloud console. To create an Active-Active database that includes one of these regions, use the REST API to [create a Pro subscription]({{< relref "/operate/rc/api/examples/manage-subscriptions#create-a-pro-subscription" >}}). You'll be able to manage these subscriptions and databases using the Redis Cloud console after they're created. Active-Active databases in these regions use single-zone replication and provide 99.99% (four-nines) availability instead of 99.999%. For more information, see [Active-Active Redis]({{< relref "/operate/rc/databases/active-active#multi-zone" >}}). -{{< /note >}} +> [!NOTE] +> Multi-AZ replication is required for all Active-Active databases. +> +> Regions with fewer than three availability zones are not available in the Redis Cloud console. To create an Active-Active database that includes one of these regions, use the REST API to [create a Pro subscription](/content/operate/rc/api/examples/manage-subscriptions.md#create-a-pro-subscription). You'll be able to manage these subscriptions and databases using the Redis Cloud console after they're created. Active-Active databases in these regions use single-zone replication and provide 99.99% (four-nines) availability instead of 99.999%. For more information, see [Active-Active Redis](/content/operate/rc/databases/active-active/_index.md#multi-zone). When finished, choose **Continue** to determine your size requirements. @@ -125,7 +123,7 @@ By default, you're shown basic settings, which include: - **Name**: A custom name for your database. - **Version**: The Redis version for your database. We recommend you choose the latest available version. -- **Advanced Capabilities**: Advanced data types or features used by the database. Active-Active databases support the [JSON]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}) data type and [Search and query]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search" >}}) features. +- **Advanced Capabilities**: Advanced data types or features used by the database. Active-Active databases support the [JSON](/content/operate/oss_and_stack/stack-with-enterprise/json/_index.md) data type and [Search and query](/content/operate/oss_and_stack/stack-with-enterprise/search/_index.md) features. {{When you create an Active-Active database, you can select the JSON and Search and query advanced capabilities.}} @@ -133,13 +131,13 @@ By default, you're shown basic settings, which include: Starting with Redis 8.0, JSON and Search and query are included by default. - See [Search and query Active-Active databases]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search/search-active-active" >}}) to learn how to use Search and query on Active-Active databases. + See [Search and query Active-Active databases](/content/operate/oss_and_stack/stack-with-enterprise/search/search-active-active.md) to learn how to use Search and query on Active-Active databases. - **Dataset size**: The amount of data needed for your dataset in GB. For Search and query databases, use the [Sizing calculator](https://redis.io/redisearch-sizing-calculator/) to estimate your index size and throughput requirements. When you're entering the dataset size for your database, add the estimated index size from the Sizing calculator to your expected dataset size. -- **Hashing policy**: Determines how data is distributed across multiple Redis processes of a database. Available options depend on your account creation date. See [Clustering]({{< relref "/operate/rc/databases/configuration/clustering#manage-the-hashing-policy" >}}) for more information. +- **Hashing policy**: Determines how data is distributed across multiple Redis processes of a database. Available options depend on your account creation date. See [Clustering](/content/operate/rc/databases/configuration/clustering.md#manage-the-hashing-policy) for more information. - **Throughput**: When you create an Active-Active database, you define the throughput for each instance. The total operations per second combines the total read ops/sec and applies the write ops/sec for each region across every region. @@ -278,8 +276,8 @@ Total ops/sec = 9000 (Region 1) + 10000 (Region 2) + 7000 (Region 3) For Search and query databases, the estimated throughput from the [Sizing calculator](https://redis.io/redisearch-sizing-calculator/) is the total amount of throughput you need. When setting throughput for your Active-Active database, use the total amount for each region and divide it depending on your read (query) and write (update) needs for each region. For example, if the total amount of throughput needed is 50000 ops/sec, you could set each region to have 20000 ops/sec for reads (queries) and 30000 ops/sec for writes (updates). -- **Data Persistence**: Defines the data persistence policy, if any. See [Database persistence]({{< relref "/operate/rs/databases/configure/database-persistence.md" >}}). -- **Supported Protocol(s)**: Choose between RESP2 and RESP3 _(Redis 7.2 or later)_. See [Redis serialization protocol]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) for details. +- **Data Persistence**: Defines the data persistence policy, if any. See [Database persistence](/content/operate/rs/databases/configure/database-persistence.md). +- **Supported Protocol(s)**: Choose between RESP2 and RESP3 _(Redis 7.2 or later)_. See [Redis serialization protocol](/content/develop/reference/protocol-spec.md#resp-versions) for details. - **Quantity**: Number of databases to create with these settings. When finished, select **Save configuration** to save your database configuration. @@ -299,7 +297,7 @@ The **Review and Create** tab provides a cost estimate for your Redis Cloud Pro {{The Review & Create tab of the New Active-Active subscription screen.}} -Redis breaks down your databases to Redis Billing Units (RBUs), each with their own size and throughput requirements. For more info, see [Billing unit types]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}#billing-unit-types). +Redis breaks down your databases to Redis Billing Units (RBUs), each with their own size and throughput requirements. For more info, see [Billing unit types](/content/operate/rc/databases/create-database/create-pro-database-new.md#billing-unit-types). The **Payment methods** section of this tab shows which payment method you're using for this database. Select the arrow on the top right of this section to view all available payment methods. @@ -319,10 +317,10 @@ Use the **Database list** to check the status of your databases. ## More info -- [Create a Pro database with a new subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) -- [Active-Active Redis]({{< relref "/operate/rc/databases/active-active" >}}) -- [Develop applications with Active-Active databases]({{< relref "/operate/rc/databases/active-active/develop/_index.md" >}}) -- Database [memory limit]({{< relref "/operate/rc/databases/configuration/sizing#dataset-size" >}}) -- Redis Cloud [subscription plans]({{< relref "/operate/rc/subscriptions/" >}}) +- [Create a Pro database with a new subscription](/content/operate/rc/databases/create-database/create-pro-database-new.md) +- [Active-Active Redis](/content/operate/rc/databases/active-active/_index.md) +- [Develop applications with Active-Active databases](/content/operate/rc/databases/active-active/develop/_index.md) +- Database [memory limit](/content/operate/rc/databases/configuration/sizing.md#dataset-size) +- Redis Cloud [subscription plans](/content/operate/rc/subscriptions/_index.md) - [Redis Cloud pricing](https://redis.io/pricing/#monthly) diff --git a/content/operate/rc/databases/active-active/develop/_index.md b/content/operate/rc/databases/active-active/develop/_index.md index 4bd99e15a7..b2ee1addd6 100644 --- a/content/operate/rc/databases/active-active/develop/_index.md +++ b/content/operate/rc/databases/active-active/develop/_index.md @@ -41,7 +41,7 @@ cross-region writes to the same data. Active-Active databases replicate data between multiple Redis Cloud provider regions. Common uses for Active-Active databases include disaster recovery, geographically redundant applications, and keeping data closer to your users' locations. MMR is always multi-directional amongst the regions -configured in the Active-Active database. For unidirectional replication, see [Active-Passive replication]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}). +configured in the Active-Active database. For unidirectional replication, see [Active-Passive replication](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive). ## Example of synchronization @@ -49,4 +49,4 @@ configured in the Active-Active database. For unidirectional replication, see [A [Learn more about synchronization for -each supported data type]({{< relref "/operate/rc/databases/active-active/develop/data-types/" >}}) and [how to develop applications]({{< relref "/operate/rc/databases/active-active/develop/develop-for-aa" >}}) with them on Redis Cloud. \ No newline at end of file +each supported data type](/operate/rc/databases/active-active/develop/data-types/) and [how to develop applications](/operate/rc/databases/active-active/develop/develop-for-aa) with them on Redis Cloud. \ No newline at end of file diff --git a/content/operate/rc/databases/active-active/manage-regions.md b/content/operate/rc/databases/active-active/manage-regions.md index 76704d82f6..42d9c6b4bb 100644 --- a/content/operate/rc/databases/active-active/manage-regions.md +++ b/content/operate/rc/databases/active-active/manage-regions.md @@ -10,7 +10,7 @@ linkTitle: Manage regions weight: 10 --- -You can add and edit regions for an Active-Active deployment after it has been created by going to the **Regions** tab of the [subscription page]({{< relref "/operate/rc/subscriptions/view-pro-subscription" >}}). +You can add and edit regions for an Active-Active deployment after it has been created by going to the **Regions** tab of the [subscription page](/content/operate/rc/subscriptions/view-pro-subscription.md). {{The Regions tab lets you manage the regions in your Active-Active subscription.}} @@ -28,7 +28,7 @@ To add a new region to an Active-Active deployment: 1. Select the desired region from the **Region** list. - 1. If you chose to deploy your Active-Active database to an existing [Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) account, you can define the VPC ID for the new region. Select **In existing VPC** and the set the VPC ID for the region. + 1. If you chose to deploy your Active-Active database to an existing [Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) account, you can define the VPC ID for the new region. Select **In existing VPC** and the set the VPC ID for the region. 1. Enter a unique CIDR address for the region. diff --git a/content/operate/rc/databases/back-up-data.md b/content/operate/rc/databases/back-up-data.md index eec1569681..18978fe8d1 100644 --- a/content/operate/rc/databases/back-up-data.md +++ b/content/operate/rc/databases/back-up-data.md @@ -20,13 +20,12 @@ The backup options for Redis Cloud databases depend on your plan: - Free plans cannot back up or export a database through the Redis Cloud console. -{{}} -The number of database backups that can run simultaneously on a subscription is limited to 4 by default. -{{}} +> [!NOTE] +> The number of database backups that can run simultaneously on a subscription is limited to 4 by default. Backups are saved to predefined storage locations available to your subscription. Backup locations need to be available before you turn on database backups. To learn more, see [Set up backup storage locations](#set-up-backup-storage-locations). -Backups are saved in RDB format. If the database is comprised of multiple shards, an RDB file will be created for each shard of the database. For more information on restoring data from a backup, see [Restore from an RDB file]({{< relref "/operate/rc/databases/import-data#restore-from-an-rdb-file" >}}). +Backups are saved in RDB format. If the database is comprised of multiple shards, an RDB file will be created for each shard of the database. For more information on restoring data from a backup, see [Restore from an RDB file](/content/operate/rc/databases/import-data.md#restore-from-an-rdb-file). Here, you'll learn how to store backups using different cloud providers. @@ -51,7 +50,7 @@ When you enable **Remote backup**, additional options appear. The options vary | **Interval** | Defines the frequency of automatic backups. Paid Redis Cloud Essentials databases are backed up every 24 hours. Redis Cloud Pro databases can be set to 24, 12, 6, 4, 2, or 1 hour backup intervals. | | **Set backup time** | When checked, this lets you set the hour of the **Backup time**. (_Redis Cloud Pro only_) | | **Backup time** | Defines the hour automatic backups are made. Note that actual backup times will vary up in order to minimize customer access disruptions. (_Redis Cloud Pro only_)
Times are expressed in [Coordinated Universal Time](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) (UTC).| -| **Storage type** | Defines the provider of the storage location, which can be: `AWS S3`, `Google Cloud Storage`, `Azure Blob Storage`, `FTP` (FTPS), or `Redis-managed repo`. `Redis-managed repo` is only available for databases created through the [Heroku]({{< relref "/operate/rc/cloud-integrations/heroku" >}}) or [Vercel]({{< relref "/operate/rc/cloud-integrations/vercel" >}}) integrations. | +| **Storage type** | Defines the provider of the storage location, which can be: `AWS S3`, `Google Cloud Storage`, `Azure Blob Storage`, `FTP` (FTPS), or `Redis-managed repo`. `Redis-managed repo` is only available for databases created through the [Heroku](/content/operate/rc/cloud-integrations/heroku.md) or [Vercel](/content/operate/rc/cloud-integrations/vercel.md) integrations. | | **Backup destination** | Defines a URI representing the backup storage location. | ## Back up and export data on demand @@ -156,9 +155,8 @@ Once the bucket is available and the permissions are set, use the name of your b To learn more, see [Using bucket policies](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-policies.html) on the AWS docs. -{{< note >}} -An AWS S3 bucket can be used by only one Redis Cloud account. If you have more than one Redis Cloud account, repeat the setup steps for multiple buckets. -{{< /note >}} +> [!NOTE] +> An AWS S3 bucket can be used by only one Redis Cloud account. If you have more than one Redis Cloud account, repeat the setup steps for multiple buckets. -tab-sep- @@ -232,9 +230,9 @@ Where: - *port*: the port number of the server, if needed. - *path*: the backup path, if needed. - {{< note >}} -If your FTP username or password contains special characters such as `@`, `\`, or `:`, you must URL encode (also known as Percent encode) these special characters. If you don't, your database may become stuck. - {{< /note >}} + > [!NOTE] + > If your FTP username or password contains special characters such as `@`, `\`, or `:`, you must URL encode (also known as Percent encode) these special characters. If you don't, your database may become stuck. + > The user account needs permission to write files to the server. diff --git a/content/operate/rc/databases/configuration/advanced-capabilities.md b/content/operate/rc/databases/configuration/advanced-capabilities.md index 24c7c8861d..f8e5c11f72 100644 --- a/content/operate/rc/databases/configuration/advanced-capabilities.md +++ b/content/operate/rc/databases/configuration/advanced-capabilities.md @@ -18,7 +18,7 @@ Available options depend on your database plan and **Type**. ## Redis Cloud Essentials {#essentials} -All Redis Cloud Essentials databases with versions prior to Redis 8.0 support [Redis Stack]({{< relref "/operate/oss_and_stack/" >}}), which enables the most frequently used capabilities. +All Redis Cloud Essentials databases with versions prior to Redis 8.0 support [Redis Stack](/content/operate/oss_and_stack/_index.md), which enables the most frequently used capabilities. {{For Essentials, the Type setting in the General section includes an option for Redis.}} @@ -28,11 +28,11 @@ When the database **Type** is set to _Redis_, the Advanced capabilities section Starting with Redis 8.0, all advanced capabilities provided by Redis Stack are included in Redis by default. -Redis Cloud is updated on a regular basis, which includes the advanced capabilities supported by the service. Versions displayed by the Redis Cloud console may vary from those shown above. For the latest details of any capability, see [Redis Stack and Redis Software]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}}). For more information about Redis Cloud version management, see [Redis version management]({{< relref "/operate/rc/databases/version-management" >}}). +Redis Cloud is updated on a regular basis, which includes the advanced capabilities supported by the service. Versions displayed by the Redis Cloud console may vary from those shown above. For the latest details of any capability, see [Redis Stack and Redis Software](/content/operate/oss_and_stack/stack-with-enterprise/_index.md). For more information about Redis Cloud version management, see [Redis version management](/content/operate/rc/databases/version-management/_index.md). ## Redis Cloud Pro {#pro} -By default, Redis Cloud Pro databases load all supported advanced capabilities. For versions prior to Redis 8.0, you can choose to load specific capabilities when you create your database. To choose which capabilities to load for your Pro database, [create it with custom settings]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) and select **More options** when adding your database in the **Sizing tab** to view advanced capability settings. +By default, Redis Cloud Pro databases load all supported advanced capabilities. For versions prior to Redis 8.0, you can choose to load specific capabilities when you create your database. To choose which capabilities to load for your Pro database, [create it with custom settings](/content/operate/rc/databases/create-database/create-pro-database-new.md) and select **More options** when adding your database in the **Sizing tab** to view advanced capability settings. {{For Pro databases, you can select the capabilities included in your database.}} @@ -45,17 +45,17 @@ You can select more than one advanced capability for a database, though there ar - Time series - Probabilistic -- [Active-Active databases]({{< relref "/operate/rc/databases/active-active/create-active-active-database" >}}) only support JSON and Search and query. +- [Active-Active databases](/content/operate/rc/databases/active-active/create-active-active-database.md) only support JSON and Search and query. To remove a selected capability, clear its checkbox. Starting with Redis 8.0, all advanced capabilities provided by Redis Stack are included in Redis by default. -To learn more, see [Redis Stack]({{< relref "/develop/get-started/" >}}) and [Redis Stack and Redis Software]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}}). For more information about Redis Cloud version management, see [Redis version management]({{< relref "/operate/rc/databases/version-management" >}}). +To learn more, see [Redis Stack](/content/develop/get-started/_index.md) and [Redis Stack and Redis Software](/content/operate/oss_and_stack/stack-with-enterprise/_index.md). For more information about Redis Cloud version management, see [Redis version management](/content/operate/rc/databases/version-management/_index.md). ### Search and query sizing -When you create a Pro database with [Search and Query]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search" >}}), you must consider the sizing and throughput requirements for search and query when you define the dataset size and throughput for your database. +When you create a Pro database with [Search and Query](/content/operate/oss_and_stack/stack-with-enterprise/search/_index.md), you must consider the sizing and throughput requirements for search and query when you define the dataset size and throughput for your database. Use the [Search and query sizing calculator](https://redis.io/redisearch-sizing-calculator/) to estimate your index size and throughput requirements. @@ -69,8 +69,8 @@ The query performance factor adds extra compute power specifically for search an {{For Pro databases, you can select the query performance factor for your database.}} -We recommend testing your application with a test database to see your baseline queries per second and determine how much you want to boost your query performance. After you have determined your queries per second and your desired performance factor, [create a new database]({{< relref "/operate/rc/databases/create-database" >}}) with the desired performance factor and [migrate data]({{< relref "/operate/rc/databases/migrate-databases" >}}) from the test database to your new database. +We recommend testing your application with a test database to see your baseline queries per second and determine how much you want to boost your query performance. After you have determined your queries per second and your desired performance factor, [create a new database](/content/operate/rc/databases/create-database/_index.md) with the desired performance factor and [migrate data](/content/operate/rc/databases/migrate-databases.md) from the test database to your new database. -For more info on how to use scalable search, see [Best practices for scalable Redis Search]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search/scalable-query-best-practices" >}}). +For more info on how to use scalable search, see [Best practices for scalable Redis Search](/content/operate/oss_and_stack/stack-with-enterprise/search/scalable-query-best-practices.md). The query performance factor is available for Redis Cloud Pro databases on Redis 7.2 and later. \ No newline at end of file diff --git a/content/operate/rc/databases/configuration/clustering.md b/content/operate/rc/databases/configuration/clustering.md index 0a48b2fb9c..b7c89ae2cc 100644 --- a/content/operate/rc/databases/configuration/clustering.md +++ b/content/operate/rc/databases/configuration/clustering.md @@ -79,7 +79,7 @@ are supported, with the following limitations: and pipelining are supported with Redis Cloud cluster as if it were a non-cluster DB. - [Active-Active databases]({{< relref "/operate/rc/databases/active-active" >}}) have stricter rules: multi-key write commands (DEL, MSET, UNLINK) can only run on keys in the same slot. Only MGET, EXISTS, and TOUCH are allowed across slots. See [Multi-key operations on Active-Active databases]({{< relref "/develop/using-commands/multi-key-operations#active-active-databases" >}}) for details. + [Active-Active databases](/content/operate/rc/databases/active-active/_index.md) have stricter rules: multi-key write commands (DEL, MSET, UNLINK) can only run on keys in the same slot. Only MGET, EXISTS, and TOUCH are allowed across slots. See [Multi-key operations on Active-Active databases](/content/develop/using-commands/multi-key-operations.md#active-active-databases) for details. ## Hashing policies and hash tags {#manage-the-hashing-policy} @@ -97,7 +97,7 @@ Redis Cloud defaults to the [Redis hashing policy](#redis-hashing-policy) **when ### Redis hashing policy -The Redis hashing policy is identical to the [hashing policy used by Redis Open Source]({{< relref "/operate/oss_and_stack/reference/cluster-spec#hash-tags" >}}). This policy is recommended for most users and you should select it if any of the following conditions apply: +The Redis hashing policy is identical to the [hashing policy used by Redis Open Source](/content/operate/oss_and_stack/reference/cluster-spec.md#hash-tags). This policy is recommended for most users and you should select it if any of the following conditions apply: - This is your first Redis Cloud account, and you are starting fresh. - You are migrating data from Redis Open Source or other Redis-managed platforms. - Your application does not use hashtags in database key names. @@ -121,19 +121,17 @@ In some cases, the Standard hashing policy behaves differently from the Redis ha - Standard hashing policy: substrings "foo}bar" and "foo}qux" will be used for the 1st and 2nd key respectively, hashed each key to a different hash-slot. - Redis hashing policy: the substring "foo" will be used for both keys, hashing them to the same slot. -{{< note >}} -To allow seamless transition between hashing policies, the following techniques are not recommended: -- Using empty hashtags to hash different keys to the same hashslot -- Using multiple curly brackets within a key’s name -{{< /note >}} +> [!NOTE] +> To allow seamless transition between hashing policies, the following techniques are not recommended: +> - Using empty hashtags to hash different keys to the same hashslot +> - Using multiple curly brackets within a key’s name ### Custom hashing policy -{{< note >}} -The custom hashing policy is not available for accounts created after March 31, 2025. - -For all other accounts, this policy is not recommended and will be deprecated in the future. Select this option only if you are already using a custom hashing policy with your existing Redis Cloud databases. -{{< /note >}} +> [!NOTE] +> The custom hashing policy is not available for accounts created after March 31, 2025. +> +> For all other accounts, this policy is not recommended and will be deprecated in the future. Select this option only if you are already using a custom hashing policy with your existing Redis Cloud databases. A Redis Cloud cluster can be configured to use a custom hashing policy. A custom hashing policy is required when different keys need to @@ -159,18 +157,17 @@ default RegEx rules that implement the standard hashing policy are: You can modify existing rules, add new ones, delete rules, or change their order to suit your application's requirements. -{{< warning >}} -If the Custom hashing policy is available, you can change the hashing policy between Standard and Custom after you create your database. However, hashing policy changes delete existing data -(using [`FLUSHDB`]({{< relref "/commands/flushdb" >}})) before they're applied. - -These changes include: - -1. Changing the hashing policy, either from standard to custom or vice versa. -1. Changing the order of custom hashing policy rules. -1. Adding rules before existing ones in the custom hashing policy. -1. Deleting rules from the custom hashing policy. -1. Disabling clustering for the database. -{{< /warning >}} +> [!WARNING] +> If the Custom hashing policy is available, you can change the hashing policy between Standard and Custom after you create your database. However, hashing policy changes delete existing data +> (using [`FLUSHDB`](/content/commands/flushdb.md)) before they're applied. +> +> These changes include: +> +> 1. Changing the hashing policy, either from standard to custom or vice versa. +> 1. Changing the order of custom hashing policy rules. +> 1. Adding rules before existing ones in the custom hashing policy. +> 1. Deleting rules from the custom hashing policy. +> 1. Disabling clustering for the database. ### Custom hashing policy notes and limitations @@ -197,15 +194,14 @@ After you select OSS Cluster API, you can select **Use external endpoint** if yo The OSS Cluster API is supported when a database uses the [standard hashing policy](#standard-hashing-policy) or the [Redis hashing policy](#redis-hashing-policy). -Review [OSS Cluster API architecture]({{< relref "/operate/rs/clusters/optimize/oss-cluster-api" >}}) to determine if you should enable this feature for your database. +Review [OSS Cluster API architecture](/content/operate/rs/clusters/optimize/oss-cluster-api.md) to determine if you should enable this feature for your database. ## Smooth scaling {#smooth-scaling} Smooth scaling is an improved resharding method for Redis Cloud Pro databases. Compared to traditional resharding, it is significantly faster and reduces latency spikes and disconnects during scaling. -{{< note >}} -Smooth scaling is available for databases that meet the following prerequisites. Other databases continue to use traditional scaling. -{{< /note >}} +> [!NOTE] +> Smooth scaling is available for databases that meet the following prerequisites. Other databases continue to use traditional scaling. ### Prerequisites diff --git a/content/operate/rc/databases/configuration/data-eviction-policies.md b/content/operate/rc/databases/configuration/data-eviction-policies.md index 6a0053adad..8e93ad9d37 100644 --- a/content/operate/rc/databases/configuration/data-eviction-policies.md +++ b/content/operate/rc/databases/configuration/data-eviction-policies.md @@ -16,7 +16,7 @@ aliases: The data eviction policy of a database controls what happens when new data exceeds the memory size of a database. Typically, such situations require _evicting_ (or deleting) data previously added to the database. -You can [edit database details]({{< relref "/operate/rc/databases/view-edit-database.md" >}}) to change the **Data eviction policy** setting at the database level. +You can [edit database details](/content/operate/rc/databases/view-edit-database.md) to change the **Data eviction policy** setting at the database level. ## Available policies @@ -37,14 +37,14 @@ For each database, you can choose from these data eviction policies: To avoid data eviction, make sure your database is large enough to hold required values. -Redis Cloud supports [Auto Tiering]({{< relref "/operate/rs/databases/flash/" >}}) on Redis Cloud Pro and [Redis Flex]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}) on Redis Cloud Essentials +Redis Cloud supports [Auto Tiering](/content/operate/rs/databases/flash/_index.md) on Redis Cloud Pro and [Redis Flex](/content/operate/rc/databases/create-database/create-flex-database.md) on Redis Cloud Essentials to prevent data eviction but maintain high performance. Auto Tiering and Redis Flex can extend your database across RAM and Flash Memory and intelligently manage "hot" (active) data in RAM and "cold" (less active) data in Flash memory (SSD). ## Active-Passive replication considerations -When using [Active-Passive replication]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}), eviction and expiration only operate on the source (active) database. The target database does not evict or expire data while Active-Passive is enabled. +When using [Active-Passive replication](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive), eviction and expiration only operate on the source (active) database. The target database does not evict or expire data while Active-Passive is enabled. Do not write to the target database while Active-Passive is enabled. Doing so can cause the following issues: @@ -54,4 +54,4 @@ Do not write to the target database while Active-Passive is enabled. Doing so ca ## Active-Active replication considerations -The eviction policy mechanism for [Active-Active databases]({{< relref "/operate/rc/databases/active-active" >}}) kicks in earlier than for standalone databases because it requires propagation to all regions. The eviction policy starts to evict keys when one of the Active-Active instances reaches 80% of its memory limit. If memory usage continues to rise while the keys are being evicted, the rate of eviction will increase to prevent reaching the Out-of-Memory state. +The eviction policy mechanism for [Active-Active databases](/content/operate/rc/databases/active-active/_index.md) kicks in earlier than for standalone databases because it requires propagation to all regions. The eviction policy starts to evict keys when one of the Active-Active instances reaches 80% of its memory limit. If memory usage continues to rise while the keys are being evicted, the rate of eviction will increase to prevent reaching the Out-of-Memory state. diff --git a/content/operate/rc/databases/configuration/data-persistence.md b/content/operate/rc/databases/configuration/data-persistence.md index 83964360b2..057450f66e 100644 --- a/content/operate/rc/databases/configuration/data-persistence.md +++ b/content/operate/rc/databases/configuration/data-persistence.md @@ -29,13 +29,12 @@ Data can be persisted in one of two ways: AOF files provide greater protection (durability) than snapshots at the cost of resources and recovery time. Although snapshot recovery is faster, the risk of data loss is higher, depending on the time between failure and the most recent snapshot. -{{}} -If you turn off data persistence, data is lost when the database goes down. -{{}} +> [!WARNING] +> If you turn off data persistence, data is lost when the database goes down. ## Configure data persistence -In Redis Cloud, data persistence is a database configuration setting that can be changed by [editing your database]({{< relref "/operate/rc/databases/view-edit-database.md" >}}) settings. +In Redis Cloud, data persistence is a database configuration setting that can be changed by [editing your database](/content/operate/rc/databases/view-edit-database.md) settings. The availability of the setting depends on your plan: diff --git a/content/operate/rc/databases/configuration/high-availability.md b/content/operate/rc/databases/configuration/high-availability.md index 74d67337a7..328021f8b9 100644 --- a/content/operate/rc/databases/configuration/high-availability.md +++ b/content/operate/rc/databases/configuration/high-availability.md @@ -29,15 +29,15 @@ Redis Cloud supports three levels of replication: - _Multi-zone replication_ means that the primary and its replicas are stored in different zones. This means that your database can remain online even if an entire zone becomes unavailable. Multi-zone replication requires a region with three or more availability zones. -Your replication options depend on your [subscription plan]({{< relref "/operate/rc/subscriptions/_index.md" >}}): +Your replication options depend on your [subscription plan](/content/operate/rc/subscriptions/_index.md): - Free Redis Cloud Essentials plans do not support replication. - Paid Redis Cloud Essentials plans and Redis Cloud Pro plans let you choose between multi-zone or single-zone replication when creating a subscription. You can also turn off replication. Whether or not you can change your replication settings after database creation depends on your plan type and what type of replication you originally selected. -- For Redis Cloud Essentials, you select the kind of replication when you create your database. If you selected Multi-zone replication when you created your database, you can't change it to Single-zone or turn it off after database creation. However, if you selected No Replication or Single-zone replication, you can switch between the two at any time by [editing your Essentials subscription]({{< relref "/operate/rc/subscriptions/view-essentials-subscription#change-high-availability-and-persistence" >}}). -- For Redis Cloud Pro, you select whether you want a multi-zone deployment during subscription creation. You can't change this setting or any [Zone settings]({{< relref "/operate/rc/databases/configuration/high-availability#zone-setting-maintenance" >}}) after subscription creation. However, you can activate or deactivate replication for each database within the subscription at any time by [editing your database]({{< relref "/operate/rc/databases/view-edit-database" >}}). +- For Redis Cloud Essentials, you select the kind of replication when you create your database. If you selected Multi-zone replication when you created your database, you can't change it to Single-zone or turn it off after database creation. However, if you selected No Replication or Single-zone replication, you can switch between the two at any time by [editing your Essentials subscription](/content/operate/rc/subscriptions/view-essentials-subscription/_index.md#change-high-availability-and-persistence). +- For Redis Cloud Pro, you select whether you want a multi-zone deployment during subscription creation. You can't change this setting or any [Zone settings](/content/operate/rc/databases/configuration/high-availability.md#zone-setting-maintenance) after subscription creation. However, you can activate or deactivate replication for each database within the subscription at any time by [editing your database](/content/operate/rc/databases/view-edit-database.md). ## Performance impact @@ -57,15 +57,15 @@ Zone settings can only be defined when a subscription is created. You cannot ch This means you can't convert a multi-zone subscription to a single zone (or vice-versa). -To use different zone settings, create a new subscription with the preferred settings and then [migrate data]({{< relref "/operate/rc/databases/migrate-databases.md" >}}) from the original subscription. +To use different zone settings, create a new subscription with the preferred settings and then [migrate data](/content/operate/rc/databases/migrate-databases.md) from the original subscription. ## Availability zones You can reduce network transfer costs and network latency by ensuring your Redis Cloud Pro cluster and your application are located in the same availability zone. -To specify the availability zone(s) for your cluster, [create your Pro database with custom settings]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}), and select *Manual Selection* under **Allowed Availability Zones** in **Advanced options**. +To specify the availability zone(s) for your cluster, [create your Pro database with custom settings](/content/operate/rc/databases/create-database/create-pro-database-new.md), and select *Manual Selection* under **Allowed Availability Zones** in **Advanced options**. -For Google Cloud clusters and [Redis Cloud BYOC]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/" >}}), select an availability zone from the **Zone name** list. +For Google Cloud clusters and [Redis Cloud BYOC](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md), select an availability zone from the **Zone name** list. {{Select one availability zone when Multi-AZ is turned off.}} @@ -73,9 +73,8 @@ For all other AWS clusters, select an availability zone ID from the **Zone IDs** {{For hosted AWS clusters, select availability zone IDs from the Zone IDs list.}} -{{< note >}} -Multi-AZ requires a region with at least three availability zones. Regions with fewer than three availability zones don't support Multi-AZ deployments. -{{< /note >}} +> [!NOTE] +> Multi-AZ requires a region with at least three availability zones. Regions with fewer than three availability zones don't support Multi-AZ deployments. If **Multi-AZ** is enabled, you must select three availability zones from the list. @@ -86,5 +85,5 @@ For more information on availability zones, see the [Google Cloud docs](https:// ## More info To learn more about high availability and replication, see: -- [Highly Available Redis]({{< relref "/operate/rs/databases/durability-ha/" >}}) -- [Database replication]({{< relref "/operate/rs/databases/durability-ha/replication.md" >}}) +- [Highly Available Redis](/content/operate/rs/databases/durability-ha/_index.md) +- [Database replication](/content/operate/rs/databases/durability-ha/replication.md) diff --git a/content/operate/rc/databases/configuration/sizing.md b/content/operate/rc/databases/configuration/sizing.md index c748c54fb8..a76a2ab7fb 100644 --- a/content/operate/rc/databases/configuration/sizing.md +++ b/content/operate/rc/databases/configuration/sizing.md @@ -22,9 +22,9 @@ Here are some general guidelines: - Memory limit represents an upper limit. You cannot store more data than the memory limit. Depending on your other selections, available memory for data may be less than expected. -- [Replication]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) doubles memory consumption; that is, 512 MB of data requires at least 1 GB of memory limit when replication is enabled. This affects both Redis Cloud Pro and Redis Cloud Essentials. For example, if you subscribe to a 1 GB Essentials plan, Redis will allocate 512 MB for your dataset and the other 512 MB for replication. +- [Replication](/content/operate/rc/databases/configuration/high-availability.md) doubles memory consumption; that is, 512 MB of data requires at least 1 GB of memory limit when replication is enabled. This affects both Redis Cloud Pro and Redis Cloud Essentials. For example, if you subscribe to a 1 GB Essentials plan, Redis will allocate 512 MB for your dataset and the other 512 MB for replication. -- [Active-Active]({{< relref "/operate/rc/databases/active-active" >}}) also doubles memory consumption and the effect is cumulative with the impact of replication. Since Active-Active requires replication to be turned on, the memory limit impact can be as large as four times (4x) the original data size. +- [Active-Active](/content/operate/rc/databases/active-active/_index.md) also doubles memory consumption and the effect is cumulative with the impact of replication. Since Active-Active requires replication to be turned on, the memory limit impact can be as large as four times (4x) the original data size. Active-Active databases also have additional sizing considerations: @@ -32,9 +32,9 @@ Here are some general guidelines: - Each Active-Active instance reserves a replication backlog for shard synchronization and an Active-Active replication backlog for synchronization between instances. By default, each backlog is set to 1% of the database size. -- [Advanced capabilities]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) also consume memory. For search databases, consider index size when you size your database. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more info. +- [Advanced capabilities](/content/operate/rc/databases/configuration/advanced-capabilities.md) also consume memory. For search databases, consider index size when you size your database. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more info. -Memory limits in Redis Cloud are subject to the same considerations as Redis Software; to learn more, see [Database memory limits]({{< relref "/operate/rs/databases/memory-performance/memory-limit" >}}). +Memory limits in Redis Cloud are subject to the same considerations as Redis Software; to learn more, see [Database memory limits](/content/operate/rs/databases/memory-performance/memory-limit.md). ## Throughput @@ -48,9 +48,9 @@ We use this setting to guide the allocation of compute power and network bandwid Some factors that can affect throughput include: - **Request size**: Smaller requests (under 3KB) consume less network bandwidth and may result in more operations per second than requested, while larger requests may result in fewer operations per second. -- **Command complexity**: Simple commands, like `GET` and `SET`, are faster and require fewer resources, whereas more complex commands involve more processing time and can reduce throughput. See the [Command list]({{< relref "/commands" >}}) to see which commands are more complex than others. -- **Replication**: Using [multi-zone replication]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) affects throughput as each write operation is executed asynchronously in each zone. -- **Security**: Some security options, such as [transport layer security]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}), may affect throughput. +- **Command complexity**: Simple commands, like `GET` and `SET`, are faster and require fewer resources, whereas more complex commands involve more processing time and can reduce throughput. See the [Command list](/content/commands) to see which commands are more complex than others. +- **Replication**: Using [multi-zone replication](/content/operate/rc/databases/configuration/high-availability.md) affects throughput as each write operation is executed asynchronously in each zone. +- **Security**: Some security options, such as [transport layer security](/content/operate/rc/security/database-security/tls-ssl.md), may affect throughput. - **Number of client connections**: The number of client connections affects throughput. Increasing or decreasing the number of client connections can result in higher or lower throughput. ### Optimize throughput @@ -60,9 +60,9 @@ Here are some things to keep in mind for optimizing throughput: - Benchmark your app to understand what latency expectations are required, and adjust throughput accordingly. - Test and monitor your app's performance and adjust the set ops/sec based on how if performs in real-world conditions. - If your average request size is larger than 3KB, consider setting your throughput higher than expected. -- Track the slow logs using the [`SLOWLOG` command]({{< relref "/commands/slowlog" >}}) or the **Slowlog** tab on the [database screen]({{< relref "/operate/rc/databases/view-edit-database" >}}). -- Use [pipelining]({{< relref "/develop/using-commands/pipelining" >}}) and [concurrent connections]({{< relref "/develop/reference/clients" >}}) effectively to optimize throughput and latency. -- Search databases have their own throughput requirements. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more info. +- Track the slow logs using the [`SLOWLOG` command](/content/commands/slowlog.md) or the **Slowlog** tab on the [database screen](/content/operate/rc/databases/view-edit-database.md). +- Use [pipelining](/content/develop/using-commands/pipelining.md) and [concurrent connections](/content/develop/reference/clients.md) effectively to optimize throughput and latency. +- Search databases have their own throughput requirements. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more info. ### Frequently asked questions diff --git a/content/operate/rc/databases/connect/_index.md b/content/operate/rc/databases/connect/_index.md index 71ab8ae484..372d10655d 100644 --- a/content/operate/rc/databases/connect/_index.md +++ b/content/operate/rc/databases/connect/_index.md @@ -11,7 +11,7 @@ linkTitle: Connect weight: 12 --- -After you [create your database]({{< relref "/operate/rc/databases/create-database" >}}), you can connect to it using the public or private endpoint. +After you [create your database](/content/operate/rc/databases/create-database/_index.md), you can connect to it using the public or private endpoint. ## Get connection information @@ -28,25 +28,25 @@ The database endpoints are listed in the **Configuration** tab for your database {{The Access section for an Essentials database.}} Redis Cloud Pro and Redis Cloud Essentials databases have a public endpoint, which you can access from the public internet. Redis Cloud Pro databases also have a private endpoint. You can connect to the private endpoint from a private network. Before you can connect to the private endpoint, you must set up a private connectivity method, such as: -- [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}) -- [Google Cloud Private Service Connect]({{< relref "/operate/rc/security/private-service-connect" >}}) (Google Cloud only) -- [AWS Transit Gateway]({{< relref "/operate/rc/security/aws-transit-gateway" >}}) or [AWS PrivateLink]({{< relref "/operate/rc/security/aws-privatelink" >}}) (AWS only) +- [VPC peering](/content/operate/rc/security/vpc-peering.md) +- [Google Cloud Private Service Connect](/content/operate/rc/security/private-service-connect.md) (Google Cloud only) +- [AWS Transit Gateway](/content/operate/rc/security/aws-transit-gateway.md) or [AWS PrivateLink](/content/operate/rc/security/aws-privatelink.md) (AWS only) -Redis Cloud Pro users can block the public endpoint for their databases. For more information, see [Block public endpoints]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}). +Redis Cloud Pro users can block the public endpoint for their databases. For more information, see [Block public endpoints](/content/operate/rc/security/database-security/block-public-endpoints.md). #### Static and dynamic endpoints {{< embed-md "rc-endpoint-description.md" >}} -You can redirect the dynamic endpoints to a different database at any time, but you cannot redirect the static endpoints. We recommend using the dynamic endpoints for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information. +You can redirect the dynamic endpoints to a different database at any time, but you cannot redirect the static endpoints. We recommend using the dynamic endpoints for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints](/content/operate/rc/databases/redirect-endpoints.md) for more information. ### Database username and password -By default, your database is protected by a [**Default user**]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) with the username `default` and a masked **Default user password**. For Essentials databases, select **Default user > Configure** and then select the eye icon to view your password. +By default, your database is protected by a [**Default user**](/content/operate/rc/security/access-control/data-access-control/default-user.md) with the username `default` and a masked **Default user password**. For Essentials databases, select **Default user > Configure** and then select the eye icon to view your password. For Pro databases, you can see the default user password in the **Security** section of the **Configuration** details for your database. Select the eye icon to show or hide the password. -If you've turned on [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}) for your database and [turned off the default User]({{< relref "/operate/rc/security/access-control/data-access-control/default-user#turn-off-default-user" >}}), use the username and password for your data access role. +If you've turned on [Role-based access control](/content/operate/rc/security/access-control/data-access-control/role-based-access-control.md) for your database and [turned off the default User](/content/operate/rc/security/access-control/data-access-control/default-user.md#turn-off-default-user), use the username and password for your data access role. ## Connect to your database with connection wizard @@ -54,9 +54,8 @@ Select **Connect** to open the connection wizard. {{< image filename="/images/rc/button-connect.png#no-click" alt="Connect button." >}} -{{< note >}} -For [Active-Active databases]({{< relref "/operate/rc/databases/active-active" >}}), you connect to one of the database instances. Choose the region you want to connect to from the region selection to access the connection information for that instance. -{{< /note >}} +> [!NOTE] +> For [Active-Active databases](/content/operate/rc/databases/active-active/_index.md), you connect to one of the database instances. Choose the region you want to connect to from the region selection to access the connection information for that instance. The connection wizard provides the following database connection methods: @@ -70,7 +69,7 @@ The connection wizard provides the following database connection methods: ### Redis Insight {#using-redisinsight} -[Redis Insight]({{< relref "/develop/tools/insight" >}}) is a free Redis GUI that lets you visualize your Redis data and learn more about Redis. +[Redis Insight](/content/develop/tools/insight/_index.md) is a free Redis GUI that lets you visualize your Redis data and learn more about Redis. You can connect to your database with Redis Insight in two ways: @@ -80,9 +79,8 @@ You can connect to your database with Redis Insight in two ways: #### Open in your browser {#ri-browser} -{{< note >}} -Opening your database with Redis Insight in your browser is only available for Essentials databases. For all other databases, [Download and install Redis Insight](#ri-app) on your computer. -{{< /note >}} +> [!NOTE] +> Opening your database with Redis Insight in your browser is only available for Essentials databases. For all other databases, [Download and install Redis Insight](#ri-app) on your computer. If Redis Insight on Redis Cloud is available for your database, select **Launch Redis Insight web** from the connection wizard to open it. @@ -94,21 +92,21 @@ You can also select **Launch** from the database page under **View and manage da Redis Insight will open in a new tab. -This browser-based version of Redis Insight has a subset of the features of Redis Insight. For more information, see [Open with Redis Insight on Redis Cloud]({{< relref "/operate/rc/databases/connect/insight-cloud" >}}). +This browser-based version of Redis Insight has a subset of the features of Redis Insight. For more information, see [Open with Redis Insight on Redis Cloud](/content/operate/rc/databases/connect/insight-cloud.md). #### Install and open on your computer {#ri-app} 1. If you haven't downloaded Redis Insight, select **Download** under **Redis Insight** in the Connection wizard to download it. -1. [Install Redis Insight]({{< relref "/develop/tools/insight" >}}). +1. [Install Redis Insight](/content/develop/tools/insight/_index.md). 1. Once installed, select **Open with Redis Insight**. 1. A pop-up asks if you wish to open the link with Redis Insight. Select **Open Redis Insight** to connect to your database with Redis Insight. -If you get an error when connecting with Redis Insight, [manually connect to your database]({{< relref "/develop/tools/insight" >}}) from Redis Insight. +If you get an error when connecting with Redis Insight, [manually connect to your database](/content/develop/tools/insight/_index.md) from Redis Insight. -You can use Redis Insight to view your data, run Redis commands, and analyze database performance. See the [Redis Insight docs]({{< relref "/develop/tools/insight" >}}) for more info. +You can use Redis Insight to view your data, run Redis commands, and analyze database performance. See the [Redis Insight docs](/content/develop/tools/insight/_index.md) for more info. ### Redis client {#using-redis-client} @@ -116,36 +114,35 @@ A Redis client is a software library or tool that enables applications to intera The connection wizard provides code snippets to connect to your database with the following programming languages: -- .NET using [StackExchange.Redis/NRedisStack]({{< relref "/develop/clients/dotnet" >}}) -- node.js using [node-redis]({{< relref "/develop/clients/nodejs" >}}) -- Python using [redis-py]({{< relref "/develop/clients/redis-py" >}}) -- Java using [Jedis]({{< relref "/develop/clients/jedis" >}}) and [Lettuce]({{< relref "/develop/clients/lettuce" >}}) -- Go using [go-redis]({{< relref "/develop/clients/go" >}}) -- PHP using [Predis]({{< relref "/develop/clients/php" >}}) +- .NET using [StackExchange.Redis/NRedisStack](/content/develop/clients/dotnet/_index.md) +- node.js using [node-redis](/content/develop/clients/nodejs/_index.md) +- Python using [redis-py](/content/develop/clients/redis-py/_index.md) +- Java using [Jedis](/content/develop/clients/jedis/_index.md) and [Lettuce](/content/develop/clients/lettuce/_index.md) +- Go using [go-redis](/content/develop/clients/go/_index.md) +- PHP using [Predis](/content/develop/clients/php/_index.md) {{The connection wizard clients.}} If the username and password are not already filled in, replace `` and `` with your username and password. -See [Clients]({{< relref "/develop/clients" >}}) to learn how to connect with the official Redis clients. +See [Clients](/content/develop/clients/_index.md) to learn how to connect with the official Redis clients. -{{< note >}} -We recommend using the [dynamic endpoints](#static-and-dynamic-endpoints) for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information. -{{< /note >}} +> [!NOTE] +> We recommend using the [dynamic endpoints](#static-and-dynamic-endpoints) for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints](/content/operate/rc/databases/redirect-endpoints.md) for more information. #### redis-cli {#using-rediscli} -The [`redis-cli`]({{< relref "/develop/tools/cli" >}}) utility is installed when you install Redis. It provides a command-line interface that lets you work with your database using core [Redis commands]({{< relref "/commands" >}}). +The [`redis-cli`](/content/develop/tools/cli.md) utility is installed when you install Redis. It provides a command-line interface that lets you work with your database using core [Redis commands](/content/commands). -To run `redis-cli`, [install Redis]({{< relref "/operate/oss_and_stack/install/install-stack/" >}}) on your machine. After it's installed, copy the `redis-cli` command under **Redis CLI** in the connection wizard and enter it into your terminal. If the username and password are not already filled in, replace `` and `` with your username and password. +To run `redis-cli`, [install Redis](/content/operate/oss_and_stack/install/install-stack/_index.md) on your machine. After it's installed, copy the `redis-cli` command under **Redis CLI** in the connection wizard and enter it into your terminal. If the username and password are not already filled in, replace `` and `` with your username and password. -If you only need the Redis CLI (`redis-cli`) and not the full Redis Open Source distribution, you can [install the standalone `redis-cli` binary]({{< relref "/operate/oss_and_stack/install/install-stack/install-redis-cli" >}}) on Linux or macOS. +If you only need the Redis CLI (`redis-cli`) and not the full Redis Open Source distribution, you can [install the standalone `redis-cli` binary](/content/operate/oss_and_stack/install/install-stack/install-redis-cli.md) on Linux or macOS. -See [Redis CLI]({{< relref "/develop/tools/cli" >}}) to learn how to use `redis-cli`. +See [Redis CLI](/content/develop/tools/cli.md) to learn how to use `redis-cli`. ## More info -- [Connect your application]({{< relref "/develop/clients" >}}) -- [Connect with TLS]({{< relref "/operate/rc/security/database-security/tls-ssl#connect-over-tls" >}}) -- [Default user]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) -- [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}) \ No newline at end of file +- [Connect your application](/content/develop/clients/_index.md) +- [Connect with TLS](/content/operate/rc/security/database-security/tls-ssl.md#connect-over-tls) +- [Default user](/content/operate/rc/security/access-control/data-access-control/default-user.md) +- [Role-based access control](/content/operate/rc/security/access-control/data-access-control/role-based-access-control.md) \ No newline at end of file diff --git a/content/operate/rc/databases/connect/insight-cloud.md b/content/operate/rc/databases/connect/insight-cloud.md index 36023333b9..ae016ce5ee 100644 --- a/content/operate/rc/databases/connect/insight-cloud.md +++ b/content/operate/rc/databases/connect/insight-cloud.md @@ -12,33 +12,32 @@ linkTitle: Redis Insight on Redis Cloud weight: 1 --- -[Redis Insight]({{< relref "/develop/tools/insight" >}}) is a free Redis GUI that lets you visualize your Redis data and learn more about Redis. +[Redis Insight](/content/develop/tools/insight/_index.md) is a free Redis GUI that lets you visualize your Redis data and learn more about Redis. -You can either [install Redis Insight]({{< relref "/develop/tools/insight" >}}) on your computer, or you can open your database in Redis Insight directly on Redis Cloud. +You can either [install Redis Insight](/content/develop/tools/insight/_index.md) on your computer, or you can open your database in Redis Insight directly on Redis Cloud. -{{< note >}} -Opening your database with Redis Insight in your browser is only available for Essentials databases. For all other databases, [install Redis Insight]({{< relref "/develop/tools/insight" >}}) on your computer and [open Redis Insight]({{< relref "/operate/rc/databases/connect#ri-app" >}}) from the database page. -{{< /note >}} +> [!NOTE] +> Opening your database with Redis Insight in your browser is only available for Essentials databases. For all other databases, [install Redis Insight](/content/develop/tools/insight/_index.md) on your computer and [open Redis Insight](/content/operate/rc/databases/connect/_index.md#ri-app) from the database page. -To open your database with Redis Insight on Redis Cloud, select **Open with Redis Insight** on the [database screen]({{< relref "/operate/rc/databases/view-edit-database" >}}). +To open your database with Redis Insight on Redis Cloud, select **Open with Redis Insight** on the [database screen](/content/operate/rc/databases/view-edit-database.md). {{Open with Redis Insight}} Redis Insight will open in a new tab. -This browser-based version of Redis Insight has a subset of the features of Redis Insight. For other Redis Insight features, [install Redis Insight]({{< relref "/develop/tools/insight" >}}) on your computer and [open Redis Insight]({{< relref "/operate/rc/databases/connect#ri-app" >}}) from the database page. +This browser-based version of Redis Insight has a subset of the features of Redis Insight. For other Redis Insight features, [install Redis Insight](/content/develop/tools/insight/_index.md) on your computer and [open Redis Insight](/content/operate/rc/databases/connect/_index.md#ri-app) from the database page. ## Browse The **Browse** tab lets you browse, filter, and visualize your Redis data structures. -- Create, read, update, and delete lists, hashes, strings, sets, sorted sets, streams, and [JSON]({{< relref "/develop/data-types/json/" >}}) +- Create, read, update, and delete lists, hashes, strings, sets, sorted sets, streams, and [JSON](/content/develop/data-types/json/_index.md) - Filter keys by key name or pattern, and by key type - Group keys according to their namespaces {{Keys in a database grouped by namespace.}} - View, validate, and manage your key values in a human-readable format using formatters that prettify and highlight data in different formats (for example, Unicode, JSON, MessagePack, HEX, and ASCII) {{Human-readable view of a hash key.}} -- Search by key values using your [search indexes]({{< relref "/develop/ai/search-and-query" >}}) +- Search by key values using your [search indexes](/content/develop/ai/search-and-query/_index.md) {{Search for keys using a search index.}} If you don't have any Redis data yet, you can select **Load sample data** to add sample data into your database. diff --git a/content/operate/rc/databases/create-database/_index.md b/content/operate/rc/databases/create-database/_index.md index 13bb1975a8..2d36d11be3 100644 --- a/content/operate/rc/databases/create-database/_index.md +++ b/content/operate/rc/databases/create-database/_index.md @@ -13,18 +13,18 @@ weight: 10 A database is the heart of any Redis Cloud deployment. -The process for Creating a database depends on the type of [subscription plan]({{< relref "/operate/rc/subscriptions" >}}) you need. +The process for Creating a database depends on the type of [subscription plan](/content/operate/rc/subscriptions/_index.md) you need. An **Essentials** plan is a fixed monthly price for a single database. It is cost-efficient and designed for low-throughput scenarios. It supports a range of availability, persistence, and backup options. Pricing supports low throughput workloads. -- [Create an Essentials database]({{< relref "/operate/rc/databases/create-database/create-essentials-database" >}}) -- [Create a Redis Flex database]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}) +- [Create an Essentials database](/content/operate/rc/databases/create-database/create-essentials-database.md) +- [Create a Redis Flex database](/content/operate/rc/databases/create-database/create-flex-database.md) A **Free** plan is a type of Essentials plan designed for learning and building test projects. It gives you enough space to learn Redis concepts and develop application prototypes. You can upgrade to a paid Essentials plan at any time. -- [Create a free database]({{< relref "/operate/rc/databases/create-database/create-free-database" >}}) +- [Create a free database](/content/operate/rc/databases/create-database/create-free-database.md) A **Pro** plan is an hourly price based on capacity. It supports more databases, larger databases, greater throughput, and unlimited connections. -- [Create a Pro database with a new subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) -- [Create a Pro database in an existing subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) -- [Create an Active-Active database]({{< relref "/operate/rc/databases/active-active/create-active-active-database" >}}) +- [Create a Pro database with a new subscription](/content/operate/rc/databases/create-database/create-pro-database-new.md) +- [Create a Pro database in an existing subscription](/content/operate/rc/databases/create-database/create-pro-database-existing.md) +- [Create an Active-Active database](/content/operate/rc/databases/active-active/create-active-active-database.md) diff --git a/content/operate/rc/databases/create-database/create-essentials-database.md b/content/operate/rc/databases/create-database/create-essentials-database.md index d11b628a71..d1c7b0a54a 100644 --- a/content/operate/rc/databases/create-database/create-essentials-database.md +++ b/content/operate/rc/databases/create-database/create-essentials-database.md @@ -17,16 +17,16 @@ Redis Cloud Essentials is cost-efficient and designed for low-throughput scenari {{< embed-md "rc-create-db-first-steps.md" >}} -3. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Essentials**. +3. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Essentials**. {{The Subscription selection panel with Essentials selected.}} - {{< note >}} -This guide shows how to create a paid Essentials database. -- If you want to create a free Essentials database, see [Create a free database]({{< relref "/operate/rc/rc-quickstart" >}}). You can only have one free database per account. -- If you'd rather create a Pro database, see [Create a Pro database with a new subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}). -- If you already have a Pro subscription and want to add a database to it, see [Create a Pro database in an existing subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}). - {{< /note >}} + > [!NOTE] + > This guide shows how to create a paid Essentials database. + > - If you want to create a free Essentials database, see [Create a free database](/content/operate/rc/rc-quickstart.md). You can only have one free database per account. + > - If you'd rather create a Pro database, see [Create a Pro database with a new subscription](/content/operate/rc/databases/create-database/create-pro-database-new.md). + > - If you already have a Pro subscription and want to add a database to it, see [Create a Pro database in an existing subscription](/content/operate/rc/databases/create-database/create-pro-database-existing.md). + > After you select **Essentials**, the rest of the database details will appear. @@ -38,7 +38,7 @@ This guide shows how to create a paid Essentials database. {{The list of available cloud vendors.}} -1. Choose a **Region** from the list. See [Supported regions]({{< relref "/operate/rc/supported-regions" >}}) for a list of supported regions by cloud vendor. +1. Choose a **Region** from the list. See [Supported regions](/content/operate/rc/supported-regions.md) for a list of supported regions by cloud vendor. 1. Select the **Database version** you want to use. @@ -48,11 +48,11 @@ This guide shows how to create a paid Essentials database. {{Available Essentials plans.}} - The plan determines the size of your database and other limits. For a comparison of available plans, see [Redis Cloud Essentials plans]({{< relref "/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details" >}}). + The plan determines the size of your database and other limits. For a comparison of available plans, see [Redis Cloud Essentials plans](/content/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details.md). 1. Select **RAM** or **RAM + SSD (Flex)** to choose between a database that uses only RAM or one that uses both RAM and Flash memory. - Choose Flex for larger datasets and cost-efficient scale when you can tolerate single-digit millisecond latency for warm data. Choose RAM when you need the absolute lowest latency for all data. To learn more about Flex, see [Create a Flex database]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}). + Choose Flex for larger datasets and cost-efficient scale when you can tolerate single-digit millisecond latency for warm data. Choose RAM when you need the absolute lowest latency for all data. To learn more about Flex, see [Create a Flex database](/content/operate/rc/databases/create-database/create-flex-database.md). 1. Choose your **High availability (replication)** settings. @@ -62,7 +62,7 @@ This guide shows how to create a paid Essentials database. - **Single-Zone**: Your database will have a primary and a replica located in the same cloud zone. If anything happens to the primary, the replica takes over and becomes the new primary. - **Multi-Zone**: The primary and its replicas are stored in different zones. This means that your database can remain online even if an entire zone becomes unavailable. - See [High availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) for more information about these settings. + See [High availability](/content/operate/rc/databases/configuration/high-availability.md) for more information about these settings. 1. Choose your **Data persistence** settings from the list. @@ -72,7 +72,7 @@ This guide shows how to create a paid Essentials database. - A **Snapshot** is a copy of the in-memory database, taken at periodic intervals (one, six, or twelve hours). You can restore data to the snapshot's point in time. - See [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) for more information about these settings. + See [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md) for more information about these settings. 1. Enter your payment details. @@ -88,4 +88,4 @@ This guide shows how to create a paid Essentials database. When you create your database, there's a brief pause while your request is processed and then the **Database details** page appears. -You can now [connect to your database]({{< relref "/operate/rc/databases/connect" >}}) and start working with Redis. \ No newline at end of file +You can now [connect to your database](/content/operate/rc/databases/connect/_index.md) and start working with Redis. \ No newline at end of file diff --git a/content/operate/rc/databases/create-database/create-flex-database.md b/content/operate/rc/databases/create-database/create-flex-database.md index 36890b6e2f..5e8f05e1b5 100644 --- a/content/operate/rc/databases/create-database/create-flex-database.md +++ b/content/operate/rc/databases/create-database/create-flex-database.md @@ -13,7 +13,7 @@ tocEmbedHeaders: true Flex allows your dataset to span both high-performance RAM and cost-efficient dedicated Flash memory. Flex automatically manages data placement between the two tiers, keeping frequently accessed (“hot”) data in RAM for sub-millisecond latency, while moving less active (“warm”) data to Flash to optimize capacity and cost. This dual memory architecture delivers predictable performance at scale, enabling larger datasets without compromising speed or operational simplicity. -Flex databases are currently compatible with most existing Redis applications, except for applications that use Time Series. [Search and Query]({{< relref "/develop/ai/search-and-query" >}}) is available on Flex databases on Redis Cloud Pro as a Preview feature; see [Search and Query on Flex](#search-and-query-on-flex-preview). +Flex databases are currently compatible with most existing Redis applications, except for applications that use Time Series. [Search and Query](/content/develop/ai/search-and-query/_index.md) is available on Flex databases on Redis Cloud Pro as a Preview feature; see [Search and Query on Flex](#search-and-query-on-flex-preview). Flex is available on both Redis Cloud Essentials and Redis Cloud Pro. @@ -30,13 +30,13 @@ Consider Flex when you need to: Flex is **not** a durable data store. It is designed for performance, elasticity, and scalability, not for long-term data persistence. While Flex can temporarily retain data in memory or Flash, it should not be used as a primary system of record or persistent storage layer. -For workloads that require durability and recovery across restarts or failures, use Redis Cloud's [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) features. +For workloads that require durability and recovery across restarts or failures, use Redis Cloud's [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md) features. ## Best practices and limitations ### Search and Query on Flex (Preview) -[Search and Query]({{< relref "/develop/ai/search-and-query" >}}) on Flex databases is available as a Preview feature on Redis Cloud Pro. It isn't available on Redis Cloud Essentials. +[Search and Query](/content/develop/ai/search-and-query/_index.md) on Flex databases is available as a Preview feature on Redis Cloud Pro. It isn't available on Redis Cloud Essentials. To use it, enable the Preview flag for Search and Query on Flex in the Redis Cloud console for your Redis Cloud Pro subscription, then create a Flex database with a Search and Query index on tiered storage. @@ -75,7 +75,7 @@ Flex databases cannot store keys or values larger than 4 GB in Flash storage. Ke {{< embed-md "rc-create-db-first-steps.md" >}} -3. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Essentials**. +3. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Essentials**. {{The Subscription selection panel with Essentials selected.}} @@ -85,7 +85,7 @@ Flex databases cannot store keys or values larger than 4 GB in Flash storage. Ke 1. Redis will generate a database name for you. If you want to change it, you can do so in the **Database name** field. -1. Choose a **Region** on Amazon Web Services for your database. See [Supported regions]({{< relref "/operate/rc/supported-regions" >}}) for a list of supported regions by cloud vendor. +1. Choose a **Region** on Amazon Web Services for your database. See [Supported regions](/content/operate/rc/supported-regions.md) for a list of supported regions by cloud vendor. 1. Select the **Database version** you want to use. @@ -93,7 +93,7 @@ Flex databases cannot store keys or values larger than 4 GB in Flash storage. Ke {{Available Flex plans.}} - For a comparison of available plans, see [Redis Cloud Essentials plans]({{< relref "/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details" >}}). + For a comparison of available plans, see [Redis Cloud Essentials plans](/content/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details.md). All Flex plans on Redis Cloud Essentials have a default RAM percentage of 10%. @@ -104,7 +104,7 @@ Flex databases cannot store keys or values larger than 4 GB in Flash storage. Ke - **None**: You will have a single copy of your database without replication. - **Single-Zone**: Your database will have a primary and a replica located in the same cloud zone. If anything happens to the primary, the replica takes over and becomes the new primary. - See [High availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) for more information about these settings. + See [High availability](/content/operate/rc/databases/configuration/high-availability.md) for more information about these settings. 1. Choose your **Data persistence** settings from the list. @@ -114,7 +114,7 @@ Flex databases cannot store keys or values larger than 4 GB in Flash storage. Ke - A **Snapshot** is a copy of the in-memory database, taken at periodic intervals (one, six, or twelve hours). You can restore data to the snapshot's point in time. - See [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) for more information about these settings. + See [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md) for more information about these settings. 1. Select the **Database version** you want to use. @@ -134,7 +134,7 @@ When you create your database, there's a brief pause while your request is proce ### Redis Cloud Pro -To create a Flex database on Redis Cloud Pro, [create a new Pro database with custom settings]({{< relref "/operate/rc/databases/create-database/create-pro-database-new#custom-settings" >}}). +To create a Flex database on Redis Cloud Pro, [create a new Pro database with custom settings](/content/operate/rc/databases/create-database/create-pro-database-new.md#custom-settings). In the **Advanced options** of the **Setup** tab, select **Redis Flex**. @@ -144,7 +144,7 @@ During the **Sizing** step, when you are provisioning your databases, you can se {{The RAM percentage setting.}} -Continue with the instructions to [create your database]({{< relref "/operate/rc/databases/create-database/create-pro-database-new#custom-settings" >}}). +Continue with the instructions to [create your database](/content/operate/rc/databases/create-database/create-pro-database-new.md#custom-settings). ## Troubleshooting diff --git a/content/operate/rc/databases/create-database/create-free-database.md b/content/operate/rc/databases/create-database/create-free-database.md index cfc05a3065..4aa2c35e97 100644 --- a/content/operate/rc/databases/create-database/create-free-database.md +++ b/content/operate/rc/databases/create-database/create-free-database.md @@ -13,13 +13,12 @@ tocEmbedHeaders: true Free databases are perfect for learning and exploring Redis. You get 30 MB of space for you to learn Redis concepts and develop application prototypes. -{{< note >}} -You can only have one free database per account. If you already have a free database, you can [delete it]({{< relref "/operate/rc/databases/delete-database" >}}) or [upgrade it to a paid Essentials plan]({{< relref "/operate/rc/subscriptions/view-essentials-subscription#upgrade-plan" >}}) before creating a new one. -{{}} +> [!NOTE] +> You can only have one free database per account. If you already have a free database, you can [delete it](/content/operate/rc/databases/delete-database.md) or [upgrade it to a paid Essentials plan](/content/operate/rc/subscriptions/view-essentials-subscription/_index.md#upgrade-plan) before creating a new one. {{< embed-md "rc-create-db-first-steps.md" >}} -3. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Try 30 MB for free**. +3. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Try 30 MB for free**. {{The Subscription selection panel with Free selected.}} @@ -35,7 +34,7 @@ You can only have one free database per account. If you already have a free data {{The list of available cloud vendors.}} - See [Supported regions]({{< relref "/operate/rc/supported-regions" >}}) for a list of supported regions by cloud vendor. + See [Supported regions](/content/operate/rc/supported-regions.md) for a list of supported regions by cloud vendor. 6. Select **Create database**. @@ -43,4 +42,4 @@ You can only have one free database per account. If you already have a free data When you create your database, there's a brief pause while your request is processed and then the **Database details** page appears. -You can now [connect to your database]({{< relref "/operate/rc/databases/connect" >}}) and start working with Redis. Once your app is ready to scale up, you can [upgrade to a paid Essentials plan]({{< relref "/operate/rc/subscriptions/view-essentials-subscription#upgrade-plan" >}}) at any time. \ No newline at end of file +You can now [connect to your database](/content/operate/rc/databases/connect/_index.md) and start working with Redis. Once your app is ready to scale up, you can [upgrade to a paid Essentials plan](/content/operate/rc/subscriptions/view-essentials-subscription/_index.md#upgrade-plan) at any time. \ No newline at end of file diff --git a/content/operate/rc/databases/create-database/create-pro-database-existing.md b/content/operate/rc/databases/create-database/create-pro-database-existing.md index 92b6a95b0c..a7a5047a38 100644 --- a/content/operate/rc/databases/create-database/create-pro-database-existing.md +++ b/content/operate/rc/databases/create-database/create-pro-database-existing.md @@ -11,11 +11,10 @@ weight: 15 tocEmbedHeaders: true --- -{{< note >}} -This guide shows how to create a Pro database in an existing subscription. -- If you don't yet have a Pro subscription, see [Create a Pro database with a new subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}). -- If you'd rather create an Essentials database, see [Create an Essentials database]({{< relref "/operate/rc/databases/create-database/create-essentials-database" >}}). -{{< /note >}} +> [!NOTE] +> This guide shows how to create a Pro database in an existing subscription. +> - If you don't yet have a Pro subscription, see [Create a Pro database with a new subscription](/content/operate/rc/databases/create-database/create-pro-database-new.md). +> - If you'd rather create an Essentials database, see [Create an Essentials database](/content/operate/rc/databases/create-database/create-essentials-database.md). To create a database in an already existing Pro subscription: @@ -27,13 +26,13 @@ To create a database in an already existing Pro subscription: This displays the **Create database** screen. -1. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Existing subscription**, and then select your existing Pro subscription from the list. +1. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Existing subscription**, and then select your existing Pro subscription from the list. {{The Subscription selection panel with Pro selected and an existing subscription selected.}} After you select your existing subscription from the list, select **Continue** to go to the **New database** page. -You can also select your subscription from the [subscription list]({{< relref "/operate/rc/subscriptions/view-pro-subscription" >}}) and select **Create database in this subscription**. +You can also select your subscription from the [subscription list](/content/operate/rc/subscriptions/view-pro-subscription.md) and select **Create database in this subscription**. {{The Create database in this subscription button.}} @@ -58,9 +57,9 @@ The available settings vary according to your subscription plan: | **Database port** | Automatically or manually assigns a database port (range: 10000-19999). You cannot assign a port that is reserved or already in use. | | **Database version** | The Redis version of your database. We recommend you choose the latest available version. | | **Type** | Controls advanced database capabilities and protocol. Supported values include _Redis_ and _Memcached_ | -| **Advanced capabilities** | [Advanced features and data types]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) used by the database. Starting with Redis 8.0, all advanced capabilities are included in Redis by default. | -| **Query performance factor** | *(Search and query databases on Redis 7.2 or later only)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **Supported Protocol(s)** | Choose between RESP2 and RESP3 _(Redis 7.2 only)_. See [Redis serialization protocol]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) for details | +| **Advanced capabilities** | [Advanced features and data types](/content/operate/rc/databases/configuration/advanced-capabilities.md) used by the database. Starting with Redis 8.0, all advanced capabilities are included in Redis by default. | +| **Query performance factor** | *(Search and query databases on Redis 7.2 or later only)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **Supported Protocol(s)** | Choose between RESP2 and RESP3 _(Redis 7.2 only)_. See [Redis serialization protocol](/content/develop/reference/protocol-spec.md#resp-versions) for details | ## Performance section @@ -70,12 +69,12 @@ The **Performance** section lets you manage the maximum size, throughput, and ha | Setting name | Description | |:--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Dataset size** | Maximum size (in GB) for your dataset. See [Dataset size]({{< relref "/operate/rc/databases/configuration/sizing#dataset-size" >}}) for sizing considerations.
Databases with Search and query have specific size requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **Throughput** | Defines throughput in terms of maximum operations per second for the database. See [Throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) for more info.
Databases with Search and query have specific throughput requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **High availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. See [High availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) for more info| -| **Query performance factor** | *(Search and query databases on Redis 7.2 or later)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **Hashing policy** | Defines the [hashing policy]({{< relref "/operate/rc/databases/configuration/clustering#manage-the-hashing-policy" >}}). | -| **OSS Cluster API** | Activates the [OSS Cluster API]({{< relref "/operate/rc/databases/configuration/clustering#oss-cluster-api" >}}) for a database.
After you select OSS Cluster API, you can select **Use external endpoint** if you want to use the external endpoint for the database. Selecting **Use external endpoint** will block the private endpoint for this database. | +| **Dataset size** | Maximum size (in GB) for your dataset. See [Dataset size](/content/operate/rc/databases/configuration/sizing.md#dataset-size) for sizing considerations.
Databases with Search and query have specific size requirements, see [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **Throughput** | Defines throughput in terms of maximum operations per second for the database. See [Throughput](/content/operate/rc/databases/configuration/sizing.md#throughput) for more info.
Databases with Search and query have specific throughput requirements, see [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **High availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. See [High availability](/content/operate/rc/databases/configuration/high-availability.md) for more info| +| **Query performance factor** | *(Search and query databases on Redis 7.2 or later)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **Hashing policy** | Defines the [hashing policy](/content/operate/rc/databases/configuration/clustering.md#manage-the-hashing-policy). | +| **OSS Cluster API** | Activates the [OSS Cluster API](/content/operate/rc/databases/configuration/clustering.md#oss-cluster-api) for a database.
After you select OSS Cluster API, you can select **Use external endpoint** if you want to use the external endpoint for the database. Selecting **Use external endpoint** will block the private endpoint for this database. | ## Durability section @@ -86,14 +85,14 @@ The **Durability** section helps you keep your database (and your data) availabl | Setting name | Description | |:-------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Data persistence** | Defines the data persistence policy, if any. See [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence.md" >}}). | -| **Data eviction policy** | Configures which [policy]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md" >}}) is applied when your database reaches its memory limit. | -| **Remote backup** | When enabled, identifies a location and interval for [data backups]({{< relref "/operate/rc/databases/back-up-data" >}}). | -| **Active-Passive Redis** | When enabled, identifies a path to the linked database. See [Migrate data]({{< relref "/operate/rc/databases/migrate-databases" >}}) for more information. | +| **Data persistence** | Defines the data persistence policy, if any. See [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md). | +| **Data eviction policy** | Configures which [policy](/content/operate/rc/databases/configuration/data-eviction-policies.md) is applied when your database reaches its memory limit. | +| **Remote backup** | When enabled, identifies a location and interval for [data backups](/content/operate/rc/databases/back-up-data.md). | +| **Active-Passive Redis** | When enabled, identifies a path to the linked database. See [Migrate data](/content/operate/rc/databases/migrate-databases.md) for more information. | ## Tags section -The **Tags** section lets you add [tags]({{< relref "/operate/rc/databases/tag-database" >}}) to the database. +The **Tags** section lets you add [tags](/content/operate/rc/databases/tag-database.md) to the database. {{Use the Tag settings to add tags to the database.}} @@ -112,10 +111,10 @@ The **Security** section helps you control access to your database. | Setting name | Description | |:-----------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Default user** | When enabled, permits access using the `default` username and a simple password (see [Default User]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}})). Turn on [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}) to turn off this setting. | +| **Default user** | When enabled, permits access using the `default` username and a simple password (see [Default User](/content/operate/rc/security/access-control/data-access-control/default-user.md)). Turn on [Role-based access control](/content/operate/rc/security/access-control/data-access-control/role-based-access-control.md) to turn off this setting. | | **Default user password** | Password assigned to the database when created. | -| **CIDR allow list** | [Allow list]({{< relref "/operate/rc/security/cidr-whitelist.md" >}}) of IP addresses/security groups permitted to access the database | -| **Transport layer security (TLS)** | Enables [transport layer security]({{< relref "/operate/rc/security/database-security/tls-ssl.md" >}}) (TLS) encryption for database access. | +| **CIDR allow list** | [Allow list](/content/operate/rc/security/cidr-whitelist.md) of IP addresses/security groups permitted to access the database | +| **Transport layer security (TLS)** | Enables [transport layer security](/content/operate/rc/security/database-security/tls-ssl.md) (TLS) encryption for database access. | ## Alerts section @@ -124,7 +123,7 @@ The **Alerts** section defines notification emails sent to your account and the {{The Alerts section defines the notification emails and their triggering conditions.}} -The available alerts vary according to the plan type. See [Configure alerts]({{< relref "/operate/rc/databases/monitor-performance#configure-metric-alerts" >}}) for more information. +The available alerts vary according to the plan type. See [Configure alerts](/content/operate/rc/databases/monitor-performance.md#configure-metric-alerts) for more information. ## Billing unit types diff --git a/content/operate/rc/databases/create-database/create-pro-database-new.md b/content/operate/rc/databases/create-database/create-pro-database-new.md index 51dd36dcb6..91abf319d6 100644 --- a/content/operate/rc/databases/create-database/create-pro-database-new.md +++ b/content/operate/rc/databases/create-database/create-pro-database-new.md @@ -15,15 +15,15 @@ Redis Cloud Pro supports more databases, larger databases, greater throughput, a {{< embed-md "rc-create-db-first-steps.md" >}} -3. Select the type of [subscription]({{< relref "/operate/rc/subscriptions" >}}) you need. For this guide, select **Pro**. +3. Select the type of [subscription](/content/operate/rc/subscriptions/_index.md) you need. For this guide, select **Pro**. {{The Subscription selection panel with Pro selected.}} - {{< note >}} -This guide shows how to create a Pro database with a new subscription. -- If you already have a Pro subscription and want to add a database to it, see [Create a Pro database in an existing subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}). -- If you'd rather create an Essentials database, see [Create an Essentials database]({{< relref "/operate/rc/databases/create-database/create-essentials-database" >}}). - {{< /note >}} + > [!NOTE] + > This guide shows how to create a Pro database with a new subscription. + > - If you already have a Pro subscription and want to add a database to it, see [Create a Pro database in an existing subscription](/content/operate/rc/databases/create-database/create-pro-database-existing.md). + > - If you'd rather create an Essentials database, see [Create an Essentials database](/content/operate/rc/databases/create-database/create-essentials-database.md). + > After you select **Pro**, the **Database settings** section will appear. @@ -50,9 +50,9 @@ If you choose to create your database with Easy create: | Database setting | Description | |:---------|:-----------| | **Name** | The name for your database. Redis will generate a database name for you, but you can change it at any time. | - | **Dataset size (GB)** | The amount of data for your dataset. See [Dataset size]({{< relref "/operate/rc/databases/configuration/sizing#dataset-size" >}}) for sizing considerations.
Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | - | **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) for more information.
Databases with Search and query have specific throughput requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | - | **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. (Warning: doubles memory consumption). See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). | + | **Dataset size (GB)** | The amount of data for your dataset. See [Dataset size](/content/operate/rc/databases/configuration/sizing.md#dataset-size) for sizing considerations.
Databases with Search and query have specific sizing requirements, see [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | + | **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput](/content/operate/rc/databases/configuration/sizing.md#throughput) for more information.
Databases with Search and query have specific throughput requirements, see [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | + | **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. (Warning: doubles memory consumption). See [High Availability](/content/operate/rc/databases/configuration/high-availability.md). | 1. Select **View all settings** to review the database settings that we selected for you. @@ -111,9 +111,9 @@ In the General settings of the **Setup** tab, you need to: 1. Select the **Region** where you want to deploy your database. - {{< note >}} -This guide is for single region database deployment. If you want to create a multi-region Active-Active database, see [Create an Active-Active database]({{< relref "/operate/rc/databases/active-active/create-active-active-database" >}}) for specific steps and configuration options exclusive to Active-Active. - {{< /note >}} + > [!NOTE] + > This guide is for single region database deployment. If you want to create a multi-region Active-Active database, see [Create an Active-Active database](/content/operate/rc/databases/active-active/create-active-active-database.md) for specific steps and configuration options exclusive to Active-Active. + > #### Advanced options {#advanced-options} @@ -123,15 +123,15 @@ The following settings are defined in the **Advanced options** of the **Setup** | Advanced option | Description | |---|---| -| **Redis Flex** | Determines if your databases are stored only in memory (RAM) or are split between memory and Flash storage (RAM+Flash). See [Redis Flex]({{< relref "/operate/rc/databases/create-database/create-flex-database/" >}}) for more information. | -| **BYOC account** | To deploy these databases to an existing cloud account, select it here. Use the **Add** button to add a new cloud account.

(Available only if [Redis Cloud Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) is enabled) | -| **AWS Resource tags** | Applies resource tags to the infrastructure deployed to your BYOC account. See [Resource tags]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/resource-tags" >}}) for more information.

(Available only if [Redis Cloud Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) is enabled) | -| **Multi-AZ** | Determines if replication spans multiple Availability Zones, which provides automatic failover when problems occur. See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). | -| **VPC configuration** | Select **In a new VPC** to deploy to a new [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC).

To deploy these databases to an existing virtual private cloud, select **In existing VPC** and then set VPC ID to the appropriate ID value.

(Available only if [Redis Cloud Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud" >}}) is enabled and you have selected an existing BYOC account) | -| **Allowed Availability Zones** | The availability zones for your selected region.

If you choose **Manual selection**, you must select at least one zone ID from the **Zone IDs** list. For more information, see [Availability zones]({{< relref "/operate/rc/databases/configuration/high-availability#availability-zones" >}}). | +| **Redis Flex** | Determines if your databases are stored only in memory (RAM) or are split between memory and Flash storage (RAM+Flash). See [Redis Flex](/content/operate/rc/databases/create-database/create-flex-database.md) for more information. | +| **BYOC account** | To deploy these databases to an existing cloud account, select it here. Use the **Add** button to add a new cloud account.

(Available only if [Redis Cloud Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) is enabled) | +| **AWS Resource tags** | Applies resource tags to the infrastructure deployed to your BYOC account. See [Resource tags](/content/operate/rc/subscriptions/bring-your-own-cloud/resource-tags.md) for more information.

(Available only if [Redis Cloud Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) is enabled) | +| **Multi-AZ** | Determines if replication spans multiple Availability Zones, which provides automatic failover when problems occur. See [High Availability](/content/operate/rc/databases/configuration/high-availability.md). | +| **VPC configuration** | Select **In a new VPC** to deploy to a new [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC).

To deploy these databases to an existing virtual private cloud, select **In existing VPC** and then set VPC ID to the appropriate ID value.

(Available only if [Redis Cloud Bring your own Cloud](/content/operate/rc/subscriptions/bring-your-own-cloud/_index.md) is enabled and you have selected an existing BYOC account) | +| **Allowed Availability Zones** | The availability zones for your selected region.

If you choose **Manual selection**, you must select at least one zone ID from the **Zone IDs** list. For more information, see [Availability zones](/content/operate/rc/databases/configuration/high-availability.md#availability-zones). | | **Deployment CIDR** | The [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) range of IP addresses for your deployment. Redis creates a new [subnet](https://en.wikipedia.org/wiki/Subnetwork) for the **Deployment CIDR** in your [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC). It cannot overlap with the CIDR ranges of other subnets used by your account.

For deployments in an existing VPC, the **Deployment CIDR** must be within your VPC's **primary** CIDR range (secondary CIDRs are not supported). | -| **Public endpoint access** | Select whether or not to [block public endpoints]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}) for all databases in the subscription. | -| **Maintenance windows** | Determines when Redis can perform [maintenance]({{< relref "/operate/rc/subscriptions/maintenance" >}}) on your databases. Select **Manual** if you want to set [manual maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). | +| **Public endpoint access** | Select whether or not to [block public endpoints](/content/operate/rc/security/database-security/block-public-endpoints.md) for all databases in the subscription. | +| **Maintenance windows** | Determines when Redis can perform [maintenance](/content/operate/rc/subscriptions/maintenance/_index.md) on your databases. Select **Manual** if you want to set [manual maintenance windows](/content/operate/rc/subscriptions/maintenance/set-maintenance-windows.md). | When finished, choose **Continue** to determine your size requirements. @@ -156,13 +156,13 @@ By default, you're shown basic settings, which include: | Database setting | Description | |:---------|:-----------| | **Name** | Redis Cloud generates a database name for you, but you can change it at any time. | -| **Version** | The Redis version for your database. We recommend you choose the latest available version. See [Redis version management]({{< relref "/operate/rc/databases/version-management" >}}) for more information. | -| **Dataset size (GB)** | The amount of data for your dataset. Specify small sizes as decimals of 1.0 GB; example: `0.1` GB (minimum). We calculate the total memory limit for you based on the other settings you choose for your database.
Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. (Warning: Doubles memory consumption). See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). | -| **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) for more information.
Databases with Search and query have specific throughput requirements. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **Hashing policy** | Determines how data is distributed across multiple Redis processes of a database. Available options depend on your account creation date. See [Clustering]({{< relref "/operate/rc/databases/configuration/clustering#manage-the-hashing-policy" >}}) for more information. | -| **Query performance factor** | *(Search and query databases on Redis 7.2 or later only)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | -| **Data Persistence** | Defines the data persistence policy, if any. See [Data persistence]({{< relref "/operate/rc/databases/configuration/data-persistence.md" >}}). | +| **Version** | The Redis version for your database. We recommend you choose the latest available version. See [Redis version management](/content/operate/rc/databases/version-management/_index.md) for more information. | +| **Dataset size (GB)** | The amount of data for your dataset. Specify small sizes as decimals of 1.0 GB; example: `0.1` GB (minimum). We calculate the total memory limit for you based on the other settings you choose for your database.
Databases with Search and query have specific sizing requirements, see [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. (Warning: Doubles memory consumption). See [High Availability](/content/operate/rc/databases/configuration/high-availability.md). | +| **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput](/content/operate/rc/databases/configuration/sizing.md#throughput) for more information.
Databases with Search and query have specific throughput requirements. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **Hashing policy** | Determines how data is distributed across multiple Redis processes of a database. Available options depend on your account creation date. See [Clustering](/content/operate/rc/databases/configuration/clustering.md#manage-the-hashing-policy) for more information. | +| **Query performance factor** | *(Search and query databases on Redis 7.2 or later only)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing](/content/operate/rc/databases/configuration/advanced-capabilities.md#search-and-query-sizing) for more information. | +| **Data Persistence** | Defines the data persistence policy, if any. See [Data persistence](/content/operate/rc/databases/configuration/data-persistence.md). | Select **More options** to specify values for the following settings. @@ -170,10 +170,10 @@ Select **More options** to specify values for the following settings. | Database option | Description | |:---------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Advanced Capabilities** | [Advanced features and data types]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) used by the database. Starting with Redis 8.0, all advanced capabilities are included in Redis by default. | -| **OSS Cluster API** | Enable to use the [OSS Cluster API]({{< relref "/operate/rc/databases/configuration/clustering#oss-cluster-api" >}}). | +| **Advanced Capabilities** | [Advanced features and data types](/content/operate/rc/databases/configuration/advanced-capabilities.md) used by the database. Starting with Redis 8.0, all advanced capabilities are included in Redis by default. | +| **OSS Cluster API** | Enable to use the [OSS Cluster API](/content/operate/rc/databases/configuration/clustering.md#oss-cluster-api). | | **Type** | Set to **Redis**, otherwise **Memcached** database for legacy database support. | -| **Supported Protocol(s)** | Choose between RESP2 and RESP3 _(Redis 7.2 and later only)_. See [Redis serialization protocol]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) for details | +| **Supported Protocol(s)** | Choose between RESP2 and RESP3 _(Redis 7.2 and later only)_. See [Redis serialization protocol](/content/develop/reference/protocol-spec.md#resp-versions) for details | | **Quantity** | Number of databases to create with these settings. | When finished, select **Save configuration** to save your database configuration. diff --git a/content/operate/rc/databases/delete-database.md b/content/operate/rc/databases/delete-database.md index 52ca0f5992..94b5d72fd2 100644 --- a/content/operate/rc/databases/delete-database.md +++ b/content/operate/rc/databases/delete-database.md @@ -12,7 +12,7 @@ weight: 45 Deleting a database requires the Account Owner role. -Deleted databases cannot be recovered. We recommend [making a backup]({{< relref "/operate/rc/databases/back-up-data.md" >}}), just in case. +Deleted databases cannot be recovered. We recommend [making a backup](/content/operate/rc/databases/back-up-data.md), just in case. Sign in to the [Redis Cloud console](https://cloud.redis.io/), then follow the steps for your plan to open the **Delete database** confirmation dialog. @@ -46,9 +46,8 @@ The **Delete database** confirmation dialog appears. If this database is the onl - Clear **Delete my subscription and stop my payment** to delete the database but keep the subscription. -{{< note >}} -You will continue to be charged for your subscription until you delete it, even if there are no databases in your subscription. -{{< /note >}} +> [!NOTE] +> You will continue to be charged for your subscription until you delete it, even if there are no databases in your subscription. {{A delete database confirmation dialog asks you to consider deleting the subscription as well.}} diff --git a/content/operate/rc/databases/flush-data.md b/content/operate/rc/databases/flush-data.md index 872e4e3fb9..e42b274715 100644 --- a/content/operate/rc/databases/flush-data.md +++ b/content/operate/rc/databases/flush-data.md @@ -10,15 +10,14 @@ weight: 40 draft: true --- -The [FLUSHALL]({{< relref "/commands/flushall" >}}) command provides a fast way to remove all data from a database. +The [FLUSHALL](/content/commands/flushall.md) command provides a fast way to remove all data from a database. -{{< note >}} -When you _flush_ a database, you remove all data.

- -This _permanently_ removes all data from the database. The data cannot be recovered, except by restoring from earlier backups.

- -We _strongly_ recommend backing up databases before flushing them. -{{}} +> [!NOTE] +> When you _flush_ a database, you remove all data.

+> +> This _permanently_ removes all data from the database. The data cannot be recovered, except by restoring from earlier backups.

+> +> We _strongly_ recommend backing up databases before flushing them. ## How to use FLUSHALL @@ -48,7 +47,7 @@ redis-cli -h redis-12345.server.cloud.redislabs.example.com -p 12345 -a xyz flus ### Redis Insight -If you install [Redis Insight]({{< relref "/develop/tools/insight" >}}) and [add your database]({{< relref "/operate/rc/rc-quickstart#using-redisinsight" >}}), you can use the Redis Insight workbench to run commands: +If you install [Redis Insight](/content/develop/tools/insight/_index.md) and [add your database](/content/operate/rc/rc-quickstart.md#using-redisinsight), you can use the Redis Insight workbench to run commands: 1. Start Redis Insight and connect to your database. diff --git a/content/operate/rc/databases/import-data.md b/content/operate/rc/databases/import-data.md index 964ea1f19d..7ebe0a8179 100644 --- a/content/operate/rc/databases/import-data.md +++ b/content/operate/rc/databases/import-data.md @@ -11,16 +11,14 @@ weight: 20 --- You can import an existing dataset into your Redis Cloud instance from an existing Redis server or an RDB file. -{{< warning >}} -Data imported into an existing database overwrites existing data. -- If you import a dataset into the target database of an [Active-Passive setup]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}), the dataset will be overwritten by any changes to the source database. -- If you import a dataset into one region in an [Active-Active database]({{< relref "/operate/rc/databases/active-active/" >}}), the dataset will also be replicated across regions. -{{< /warning >}} +> [!WARNING] +> Data imported into an existing database overwrites existing data. +> - If you import a dataset into the target database of an [Active-Passive setup](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive), the dataset will be overwritten by any changes to the source database. +> - If you import a dataset into one region in an [Active-Active database](/content/operate/rc/databases/active-active/_index.md), the dataset will also be replicated across regions.
-{{< note >}} -Expired keys are not imported. -As a result, the number of keys in the source and destination databases can be different after the import is complete. -{{< /note >}} +> [!NOTE] +> Expired keys are not imported. +> As a result, the number of keys in the source and destination databases can be different after the import is complete. ## Prerequisites @@ -72,14 +70,14 @@ Select the tab for your storage location type. - `path` - Path to the file, if necessary - `filename` - Filename of the RDB file, including the `.gz` suffix if the file is compressed - {{< note >}} -If your FTP username or password contains special characters such as `@`, `\`, or `:`, you must URL encode (also known as Percent encode) these special characters. If you don't, your database may become stuck. - {{< /note >}} + > [!NOTE] + > If your FTP username or password contains special characters such as `@`, `\`, or `:`, you must URL encode (also known as Percent encode) these special characters. If you don't, your database may become stuck. + > 4. For sharded databases with multiple RDB files, select **Add source** to add another RDB file. - {{< warning >}} -For sharded databases with multiple RDB files, make sure to add every file before proceeding. - {{< /warning >}} + > [!WARNING] + > For sharded databases with multiple RDB files, make sure to add every file before proceeding. + > 5. Select **Import**. diff --git a/content/operate/rc/databases/migrate-databases.md b/content/operate/rc/databases/migrate-databases.md index 97d6dc8e96..979d46d1e1 100644 --- a/content/operate/rc/databases/migrate-databases.md +++ b/content/operate/rc/databases/migrate-databases.md @@ -21,11 +21,11 @@ The most common way to transfer data to a new database is to import a copy of th Here's how it works: -1. [Select an export storage destination]({{< relref "/operate/rc/databases/back-up-data#set-up-backup-storage-locations" >}}) and verify that it's ready for use and has sufficient space. +1. [Select an export storage destination](/content/operate/rc/databases/back-up-data.md#set-up-backup-storage-locations) and verify that it's ready for use and has sufficient space. -1. [Export]({{< relref "/operate/rc/databases/back-up-data.md" >}}) the data from the original database to the storage location. +1. [Export](/content/operate/rc/databases/back-up-data.md) the data from the original database to the storage location. -1. [Import]({{< relref "/operate/rc/databases/import-data.md" >}}) the exported data into the target database, the one hosted by the new subscription. +1. [Import](/content/operate/rc/databases/import-data.md) the exported data into the target database, the one hosted by the new subscription. The migrated data reflects the state of the data at the time it was originally exported. @@ -51,13 +51,12 @@ To migrate data using Active-Passive syncing, specify the target database as an 4. Turn off Active-Passive for the target database. 5. Switch apps and other connections to the target database. -{{< note >}} -Before you use Active-Passive, be aware of the following limitations: - -- 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 "/operate/rc/databases/configuration/data-eviction-policies.md" >}}). **Do not write to the target database while Active-Passive is enabled.** We recommend that you turn off Active-Passive after the databases are synced. - -- Turning on Active-Passive will flush the target database. Make sure that your target database has no important data before you turn on Active-Passive. -{{< /note >}} +> [!NOTE] +> Before you use Active-Passive, be aware of the following limitations: +> +> - 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](/content/operate/rc/databases/configuration/data-eviction-policies.md). **Do not write to the target database while Active-Passive is enabled.** We recommend that you turn off Active-Passive after the databases are synced. +> +> - Turning on Active-Passive will flush the target database. Make sure that your target database has no important data before you turn on Active-Passive. ### Detailed Active-Passive syncing process {#sync-using-active-passive} @@ -87,9 +86,9 @@ Follow these detailed steps to migrate data using Active-Passive syncing: - **Source database not hosted on Redis Cloud** (for example, a self-managed Redis deployment): select **External**. - {{< note >}} -Don't select **External** to sync from a database hosted in a *different* Redis Cloud account. Redis Cloud rejects Active-Passive connections between accounts and returns an error, even if you enter that database's public endpoint here. [Contact support](https://redis.io/support/) to migrate a database between Redis Cloud accounts using Active-Passive. - {{< /note >}} + > [!NOTE] + > Don't select **External** to sync from a database hosted in a *different* Redis Cloud account. Redis Cloud rejects Active-Passive connections between accounts and returns an error, even if you enter that database's public endpoint here. [Contact support](https://redis.io/support/) to migrate a database between Redis Cloud accounts using Active-Passive. + > 1. In the **Enter the source URI** field, type `redis://` and then paste in the public endpoint details. @@ -137,9 +136,8 @@ Don't select **External** to sync from a database hosted in a *different* Redis Active-Passive sync lets you migrate data while apps and other connections are using the source database. Once the data is migrated, you should migrate active connections to the target database. -{{< warning >}} -Do not write to the target database until turning off Active-Passive. Writing to the target database of an Active-Passive setup can cause data consistency issues and replication failures. See [Active-Passive replication considerations]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md#active-passive-replication-considerations" >}}) for more information. -{{< /warning >}} +> [!WARNING] +> Do not write to the target database until turning off Active-Passive. Writing to the target database of an Active-Passive setup can cause data consistency issues and replication failures. See [Active-Passive replication considerations](/content/operate/rc/databases/configuration/data-eviction-policies.md#active-passive-replication-considerations) for more information. ### Active-Passive memory requirements @@ -149,7 +147,7 @@ To illustrate, suppose you want to migrate a 1 GB source database without r ## Next steps -If you want to redirect your application's connections to the target database, you can [redirect your database endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) to the target database. +If you want to redirect your application's connections to the target database, you can [redirect your database endpoints](/content/operate/rc/databases/redirect-endpoints.md) to the target database. Before you redirect your endpoints, make sure: - The import or replication is finished. diff --git a/content/operate/rc/databases/monitor-performance.md b/content/operate/rc/databases/monitor-performance.md index 8bb78fa4e2..777a761613 100644 --- a/content/operate/rc/databases/monitor-performance.md +++ b/content/operate/rc/databases/monitor-performance.md @@ -58,24 +58,24 @@ Several metric graphs are available: | **Metric** | **Description** | |------------|-----------------| -| [Ops/sec]({{< relref "/operate/rs/references/metrics/database-operations#opssec" >}}) | The number of overall operations per sec for all Redis commands | -| [Reads/sec]({{< relref "/operate/rs/references/metrics/database-operations#readssec" >}}) | The number of read operations per second | -| [Writes/sec]({{< relref "/operate/rs/references/metrics/database-operations#writessec" >}}) | The number of write operations per second | -| [Other cmds/sec]({{< relref "/operate/rs/references/metrics/database-operations#other-commandssec" >}}) | The number of other Redis commands per second | -| [Latency]({{< relref "/operate/rs/references/metrics/database-operations#latency" >}}) | Latency per operation, in milliseconds | -| [Reads latency]({{< relref "/operate/rs/references/metrics/database-operations#reads-latency" >}}) | Latency per read operation, in milliseconds | -| [Writes latency]({{< relref "/operate/rs/references/metrics/database-operations#writes-latency" >}}) | Latency per write operation, in milliseconds | -| [Other latency]({{< relref "/operate/rs/references/metrics/database-operations#other-commands-latency" >}}) | Latency of other commands, in milliseconds | -| [Used memory]({{< relref "/operate/rs/references/metrics/resource-usage#used-memory" >}}) | Amount of memory used by the database | -| [Total keys]({{< relref "/operate/rs/references/metrics/database-operations#total-keys" >}}) | Total number of keys in the database | -| [Connections]({{< relref "/operate/rs/references/metrics/resource-usage#connections" >}}) | Total number of connections to the endpoint | -| [Evicted objects/sec]({{< relref "/operate/rs/references/metrics/database-operations#evicted-objectssec" >}}) | Number of objects evicted from the database per second. | -| [Expired objects/sec]({{< relref "/operate/rs/references/metrics/database-operations#expired-objectssec" >}}) | Number of expired objects per second. An expired object is an object with expired TTL that was deleted from the database. | -| [Hit ratio]({{< relref "/operate/rs/references/metrics/database-operations#hit-ratio" >}}) | Percent of operations on existing keys out of the total number database operations | +| [Ops/sec](/content/operate/rs/references/metrics/database-operations.md#opssec) | The number of overall operations per sec for all Redis commands | +| [Reads/sec](/content/operate/rs/references/metrics/database-operations.md#readssec) | The number of read operations per second | +| [Writes/sec](/content/operate/rs/references/metrics/database-operations.md#writessec) | The number of write operations per second | +| [Other cmds/sec](/content/operate/rs/references/metrics/database-operations.md#other-commandssec) | The number of other Redis commands per second | +| [Latency](/content/operate/rs/references/metrics/database-operations.md#latency) | Latency per operation, in milliseconds | +| [Reads latency](/content/operate/rs/references/metrics/database-operations.md#reads-latency) | Latency per read operation, in milliseconds | +| [Writes latency](/content/operate/rs/references/metrics/database-operations.md#writes-latency) | Latency per write operation, in milliseconds | +| [Other latency](/content/operate/rs/references/metrics/database-operations.md#other-commands-latency) | Latency of other commands, in milliseconds | +| [Used memory](/content/operate/rs/references/metrics/resource-usage.md#used-memory) | Amount of memory used by the database | +| [Total keys](/content/operate/rs/references/metrics/database-operations.md#total-keys) | Total number of keys in the database | +| [Connections](/content/operate/rs/references/metrics/resource-usage.md#connections) | Total number of connections to the endpoint | +| [Evicted objects/sec](/content/operate/rs/references/metrics/database-operations.md#evicted-objectssec) | Number of objects evicted from the database per second. | +| [Expired objects/sec](/content/operate/rs/references/metrics/database-operations.md#expired-objectssec) | Number of expired objects per second. An expired object is an object with expired TTL that was deleted from the database. | +| [Hit ratio](/content/operate/rs/references/metrics/database-operations.md#hit-ratio) | Percent of operations on existing keys out of the total number database operations | | Network Ingress bytes/sec | Amount of traffic in bytes per second entering the database network | | Network Egress bytes/sec | Amount of traffic in bytes per second exiting the database network | -For more detailed analysis, consider using [Redis Insight]({{< relref "/develop/tools/insight" >}}) or [Prometheus and Grafana]({{< relref "/integrate/prometheus-with-redis-cloud/" >}}). +For more detailed analysis, consider using [Redis Insight](/content/develop/tools/insight/_index.md) or [Prometheus and Grafana](/content/integrate/prometheus-with-redis-cloud/_index.md). ## Configure alerts {#configure-metric-alerts} @@ -100,7 +100,7 @@ Alert settings are specific to each database. Make sure you've configured alerts Any member of the account team can receive alert emails. -To update alert settings for one or more team members, select **Access Management** from the Redis Cloud console menu and then select the **Team** tab. For details, see [Access management]({{< relref "/operate/rc/security/access-control/access-management" >}}). +To update alert settings for one or more team members, select **Access Management** from the Redis Cloud console menu and then select the **Team** tab. For details, see [Access management](/content/operate/rc/security/access-control/access-management.md). If you subscribe to Redis Cloud through a Platform-as-a-Service (PaaS) provider (such as Heroku), you will need to review your provider's documentation for help managing your team. @@ -110,7 +110,7 @@ Redis Cloud exposes a Prometheus endpoint for Redis Cloud Pro databases. You can {{< embed-md "rc-get-prometheus-endpoint.md" >}} -For more information on how to connect Prometheus to Redis Cloud, see [Prometheus and Grafana with Redis Cloud]({{< relref "/integrate/prometheus-with-redis-cloud/" >}}). +For more information on how to connect Prometheus to Redis Cloud, see [Prometheus and Grafana with Redis Cloud](/content/integrate/prometheus-with-redis-cloud/_index.md). ## Continue learning with Redis University diff --git a/content/operate/rc/databases/redirect-endpoints.md b/content/operate/rc/databases/redirect-endpoints.md index 806f10dcc9..47af070cb4 100644 --- a/content/operate/rc/databases/redirect-endpoints.md +++ b/content/operate/rc/databases/redirect-endpoints.md @@ -13,13 +13,13 @@ bannerText: Dynamic endpoint redirection is currently in public preview. Feature Dynamic endpoints allow you to redirect application traffic from one database to another in the same Redis Cloud account without updating the endpoints in your application. Redis manages endpoint redirection for you. -You can redirect any database's dynamic endpoints to any Redis Cloud Pro database in the same account. If you need to replicate the data from the source database, you should [migrate your data]({{< relref "/operate/rc/databases/migrate-databases" >}}) to the target database before you redirect your endpoints. +You can redirect any database's dynamic endpoints to any Redis Cloud Pro database in the same account. If you need to replicate the data from the source database, you should [migrate your data](/content/operate/rc/databases/migrate-databases.md) to the target database before you redirect your endpoints. ## When to redirect dynamic endpoints Use endpoint redirection to seamlessly migrate your application traffic to a different database within the same Redis Cloud account. There is no need to update the endpoints in your application, since they'll remain the same. For example, you might want to: -- Upgrade your database's subscription from an [Essentials Plan to a Pro Plan]({{< relref "/operate/rc/subscriptions/upgrade-essentials-pro" >}}) +- Upgrade your database's subscription from an [Essentials Plan to a Pro Plan](/content/operate/rc/subscriptions/upgrade-essentials-pro.md) - Move between Redis Cloud offerings, such as Redis on RAM to Redis Flex - Split a subscription or combine databases from multiple subscriptions into one - Migrate your database to a different cloud provider, region, or availability zone @@ -43,7 +43,7 @@ Read the following sections to prepare for endpoint redirection. ### Scope and impact -This process redirects a source database's dynamic endpoints to a selected target database, including both public and private (if available) endpoints. **Redirecting endpoints does not migrate the data in your database.** You can choose to redirect the endpoints without migrating your data. If you need your data to be available in the target database, you must [migrate your data]({{< relref "/operate/rc/databases/migrate-databases" >}}) to the target database **before** you redirect your endpoints. +This process redirects a source database's dynamic endpoints to a selected target database, including both public and private (if available) endpoints. **Redirecting endpoints does not migrate the data in your database.** You can choose to redirect the endpoints without migrating your data. If you need your data to be available in the target database, you must [migrate your data](/content/operate/rc/databases/migrate-databases.md) to the target database **before** you redirect your endpoints. To ensure all connections are redirected to the target database, Redis Cloud will block all traffic to the source database for at least 5 minutes. This block period gives DNS caches time to expire and allow clients to reconnect and re-resolve the endpoint. All existing connections to the source database will be terminated and new connections will be refused. To reduce the risk of traffic being split between the source and target database, traffic will remain blocked until you [unblock it](#unblock-database-traffic). @@ -53,7 +53,7 @@ We recommend redirecting during a low-traffic window. #### Redirecting endpoints after data migration -If you [migrated your data]({{< relref "/operate/rc/databases/migrate-databases" >}}) to the target database before redirecting your endpoints, make sure that: +If you [migrated your data](/content/operate/rc/databases/migrate-databases.md) to the target database before redirecting your endpoints, make sure that: - The import or replication is finished. - Basic metrics for both the source and target databases are reporting normally. - The application authentication and authorization are set up correctly for the target database. @@ -66,9 +66,9 @@ Different applications have different availability and consistency requirements. Make sure you have met the following prerequisites: - Your application is using the dynamic endpoint. Endpoint redirection does not redirect [static endpoints](#applications-that-use-legacy-static-endpoints). -- You have [created a target Redis Cloud Pro database]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) in the same account that [is compatible with the source database](#redirection-compatibility). -- If you monitor the source database with Prometheus, add the target database to Prometheus before your redirect the endpoint so that you can monitor the target database after the redirection. See [Connect to Prometheus]({{< relref "operate/rc/databases/monitor-performance#connect-to-prometheus" >}}) for more information. -- Make sure that your client connections are configured with socket/connection timeouts. If you do not configure them, your client may hang indefinitely and the connection will not refresh until the application is restarted. Refer to the [Client documentation]({{< relref "/develop/clients" >}}) for your client for more information. +- You have [created a target Redis Cloud Pro database](/content/operate/rc/databases/create-database/create-pro-database-new.md) in the same account that [is compatible with the source database](#redirection-compatibility). +- If you monitor the source database with Prometheus, add the target database to Prometheus before your redirect the endpoint so that you can monitor the target database after the redirection. See [Connect to Prometheus](/content/operate/rc/databases/monitor-performance.md#connect-to-prometheus) for more information. +- Make sure that your client connections are configured with socket/connection timeouts. If you do not configure them, your client may hang indefinitely and the connection will not refresh until the application is restarted. Refer to the [Client documentation](/content/develop/clients/_index.md) for your client for more information. #### Redirection compatibility @@ -77,15 +77,15 @@ Endpoint redirection is only allowed when the source and target databases are co If any of the following properties differ, the databases are not compatible and you cannot redirect the endpoints: - Port number - Connectivity settings, such as: - - [TLS settings]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}) - - [VPC Peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or other connectivity method settings - - [Default User settings]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) - - [CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist" >}}) settings + - [TLS settings](/content/operate/rc/security/database-security/tls-ssl.md) + - [VPC Peering](/content/operate/rc/security/vpc-peering.md) or other connectivity method settings + - [Default User settings](/content/operate/rc/security/access-control/data-access-control/default-user.md) + - [CIDR allow list](/content/operate/rc/security/cidr-whitelist.md) settings Some differences may be intentional but can affect application behavior. In those cases, the console will warn you about the difference but allow you to proceed with redirection. The following differences will cause a warning: - Redis version -- [RESP Database protocol version]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) -- [OSS Cluster API]({{< relref "/operate/rc/databases/configuration/clustering#oss-cluster-api" >}}) configuration +- [RESP Database protocol version](/content/develop/reference/protocol-spec.md#resp-versions) +- [OSS Cluster API](/content/operate/rc/databases/configuration/clustering.md#oss-cluster-api) configuration ### Limitations @@ -108,7 +108,7 @@ To redirect your database endpoints: {{Select the target database from the database list.}} -1. If you want to assign the same [Role-based Access Control (RBAC) roles]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}) to the target database that are assigned to the source database, select **Assign the same ACLs to the target database**. +1. If you want to assign the same [Role-based Access Control (RBAC) roles](/content/operate/rc/security/access-control/data-access-control/role-based-access-control.md) to the target database that are assigned to the source database, select **Assign the same ACLs to the target database**. {{Select **Assign the same ACLs to the target database** to assign the same roles to the target database.}} diff --git a/content/operate/rc/databases/tag-database.md b/content/operate/rc/databases/tag-database.md index c81d109fbc..9cac74abdc 100644 --- a/content/operate/rc/databases/tag-database.md +++ b/content/operate/rc/databases/tag-database.md @@ -10,7 +10,7 @@ description: null weight: 33 --- -Tags are key-value pairs that let you categorize your databases. You can create tags and add them to your databases to associate them with each other. Once you've added tags, you can filter your databases in the [database list]({{< relref "/operate/rc/databases/view-edit-database#manage-the-database-list" >}}) or in the [cost report]({{< relref "/operate/rc/billing-and-payments/cost-report" >}}) by tag key or value. +Tags are key-value pairs that let you categorize your databases. You can create tags and add them to your databases to associate them with each other. Once you've added tags, you can filter your databases in the [database list](/content/operate/rc/databases/view-edit-database.md#manage-the-database-list) or in the [cost report](/content/operate/rc/billing-and-payments/cost-report.md) by tag key or value. ## Manage tags @@ -23,7 +23,7 @@ After you open the [tag manager](#tag-manager), you can use it to add, edit, or ### Open tag manager from the Configuration tab {#configuration-tab} -To learn how to navigate to your database, see [View and edit databases]({{< relref "/operate/rc/databases/view-edit-database" >}}). Select the **Configuration** tab to view the tags that are set for your database. For Essentials databases, the **Manage tags** button is at the top of the tab; for Pro databases, go to the **General** section. +To learn how to navigate to your database, see [View and edit databases](/content/operate/rc/databases/view-edit-database.md). Select the **Configuration** tab to view the tags that are set for your database. For Essentials databases, the **Manage tags** button is at the top of the tab; for Pro databases, go to the **General** section. {{The Configuration tab of the Database details screen.}} diff --git a/content/operate/rc/databases/version-management/_index.md b/content/operate/rc/databases/version-management/_index.md index 94702d70a0..7d0123b5b6 100644 --- a/content/operate/rc/databases/version-management/_index.md +++ b/content/operate/rc/databases/version-management/_index.md @@ -16,9 +16,8 @@ aliases: Redis Cloud provides comprehensive database version management that prioritizes customer control over major changes. -{{< note >}} -This page describes database version management for Redis Cloud. Redis Cloud manages the cluster version for you automatically. -{{< /note >}} +> [!NOTE] +> This page describes database version management for Redis Cloud. Redis Cloud manages the cluster version for you automatically. ## Redis version structure @@ -39,9 +38,8 @@ When a Redis version reaches **End-of-Life (EOL)**, Redis Cloud will automatical ## Supported database versions -{{< note >}} -**We strongly recommend using the latest available database version** to benefit from the newest features, performance improvements, and security updates. -{{< /note >}} +> [!NOTE] +> **We strongly recommend using the latest available database version** to benefit from the newest features, performance improvements, and security updates. | Version | Support model | Status | EOL Date | Plans | |---------|--------|--------|----------|-------| @@ -66,7 +64,7 @@ For existing databases, minor version auto-upgrades apply differently by plan: - **Essentials**: Minor version auto-upgrades apply for all Redis versions. - **Pro**: Minor version auto-upgrades apply for Redis 8.4 and later only (with opt-out available). For Redis 8.2 and earlier, minor upgrades must be done manually. -See [Upgrade database version]({{< relref "/operate/rc/databases/version-management/upgrade-version" >}}) for more details. +See [Upgrade database version](/content/operate/rc/databases/version-management/upgrade-version.md) for more details. ### Plan differences @@ -75,7 +73,7 @@ See [Upgrade database version]({{< relref "/operate/rc/databases/version-managem | Minor version auto-upgrades | All versions, always enabled | Redis 8.4+ only, default enabled (can disable) | | Major version upgrades | Customer controlled | Customer controlled | | Manual upgrades | Major upgrades only | Yes | -| [Automatic upgrade time]({{< relref "/operate/rc/subscriptions/maintenance" >}}) | Standard - between 12 AM and 6 AM region time | Configurable - [Set maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}) | +| [Automatic upgrade time](/content/operate/rc/subscriptions/maintenance/_index.md) | Standard - between 12 AM and 6 AM region time | Configurable - [Set maintenance windows](/content/operate/rc/subscriptions/maintenance/set-maintenance-windows.md) | ## Manual upgrades @@ -83,11 +81,11 @@ You can update your databases to a later version if by selecting **More actions* Before upgrading, you should: -- Review the [release notes]({{< relref "/operate/rc/changelog/version-release-notes" >}}) for your target version and all versions in between to ensure compatibility with your applications. -- [Back up your data]({{< relref "/operate/rc/databases/back-up-data" >}}), review [breaking changes]({{< relref "/operate/rc/changelog/version-release-notes" >}}). +- Review the [release notes](/content/operate/rc/changelog/version-release-notes/_index.md) for your target version and all versions in between to ensure compatibility with your applications. +- [Back up your data](/content/operate/rc/databases/back-up-data.md), review [breaking changes](/content/operate/rc/changelog/version-release-notes/_index.md). - Upgrade your staging or QA database before upgrading your production database. -See [Upgrade database version]({{< relref "/operate/rc/databases/version-management/upgrade-version" >}}) for detailed instructions. +See [Upgrade database version](/content/operate/rc/databases/version-management/upgrade-version.md) for detailed instructions. ## FAQ @@ -98,7 +96,7 @@ Pro users can opt out of minor version auto-upgrades for Redis 8.4+. Redis Cloud will force upgrade after notifications during your next maintenance window to ensure security and support. **Can I downgrade?** -Automatically reverting to a previous Redis version is not supported on Redis Cloud. See [Manually revert upgrade]({{< relref "/operate/rc/databases/version-management/upgrade-version#manually-revert-upgrade" >}}) for more details. +Automatically reverting to a previous Redis version is not supported on Redis Cloud. See [Manually revert upgrade](/content/operate/rc/databases/version-management/upgrade-version.md#manually-revert-upgrade) for more details. **How do I identify LTS vs STS?** Check the [supported versions table](#supported-versions). \ No newline at end of file diff --git a/content/operate/rc/databases/version-management/upgrade-version.md b/content/operate/rc/databases/version-management/upgrade-version.md index a899694f7c..8cd7357ba9 100644 --- a/content/operate/rc/databases/version-management/upgrade-version.md +++ b/content/operate/rc/databases/version-management/upgrade-version.md @@ -15,23 +15,22 @@ aliases: You can upgrade databases that are not on the latest available version of Redis to a later database version at any time. -{{< note >}} -Please keep in mind the following before upgrading your database version: - -- We recommend that you [back up your data]({{< relref "/operate/rc/databases/back-up-data" >}}) before upgrading to make it easier to [manually revert the upgrade](#manually-revert-upgrade) if needed. - -- We recommend that you upgrade your database during off-peak hours or during application maintenance to minimize reconnections. - -- Review the breaking changes for the new database version before upgrading: - - [Redis 7.2]({{< relref "/operate/rc/changelog/version-release-notes/7-2" >}}) - - [Redis 7.4]({{< relref "/operate/rc/changelog/version-release-notes/7-4" >}}) - - [Redis 8.0]({{< relref "/operate/rc/changelog/version-release-notes/8-0" >}}) - - [Redis 8.2]({{< relref "/operate/rc/changelog/version-release-notes/8-2" >}}) - - [Redis 8.4]({{< relref "/operate/rc/changelog/version-release-notes/8-4" >}}) - - [Redis 8.6]({{< relref "/operate/rc/changelog/version-release-notes/8-6" >}}) - -- You must upgrade the target database in an [Active-Passive]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}) setup before you upgrade the source database to prevent compatibility issues. -{{< /note >}} +> [!NOTE] +> Please keep in mind the following before upgrading your database version: +> +> - We recommend that you [back up your data](/content/operate/rc/databases/back-up-data.md) before upgrading to make it easier to [manually revert the upgrade](#manually-revert-upgrade) if needed. +> +> - We recommend that you upgrade your database during off-peak hours or during application maintenance to minimize reconnections. +> +> - Review the breaking changes for the new database version before upgrading: +> - [Redis 7.2](/content/operate/rc/changelog/version-release-notes/7-2.md) +> - [Redis 7.4](/content/operate/rc/changelog/version-release-notes/7-4.md) +> - [Redis 8.0](/content/operate/rc/changelog/version-release-notes/8-0.md) +> - [Redis 8.2](/content/operate/rc/changelog/version-release-notes/8-2.md) +> - [Redis 8.4](/content/operate/rc/changelog/version-release-notes/8-4.md) +> - [Redis 8.6](/content/operate/rc/changelog/version-release-notes/8-6.md) +> +> - You must upgrade the target database in an [Active-Passive](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive) setup before you upgrade the source database to prevent compatibility issues. ## Upgrade database @@ -47,7 +46,7 @@ To upgrade a single-region Redis Cloud database: {{< image filename="/images/rc/database-version-upgrade.png" alt="The Redis version upgrade screen." width=80% >}} - If your database has not been backed up before, we recommend that you back up your database. Select **Go to backup** to go to the [backup settings]({{< relref "/operate/rc/databases/back-up-data" >}}). + If your database has not been backed up before, we recommend that you back up your database. Select **Go to backup** to go to the [backup settings](/content/operate/rc/databases/back-up-data.md). 1. Select **Upgrade Now** to start the upgrade. @@ -62,19 +61,19 @@ You can continue to use the Redis Cloud console for other tasks during the upgra Automatically reverting to a previous Redis database version is not supported on Redis Cloud. -If you [backed up your database]({{< relref "/operate/rc/databases/back-up-data" >}}) before you upgraded your database version, you can: +If you [backed up your database](/content/operate/rc/databases/back-up-data.md) before you upgraded your database version, you can: -1. [Delete your database]({{< relref "/operate/rc/databases/delete-database" >}}) without deleting your subscription. -1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription with the following settings: +1. [Delete your database](/content/operate/rc/databases/delete-database.md) without deleting your subscription. +1. [Create a new database](/content/operate/rc/databases/create-database/create-pro-database-existing.md) in your subscription with the following settings: - **Port number**: Use the same port number as the old database. - **Version**: Select the original version of Redis. -1. [Import the backup files]({{< relref "/operate/rc/databases/import-data" >}}) into the new database. +1. [Import the backup files](/content/operate/rc/databases/import-data.md) into the new database. This allows you to connect to the database on the previous version without changing your connection details in your application. If you did not back up your database before upgrading: -1. [Back up your database]({{< relref "/operate/rc/databases/back-up-data" >}}). -1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription and select the original version of Redis. -1. [Import the backup files]({{< relref "/operate/rc/databases/import-data" >}}) into the new database. +1. [Back up your database](/content/operate/rc/databases/back-up-data.md). +1. [Create a new database](/content/operate/rc/databases/create-database/create-pro-database-existing.md) in your subscription and select the original version of Redis. +1. [Import the backup files](/content/operate/rc/databases/import-data.md) into the new database. 1. Change connection details in your application from the old database to the new database. \ No newline at end of file diff --git a/content/operate/rc/databases/view-edit-database.md b/content/operate/rc/databases/view-edit-database.md index 7f53b39840..8a90c6c305 100644 --- a/content/operate/rc/databases/view-edit-database.md +++ b/content/operate/rc/databases/view-edit-database.md @@ -25,13 +25,13 @@ To view the details of a database: The **Database** screen lets you review: - Configuration details of a database - Graphs showing performance metrics -- Recent activity via a "[slowlog]({{< relref "/commands/slowlog" >}})," which lists queries that exceed a certain execution time. +- Recent activity via a "[slowlog](/content/commands/slowlog.md)," which lists queries that exceed a certain execution time. For help changing database settings, see [Edit database details](#edit-database-details). ## Configuration tab -The **Configuration** screen is divided into sections, each dedicated to a specific category. Note that not every section or setting is available to every [subscription plan]({{< relref "/operate/rc/subscriptions/" >}}). +The **Configuration** screen is divided into sections, each dedicated to a specific category. Note that not every section or setting is available to every [subscription plan](/content/operate/rc/subscriptions/_index.md). The Configuration tab is organized differently for Essentials and Pro databases. Select your plan type below. @@ -47,11 +47,11 @@ The **Performance & availability** section defines the plan and backup settings | Setting name | Editable | Description | |---|---|---| -| **Plan** | ✅ Yes | The plan for your database.

Your Essentials plan determines the size of your database and other limits. For a comparison of available plans, see [Redis Cloud Essentials plans]({{< relref "/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details" >}}). | -| **High Availability** | ✅ Yes | Whether and how your data replicates across multiple nodes; see [available options]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) | -| **Data persistence** | ✅ Yes | Defines whether (and how) data is saved to disk; see [available options]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) | -| **Remote backup** | ✅ Yes | When enabled, identifies a location and interval for [data backups]({{< relref "/operate/rc/databases/back-up-data" >}}). | -| **Data eviction policy** | ✅ Yes | Configures which [policy]({{< relref "/operate/rc/databases/configuration/data-eviction-policies" >}}) is applied when your database reaches its memory limit | +| **Plan** | ✅ Yes | The plan for your database.

Your Essentials plan determines the size of your database and other limits. For a comparison of available plans, see [Redis Cloud Essentials plans](/content/operate/rc/subscriptions/view-essentials-subscription/essentials-plan-details.md). | +| **High Availability** | ✅ Yes | Whether and how your data replicates across multiple nodes; see [available options](/content/operate/rc/databases/configuration/high-availability.md) | +| **Data persistence** | ✅ Yes | Defines whether (and how) data is saved to disk; see [available options](/content/operate/rc/databases/configuration/data-persistence.md) | +| **Remote backup** | ✅ Yes | When enabled, identifies a location and interval for [data backups](/content/operate/rc/databases/back-up-data.md). | +| **Data eviction policy** | ✅ Yes | Configures which [policy](/content/operate/rc/databases/configuration/data-eviction-policies.md) is applied when your database reaches its memory limit | ### Access @@ -62,7 +62,7 @@ The **Access** section shows the connection information for your database. Here, you can: - View the number of active connections to your database. - View the Public endpoint of your database. -- Select **Connect** to [connect to your database]({{< relref "/operate/rc/databases/connect" >}}) +- Select **Connect** to [connect to your database](/content/operate/rc/databases/connect/_index.md) ### Data @@ -70,8 +70,8 @@ In the **Data** section, you can: The Data section for an Essentials database. -- [Import data]({{< relref "/operate/rc/databases/import-data" >}}) into your database -- Open [Redis Insight]({{< relref "/operate/rc/databases/connect/insight-cloud" >}}) to explore your data. +- [Import data](/content/operate/rc/databases/import-data.md) into your database +- Open [Redis Insight](/content/operate/rc/databases/connect/insight-cloud.md) to explore your data. ### Security @@ -81,9 +81,9 @@ The **Security** section helps you control access to your database. | Setting name | Editable | Description | |---|---|---| -| **Default user** | ✅ Yes | When **On**, permits access using the `default` username with a simple password. Select **Configure** to turn off the default user or change the password. See [Default user]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) for more information. | -| **CIDR allow list** | ✅ Yes | [Allow list]({{< relref "/operate/rc/security/cidr-whitelist.md" >}}) of IP addresses/security groups permitted to access the database. Select **Configure** to edit the CIDR allow list. | -| **Transport layer security (TLS)** | ✅ Yes | Select **Configure** to turn on [transport layer security]({{< relref "/operate/rc/security/database-security/tls-ssl.md" >}}) (TLS) encryption for database access. | +| **Default user** | ✅ Yes | When **On**, permits access using the `default` username with a simple password. Select **Configure** to turn off the default user or change the password. See [Default user](/content/operate/rc/security/access-control/data-access-control/default-user.md) for more information. | +| **CIDR allow list** | ✅ Yes | [Allow list](/content/operate/rc/security/cidr-whitelist.md) of IP addresses/security groups permitted to access the database. Select **Configure** to edit the CIDR allow list. | +| **Transport layer security (TLS)** | ✅ Yes | Select **Configure** to turn on [transport layer security](/content/operate/rc/security/database-security/tls-ssl.md) (TLS) encryption for database access. | ### Database info @@ -97,10 +97,10 @@ The **Database info** section defines basic properties about your database. | **ID** | ❌ No | The database's numeric ID | | **Creation** | ❌ No | Date the database was created | | **Last changed** | ❌ No | Date of last update | -| **Advanced Capabilities** | ❌ No | This setting appears when an [advanced capability]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) is enabled for a database | -| **Architecture** | ❌ No | Shows whether the database runs in **RAM** or is a [**Flex**]({{< relref "/operate/rc/databases/create-database/create-flex-database" >}}) database | +| **Advanced Capabilities** | ❌ No | This setting appears when an [advanced capability](/content/operate/rc/databases/configuration/advanced-capabilities.md) is enabled for a database | +| **Architecture** | ❌ No | Shows whether the database runs in **RAM** or is a [**Flex**](/content/operate/rc/databases/create-database/create-flex-database.md) database | | **Version** | ✅ Yes | The Redis version your database uses | -| **Protocol** | ✅ Yes | Shows which version of RESP the database uses. See [Redis serialization protocol]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) for details | +| **Protocol** | ✅ Yes | Shows which version of RESP the database uses. See [Redis serialization protocol](/content/develop/reference/protocol-spec.md#resp-versions) for details | -tab-sep- @@ -116,19 +116,19 @@ The available settings vary according to your cloud provider and design choices. |:--------------------------|:---------|:------------| | **Database Name** | ✅ Yes | The name given to your database | | **Subscription Name** | ❌ No | The name for the subscription your database is a part of | -| **Public endpoint** | ❌ No | Public URI used by any application or client to access the database. You can [block the public endpoint]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}). | +| **Public endpoint** | ❌ No | Public URI used by any application or client to access the database. You can [block the public endpoint](/content/operate/rc/security/database-security/block-public-endpoints.md). | | **Private endpoint** | ❌ No | Private endpoint URI available to approved clients; use CIDR allow list, VPC peering, or other connectivity options to enable access. | -| **Tags** | ✅ Yes | A list of the [tags]({{< relref "/operate/rc/databases/tag-database" >}}) associated with the database. Select [Manage tags]({{< relref "/operate/rc/databases/tag-database#configuration-tab" >}}) to manage the database tags. | +| **Tags** | ✅ Yes | A list of the [tags](/content/operate/rc/databases/tag-database.md) associated with the database. Select [Manage tags](/content/operate/rc/databases/tag-database.md#configuration-tab) to manage the database tags. | | **Vendor** | ❌ No | The Cloud vendor hosting your database: AWS, Google Cloud, or Azure. | | **Region** | ❌ No | The Cloud vendor region hosting your database | | **Type** | ❌ No | Displays 'Redis', 'Redis Stack' or 'memcached' based on the value selected when the database was created | | **Redis version** | ❌ No | Redis version of the database | | **Auto Tiering** | ❌ No | Checked when the subscription supports Auto Tiering | -| **Active-Active Redis** | ❌ No | Checked when the database is part of an [Active-Active]({{< relref "/operate/rc/databases/active-active" >}}) relationship | +| **Active-Active Redis** | ❌ No | Checked when the database is part of an [Active-Active](/content/operate/rc/databases/active-active/_index.md) relationship | | **Creation time** | ❌ No | Date and time the database was created | | **Last changed** | ❌ No | Date and time of last update | -| **Supported Protocol(s)** | ✅ Yes | Shows which version of RESP the database uses. See [Redis serialization protocol]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) for details | -| **Advanced Capabilities** | ❌ No | This setting appears when an [advanced capability]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) is enabled for a database | +| **Supported Protocol(s)** | ✅ Yes | Shows which version of RESP the database uses. See [Redis serialization protocol](/content/develop/reference/protocol-spec.md#resp-versions) for details | +| **Advanced Capabilities** | ❌ No | This setting appears when an [advanced capability](/content/operate/rc/databases/configuration/advanced-capabilities.md) is enabled for a database | ### Performance section @@ -138,14 +138,14 @@ The **Performance** section describes the memory size, throughput, and hashing p | Setting name | Editable | Description | |:----------------------|:---------|:------------| -| **Dataset size** | ✅ Yes | Maximum size (in GB) for your dataset. See [Dataset size]({{< relref "/operate/rc/databases/configuration/sizing#dataset-size" >}}). | -| **Throughput** | ✅ Yes | Defines [throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) in terms of maximum operations per second for the database. | +| **Dataset size** | ✅ Yes | Maximum size (in GB) for your dataset. See [Dataset size](/content/operate/rc/databases/configuration/sizing.md#dataset-size). | +| **Throughput** | ✅ Yes | Defines [throughput](/content/operate/rc/databases/configuration/sizing.md#throughput) in terms of maximum operations per second for the database. | | **Memory used** | ❌ No | Memory currently used for your database. | -| **High availability** | ✅ Yes | Replicates your data across multiple nodes; see [available options]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) | -| **Hashing policy** | ✅ Yes | Defines the [hashing policy]({{< relref "/operate/rc/databases/configuration/clustering#manage-the-hashing-policy" >}}). | -| **OSS Cluster API** | ✅ Yes | Enables the [Cluster API]({{< relref "/operate/rc/databases/configuration/clustering#oss-cluster-api" >}}) for a database.

When this option is enabled, you cannot define a custom hashing policy.| +| **High availability** | ✅ Yes | Replicates your data across multiple nodes; see [available options](/content/operate/rc/databases/configuration/high-availability.md) | +| **Hashing policy** | ✅ Yes | Defines the [hashing policy](/content/operate/rc/databases/configuration/clustering.md#manage-the-hashing-policy). | +| **OSS Cluster API** | ✅ Yes | Enables the [Cluster API](/content/operate/rc/databases/configuration/clustering.md#oss-cluster-api) for a database.

When this option is enabled, you cannot define a custom hashing policy.| -To learn more about these settings and when to use them, see [Sizing]({{< relref "/operate/rc/databases/configuration/sizing" >}}) and [Database clustering]({{< relref "/operate/rc/databases/configuration/clustering" >}}). +To learn more about these settings and when to use them, see [Sizing](/content/operate/rc/databases/configuration/sizing.md) and [Database clustering](/content/operate/rc/databases/configuration/clustering.md). ### Durability section @@ -155,10 +155,10 @@ The Durability section helps protect your data when problems occur. These setti | Setting name | Editable | Description | |:-------------------------|:---------|:------------| -| **Data persistence** | ✅ Yes | Defines whether (and how) data is saved to disk; see [available options]({{< relref "/operate/rc/databases/configuration/data-persistence" >}}) | -| **Data eviction policy** | ✅ Yes | Configures which [policy]({{< relref "/operate/rc/databases/configuration/data-eviction-policies" >}}) is applied when your database reaches its memory limit | -| **Remote backup** | ✅ Yes | When enabled, identifies a location and interval for [data backups]({{< relref "/operate/rc/databases/back-up-data" >}}). | -| **Active-Passive Redis** | ✅ Yes | When enabled, identifies a path to the [linked database]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}). | +| **Data persistence** | ✅ Yes | Defines whether (and how) data is saved to disk; see [available options](/content/operate/rc/databases/configuration/data-persistence.md) | +| **Data eviction policy** | ✅ Yes | Configures which [policy](/content/operate/rc/databases/configuration/data-eviction-policies.md) is applied when your database reaches its memory limit | +| **Remote backup** | ✅ Yes | When enabled, identifies a location and interval for [data backups](/content/operate/rc/databases/back-up-data.md). | +| **Active-Passive Redis** | ✅ Yes | When enabled, identifies a path to the [linked database](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive). | ### Security section @@ -169,9 +169,9 @@ The **Security** section helps you control access to your database. |Setting name| Editable | Description | |:-----------|:---------|:------------| | **Default user** | ✅ Yes | When enabled, permits access using a simple password | -| **Default user password** | ✅ Yes | Password for default user. A default password is assigned to the database on creation and may be updated. If you [block the public endpoint]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}), you can also turn on passwordless authentication for the default user here. | -| **CIDR allow list** | ✅ Yes | [Allow list]({{< relref "/operate/rc/security/cidr-whitelist.md" >}}) of IP addresses/security groups permitted to access the database. | -| **Transport layer security (TLS)** | ✅ Yes | Enables [transport layer security]({{< relref "/operate/rc/security/database-security/tls-ssl.md" >}}) (TLS) encryption for database access. | +| **Default user password** | ✅ Yes | Password for default user. A default password is assigned to the database on creation and may be updated. If you [block the public endpoint](/content/operate/rc/security/database-security/block-public-endpoints.md), you can also turn on passwordless authentication for the default user here. | +| **CIDR allow list** | ✅ Yes | [Allow list](/content/operate/rc/security/cidr-whitelist.md) of IP addresses/security groups permitted to access the database. | +| **Transport layer security (TLS)** | ✅ Yes | Enables [transport layer security](/content/operate/rc/security/database-security/tls-ssl.md) (TLS) encryption for database access. | ### Alerts section @@ -180,7 +180,7 @@ The **Alerts** section defines notification emails sent to your account and the The Alerts section defines the notification emails and their triggering conditions. -The available alerts vary according to the plan type. See [Configure alerts]({{< relref "/operate/rc/databases/monitor-performance#configure-metric-alerts" >}}) for more information. +The available alerts vary according to the plan type. See [Configure alerts](/content/operate/rc/databases/monitor-performance.md#configure-metric-alerts) for more information. ### Danger zone @@ -190,10 +190,10 @@ Actions in the **Danger Zone** are permanent and should not be taken lightly. Here, you can: -- Delete the database. Databases must be active before they can be deleted. To learn more, see [Delete a database]({{< relref "/operate/rc/databases/delete-database.md" >}}). +- Delete the database. Databases must be active before they can be deleted. To learn more, see [Delete a database](/content/operate/rc/databases/delete-database.md). - Flush the database (_Active-Active databases only_). -For best results, we recommend [backing up data]({{< relref "/operate/rc/databases/back-up-data" >}}) before any danger zone actions. +For best results, we recommend [backing up data](/content/operate/rc/databases/back-up-data.md) before any danger zone actions. {{< /multitabs >}} @@ -201,11 +201,11 @@ For best results, we recommend [backing up data]({{< relref "/operate/rc/databas The **View Database** screen also has tabs that let you view: -- **Metrics**: a series of graphs showing database performance over time. See [Monitor performance]({{< relref "/operate/rc/databases/monitor-performance" >}}) for more information. +- **Metrics**: a series of graphs showing database performance over time. See [Monitor performance](/content/operate/rc/databases/monitor-performance.md) for more information. -- **Slowlog**: a log showing recent [slow queries]({{< relref "/commands/slowlog" >}}) run against your database. The log displays when the action started, the duration, the complexity of the operation, and any parameters passed to the operation. +- **Slowlog**: a log showing recent [slow queries](/content/commands/slowlog.md) run against your database. The log displays when the action started, the duration, the complexity of the operation, and any parameters passed to the operation. -- **Alerts** (_Essentials databases only_): the notification emails sent to your account and the conditions that trigger them. See [Configure alerts]({{< relref "/operate/rc/databases/monitor-performance#configure-metric-alerts" >}}) for more information. +- **Alerts** (_Essentials databases only_): the notification emails sent to your account and the conditions that trigger them. See [Configure alerts](/content/operate/rc/databases/monitor-performance.md#configure-metric-alerts) for more information. ## Edit database details