| 开发者 | vpssnaps |
|---|---|
| 更新时间 | 2026年9月9日 21:44 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
exec() is disabled, there is no mysqldump, and nobody can add a cron job.
Backups are written to your own cloud storage (S3, Cloudflare R2, Backblaze B2,
DigitalOcean Spaces, Wasabi, or any S3-compatible bucket). The plugin never holds your
storage credentials: it asks VPS Snaps for a short-lived, single-object upload link each
time it needs one, so a break-in on this site cannot reach the rest of your bucket.
What this plugin sends to an external service
This plugin requires an account at vpssnaps.com and does not work
without one. There is a free tier that covers one site, one backup job and one storage
destination, which is everything this plugin needs; paid plans exist for people running
more than one site. Nothing in this plugin is switched on or off by which plan you are on.
You paste a site token from your dashboard into the plugin, and the plugin then talks to
https://vpssnaps.com to:
No. That is the point of this plugin. If your host does let you add a real cron job,
pointing one at wp-cron.php makes scheduling more reliable — see below.
Not exactly. WordPress runs scheduled tasks when someone visits the site rather than on a
clock, so on a quiet site a check can run late or be skipped. Treat backup times as
approximate. A real cron job calling wp-cron.php every minute removes the guesswork.
In the bucket you configured in your VPS Snaps account. You keep ownership and access.
Not in this version.