Use the PD DigitalOcean Droplets Rebuild control when you intend to replace the server’s main disk with its original operating system or an available manual snapshot. This is a destructive disk operation, not a preview of an older recovery point.

Prepare the recovery

Identify the correct service and the intended recovery source. Preserve current data you still need and arrange a maintenance window. Changes on the main disk after a snapshot will be replaced when restoring that snapshot.

Attached additional storage is not part of the Droplet snapshot. Do not assume the extra volume’s data rolls back with the main disk; coordinate application/database recovery across the storage you use.

Choose the intended source

Enable Client: Rebuild only for offerings where your customers should have this destructive control. The following steps describe the customer’s service view; agree the recovery source and maintenance window with your customer before the action.

1. Your customer signs in to the Blesta client area and opens the service’s Information tab.
2. Confirm that your offering allows Client: Rebuild and that no competing operation is in progress.
3. Open Rebuild and choose the original operating system for a fresh reinstall, or the intended available snapshot for recovery.
4. Read the data-replacement confirmation and continue only when that is the result you intend.
5. Submit once and follow the service state and Activity until completion.
6. Check the resulting server, connection details and application before considering recovery complete.

Rebuilding the existing Droplet retains its IP address. The module does not apply keys saved later on the service’s SSH Keys page during rebuild. A snapshot recovery replaces disk contents, so verify the login credentials and authorised keys available in that recovery point. Do not rebuild to try to install a newly saved team key.

Verify the application, not just Running

Check expected files, application/database state, network access and attached storage. A running server is not proof that the application recovered to the intended point. Check dependent services and the login method you use before handing it back.

Automated backup restoration is offered through Backups when enabled; see the backup guide for that source instead of assuming every backup appears as a manual snapshot.

If the operation stalls

Keep the selected source, request time and latest Activity result. Compare the corresponding action and server state using your own DigitalOcean access. Do not start another rebuild or delete the service to force progress. Repeated destructive operations can replace evidence and data needed for recovery.

See the PD DigitalOcean Droplets Blesta guide for related tasks, or explore the module.