Expiration and Renewal

This document details the expiry rules, renewal procedures, and alert mechanisms for VPS instances and their associated resources. Properly managing the resource lifecycle is crucial for ensuring business continuity and data security.

Alert Mechanism

The system proactively notifies you of resource status changes through the following alerts. It is essential to keep your contact information up-to-date and to check these notifications promptly.

Alert Type	Trigger Time	Delivery Channels
Upcoming Expiry Alert	7 days before resource expiry	In-app message, Email
Expiry Alert	On the resource expiry date	In-app message, Email

We recommend regularly checking resource expiry dates in your console and confirming your contact email is correct, so you don't miss any important updates.

Renewal Management

1. Manual Renewal

You can manually extend the service duration of a resource at any time before it expires.

Log into the server console. In the left navigation pane, select VPS or Disk.
From the resource list or details page, click the Renew button.

2. Auto-Renewal

Log into the server console. In the left navigation pane, select VPS or Disk.
In the resource list, toggle the Auto-Renewal switch for the desired resource.

Once enabled, the system will automatically process payment for renewal to prevent service interruption.

Payment Rules:

The system will begin automatic payment attempts 3 days before the resource expires.
Attempts will continue until payment is successful or the resource expires.
Payments are sourced from your account credit.

Renewal Scope:

Auto-renewal for a VPS instance includes: CPU, memory, system disk, bandwidth/data transfer, and public IP.
Auto-renewal for a Data Disk must be configured separately. Please locate the corresponding Disk in the Disk list within the console to manage its settings.

Please ensure your account has sufficient credit after enabling Auto-Renewal to avoid resource expiration due to failed payment.

Instance Resource Expiry

Before a resource expires, it is recommended that you renew it promptly to avoid data and business loss. The post-expiry handling of relevant resources is as follows:

Resource Type	Within 7 Days After Expiry	7 Days After Expiry
Instance (vCPU, Memory, System Disk, Public IP)	Instance resources (vCPU, memory, system disk, IP) are retained, but the instance is suspended. If renewed successfully within this period, the instance will resume operation.	Compute resources (vCPU, memory, system disk, IP) are released. All configurations and data (system disk data, associated Snapshots) are permanently deleted and irrecoverable.
Data Disk	Automatically detached from the instance and cannot be mounted to any instance. If renewed successfully within this period, the Disk can be reattached and will return to normal use.	The Data Disk is released. All data is permanently deleted and irrecoverable.

Snapshot Expiry

A Snapshot's lifecycle is determined by the retention period set at creation. It will be cleared upon expiry, and operations such as "renewal" or "extending the retention period" are not currently supported.
To retain the data, you must manually create a new Snapshot before the original one expires and set a new retention period.
To avoid losing data backups due to snapshot expiration, it is essential to:

Plan retention periods appropriately: Set a sufficient number of retention days based on the importance of your data and backup strategy (e.g., retain monthly backups for over 30 days, retain critical operation backups for longer).
Perform regular checks: Regularly review the expiry dates of important Snapshots on the instance's snapshot list page and create new replacement Snapshots in advance.