Error 200 when local restore

  • ExtraPaul

    (@extrapaul)


    6 years, 1 month ago

    1. I make a SQL backup on my public site
    2. I download this backup in my local site, in wp-content/backups-xxxxx
    3. On my local site, WP is installed and xclone plugin is activated, so I use “Restore Backups” to begin the procedure…
    4. [CHECK CONNECTION] : ok, folder found.
    5. I choose my backup file in the combolist, then [RESTORE] : all ok.
    6. I change the domain to my local, then [RESTORE] : works few seconds and then “200” in red appears. Procedure stopped !

    Here is my theory : the options table (wp-options) contains the name of xcloner backup folder.
    In my local site the folder is “backups-xxxxx”, but in my remote site it’s “backups-yyyyy”.
    So when xcloner writes values in wp-options… it changes the value of it’s own backup folder, then it does not find it to continue the restore.

    Is it right ?

    And the option “Force Temporary Path Within XCloner Storage” is set to On.

    • This topic was modified 6 years, 1 month ago by ExtraPaul.
    • This topic was modified 6 years, 1 month ago by ExtraPaul.
    • This topic was modified 6 years, 1 month ago by ExtraPaul.
Viewing 5 replies - 1 through 5 (of 5 total)
  • XCloner

    (@xcloner)

    6 years, 1 month ago

    Can you try and restore to a different empty database as compared to the existing one?

    Thread Starter ExtraPaul

    (@extrapaul)

    6 years, 1 month ago

    Same procedure tested with another site : aborted in 2/3 with “400 undefined”.
    Then if come back in Site Backup Dashboard I get a lot of errors :

    Fatal error: Uncaught Error: Call to a member function get_storage_usage() on null in C:\Users\MediaMonster\Sites web\Philantros\www\wp-content\plugins\xcloner-backup-and-restore\admin\partials\xcloner_init_page.php on line 126

    Error: Call to a member function get_storage_usage() on null in C:\Users\MediaMonster\Sites web\Philantros\www\wp-content\plugins\xcloner-backup-and-restore\admin\partials\xcloner_init_page.php on line 126

    Fatal error: Uncaught UnexpectedValueException: There is no existing directory at "php:" and its not buildable: No such file or directory in C:\Users\MediaMonster\Sites web\Philantros\www\wp-content\plugins\xcloner-backup-and-restore\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 171

    UnexpectedValueException: There is no existing directory at "php:" and its not buildable: No such file or directory in C:\Users\MediaMonster\Sites web\Philantros\www\wp-content\plugins\xcloner-backup-and-restore\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 171

    • This reply was modified 6 years, 1 month ago by ExtraPaul.
    XCloner

    (@xcloner)

    6 years, 1 month ago

    When you are doing a restore to the same installation, files usually get overwritten and while doing that errors might popup, this is not the best way to do a full restore.

    The safest way to do a restore is to download the restore script provided in the Restore Panel backend, upload it to the new restore location, can be local or remote, and paste it’s url in the input restore box from the Restore Panel page, that will serve as a standalone API endpoint and can continue the restore process from there.

    Thread Starter ExtraPaul

    (@extrapaul)

    6 years, 1 month ago

    OK, I understand. Thank you.

    However, I have a lot of WP sites, and I’m looking for the best way to “reset” my local sites with data from remote sites.
    Xcloner is a very good tool and I’m sure to find the good way to clone when WP is already installed…

    XCloner

    (@xcloner)

    6 years, 1 month ago

    I would suggest to multi-restore setups, specially for localhost ones, to setup a base WordPress installation from where you would launch the restore, and do a restore from it’s panel targeting your development folders and database making sure you can access to them.

    So the point is targeting a remote install and not your base one in case of local restores, this if you don’t prefer to download the XCloner restore script and use it’s api endpoint url.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Error 200 when local restore’ is closed to new replies.