| 开发者 | nagarajdev |
|---|---|
| 更新时间 | 2026年10月13日 00:23 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-config.php is never included, because it holds your site's security keys. The scan screen tells you this before each backup.wp-config.php and BackupScope's own settings are kept.wp-config.php), the connection status shows when it was last tested, and you choose whether to keep the copy on your server.Yes. BackupScope Free creates, verifies and lets you download full backups of your files and database. It has no time limit and needs no account.
Scheduled backups, restore with a safety backup, off-site copies to S3-compatible storage, backup history and retention, email notifications with secure download links, Storage Analytics with automatic monitoring and alerts, Media review and Safe Cleanup. See "Why upgrade to BackupScope Pro?" above for details.
No. BackupScope Pro includes the same backup engine and works on its own. When you activate Pro, it switches the free plugin off and keeps your backups and settings, so you can delete the free plugin afterwards.
Nothing is deleted or locked. Your existing backups stay available to download and restore. Scheduled backups, off-site uploads, updates and support stop until you renew.
Yes. Full Backup includes your files and your database. Custom Backup lets you choose.
Not with one click. BackupScope Free creates and verifies your backup. To restore manually:
files/wordpress/ to your web root (and any folders under files/external/, as listed in manifest.json).database/database.sql into an empty database with phpMyAdmin, Adminer or the mysql command line tool.wp-config.php. On a new host, create one from wp-config-sample.php with the new database details and fresh keys from https://api.wordpress.org/secret-key/1.1/salt/.wp search-replace), not a plain text replace.No. wp-config.php is never put into a backup, wherever it is stored, so its authentication keys and salts never leave your server. Other PHP files in the WordPress folder that mention a key or salt (for example a separate salts file loaded by wp-config.php) are left out too. BackupScope only checks file names and text for this; it never reads, copies or changes the key values. Each file left out is listed in the backup's manifest.json under files.excluded. When you restore, keep your existing wp-config.php, or create a new one from wp-config-sample.php.
In wp-content/uploads/backupscope/. The folder is protected from direct web access (.htaccess and web.config deny rules plus empty index files), and every backup file has a long random name. Downloads require an administrator login. Some servers, such as Nginx, ignore those rules, so after each backup BackupScope checks whether the folder can be reached from the internet and warns you if it can. You can choose your own folder outside the website by adding define( 'BACKUPSCOPE_STORAGE_DIR', '/path/outside/your/site' ); to wp-config.php.
So you can see how many files and how much space the backup needs before it starts, and so BackupScope can choose the best method for your server.
Yes. The work is split into short, resumable steps, so server time limits do not stop it, and archives above 5 GB are written with a streaming ZIP64 engine. Keep the page open while it runs; if it is interrupted, you can resume. Your server still needs enough free disk space for the archive.
Temporary files are removed and your previous backup is kept.
The latest one. Your previous backup is deleted only after the new backup has been created and verified.
Stored backups are deleted too, because they contain sensitive data. Download your backup first. To keep backup files when deleting the plugin, add define( 'BACKUPSCOPE_KEEP_BACKUPS_ON_UNINSTALL', true ); to wp-config.php.
Not in this version.