Whole site backup is corrupting data
I had to restore numerious sites over the weekend due to a DNS issue with the company so we backed them up and this weekend during the restore of the sites we ran into time and time again where data was corrupt in the backup.
At first i thought it was just a flook and so i got that fixed and went to the next site same issue, and then the next had had the same issue. I have now done 4 sites and every one of the backups had some kind of corruption in it.
Things like:
image extentions .jp and not .jpg or .gi and not .gif and so on
html files with extentions .htm instead of .html
most of the corruption was just file extension stuff. But then we ran accross whole dir that were not backed up and files were totally empty.
And then we had sql files that had corrupted items in it such as this for example.
as you can see in the image the table insert line is totally messed up, and then in the example under that the code changes from green/black to red so something on that line is corrupted to cause that, the rest of the sql file is red.
And these are just the items that i found or caught via errors. How much stuff is out there that i didnt catch sitting in my db right now or in my sites?
Image below.
-
My 5th site i had to go thru the Wordpress install completely as there were .ph should be .php .j should be .js and .cs should be .css and there were so many files it took me about 1.5 hours to fix them all. and then the next site was so badly corrupted that i had to use a previous backup from a week before and it gave me no issue at all. So it appears that possibly the last cpanel update is doing this as my host updated recently. 0 -
I also just discovered that all this time 2+ years the backup has been overwriting my DDP subfolder with my ddp subfolder. If php knows the difference and http request knows the difference then why does the backup not know the difference? 0 -
Hello :) Do you have root access to this system? If so, were the backups completed automatically? Look for the backup logs in: /usr/local/cpanel/logs/cpbackup
Check the file that matches the date of the backup generation and review the log file for any particular error messages that indicate why the archives may have been corrupted. Thank you.0 -
Hi, thanks for the reply :) no sir, they were not done auto. I did them manually before i took the sites down. I will check for the logs but im sure those logs are gone because we had some dns issues and had to pretty much redo the whole server to fix the problem. If the logs are gone does that mean that the solution is lost? 0 -
The backup logs would have been helpful in determining what specifically prevented a successful backup generation. You may want to try generating new backups for the accounts and look to see if you can reproduce the previous problems, or if new backups generate successfully. Thank you. 0 -
Well as much as i would like to help track this down i just dont have the time, this would mean developing a entire test area to upload scripts from other backups and install the software to see if there are failures. I am sorry but i cannot devote time managment to that project. I feel i did my part, i told you all about database corruption, which i understand could be caused by certain issues within the server itself. But i also told you that it was not putting the last character every time on file extentions, (example ph for php j for js gi for gif and pn for png and jg for jpg and htm for html) as well as others. This last character issue did not happen all the time, but just with some files (totally random) because it was never the same file between one site restore or another. so there must be a way for you to trace that process and make sure your process is high and tight. I also informed you that the backups are seing ddp the same as DDP and that also can be tracked to a specific process within your software. I also informed you that this was not just one backup, it was a host of backup zips so it was not an isolated issue. Again i wish i had to the time and manpower but i dont, so i guess the information i have given you will either trickle down to the developers or it will not, that is not my call, i told you and thats all i can do. Thanks for your time... 0 -
It sounds like there may have been a resource limitation on the server that was preventing backups from generating successfully. The issues you are describing are not reproducible on test environments. The exception is that we may be able to reproduce the issue with your sub-directory and the capital letters. Could you provide some more details on this? For instance, you mentioned a directory was overwritten. Was this during a restore of an archive to an existing account? Note that you are welcome to submit a support ticket for any specific issue that you want us to take a closer look at. Thank you. 0
Please sign in to leave a comment.
Comments
7 comments