failed at milestone 6000/9267 ?
-
[STEP] [2021-01-23 05:42:00] Initializing backup…
[INFO] [2021-01-23 05:42:00] Backup & Migration version: 1.0.7
[INFO] [2021-01-23 05:42:00] Site which will be backed up: https://www..com
[INFO] [2021-01-23 05:42:00] PHP Version: 7.0.33
[INFO] [2021-01-23 05:42:00] Web server: Apache
[INFO] [2021-01-23 05:42:00] Max execution time (in seconds): 86400
[INFO] [2021-01-23 05:42:00] Checking if backup dir is writable…
[INFO] [2021-01-23 05:42:00] Initializing custom error handler
[INFO] [2021-01-23 05:42:00] Premium plugin is enabled and activated
[SUCCESS] [2021-01-23 05:42:00] Yup it is writable…
[STEP] [2021-01-23 05:42:01] Scanning files…
[STEP] [2021-01-23 05:42:07] Checking free space, reserving…
[INFO] [2021-01-23 05:42:07] Requires at least 3542450186 bytes.
[INFO] [2021-01-23 05:42:07] Disk free space function is not disabled – using…
[SUCCESS] [2021-01-23 05:42:07] There is 45,095.73 MB free.
[SUCCESS] [2021-01-23 05:42:07] Great! We have enough space.
[SUCCESS] [2021-01-23 05:42:07] Confirmed, there is more than enough space, checked: 3542450186 bytes
[INFO] [2021-01-23 05:42:07] Scanning done – found 9267 files…
[SUCCESS] [2021-01-23 05:42:07] Backup initialized…
[STEP] [2021-01-23 05:42:07] Initializing archiving system…
[SUCCESS] [2021-01-23 05:42:07] Archive system initialized…
[STEP] [2021-01-23 05:42:07] Preparing map of files…
[SUCCESS] [2021-01-23 05:42:07] Files prepared.
[INFO] [2021-01-23 05:42:07] Starting compression process…
[STEP] [2021-01-23 05:42:07] Smart memory calculation…
[INFO] [2021-01-23 05:42:07] There is 256 MBs of memory to use
[SUCCESS] [2021-01-23 05:42:07] Setting the safe limit to 64 MB
[STEP] [2021-01-23 05:42:07] Making database backup
[INFO] [2021-01-23 05:42:07] Iterating database…
[SUCCESS] [2021-01-23 05:59:39] Database backup finished
[STEP] [2021-01-23 05:59:39] Making archive
[INFO] [2021-01-23 05:59:39] Compressing…
[INFO] [2021-01-23 05:59:39] Using PclZip to create Backup (forced)
[INFO] [2021-01-23 06:00:46] Milestone: 1000/9267
[INFO] [2021-01-23 06:01:37] Milestone: 2000/9267
[INFO] [2021-01-23 06:02:41] Milestone: 3000/9267
[INFO] [2021-01-23 06:04:49] Milestone: 4000/9267
[INFO] [2021-01-23 06:07:38] Milestone: 5000/9267
[INFO] [2021-01-23 06:13:06] Milestone: 6000/9267
[DOWNLOAD GENERATED] File downloaded on (server time): 2021-01-23 09:18:46
[DOWNLOAD GENERATED] Last update (seconds): 9188 seconds ago
[DOWNLOAD GENERATED] Last update (date): 2021-01-23 06:45:38
-
Following-up on above —
Parallel to using Backup-Migration I was also trying All In 1 Backup and WP Clone tools.
All In 1 Backup had worked before when the site size was only ~ 2GB, but now that site is ~ 6GB AI1 tool kept randomly failing, possibly also due to hitting 508 Resource Limit lockouts imposed by WP host; did not investigate. AI1 tech support suggested I upgrade to $99 extended version to handle 6GB. I did not try this as WP Clone tool succeeded in completing a backup before I could buy and try.
WP Clone free version hung several times during attempted backups (no doubt also because of hitting 508 Resource Limits), but several times it did complete the process and then listed URLs to the backed-up files (which are wisely in zip format). I entered one of the URLs into the destination new site (being migrated to), and everything worked perfectly except for one tiny thing — the style of the permalinks was messed up so badly that no links worked. I changed the style to /year/month/post-title and boom, everything is working perfectly.
WPClone did what I needed. If it breaks in the future I will try your suggestion first and probably follow-up here.
Script timeout on the WP host server was not the problem; rather, the WP hosting company has some other limitations in-place, probably something to do with requests to database per second and/or total bytes transferred. Something mysterious and annoying like that — *the* primary reason the client is leaving that hosting company.
I should point out that a very nice feature of your backup tool is its output of specific and detailed log information as a standard practice. This is quite welcome and is far above the near-total lack of feedback/info given by all other backup/restore tools I’ve tried. Also, the interface is nice — sleek and simple, but with immediate access / pull-down ability to get to some important advanced features…I didn’t need those features, but it’s good to see software written by ‘old-school’ minds for the same.
1. Because I was able to migrate the first site using another tool, I removed/deinstalled both free and pro versions of backup-backup from the first site.
2. Subsequently I received via email the latest zip (1.0.7.992) of backup-backup for both the free and also pro versions; I installed both on a new site that needs migration. (thank you, this was very nice, made me feel not forgotten)
3. For reference, I used AllIn1 to create a backup .wpress file that is 3.5 GB and sits on this new site.
4. During install of 1.0.7.992 pro version of backup-backup on new site it insisted my license of one live seat would be exceeded by my current installation request on new site, even though (per 1. above) I had deactivated/removed backup-backup from first site. [IMHO, for this you need a website where customers can go and revoke / recover their license(s) from any outstanding installs and thus allow easy move from site to site.]
5. Meanwhile, I went with AllIn1 pro US$70 lifetime pay once. Per 3. it backed up a 3.5GB file and is currently importing 20% done onto fresh WP install. I will be back to try a third time backup-backup if AllIn1 fails.
6. I also looked at BlogVault, which seems unduly complex, involved, and seems to seek a kind of tech lock-in — at least I got that feeling, being constantly probed to give more info, pay more, not being able to quickly see my data and download it as a single file, constant hype of cloud storage (which also means someone else controls my data), etc. Because BV claims so many biggies as clients, I will look at them again as fall-back in due diligence, if AllIn1 fails and I’m unable to get backup-backup working.
Hello @brendendigital
Thank you for the feedback
Yesterday we released v1.0.8 which has 4 more backup techniques to pick.If your site don’t have shell functions blocked that can already backup 20 GB site with 80k+ files ??
Of course only if PHP CLI is supported by your server.
The process will take a lot of time but it can work in the background (so you can leave the site or even turn off your computer).In next version v1.0.9 we’re planning to add PHP CLI support for migration.
Which will allow to restore such a big backups without worries about server timeout.
+ On some web servers like Litespeed the download is timed out, we will also make solution for it so migration process will be able to work flawlessly ??Also as you’re the premium user you can always contact us via email, we will debug things for you and possibly create a special fix for sites like your ??
- The topic ‘failed at milestone 6000/9267 ?’ is closed to new replies.
