As the hosting operator, you choose whether your customers can use snapshot recovery. This guide explains what the client-area Restore action does and how your team can check the result. It replaces the current server system with the selected manual snapshot; it does not open a separate preview of an old backup.

Understand the effect first

PD AWS Lightsail rebuilds the server from the selected snapshot. Changes on the system disk after that snapshot are replaced. Arrange a suitable maintenance window and preserve any current data you still need before starting.

If the service has an extra storage disk, the module moves that disk across in its current state; it does not roll it back to the snapshot time. Plan application and database recovery accordingly, particularly when their data is split across the system disk and the extra disk.

An existing static IP is moved to the replacement server. Without a static IP, check the resulting public address and any DNS or external connections that depend on it after the operation. Do not promise uninterrupted service during a restore.

Prepare access and explain the customer steps

Before directing a customer to recovery, check Client: Snapshots in the offering’s module settings and confirm the intended service has snapshot controls. Agree the recovery point and maintenance window with your customer. The client-area steps are:

1. Sign in to the WHMCS client area and open the correct Lightsail service.
2. Open Snapshots for that service.
3. Check the name, creation time and available state of the intended manual snapshot.
4. Choose its Restore action and read the confirmation. Continue only when you intend to replace the current server system.
5. Submit the request once. Follow the service state and Activity while the replacement is prepared.
6. Wait for the operation to finish before trying another restore, reinstall or plan change.

Verify recovery

Check the service’s running state, current address and connection details. Sign in through the permitted access method, then verify the application itself: expected files, database state, services and any attached storage. A server reporting Running does not establish that the application has recovered correctly.

If an address changed, update the relevant external configuration only after confirming the correct new address. Keep your recovery notes and snapshot reference until the result has been checked.

Check a restore that has paused or failed

As the hosting operator, open the affected service under PD Modules → PD AWS Lightsail → Clients & Services and read Activity for the requested restore. Record its status, the last reported step, the selected snapshot and the request time.

Compare that information with the instances, snapshot and any attached extra disk you can see in your own AWS account, in the service’s region. A browser request ending does not establish that replacement has finished. If the module still reports work in progress, follow that operation rather than starting a different recovery action or removing resources involved in it.

If a specific AWS permission or snapshot error is shown, check the named requirement in your account.

For preparation next time, use the manual snapshot guide.

See the PD AWS Lightsail WHMCS guide for related tasks, or explore the module.

Clients who need help with an unexplained module result can follow our reporting guide (client sign-in required).