• I specifically tested the WordPress backup and restore process.

    I created a full backup using the “WordPress files + database” option. After that, I deliberately:

    • created a new page;
    • deleted the xmlrpc.php file;
    • modified wp-config.php.

    Then I restored the previous backup.

    The result: the database was restored and the newly created page disappeared, but the deleted file was not restored and the changes in wp-config.php remained.

    So the plugin reports that the backup and restore were completed successfully, while in reality the full WordPress state is not restored.

    For a backup plugin, this is a critical failure. The worst part is that the user sees a “successful” status and may believe they have a valid backup, while the restore can actually be incomplete.

    The plugin also leaves .qwp files inside wp-content/qnap-backups instead of cleaning them up properly.

    Looking at other user reviews, these issues have existed for years: incomplete backups, incorrect backup sizes, failed restores, empty backups, and critical errors. Yet the core reliability problems still appear to remain unresolved.

    I would never use this plugin for a serious or production website.

    A backup solution that cannot reliably restore what it claims to have backed up is failing at its most basic purpose.

    In my opinion, leaving such critical backup/restore issues unresolved for this long is irresponsible development.

    1/5. Not recommended.

    • This topic was modified 1 week, 2 days ago by krulko2025.

You must be logged in to reply to this review.