XCloner
Forum Replies Created
-
The “Could not write to new host”. means the restore script is unable to write files within it’s folder, it needs writeable permissions in order to do it’s migration, you can reset them afterwards.
Hi René, XCloner does not support Extended Inserts which is the feature that makes phpmyadmin faster on import, since this mode would probably break the incremental restore option. I might look in the future into a possible solution for incremental Extended Inserts, so feel free to submit a Feature request on XCloner github page
The issue you have is probably related to mysql server running in strict mode, you can check here for a more detailed explanation https://forum.level1techs.com/t/mysql-incorrect-integer-value-for-column-a-column-name-at-row-1-solved/130862 . Solution would be to either disable STRICT_TRANS_TABLES for your mysql server or set
sql_mode = NO_ENGINE_SUBSTITUTION
in your my.cnf mysql config. Have you tried importing the XCloner mysql backup through phpmyadmin?
Please check the XCloner log from it’s dashboard, you should see there if there are any errors in adding those tables, can you post a screenshot of your backup selection?
HI there, you can simply download the restore script from the XCloner Restore page and start a remote restore process as specified on that page, that will restore you all files.
The red icon means that the remote backup does not have a copy of the file on the local system storage and you would need to download it in order to restore it. If that is not the case it might be a bug, so please report it in the github repository of xcloner.
Forum: Plugins
In reply to: [Backup, Restore and Migrate your sites with XCloner] What’s is this file?The restore/vendor.build.txt is actually a phar file containing the vendor/ folder files, so it’s a false positive because of the name probobly.
Hope it helps
Forum: Plugins
In reply to: [Backup, Restore and Migrate your sites with XCloner] Temporary Folder errorThe option is automatically added in the scheduled backup process, no need to activate anything else
To fix the scheduler table error, you could manually create the table using this query
CREATE TABLE
wor1004_xcloner_scheduler
(
id
int(11) NOT NULL AUTO_INCREMENT,
name
varchar(255) NOT NULL,
recurrence
varchar(25) NOT NULL,
params
text NOT NULL,
start_at
datetime,
remote_storage
varchar(10) DEFAULT NULL,
hash
varchar(10) DEFAULT NULL,
status
int(1) NOT NULL,
last_backup
varchar(100) DEFAULT NULL,
PRIMARY KEY (id
)
)Please attach here a sanitised copy of the xcloner debugger log to see if I can spot anything regarding your schedule
Additionally, feel free to send it to https://www.thinkovi.com/contact/ if you cannot sanitise it.
Hi Jan, do you have any backups available in your remote storage, it might be a failed check which i will fix in the next release, it seems to display ok when backups are available.
Do you have any other plugins that are connecting to google drive? It could be a conflict with one of the plugins you have there, so try testing to see if you still get that error with only XCloner and XCloner Google Drive plugins installed
Do you see any errors in the XCloner logger from it’s dashboard?
It’s best to check the server error logs to see if you get a more detailed output of the 403 error. I would suggest to check permissions on your web folder and to check/delete the restored htaccess code.
Hi Jess, yes, you can backup multisite installs, the error you have there might be from your local server, try and upload the backup archive files manually in your plugins folder and see if it helps.
I would suggest extracting the backup archive files manually on your new location and then just start the restore and skip the files restore. Feel free to contact me here https://www.thinkovi.com/contact/ for a quote on the restore