When an ApsaraDB for Redis instance expires or has overdue payments, the instance may not be able to run normally. If you want to continue using the instance, renew the instance or enable auto-renewal for the instance.

Impacts of expiration and overdue payments

Warning The system sends notifications to you when an instance expires or has overdue payments. To avoid service suspension, we recommend that you renew the instance at the earliest opportunity.
When an ApsaraDB for Redis instance expires or has overdue payments, the instance is handled based on the amount of time elapsed since the expiration date and the billing method of the instance. The following table describes how the instances are handled.
Table 1. Subscription instances
Time elapsed since the expiration date Description
Day 1 to day 15 The instance runs normally.
Day 16 to day 30 The instance is in the Disabled state and cannot be accessed. If you want to continue using the instance, you must renew the instance in a timely manner. For more information, see Manually renew an instance.
Note
  • If the instance is in the Disabled state, the subscription duration starts from the time when you renew your instance. For example, if your instance expires on April 10, 2021 and you renew the instance on April 15, 2021 to extend the service for one month, the expiration date of the instance is extended to May 15, 2021.
  • If you do not renew an expired instance within the specified time period, the data stored in the instance may be lost. To prevent data loss, you can enable the auto-renewal feature for an instance after you purchase the instance.
Day 31 to day 37

The instance is in the Released state. You are notified with a text message or an email. Data is retained for the next eight days. If you want to continue using the instance, you can restore the instance from the recycle bin. When you restore the instance from the recycle bin, ApsaraDB for Redis creates an instance by replicating the data of the original instance. For more information, see Manage ApsaraDB for Redis instances in the recycle bin.

Day 38
The instance is permanently deleted. The data that is stored in the instance cannot be restored.
Warning To retain the data in the instance, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.
Table 2. Pay-as-you-go instances
Time elapsed since the expiration date Description
Day 1 to day 15 The instance runs normally.
Day 16 to day 30 The instance is in the Disabled state and cannot be accessed. While the instance is in this state, billing of the instance is suspended.

If you want to continue using the instance, make sure that you have sufficient balance within your account. Billing is resumed after you top up your account and settle the overdue payments.

Day 31 to day 37

The instance is in the Released state. You are notified with a text message or an email. Data is retained for the next eight days. If you want to continue using the instance, you can restore the instance from the recycle bin. When you restore the instance from the recycle bin, ApsaraDB for Redis creates an instance by replicating the data of the original instance. For more information, see Manage ApsaraDB for Redis instances in the recycle bin.

Day 38
The instance is permanently deleted. The data that is stored in the instance cannot be restored.
Warning To retain the data in the instance, you must renew the instance before it is deleted. Otherwise, the data cannot be restored.

Renewal overview

The renewal feature is applicable only to subscription instances. Pay-as-you-go instances do not need to be renewed, but you must make sure that you have sufficient balance within your account to cover relevant costs.

  • Auto-renewal (recommended)

    To prevent your instance from being automatically released if you forget to renew the instance, we recommend that you enable auto-renewal for the instance.

    After you enable auto-renewal for an instance, the instance is automatically renewed before the expiration date. Make sure that you have sufficient balance within your account. If an auto-renewal attempt fails seven days before the expiration date, you are notified with a text message or an email.
    Note If an auto-renewal attempt fails because you do not have sufficient balance within your account, the instance expires and the system does not initiate another auto-renewal attempt. In this case, you must manually renew the instance before the instance is automatically released.
  • Manual renewal

    You can manually renew an instance at a point in time before the instance expires.

For more information, see Renew an instance.