Backup failed

  • Resolved vipteam

    (@vipteam)


    1 year, 8 months ago

    Hi Support,

    FastDup: Website live on server. Backup started but without success. The circle spins on the database. Infinity. No notice whatsoever. To no avail. Deactivated.

    I tried the following plugins (JUST TO EXPLAIN how FastDup should work):

    Total Upkeep: Backup failed. The plugin reports an error but cannot detect which error it is. The user does not know what to do next. Deactivated and deleted.

    Backup Migrate: Backup succeeded. I followed the instructions (from support forum) for the restricted server settings, as a precaution. The plugin is fine but I don’t like the way it works. The result is that there is no “standalone installation” (no installer.php and archive.zip). Restore and migrate work in such a way that it is first necessary to install WordPress on the destination address. Then the plugin is installed and the backup is loaded through it. Big waste of time.

    Duplicator: Settings > SQL Mode: Mysqldump, Archive Engine: ZipArchive. Backup started. It reports an error and requests that the SQL Mode be switched to PHP Code (Runtime error in DUP_Database::Build. Shell mysql dump error. Change SQL Mode to the “PHP Code” in the Duplicator > Settings > Packages.). Restarted backup. Completely successful.

    My idea for FastDup:

    1. FastDup should not be the fastest plugin but the SIMPLEST and MOST RELIABLE plugin.
    2. Dialogues and warnings are missing here (only to the extent that it is necessary).
    3. There are no settings. Maybe they should exist or FastDup should work by default with restricted server settings. The plugin should work on all servers. For example: With System ZIP and PHP Mode, FastDup will work on all servers. MySQL dump will not work on all servers. Mysqli extension is present in PHP v8.1, but in PHP version 8.2 it is no longer there. Support for 8.1 ends at the end of the year. The database should be downloaded in the style of a complete file or broken into tables. The database is the smallest segment in the archive, and here it is not speed that is needed, but verification, reliability and security. It doesn’t matter if it lasts 10 or 120 seconds.
    4. ZIP should not be done by brute force. The servers will not allow this. This should be done in chunks of acceptable size (times). Chunk, pause, chunk, pause, … This way the plugin will work on all servers.

    I hope you will consider these ideas and after a few updates FastDup will become the easiest and most reliable backup/clone/migrate plugin. Thanks in advance.

    Have a nice day. Regards,

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

  • Hi @vipteam ,

    Thanks for reaching out!

    Could you please record a short screencast of this issue?

    Kind regards,
    Alina

    Thread Starter vipteam

    (@vipteam)

    Hi @alina98

    FIRST – Full Site

    Build Package always stuck on Database at 10%. Five tries, always the same.

    FastDup – step 1 – New package
    https://i.imgur.com/FBkytMr.png

    FastDup – step 2 – Full Site
    https://i.imgur.com/DFdSRee.png

    FastDup – step 3 – Create package
    https://i.imgur.com/0gjW26R.png

    FastDup – step 4 – Failed
    https://i.imgur.com/QDnOuct.png

    SECOND – Database only

    Same thing. Unable to process/download Database.

    Thread Starter vipteam

    (@vipteam)

    Error log

    [29-Mar-2023 17:45:04 Europe/Berlin] PHP Warning: session_start(): Session cannot be started after headers have already been sent in /home/MYSITE/public_html/wp-content/plugins/fastdup/includes/Admin/Package.php on line 89

    [29-Mar-2023 17:45:04 Europe/Berlin] PHP Warning: session_destroy(): Trying to destroy uninitialized session in /home/MYSITE/public_html/wp-content/plugins/fastdup/includes/Admin/Package.php on line 90

    [29-Mar-2023 17:45:04 Europe/Berlin] PHP Warning: fopen(/home/MYSITE/public_html/wp-content/njt-fastdup/tmp/): Failed to open stream: Is a directory in /home/MYSITE/public_html/wp-content/plugins/fastdup/vendor/ifsnop/mysqldump-php/src/Ifsnop/Mysqldump/Mysqldump.php on line 1436

    Hi @vipteam ,

    Please let me check this with the dev team, I will feed you back as soon as possible.

    Thank you!

    Kind regards,
    Alina

    Plugin Support Bruce

    (@ninjateamwp)

    Hi @vipteam ,

    As our dev team are trying to check and fix the issue, so we can have a general update.

    We have a question;
    Is your website connecting to a database host with non-3306 port?

    Because, by default, mysql database uses 3306-port, but some websites use another port, 3307 for example.

    Thank you.

    Kind regards,
    Bruce

    • This reply was modified 1 year, 7 months ago by Bruce.
    Thread Starter vipteam

    (@vipteam)

    Hi @ninjateamwp ,

    On the website on localhost with XAMPP I use (default) port 3306. For a live server, I’m not sure. I’m using the default, I haven’t changed anything. How can I check the port?

    Thanks in advance. Regards,

    Thread Starter vipteam

    (@vipteam)

    I checked with info.php. Everything is OK. Live server

    mysqli.default_port: 3306

    Hi @vipteam ,

    Could you please open wp-config.php and look for DB_HOST then send us a screenshot?

    Thank you!

    Kind regards,
    Alina

    Thread Starter vipteam

    (@vipteam)

    /** MySQL hostname */
    define( ‘DB_HOST’, “localhost” );

    Hi @vipteam ,

    Please let me check this with the dev team and I will feed you back as soon.

    Thank you!

    Kind regards,
    Alina

    Plugin Support mialewp

    (@mialewp)

    Hi @vipteam ,

    Thanks for your patience. In this case, Our dev would like to check more details on your issue, please reach out technical team to help you check it: ninjateam.org/support
    We are looking forward to hearing back from you.

    Best regards,
    Mia

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Backup failed’ is closed to new replies.