Overview

Introduction

Yearly/Monthly MAS instances cannot run after their subscription expires. To continue using them, renew your subscription within the specified period. Otherwise, your instance resources will be deleted, and your data will be lost and cannot be restored.

Only yearly/monthly MAS instances can be renewed. Pay-per-use MAS instances can run as long as you have sufficient account balance.

If your subscription is renewed before it expires, all resources are retained and your MAS instances are not affected. For details about the status of a MAS instance after it expires, see Impact of Expiration.

Renewal

Table 1 describes how to renew MAS instances.

You can renew your subscription across the lifecycle of your yearly/monthly MAS instance, as shown in Figure 1.

Figure 1 Lifecycle of a MAS instance

• A MAS instance is in the Running state from the time when it is purchased to the time when it expires.
• After the instance expires, its status changes to Expired.
• If the instance is not renewed upon expiration, it enters the grace period. If it is not renewed after the grace period ends, the status changes to Frozen.
• If you do not renew your subscription after the grace period ends, your instance enters the retention period. If you do not renew the subscription within the retention period, your instance will be automatically deleted.

Both the grace and retention periods are 15 days.

Auto-renewal can be enabled anytime before a MAS instance expires. The system attempts to automatically renew the instance at 03:00 seven days before the instance expires. If the fee deduction fails, there will be one attempt at 03:00 every day until the instance expires or the renewal is successful. By default, fees are deducted seven days before your subscription expires. You can change this deduction date as required.