Yearly/Monthly Billing
If you expect to use resources for a longer period, you can save money by selecting yearly/monthly billing. This section describes the billing rules for yearly/monthly DRS tasks.
Application Scenarios
- If you want to ensure resource stability over a certain period of time, yearly/monthly billing is a good choice.
- Real-time migration supports only the pay-per-use billing mode. Real-time synchronization and DR tasks support pay-per-use and yearly/monthly billing modes.
Billed Items
|
Billed Item |
Description |
|---|---|
|
Configuration fee |
Configuration fees are generated when you use compute and storage resources and process data. In yearly/monthly mode, you need to make upfront payments on a yearly or monthly basis. |
|
Data transmission fee |
Data transmission fees are generated when you process or transfer data through a public network (excluding VPN, VPC, Direct Connect, and CC networks). You are billed based on the actual public network traffic you use in GB. |
The prices in the figure are just examples. The actual prices are those displayed on DRS Price Calculator.
Billed Usage Period
A yearly/monthly task is billed for the purchased duration. The billing starts from when you activated or renewed the subscription, and ends at 23:59:59 of the expiry date.
It takes a certain time to create a DRS task. The billing starts from the Started time. You can view the Task Created time and Started time on the Basic Information page of a DRS task.
For example, if you purchased and started a one-month DRS task on March 08, 2023, 15:50:04, the billed usage period is from March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59.
Billing Examples
Suppose you purchased and started a one-month DRS task on March 08, 2023, 15:50:04, and renewed the subscription for one more month before the initial subscription expired. The following usage periods will be billed:
- March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59
- April 08, 2023, 23:59:59 to May 08, 2023, 23:59:59
You need to pay in advance for each billed usage period.
Price Change After Specification Change
If the specifications of a yearly/monthly DRS task no longer meet your needs, you can change the specifications on the console. The system will recalculate the price and either bill or refund you the difference.
- If you upgrade your task specifications, you need to pay the difference in price.
The price difference will be calculated as follows:
Price difference for the specification upgrade = Price for the new specifications × Remaining period - Price for the original specifications × Remaining period
- The prices in the example are only for reference. The actual prices are those displayed on DRS Price Calculator.
- DRS allows you to select and change specifications for some specified synchronization and DR tasks. For details, see Specification Description.
Impact of Expiration
Figure 1 shows the statuses a yearly/monthly task can go through throughout its lifecycle. After a task is purchased and started, it enters the valid period and runs normally during this period. If the task is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.
Expiration Reminder
The system will send you a reminder (by email, SMS, or in-app message) 7 days before a yearly/monthly task expires to remind you to renew the subscription.
Impact of Expiration
If your yearly/monthly task is not renewed after it expires, it changes to the Expired state and enters a grace period. During the grace period, you can access the DRS task but cannot perform operations such as changing task specifications.
If the yearly/monthly task is not renewed after the grace period ends, its status turns to Frozen and it enters a retention period. You cannot perform any operations on the task while it is in the retention period.
If the yearly/monthly task is not renewed by the time the retention period ends, it will be released and data cannot be restored.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
