XCloner

Are you sure the files get uploaded by XCloner? Cause XCloner is only setup to send backup archives( .tar or .tgz files), if you see other files than those being sent, it’s probably not XCloner doing this.

And yes, XCloner needs it’s plugin files to run, it does not store anything in the database.

Ovidiu

The databases listed there are the ones that your setup mysql user has access to, check your XCloner Config Mysql tab for the current mysql username

1. Yes, that’s correct

1. you simply don’t include them in the backup, by default, only the main database setup in XCloner Mysql tab is included in the backup

3. should be no issue as that is a common user cron manager

4. yes, that feature only works in cron mode

1. No, it’s only a file structure exclude option

3. i don’t think so, but it depends on what kind of hosting setup you have there

4. check the cronlog, usually you have there the delete backups message as well as the deleted archives, have you checked the server date of the backups from the View Backups screen?

1. Simply add the folder full path in the exclude area, one per line, to exclude a directory; if you want to backup multiple database, you need to assign the default mysql user you have setup in XCloner to those additional databases, and they will get listed in an Additional databases to exclude area

2. that’s normal, the site is not down, just the server won’t serve a new connection to you until that is finished, better use cpanel or a ftp client to download the backup

1) to achieve that, simply exclude the sub-folders from the File Exclusion manager when generating the backup

2) you can exclude the subfolders when using the cron mode by adding them to the exclude files/foldes list in XCloner Config Cron tab; in cron mode XCloner does not split backups larger than 2GB, yet…., so it might be a system limitation(on some servers, you can’t create files larger than 2GB with php), so to fix it, either try and get the backup under 2GB or simply use the main generate backup panel when creating a full backup, backups created there are being split automatically when that limitation is reached

3) use the main Generate backup option from XCloner backend, you can easily follow there the backup process and download it/them(if multiple parts) when finished

Hope it helps! Ovidiu

This is probably a bug i need to check, for a quick fix, you can try and remove the ‘ or ” chars from your mysql password by using the mysql control panel, then update the XCloner Config details! Ovidiu

The 404 error during a backup process usually means the server is limiting the backup process to continue, it could be a memory issue, or an max_execution_time issue.

If your server has support for php version bigger than 5.2.3, you could set the “Backup refresh mode” to AJAX in your XCloner Config->System tab and see if it helps, usually that deals nicely with server timeouts.

We are more than happy to help you find and fix the issue if you can give us more details about your environment and XCloner Config changes you made.

All the best, Ovidiu

Try and install it under another environment and see if you still have issues, the package works fine from here. You might want to enable full php errors on your server to debug the issue, XCloner can also be accessed directly using the https://[mysite.com]/wp-content/plugins/xcloner-backup-and-restore/ url

Ovidiu

Might want to check with your hosting provider to see the exact error behind the blank page

I have this on my development list and it will be implemented at some point!

Regards, Ovidiu

Ahh, that would explain it, yes, the login is case sensitive, i will make a note of that and add a notification text

Thanks for pointing this out! Ovidiu

I am pretty sure that option works correctly as we usually change the default user and pass also.

If you like to debug the code, you can simply open the file wp-content/plugins/xcloner-backup-and-restore/admin.cloner.php and look at the line 52, that’s where the authentication takes place, you can easily check there if the proper variables are being parsed from the cloner config or the login form.

Ovidiu

Hey there! The username is not being hardcoded, otherwise the editing field would not have a point. You can easily verify this by opening the wp-content/plugins/xcloner-backup-and-restore/cloner.config.php file and look at the ‘jcuser‘ parameter to see it’s value, the password is being generated using the md5() algorithm and that can be checked also!

If you think it’s a bug I might have missed, would be happy to fix it! Ovidiu