Website hosed after backup

Hi,

My website is totally hosed after doing a backup and then restore. 

This is all you get now:

checkAction() fatal error. Unknown action ID: 0

The system says it was a successful restore - NOT!

ALSO - The Admin section looks like the photo attached after I tried to re-compile the languages.

No doubt your ownership's and permissions are not correct after restore.

 Was able to restore most of the site with a back-up I made from mysqladmin. Had to delete the crap one made by the Dolphin Back-up and use the one I made. Got the site back. But I would be careful using the Dolphin Back-up. Maybe it is just me - but it is not working.

 You didn't say that! I have never been able to make that work. 

I always do it manually.

Hi Newton,

Yeap saved the site with my handy-dandy simple backup program I made using the mysql backup I made manually. It will backup the whole site.

I got it from GoDaddy.com and made a few tweeks to run on any website.

I've attached it. You just need to change the password in the script and place it in your root. It zips your site (mine is about 90megs-zipped). But, it does use all the available ram on a VPS to do the zip. There does not seam to be any slow down of the site displaying cached pages.

See what you think, just tying to help when I can.

PS-FYI: I'm evaluating Dolphin and Jomsocial for a possible article and found this interesting comparison Dolphin with about 105megs of uploaded videos zips to 88.9megs - Jomsocial takes over 1.6gigs for a BASIC set-up using the sitebackup script I've attached. 

thanks for that, I will be testing that tonight.

some of my sites are music loaded, upwards of 10GB, I bet I knock my server out trying this.. what you think?

I will also give it a try tonight Thumper, Thanks 

 The script does use most of the memory. But I don't think 10gigs will be a problem - should zip the FullSite to about 4-6gigs. I use PuTTY.exe with "top -c" to watch the zipping process. I watched the top -c window and it zipped my site in about 2 mins 40 secs. The only issue on a 10gig site will be execution time.

 Do you bypass CloudFlare when you do these actions? I made my final decision to do away with CloudFlare. It caused problems with module installs, FTP'ing etc. Weird stuff happens. I used cpanel's file manager to upload a module and unzip. The module sent errors when I tried to run it. I FTP'ed in with wsFTP and could not even see the directory the module was in. Looked with cpanel's File Manager and could see it. Disabled CloudFlare and all issues went away.

 Hi Tony,

Hope all is well for you this weekend buddy.

I've not had a problem with the sitebackup script and Cloudflare.com.  When I install a 3rd party module I do the following. I stop Cloudflare - clear the Cloudflare cache and the Boonex cache.  Also do a manual clear via FTP or SFTP of the cache before the install. Then run the module with out Cloudflare.com for a bit. Then if all is well - re-start Cloudflare.com. So far this seam to work for our site. Just remember that Couldflare.com just like Dolphin has to be seduced into submission ;-)

Thanks for the info. After I digest all this,I will consider CloudFlare again because it sure takes the load off of my server and stops spam bots in their spot.

 those are set high already.. very high.. lol

 Tony - I though the exact same thing when I first started using Clouflare.com. But - it just came down to caches. I hope it works for you Tony, cause I love your site. Your site is to important not to have it working at top performance.

Warning... off topic.

 Too bad more people in the USA don't understand that freedom is lost one Right at a time. One on the many famous quotes on my site:

 So True - one of these days brother - I'm going to buy you a beer! You might get attacked by your post - but I'm going out on the limb and being your wing man here. Dolphin is using both Capitalist and Socialistic business models. The capitalism model is change a bunch for the software - the socialistic model is provide a community support system. This is Boonex only weakness: I know-  I've taught this at the college level and my wife is a politician as you already know by her Wikipedia page and we see this and advise several international companies on the differences of either being a capitalistic or socialist company. Now, each business models has plus and minus. But to combine both is not profitable and bad for the business consumer and okay for the hobbyist social network customer.  And most likely Boonex will say "we are not about profit". You should beware of any for-profit and even a non-profit group that says this. We know - we work in both industries. We own a few for- profit business and have founded one of the the top animal welfare non-profit groups in America(we provide aircraft to rescue animals- skyark.org). You have to make a profit before you can help animals or humans.  

Now in defense of Boonex - even thou they have a horrible socialistic business model - this is very very important - one of the main reasons we bought Boonex , is their love of Dolphins. they and whales need our protection. It is a shame that they were not more capitalistic - hence more Dolphins would be saved.

Sounds like you guys have your backups under control, but I'll offer up this script again if you're interested in checking it out:

http://www.boonex.com/forums/#topic/Protect-your-ASSets-MySQL-Backups-.htm

The compression is excellent - I have over 7 databases (3 of which are moderate dolphin sites) tarred together for a grand total of 15MB on disk. This allows me to keep a full month of nightly backups sitting standby on my server, and two days of hourly backups without sweating about disk space. 

I have a monthly job that pulls them to a remote location (my workstation), then purges them from the website server. 

I learned a log time ago that you should never rely on any built in backup utilities for dolphin (or any platform). Go straight to the source :)

I am playing around with a database replication setup with my new 7.1 site. Essentially, a mirror of the database would be kept at a remote site & all backup operations performed from there = no load on the production web server.