Create Local Backups
Use manual local full, database, or files backups and review job status before update windows or risky maintenance.
Product docs
Backup & Restore Manager Documentation
Create and restore local WordPress backups with explicit confirmation, job history, local retention boundaries, and practical recovery planning.
Editorial trust
- Publisher
- WPlura Editorial Team
- Updated
- Topics
- Doc, Product Documentation
- Verified sources
- 1 references
Problem, cause, fix, verify
Problem
A local backup tool can support recovery, but it should not be presented as off-site disaster recovery unless that workflow is actually configured.
Why it matters
The free plugin stores local backups and keeps one retained slot per backup type.
Safe check
Install the free Backup & Restore Manager plugin before a risky update, migration, or maintenance window.
Verify
Review backup type, slot age, readiness notes, and confirmation requirements before the maintenance window.
On this page
Scope
A local backup tool can support recovery, but it should not be presented as off-site disaster recovery unless that workflow is actually configured.
For: Administrators and agencies responsible for site recovery and maintenance windows.
- The free plugin stores local backups and keeps one retained slot per backup type.
- Local backup availability depends on the WordPress host and filesystem.
- Off-site disaster recovery requires a separate verified workflow.
Quick Start
Set up the workflow in a safe order
- Step 1
Install the free Backup & Restore Manager plugin before a risky update, migration, or maintenance window.
- Step 2
Create the right local backup type: full-site, database-only, or files-only.
- Step 3
Confirm which retained local slot will be replaced before starting a new backup.
- Step 4
Review restore readiness before using any restore action.
- Step 5
Use cloud-managed recovery only when Web Plura Cloud, entitlement, and the Pro workflow are active.
Workflow
Setup and operating notes
Restore With Confirmation
Use explicit restore confirmation and job history so destructive recovery steps are deliberate and accountable.
Plan Beyond Local Storage
Document retention, off-site copies, restore testing, and recovery approvals separately from local plugin backup creation.
Tutorials
Detailed product walkthroughs
Create a local backup before an update
FreeUse a deliberate local backup routine before plugin, theme, core, content, or settings changes.
- 1Choose full-site, database-only, or files-only based on what is about to change.
- 2Check whether an existing retained local slot will be replaced.
- 3Run the backup and watch job progress instead of leaving the maintenance window undocumented.
- 4Review job history and storage visibility when the backup completes.
- 5Record where off-site copies or host-level backups live if the site needs disaster recovery.
Restore from a plugin-created local backup slot
FreeRecover deliberately by reviewing the slot, confirmation prompt, and affected site areas before restore.
- 1Open the Restore screen and confirm the available plugin-created local restore point.
- 2Read the restore readiness details before approving a destructive action.
- 3Confirm the restore explicitly; restore actions should never run silently.
- 4Check the site, admin, forms, checkout, and critical pages after completion.
- 5Escalate to managed recovery when local storage or host state is not enough.
Guides
How to use this documentation
Backup and recovery guide
Use local backups for immediate maintenance safety, then document off-site retention and restore testing separately.
Open related guideDisaster recovery checklist
A local backup slot is not the same as an off-site disaster recovery plan; business-critical sites need retention, approvals, and tested restore paths.
Open related guideCommon Problems
Issues this product helps organize
A local backup exists but restore confidence is low
Symptom: The team cannot explain what would happen during restore.
Resolution: Review backup type, slot age, readiness notes, and confirmation requirements before the maintenance window.
The retained local slot would be overwritten
Symptom: A new backup risks replacing the only recent local backup of that type.
Resolution: Confirm replacement deliberately and keep independent off-site copies when the site needs stronger recovery.
A failed local job needs retry
Symptom: Backup or restore work stopped before completion.
Resolution: Use the job history and resume/requeue flow where available instead of starting undocumented duplicate work.
FAQ
Answers before installation or escalation
Does Free include off-site cloud backup?
No. Free focuses on manual local backups, restore points, job history, storage visibility, and recovery readiness notes.
How many local backups does Free keep?
The documented Free behavior keeps one retained local slot per backup type.
Can restore actions run without confirmation?
No. Restore actions are designed around explicit administrator confirmation.
When is Pro appropriate?
Use Pro and Cloud when the site needs scheduled cloud backup, cloud restore, disaster recovery workflows, retention, approvals, or managed recovery coordination.
Free vs Pro
Capability boundaries
Free
Manual local backup, restore from plugin-created local slots, explicit confirmations, job history, storage visibility, and readiness notes are Free.
Pro
Cloud-managed backup, restore, disaster recovery, reports, and policy-governed workflows belong to Pro when connected and entitled.
Cloud
Web Plura Cloud owns account connection, entitlement, consent, policy summary, and cloud-managed backup or restore coordination.
Planned
Do not describe local backups as off-site disaster recovery unless that separate workflow is active and verified.
Verified Sources
Where these claims come from
Continue