
WordPress backups: save files and the database
Create a matched WordPress recovery set, restore safely in staging, and check the pages and application tasks visitors depend on.
Read the 6-minute guideRecover beyond the hosting account.
A virtual private server often holds both replaceable software and unique application data. Separate the instance rebuild from the records you cannot recreate. Provider snapshots may serve one role; an independently stored application recovery set can address a different failure, such as losing access to the hosting account.
Identify the application’s write behavior before choosing a capture method. Coordinate data and uploads into a named set, and record any downtime or consistency requirements. Keep a verified copy outside the provider account when that boundary is part of your recovery goal.
Build a temporary instance using the runbook, restore the data, and perform a representative application task. Keep outbound jobs and customer-facing integrations disabled. Measure provisioning and verification as well as the archive download.
Not automatically. A snapshot’s consistency depends on the capture method and application state. Use the database’s supported procedure and test the resulting restore rather than inferring consistency from a successful snapshot operation.