- This topic has 14 replies, 2 voices, and was last updated 10 years ago by udadmin.
-
Posts
-
Wow it was taking a long time and both cores on my server was going 100% for hours! It’s super slow to upload. I guess because it’s using apache.
The backup has 6 big data .zip files. It uploaded not all the 1st one stop at about 1.5 GB. It’s should’ve been about 2 GB zip.
On both my server I can use samba. As I typed this I drag and drop the 2 GB to the same place from updraft where it should go. It only took about 3 minutes to upload it like that!
Can only guess it error uploading with UpdraftPlus because it took so long and the hard drive went to sleep. Not sure.
Can see it only takes about 16 minutes to upload the rest of the big backup .zip files in that photo.
Guess with UpdraftPlus it would of been more then 24 hours with both cores of the CPU going 100%
Got a little LCD screen on my server and got this photo of htop when updraftplus was uploading.
Not sure if there is a better faster way to upload with in WordPress. That don’t take a lot of CPU power and time.
-Raymond Day
Hi Ray,
Please can you post the backup log file? (Find it on the “Existing Backups” tab – each backup has a log button). Use pastebin.com or something similar to post it, as it’ll be too long for this forum.
I would imagine that UD hadn’t actually reached the uploading stage yet – because, uploading does not use any significant CPU resources. It’s the creating of the zips that uses CPU and disk I/O, as files are read, written and compressed (which is unavoidable with a zip-based backup – see: https://updraftplus.com/faqs/how-much-resources-does-updraftplus-need/ ).
Best wishes,
DavidP.S. I notice from the screenshot that you’ve put the ‘split’ size up to 2Gb. The link in my previous post explains why this will very significantly increase CPU and disk I/O usage.
Best wishes,
DavidHi Ray,
The SFTP file storage method doesn’t use chunked/resumable uploads (because these weren’t available in the PHP SFTP library). As a result, the PHP timeout on your webserver has to be high enough to upload 100% of the zip archive before the timeout hits.
You can work around this by any of these:
a) increasing the PHP timeout
or
b) reducing the ‘split’ size in the expert section at the bottom of the ‘Settings’ tab, to produce smaller zip files
or
c) switch to a remote storage method that supports chunked/resumable uploading: these include: FTP, FTPS, S3, Dropbox, Rackspace, Google Drive, Copy.Com.Best wishes,
DavidDon’t get why it all ways stop uploading on the 1ST backup .zip file and it takes hours and a lot of CPU time to do it.
I just heard my CPU fan going a lot on my server. So I did htop to see why. It was updraftplus doing it’s backup.
Got this photo to show that.
I got this script that can back up my WordPress very fast. In like 3 minutes make the backup of my database and and upload folder to my WordPress. The upload folder has a lot of photos and videos in it so it’s big.
Here is the script and I bet others would like it.
#!/bin/bash #Variables name_base=<code>date +"%Y-%m-%d"</code> #define name base for archive off of date backupdir="/media/USBdisk2-3TB/home/part2/mystuff/WordPress_Backup" contentdir="/usr/share/wordpress/wp-content/uploads/" #Start backup tar cvf WordPress_Data-$name_base.tar $contentdir mysqldump -u root --password=########## --databases wordpress > $backupdir/WordPress_Data-$name_base.sql #Create tar file #Add mysql dump to archive tar -rvf $backupdir/WordPress_Data-$name_base.tar $backupdir/WordPress_Data-$name_base.sql #Cleanup rm $backupdir/WordPress_Data-$name_base.sqlAt the top can just change that for other servers and it will work.
I just need to make it so it saves to my other LAN sever that will be easy.
Can log in to it with out having a password in the script because I did a long key on it to both just easy 2 commands like this:
ssh-keygen -t rsa cat /root/.ssh/id_rsa.pub | ssh [email protected] "mkdir -p ~/.ssh && cat >> /root/.ssh/authorized_keys"Have to change that a little too like the IP for others.
Then have to get it to only save like 2 or so backups and delete the old backups.
Seems like this is a better faster way to do a backup of WordPress.
I guess in a few days my have that script so it does the 2 other things I said. Seems a lot better then updraftplus.
Can just have a cron job run this script every 24 hours.
-Raymond Day
I set the upload chunk form 2000 to 500 and now looks like it’s working!
Clicked to start the backup and looks like it auto started a new one. Looks like it will finish this time.
I guess I could put the size to 1500 because that’s seems when it errored on the big .zip files. But to be on the save side I guess 1300 by be good.
Just don’t like it that it has to put a backup’s in a lot of files if it could just be one file.
All so I put my big key in the log in. So it don’t show my root password on there.
The key is stored at:
/root/.ssh/id_rsa file.
I removed the Begin and end RSA Private key lines.
-Raymond Day
Hi Ray,
I’ve emailed you a new version of UpdraftPlus which adds support for chunking/resuming for SFTP. Please give it a try, and let me know how you get on.
David
Hi Ray,
Great – glad it worked for you!
Waiting until scheduled time to retry because of errors
When you see this, it’s best to wait until the job gives a final finishing state. UpdraftPlus has various re-try strategies, to try to overcome temporary conditions.
Best wishes,
David
- The topic ‘It could not upload it all!’ is closed to new replies.