Backups
Website backups for beginners: how many copies are enough?
A backup strategy answers three questions: what must be recoverable, how much recent work can be lost, and how far back you may need to restore. “A backup exists” is not enough information by itself.
Back up the data that actually changes
Website files may change infrequently while a store database changes with every order. Choose backup frequency based on the data you cannot easily recreate.
Keep more than one restore point
A corrupted site can be backed up successfully. Retention across several dates gives you a chance to restore from before the problem began.
Separate at least one copy from the live account
A backup stored only inside the same hosting account can be lost with the account or server. Off-site separation protects against a wider class of failures.
Test restoration before trusting the system
A green backup job is evidence that data was copied, not proof that the site can be restored. Periodic restore tests verify the process and the completeness of the copy.
Choose copies by failure scenario
One recent copy can help with an accidental edit but may not help if corruption or compromise went unnoticed for weeks. Keep enough restore points to cover the time it could realistically take to discover a problem.
Also separate at least one useful copy from the live account. A backup stored only beside the website can disappear with the same account, storage or access failure you were trying to recover from.
Common questions
How often should a beginner back up WordPress?
It depends on how frequently content and data change. A mostly static site can tolerate a longer interval than a busy store. Back up before risky changes even if an automatic schedule already exists.