All Products
Search

This Product

    Tair (Redis® OSS-Compatible):Clone data from an instance that runs Redis 2.8 to an instance that runs Redis 5.0

    Document Center

    Tair (Redis® OSS-Compatible):Clone data from an instance that runs Redis 2.8 to an instance that runs Redis 5.0

    Last Updated:Oct 24, 2024

    Tair（Redis OSS-compatible） instances that run Redis 2.8 can be directly upgraded to run Tair 5.0. However, if you want to validate the upgrade against your current business logic in Tair 5.0, you can refer to this topic to clone the backup data of an instance that runs Tair 2.8 to a new instance that runs Tair 5.0.

    Background information

    With the development of Tair（Redis OSS-compatible） and advancements in open source Redis technology, the Redis open source community no longer maintains Redis 2.8. Starting July 31, 2024, Tair（Redis OSS-compatible） is also scheduled to discontinue full support for instances that run Tair 2.8. If you continue to use Tair 2.8 after July 31, 2024, significant risks may occur.

    Note

    Given the same specifications and architecture, the cost of an instance that runs Tair 5.0 is the same as that of an instance that runs Tair 2.8.

    Procedure

    1. In the upper part of the Instances page, select the region of the ApsaraDB for Redis instance that runs Tair 2.8 and click the ID of the instance.

    2. In the left-side navigation pane, click Backup and Recovery.

    3. Clone the instance based on the instance architecture.

      Non-cluster architecture

      Find the backup set that you want to use. In most cases, the latest backup set is used. Then, click Recovery in the Action column.

      Cluster architecture

      If the instance uses the cluster architecture, select the backup sets of all shards of the instance. For example, if you have a cluster instance that has four shards, you must select the following backup sets:

      • r-bp1vhgd6dzgu89****-db-0

      • r-bp1vhgd6dzgu89****-db-1

      • r-bp1vhgd6dzgu89****-db-2

      • r-bp1vhgd6dzgu89****-db-3

      Then, click Recovery in the upper-left corner.

    4. In the message that appears, read the prompt and click OK.

    5. On the Clone Instance page, configure the required parameters. The parameters displayed in the console prevail.

      • Set the Version parameter to Redis 5.0.

        Note

        You can also select an ApsaraDB for Redis Enhanced Edition (Tair) DRAM-based instance, which delivers performance three times that of an ApsaraDB for Tair Community Edition instance that has the same specifications.

      • The new instance specifications must be greater than or equal to the original instance specifications.

      Use the default values for other parameters.

    6. Read and select the Tair terms of service.

    7. Click Buy Now.

      After you complete the payment, wait for 1 to 5 minutes. Then, you can view the new instance created based on the data of the instance that runs Tair 2.8 in the ApsaraDB for Tair console.

    What to do next

    • After the instance is cloned, you can migrate your business to the new instance. You only need to add the IP address of your client to a whitelist of the new instance and update the endpoint in the code. For more information, see Configure whitelists and View endpoints.

    • You can also release the instance and directly upgrade the major version of the original instance from Tair 2.8 to Tair 5.0. After the upgrade, the instance ID, endpoint, data, and whitelist settings remain unchanged. For more information, see Upgrade the major version.

    References