upgrade Redis enterprise

Glenn Maxwell 10,146 Reputation points
2024-03-12T00:45:24.0633333+00:00

Hi All

I am new to Azure Redis Enterprise, i have an existing Azure Redis Enterprise setup running with the configuration Enterprise 4 GB (1 x 4 GB). I have a requirement to upgrade it to E10 12GB cache memory with 2 VMs(Capacity). Please guide me how to achieve this as i am not aware and does this configuration change requires any reboot. please guide me.

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
216 questions
{count} votes

Accepted answer
  1. ShaktiSingh-MSFT 13,436 Reputation points Microsoft Employee
    2024-03-12T04:03:21.2633333+00:00

    Hi Glenn Maxwell •,

    Welcome to Microsoft Q&A forum.

    As I understand, you want to upgrade your Enterprise Azure Cache for Redis from 4 GB (1 x 4 GB) to E10 12GB cache memory with 2 VMs(Capacity).

    In the Enterprise and Enterprise Flash tiers of Azure Cache for Redis, we recommend prioritizing scaling up over scaling out. Prioritize scaling up because the Enterprise tiers are built on Redis Enterprise, which is able to utilize more CPU cores in larger VMs.

    Enterprise and Enterprise Flash tiers are inherently clustered, in contrast to the Basic, Standard, and Premium tiers. The implementation depends on the clustering policy that is selected. The Enterprise tiers offer two choices for Clustering Policy: OSS and Enterprise. OSS cluster policy is recommended for most applications because it supports higher maximum throughput, but there are advantages and disadvantages to each version.

    Refer: https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-best-practices-enterprise-tiers

    Steps for Scaling via Azure Portal:

    To scale your cache, browse to the cache in the Azure portal and select Scale from the Resource menu.

    Screenshot showing Scale selected in the Resource menu for an Enterprise cache.

    To scale up, choose a different Cache type and then choose Save.

    Screenshot showing the Enterprise tiers in the working pane.

    To scale out, increase the Capacity slider. Capacity increases in increments of two. This number reflects how many underlying Redis Enterprise nodes are being added. This number is always a multiple of two to reflect nodes being added for both primary and replica shards.

    Screenshot showing Capacity in the working pane a red box around it.

    While the cache is scaling to the new tier, a Scaling Redis Cache notification is displayed.

    Screenshot showing notification of scaling an Enterprise cache.

    When scaling is complete, the status changes from Scaling to Running.

    Steps for Scaling via Azure Powershell:

    You can scale your Azure Cache for Redis instances with PowerShell by using the Update-AzRedisEnterpriseCache cmdlet. You can modify the Sku property to scale the instance up. You can modify the Capacity property to scale out the instance. The following example shows how to scale a cache named myCache to an Enterprise E20 (25 GB) instance with capacity of 4.

    Update-AzRedisEnterpriseCache -ResourceGroupName myGroup -Name myCache -Sku Enterprise_E20 -Capacity 4

    Steps for Scaling via Azure CLI:

    To scale your Azure Cache for Redis instances using Azure CLI, call the az redisenterprise update command. You can modify the sku property to scale the instance up. You can modify the capacity property to scale out the instance. The following example shows how to scale a cache named myCache to an Enterprise E20 (25 GB) instance with capacity of 4.

    az redisenterprise update --cluster-name "myCache" --resource-group "myGroup" --sku "Enterprise_E20" --capacity 4

    Refer https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-scale?tabs=scale-up-and-down-with-basic-standard-and-premium for prerequisites, limitations and more details.

    Hope this helps.

    Let us know if you have further queries.

    Thanks.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Dr. S. Gomathi 630 Reputation points MVP
    2024-03-12T02:48:04.2233333+00:00

    Hi Glenn,

    Upgrading your Azure Redis Enterprise cache involves a few steps and considerations. The process is designed to be as smooth as possible, usually without significant downtime, but it's essential to plan and understand the implications, especially regarding configuration changes and potential reboots. Here’s a guide to help you through the upgrade process:

    1. Pre-Upgrade Steps
    • Backup Your Data: Always start with a backup of your data. Azure Redis Enterprise supports data persistence, so you can export your dataset before making changes.
    • Review Documentation: Check the latest Azure and Redis Enterprise documentation for any specific instructions or recommendations regarding upgrades.
    • Plan for Downtime (if applicable): While Azure Redis Enterprise is designed to handle upgrades with minimal disruption, it's wise to plan for a short maintenance window, just in case. Inform your users if you anticipate any performance impact or brief downtime.
    1. Upgrading Your Redis Enterprise Cache

    To upgrade your Azure Redis Enterprise cache to a larger or more powerful plan (e.g., from Enterprise 4GB to E10 12GB with 2 VMs), follow these steps:

    Azure Portal Method:

    Log in to the Azure Portal: Go to the Azure Portal and log in with your credentials.

    Navigate to Your Redis Cache: Find your Redis Enterprise cache by searching for "Redis" in the top search bar or by finding it under “All resources.”

    Open Redis Enterprise Resource: Click on your Redis Enterprise cluster to open its overview page.

    Scaling: Look for a scaling option in the menu, which might be under "Settings" or directly available as an option like "Scale," "Size," "Pricing tier," or similar.

    Select New Configuration: Choose the new configuration you desire (E10 12GB cache memory with 2 VMs in your case). The interface will show you the different options available, including VM size, memory capacity, and pricing.

    Apply Changes: Once you've selected the new configuration, confirm any changes and agree to any pricing adjustments. Azure will begin the process of scaling your Redis cache.

    Azure CLI:

    If you prefer using the Azure CLI, you can also resize your Redis Enterprise cluster using the command line. The general command structure for updating a Redis cache (modifying properties like size) looks like this:Upgrading your Azure Redis Enterprise cache involves a few steps and considerations. The process is designed to be as smooth as possible, usually without significant downtime, but it's essential to plan and understand the implications, especially regarding configuration changes and potential reboots. Here’s a guide to help you through the upgrade process:

    1. Pre-Upgrade Steps
    • Backup Your Data: Always start with a backup of your data. Azure Redis Enterprise supports data persistence, so you can export your dataset before making changes.
    • Review Documentation: Check the latest Azure and Redis Enterprise documentation for any specific instructions or recommendations regarding upgrades.
    • Plan for Downtime (if applicable): While Azure Redis Enterprise is designed to handle upgrades with minimal disruption, it's wise to plan for a short maintenance window, just in case. Inform your users if you anticipate any performance impact or brief downtime.
    1. Upgrading Your Redis Enterprise Cache

    To upgrade your Azure Redis Enterprise cache to a larger or more powerful plan (e.g., from Enterprise 4GB to E10 12GB with 2 VMs), follow these steps:

    Azure Portal Method:

    Log in to the Azure Portal: Go to the Azure Portal and log in with your credentials.

    Navigate to Your Redis Cache: Find your Redis Enterprise cache by searching for "Redis" in the top search bar or by finding it under “All resources.”

    Open Redis Enterprise Resource: Click on your Redis Enterprise cluster to open its overview page.

    Scaling: Look for a scaling option in the menu, which might be under "Settings" or directly available as an option like "Scale," "Size," "Pricing tier," or similar.

    Select New Configuration: Choose the new configuration you desire (E10 12GB cache memory with 2 VMs in your case). The interface will show you the different options available, including VM size, memory capacity, and pricing.

    Apply Changes: Once you've selected the new configuration, confirm any changes and agree to any pricing adjustments. Azure will begin the process of scaling your Redis cache.

    Azure CLI:

    If you prefer using the Azure CLI, you can also resize your Redis Enterprise cluster using the command line. The general command structure for updating a Redis cache (modifying properties like size) looks like this:

    az redis enterprise database update --cluster-name <your-cluster-name> --resource-group <your-resource-group-name> --name <your-database-name> --client-protocol <protocol> --clustering-policy <policy> --eviction-policy <policy> --persistence <persistence> --port <port-number> --modules <module-settings>

    You'll need to customize this command according to your specific requirements, including the desired capacity and any other parameters you wish to configure.

    1. Post-Upgrade Considerations
    • Monitoring: After the upgrade, monitor your Redis Enterprise cache closely for any performance changes or issues.
    • Testing: Validate that your application is functioning correctly with the newly scaled resources.

    Reboot Requirements

    Upgrading your plan should not typically require a manual reboot of your Redis instances. Azure Redis Enterprise is designed to handle these changes with minimal disruption. However, it's possible that under certain circumstances or for specific configurations, a reboot might be necessary. Azure will manage this as smoothly as possible, but you should monitor your service and be prepared.

    If the answer helped, or pointed you in the right direction, please click accept answer or please share more information to help you better.

    Regards,

    Dr. Gomathi S

    0 comments No comments