Site backups
BackupsWe copy your files and database. We lock the copy. Pro and Shield Care copy every day. Basic copies once a week. A site not linked to the Hub copies every day on this computer. We keep 14 daily copies on Pro, 30 on Shield Care, and 2 weekly copies on Basic.
We copy every file in wp-content, your site settings file, and the whole database. Big photo files are included. After the first copy, we only send files that changed. The first automatic copy starts in a few minutes, or click Copy now.
We keep 14 daily copies on Pro, 30 on Shield Care, and 2 weekly copies on Basic. A site not linked to the Hub keeps 14 copies on that computer. Older copies are removed.
Restore puts this copy back on the linked site. First we show what would change. A safety copy is saved on the site before anything is overwritten. Download is your locked copy. The link stops working in 15 minutes.
Copies stay encrypted. We lock the copy before it leaves this host. A copy on the same computer does not count as Protected. Protected means a checked locked copy sits in an S3-compatible bucket (Amazon S3, Cloudflare R2, or Backblaze B2) inside the keep window.
You can paste bucket keys in Hub Backups. We lock those keys. Click Show to see them. Server environment keys (BSH_BACKUP_S3_*) still work and win if set. We never write keys to logs or git.
We never delete the last good offsite copy when a new copy fails. If this computer looks dirty, restore the Hub offsite copy taken before the hack. Restore needs a working Hub link.
Needs a bucket and keys. An attacker who also has those keys is out of scope. First Protected needs a successful run. This is not a substitute for host patching.