WordPress maintenance serviceKey points
Four points for a sound decision
- The database and files may need different backup intervals.
- Backups on the same server do not provide sufficient protection against server or account compromise.
- Checksums, sizes and timestamps make transfers traceable.
- The latest verified recovery point must remain protected from automatic cleanup.
- 01Capture completely
- 02Transfer securely with encryption
- 03Verify integrity
- 04Verify the restore
Our own process illustration · not a generic vendor guarantee · the actual process depends on the website and service profile.
01
What must a WordPress backup contain?
The database contains posts, settings, orders and much plugin data. The file system holds uploads, themes, plugins and configuration files. The components required for a full restore depend on the hosting and architecture. The scope should therefore be explicitly described as a full backup or separate database/file backups.
An export without version context is difficult to verify. Every recovery point needs a creation time, scope, data volume, verification result and retention end date. In Kayba’s customer portal, only fully transferred and approved backup points are offered for recovery.
- Database included
- Uploads and required files included
- off-site storage destination
- Encryption in transit and at rest
- Integrity status and retention end date
02
How often should backups run and how long should they be kept?
The right interval depends on potential data changes. Daily backups may suffice for an information site that rarely changes. With a 24-hour interval, a shop or booking system could lose a whole working day. High frequency does not replace adequate retention: an unnoticed error may already exist in several recent copies.
Kayba therefore tiers intervals and retention by service profile. Care retains backups for 14 days, Business for 30 days and Premium for 60 days. The actual recovery point is chosen deliberately; the latest copy is not automatically the last healthy state.
03
How can you recognise a tested recovery process?
A responsible process separates selection, approval and execution. Before recovery, the website, point in time and potential data loss are confirmed. No second backup or restore process may modify the same data during execution. Technical and functional checks follow completion.
Kayba Operations keeps an auditable record of the selected backup point, operator, decision and execution status. Deleted backups remain immutably marked in the decision history; the file itself is no longer available after successful cleanup.
Review basis
Primary sources and our operational status
The technical principles were checked against the following vendor documentation on 10.09.2026. Plan values and Kayba processes come from our versioned service catalogue and operations system.
Sources support general product and operational principles. They are not endorsements or certification of Kayba by the named vendors.