Forum Replies Created

Viewing 15 replies - 91 through 105 (of 163 total)
  • @gulflee

    Best thing to do is to switch one server off and see if the website is still alive. I do this with

    service mysqld stop

    Forum: Plugins
    In reply to: [HyperDB] Hyperdb help!

    I think I’ve answered your question in this thread:

    http://wordpress.org/support/topic/hyperdb-installation?replies=4

    Forum: Plugins
    In reply to: hyperdb installation

    Hi there,

    only a few lines are “live” in db-config.php. Three towards the top of the file, and two blocks underneath the heading

    /** Sample Configuration 1: Using the Default Server **/
    /** NOTE: THIS IS ACTIVE BY DEFAULT. COMMENT IT OUT. **/

    What the guys have done here is give you a “sample configuration” which uses the values from your wp-config.php file. Hence by just installing the plugin it would be switched on, but you wouldn’t notice any differences (since only one database server is active for reads and writes).

    Now you copy the second block and add the values for your second database server – that’s how you configure it. This will work on shared hosting, but it only makes sense if you have more than one database server so you’d configure one for reading and one for writing (or reading and writing).

    Please note that HyperDB DOES NOT replicate your database or user accounts! You need to do this yourself. You can refer to this article from the MySQL manual:

    http://dev.mysql.com/doc/refman/5.1/en/replication-howto.html

    I have the same issue –

    I guess it’s an incompatibility with WordPress 3.2.x

    Maually embedding the forum still works like this:

    <script type="text/javascript" src="http://yourwebsite.com/yourforum/plugins/embedvanilla/remote.js"></script>

    Plugin Author Jay Versluis

    (@versluis)

    There are other solutions that do an even better job at backing up your site:

    Vaultpress.com
    BackupBuddy
    BlogVault

    They all cost money but are excellent at what they do.

    Plugin Author Jay Versluis

    (@versluis)

    Good point..

    I’ve implemented this check at the beginning of the plugin once, but not explicitly before every single command execution.

    I’m not a PHP coder so any help on making this thing better is appreciated.

    Plugin Author Jay Versluis

    (@versluis)

    Hi mjefferson96,

    very sorry to hear you Snapshot doesn’t work for you. I know that on some shared hosting systems they don’t let you execute shell commands – which I stated this plugin uses.

    If your site had a problem, then it wasn’t actually my plugin which costs you days to recreate your site. It was your oversight of not testing the plugin beforehand. Blindly relying on a free solution to do a perfect job is never a good idea.

    I agree with you 100%: do not trust Snapshot Backup to be the end-all solution to a safe backup. It’s an attempt to do this, and it works very well for me. But that’s because I have tested it on my system to do what it’s supposed to do. I’m distributing it in the hope that it will be useful to others, but never have I made any claims that it will work on every server.

    Plugin Author Jay Versluis

    (@versluis)

    Hi frods,

    thanks for the coffee – very sorry for the late reply here. Yes your theory is correct, there’s only 1 tarball that’s left on the local system which gets overwritten when you create a new backup.

    It’s different on the FTP server though as you can leave several on there and the oldest one gets overwritten when a new one comes along.

    If you’re using the same FTP account as your current website (i.e. the same server) then they’d add up: so the local site would have 1 tarball, and the FTP directory would have the same tarball, plus any of the older ones you’ve chosen to keep.

    Hope this makes sense.

    Plugin Author Jay Versluis

    (@versluis)

    Hi Cresten,

    I think out of over 16.000 downloads you’re the only person who’s experienced that. So you’re saying the plugin backed up your site fine, then you downloaded the file, and as a little parting gift it deleted all content on your server?

    If this would be an issue then don’t you think other users would have told me about this already? I’m really sorry about your site, whatever happened to it. But blaming random people like me won’t help bring it back. And I’m pretty certain that my plugin didn’t do it.

    Plugin Author Jay Versluis

    (@versluis)

    Some hosts don’t allow PHP to execute FTP and shell commands – probably due to security restrictions. Your host seems to be one of them.

    It basically means that the plugin can’t do what it needs to in order to work properly.

    Plugin Author Jay Versluis

    (@versluis)

    I know that plugin, it’s very good indeed.

    The difference is that my plugin uses a Linux Shell Command to read out the database (mysqldump) whereas WP DB Manager uses a PHP script. I’m not that good with PHP so I went the other way, but it may mean that for whatever reason your host does not allow the execution of said command. It could be that the SQL file is not read out because of restrictions put in place by your host.

    I’ll see if I can read out the database some other way in a future update. Sorry it’s not working out for you right now.

    Plugin Author Jay Versluis

    (@versluis)

    Hi Jim,

    that’s not good… we wouldn’t want a backup plugin that doesn’t back up 😉

    Did you receive any error messages, particularly when you generate a manual backup?

    Are you looking at the one in the wp-content/uploads folder? The .tar file saves the entire directory structure of your server so it’s hard to describe where exactly this location is. On my system for example, the full path is

    /var/www/vhosts/mydomain.com/httpdocs/wp-content/uploads/filename.sql

    but this is different depending on your Linux distribution. I’ve just checked mine and it’s there safe and sound, 4.1MB in size.

    Plugin Author Jay Versluis

    (@versluis)

    Ah, now it all makes sense:

    It’s not the plugin they don’t like, they don’t want you to store .TAR files anywhere in your webspace. That’s very cheeky – like you say – unlimited is unlimited where I come from.

    You can always sign up with one of my FTP packages – they’re optimised for speed and backup, no penalties attached, usable immediately:

    http://wpguru.co.uk/hosting/ftp/

    Plugin Author Jay Versluis

    (@versluis)

    Bizarre–

    try a manual delete and restore. It’s definitely on the system:

    http://wordpress.org/extend/plugins/snapshot-backup/

    Plugin Author Jay Versluis

    (@versluis)

    Anjaan,

    yes those errors are another mystery to me… They were in the previous version too and again don’t show up on my server. Did you say the backups are created fine?

    I’m afraid I can’t give you a timing on when the restore option will be available, but it’ll most likely be a standalone script rather than an integration. I’ll see what works. Restore is easy when you’re restoring to the same domain and server, but it can get hairy when you want to restore onto a different domain or into a subdirectory – however those would be super cool options. Imagine you have pre-built websites you can roll out to clients at the touch of a button?

    ————–

    Robin,

    I think what Hostpapa are concerned about is not bandwidth but as Anjaan said CPU power and overall responsiveness of their server. When Snapshot creates a backup it hogs the server resources a bit – and I’m sure that’s what they’ve picked up. Shared hosting is a very sensitive environments.

    The good news is that I’ve found a solution which will slow the process down so it takes longer, but doesn’t hog the resources. I’ll test it and will let you know – it’ll be a feature in 2.1 which I may release early next week.

Viewing 15 replies - 91 through 105 (of 163 total)