Recover resource

This document provides a guide for resource recovery, describing in detail the steps involved in managing resources and the costs associated with resource recovery. Some steps will be simplified and only mentioned as part of the process.

Resource recovery feature applies to

• Target: Prepaid users.

• Source of money: VNG Cloud wallet or other sources (via payment gateway).

• Resources: All resources belonging to VNG Cloud products.

Resource recovery process

Users can only recover resources when:

The resource has expired for no more than n days and has been moved to the trash before being permanently deleted: Depending on the regulations of each product, resources may exist in the trash for 3 or 7 days. The resource has been deleted (by the user or the system) and has been moved to the trash within 7 days before being permanently deleted: Depending on the processing mechanism of each product, resources may be permanently deleted or moved to the trash when the user actively deletes the resource.

Resource Recovery Steps

• Step 1: Select the resource to recover.

  • 1.1 Access the vServer, vStorage, vMonitor product pages.

  • 1.2 Select the resource to recover in the trash on the product page.

  • 1.3 Confirm resource recovery to proceed to payment: At this point, the system will redirect the user to the resource payment page.

• Step 2: Resource Payment -> See detailed instructions here.

• Step 3: Check resource and payment information .

  • 3.1 Check resource information on the product page.

  • 3.2 Check payment information, and invoice at User Portal: https://dashboard.console.vngcloud.vn/

• Step 4: System Implementation

  • Email notification of the recovered resource information.

  • New invoice corresponding to the resource usage time.

Why do we need to recover resources?

Basically, recovering expired resources is similar to creating new resources.

However, when recovering expired resources, users can skip the step of selecting resource configurations because the system will default to retaining the previous configuration of the resource before expiration. This helps to speed up the resource creation process compared to having to reconfigure from scratch.