Backups move out of the plugin directory, where a plugin update used to delete them.\nExisting archives are carried over automatically when the files were replaced by hand.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3650163,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3650163,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3650163,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3650163,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3650163,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3650163,"resolution":"1","location":"assets","locale":"","width":1280,"height":1010},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3650163,"resolution":"2","location":"assets","locale":"","width":1280,"height":877},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3650163,"resolution":"3","location":"assets","locale":"","width":1280,"height":559},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3650163,"resolution":"4","location":"assets","locale":"","width":1280,"height":774},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3650163,"resolution":"5","location":"assets","locale":"","width":1280,"height":761},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3650163,"resolution":"6","location":"assets","locale":"","width":1280,"height":2126},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3650163,"resolution":"7","location":"assets","locale":"","width":1280,"height":684},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3650163,"resolution":"8","location":"assets","locale":"","width":1280,"height":839}},"screenshots":{"1":"The dashboard: one verdict on whether the site is protected, and the shortcut that fixes what is missing.","2":"The Backup Manager: every archive with its size, its origin and what the last integrity check concluded.","3":"Starting a backup, with the size the archive is expected to reach.","4":"The restore wizard: choosing the restore point, before anything is written.","5":"Scheduled backups: the hour each task starts at, its retention rule, and when it next runs.","6":"Security: what encryption covers, the keyring, and the master password that lets an archive travel.","7":"Settings: what deleting the plugin does to your archives \u2014 nothing, unless you say so.","8":"Logs: every journal the plugin keeps of its own work, ready to be read or cleared."}},"plugin_section":[],"plugin_tags":[151,12167,4155,152,264458],"plugin_category":[59],"plugin_contributors":[268121],"plugin_business_model":[],"class_list":["post-350181","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-encryption","plugin_tags-migration","plugin_tags-restore","plugin_tags-scheduled-backups","plugin_category-utilities-and-tools","plugin_contributors-digipacket","plugin_committers-digipacket"],"banners":{"banner":"https:\/\/ps.w.org\/digipacket\/assets\/banner-772x250.png?rev=3650163","banner_2x":"https:\/\/ps.w.org\/digipacket\/assets\/banner-1544x500.png?rev=3650163","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/digipacket\/assets\/icon.svg?rev=3650163","icon":"https:\/\/ps.w.org\/digipacket\/assets\/icon.svg?rev=3650163","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-1.png?rev=3650163","caption":"The dashboard: one verdict on whether the site is protected, and the shortcut that fixes what is missing."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-2.png?rev=3650163","caption":"The Backup Manager: every archive with its size, its origin and what the last integrity check concluded."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-3.png?rev=3650163","caption":"Starting a backup, with the size the archive is expected to reach."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-4.png?rev=3650163","caption":"The restore wizard: choosing the restore point, before anything is written."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-5.png?rev=3650163","caption":"Scheduled backups: the hour each task starts at, its retention rule, and when it next runs."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-6.png?rev=3650163","caption":"Security: what encryption covers, the keyring, and the master password that lets an archive travel."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-7.png?rev=3650163","caption":"Settings: what deleting the plugin does to your archives \u2014 nothing, unless you say so."},{"src":"https:\/\/ps.w.org\/digipacket\/assets\/screenshot-8.png?rev=3650163","caption":"Logs: every journal the plugin keeps of its own work, ready to be read or cleared."}],"raw_content":"\n
Digipacket Backup Toolkit copies your files and your database into a single Everything runs on your own server. The plugin makes no outbound connection<\/strong>,\nhas no account, no telemetry and no paid tier hidden behind a button.<\/p>\n\n Shared hosting kills long requests. Every operation here is therefore cut into\nslices that fit inside In The folder is protected by an The plugin needs PHP 8.2, WordPress 6.8, and the No. The plugin makes no outbound connection of any kind. Your archives stay on your\nserver until you download them yourself.<\/p><\/dd>\n Open Backup Toolkit \u2192 Scheduled Backups<\/strong>. If the screen says WP-Cron is not firing,\nthat is the answer: WordPress only runs scheduled work when a request comes in,\nand it triggers that work through a request the server makes to itself. A local\ninstall, a firewall or an HTTP password blocks it, and nothing ever runs.<\/p>\n\n The fix is a real cron. Add to then, every five minutes:<\/p>\n\n Check the timezone too. The Next run<\/strong> tile is written on the site's clock, in\nSettings \u2192 General<\/strong>, which is not always the one on your wall.<\/p><\/dd>\n Two reasons, usually together. First, a new schedule fires one full interval after\nyou create it \u2014 a daily task runs in 24 hours, not tonight. The Next run<\/strong> column\ntells you exactly when. Second, WP-Cron only wakes up when someone loads a page, so\non a site with no traffic nothing happens until your next visit. For a dependable\nschedule, disable WP-Cron and call Yes. Pick Every day<\/strong> or Every week<\/strong>, then fill Start at<\/strong> \u2014 and for a\nweekly one, tick the days. The hour is the one on your site's clock, and it stays\nthat hour when the clocks change.<\/p>\n\n Leave it empty and the frequency behaves as a plain interval: a daily task\ncreated at 14:07 runs at 14:07 the next day.<\/p><\/dd>\n The notice names the cause itself. The full account is in Backup Toolkit \u2192 Logs<\/strong>,\njournal One cause looks like a failure but is not: if a backup was already running when\nthe schedule fired \u2014 a manual one whose tab was closed keeps the engine busy for\nup to an hour \u2014 the task simply waits and starts on its own within minutes. It\nis not marked failed and its next run is not pushed to tomorrow.<\/p><\/dd>\n The safety snapshot. Before a restore writes anything, the plugin takes a complete\nbackup of the site as it stands, so a failure can be undone. It is a normal backup,\nmarked \"Safety copy\" in the library. It is never deleted automatically \u2014 delete it\nyourself once you are satisfied the restore worked.<\/p><\/dd>\n No, and neither can anyone else. That is what encryption means. The keyring in\n storage\/keys\/keyring.json opens the archives sealed on this site; back it up\nsomewhere safe, or set a master password so an archive can travel to another site.<\/p><\/dd>\n Yes. Import the archive on the other site, then restore it. If the archive is\nencrypted and the other site does not have your keyring, the import pauses and asks\nfor the master password instead of failing.<\/p><\/dd>\n No. Uninstalling removes nothing by default. There is a setting to opt into a full\ncleanup, and it is off unless you turn it on.<\/p><\/dd>\n Nginx never reads If you moved the storage with the .dpbackup<\/code>\narchive, puts that archive back when you need it, and can seal it with AES-256-GCM\nso a stolen copy is worth nothing without your key.<\/p>\n\nBuilt for hosts that cut you off<\/h4>\n\n
max_execution_time<\/code> and resume where they stopped \u2014 the\nfile scan, the SQL dump, the compression, the encryption, the extraction and the\nrow-by-row replay of the database. A 100,000-file site is backed up and restored\nwith flat memory, in as many requests as it takes.<\/p>\n\nWhat it does today<\/h4>\n\n
\n
wp-content<\/code>, plugins, themes or uploads.\nProgress is reported live, with the size, the duration and the checksum of the archive.<\/li>\nWhere your backups live<\/h4>\n\n
wp-content\/digipacket-backups\/<\/code>, outside the plugin directory \u2014 because\nWordPress deletes a plugin's own folder before installing a new version, and a\nbackup plugin that stored its archives there would destroy them at every update.<\/p>\n\n.htaccess<\/code> and a silent index.php<\/code>, both written\nat activation. Nginx ignores .htaccess<\/code>, so on Nginx the equivalent rule has to\nbe added by hand \u2014 see the FAQ below. The digipacket_wp_backup_storage_path<\/code>\nfilter moves the whole thing anywhere you like, including outside the web root,\nwhich is stronger than any web server rule.<\/p>\n\nWhat it does not do<\/h4>\n\n
\n
\n
zip<\/code> and openssl<\/code> PHP extensions.\nIf any of these is missing it stays inert and explains why in a notice, rather than\nfailing with an error.<\/p>\n\n\n\n
Are my backups sent anywhere?<\/h3><\/dt>\n
The task says Active, the hour has passed, and nothing ran.<\/h3><\/dt>\n
wp-config.php<\/code>:<\/p>\n\ndefine('DISABLE_WP_CRON', true);\n<\/code><\/pre>\n\ncurl -s https:\/\/example.com\/wp-cron.php?doing_wp_cron > \/dev\/null\n<\/code><\/pre>\n\nMy scheduled backup never ran. Why?<\/h3><\/dt>\n
wp-cron.php<\/code> from a real system cron.<\/p><\/dd>\nCan I choose the hour a scheduled backup runs at?<\/h3><\/dt>\n
My scheduled backup says it failed. Where do I see why?<\/h3><\/dt>\n
schedule<\/code>, and in the task's own History<\/strong> \u2014 the \u22ee menu of its row.<\/p>\n\nWhat is this pre_restore_\u2026 file?<\/h3><\/dt>\n
I lost my master password. Can you recover my archives?<\/h3><\/dt>\n
Can I restore a backup on a different site?<\/h3><\/dt>\n
Does deleting the plugin delete my backups?<\/h3><\/dt>\n
I run Nginx. How do I protect the backup folder?<\/h3><\/dt>\n
.htaccess<\/code>, so the guard the plugin writes has no effect there.\nAdd this to your server { }<\/code> block, before the generic location ~ \\.php$<\/code> block,\nthen reload with nginx -t && systemctl reload nginx<\/code>:<\/p>\n\nlocation ~* \/wp-content\/digipacket-backups\/ { deny all; return 403; }\n<\/code><\/pre>\n\ndigipacket_wp_backup_storage_path<\/code> filter, use\nyour own path in that rule. Better still, point the filter at a directory outside\nthe document root \u2014 \/var\/backups\/digipacket\/<\/code>, readable and writable by the PHP\nuser \u2014 and no web server rule is needed at all, because there is no URL that can\nreach the archives.<\/p><\/dd>\n