When an ApsaraDB for Redis instance expires or has overdue payments, you can renew the instance to unlock it, delete the instance, or recreate the instance.

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 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 as expected.
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 at the earliest opportunity. For more information, see Procedure (manual renewal).
Note
  • If the instance is in the Disabled state, the subscription duration starts from the time that 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, then the instance expires on May 15, 2021.
  • If you do not renew an expired instance within the specified time period, the data stored on the instance may be lost. To prevent data loss, you can enable the auto-renewal feature after you purchase the instance.
Day 31 to day 37

The instance is in the Released state. You receive a text message or an email. Data is retained for 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 as expected.
Day 16 to day 30 The instance is in the Disabled state and cannot be accessed. When the instance is in this state, billing of the Redis instance is suspended.

If you want to continue using the instance, make ensure that your account has a sufficient balance. 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 receive a text message or an email. Data is retained for 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.