As the hosting operator, enable the intended snapshot access and guide your customer through requesting a manual recovery point before planned work. Verify its final status before relying on it as a usable recovery point.

Customer steps: request the intended snapshot

1. Open the service’s Snapshots page.
2. Review existing entries and any operation already running.
3. Choose Take snapshot and enter a recognisable label where offered.
4. Read the confirmation and submit once.
5. Follow the request under Activity, then refresh the snapshot list.
6. Confirm the intended snapshot reaches its available state.

Check the offering’s snapshot control and whether the affected service allows changes. A queued request or an entry marked creating is not a completed backup. Do not keep requesting duplicates just because creation is still in progress.

Understand manual and automated recovery

Manual snapshots and the provider’s automated backup history are different. The module’s list should not be treated as an exhaustive backup inventory; Lightsail’s module snapshot list contains manual snapshots, while automated recovery is handled through its provider workflow.

The module’s customer page does not provide a Restore button merely because a snapshot exists. Use recovery planning with your AWS administrator to establish the recovery resource, endpoint and service tracking.

Check retention before relying on a snapshot

Module termination can remove matching module-owned manual snapshots and automated backup history, and does not automatically create a final snapshot. A manual snapshot visible here is not an independent copy protected from that cleanup.

Before deleting or terminating anything, verify the required recovery copy and its scope with your database administrator.

See the PD AWS MySQL Blesta guide for related tasks, or explore PD AWS MySQL.