• Resolved DOOMdesign

    (@doomdesign)


    Hi there!
    Today I updated my site to the current BackWPUp version, with the new admin interface and all.
    Since then, backing up my database throws the following errors and won’t get completed:

    [18-Sep-2025 12:44:59] 1. Versuche, die Datenbank zu sichern …
    [18-Sep-2025 12:44:59] FEHLER: The option "compression" with value null is expected to be of type "string", but is of type "null".
    [18-Sep-2025 12:44:59] 2. Versuche, die Datenbank zu sichern …
    [18-Sep-2025 12:44:59] FEHLER: The option "compression" with value null is expected to be of type "string", but is of type "null".
    [18-Sep-2025 12:44:59] 3. Versuche, die Datenbank zu sichern …
    [18-Sep-2025 12:44:59] FEHLER: The option "compression" with value null is expected to be of type "string", but is of type "null".
    [18-Sep-2025 12:44:59] FEHLER: Schritt abgebrochen: zu viele Versuche!
    [...]

    The file backup up gets done without errors, only the database job fails.
    I already tried deleting legacy jobs, reinstalling the whole plugin, and tried the backup job with every available file fomat (TAR, TAR.GZ, ZIP), but nothing helped so far.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Same problem here.

    Plugin Support Plugin Support

    (@saranshwpm)

    Hi,

    Thank you for the details. Can you let me know from which BackWPup version you upgraded to the latest? Also, does the same error appear if you create a brand-new job instead of using the existing one?

    This will help us narrow down where the issue is coming from.

    Best regards,

    Thread Starter DOOMdesign

    (@doomdesign)

    I upgraded from v.4.1.7 to v5.5.0 .
    Deleting the existing database backup job and creating a new one (and run it), is giving the exact same errors.


    I have two other sites where I upgraded from v5.x.x to v.5.5.0 today as well, and they don’t give me those errors when backing up the database.

    Plugin Support Plugin Support

    (@saranshwpm)

    Hi,

    Thank you for confirming those details. Since the issue appeared only after upgrading from v4.1.7 to v5.5.0 and isn’t happening on your other sites, this could be due to a migration issue where some old job data wasn’t carried over properly.

    If it’s fine for you to reset, I would suggest reinstalling BackWPup completely, this will reset the jobs and may resolve the error.

    If that’s not an option, I’d recommend reaching out to our support directly so we can take a deeper look into your setup and help sort this out.

    Best regards,

    Nothing changed after reinstalling completely BackWup. Sorry, I don’t have time to look after the problem, I will search for an alternative that works for me.

    Plugin Support Plugin Support

    (@saranshwpm)

    Hi @doomdesign,

    Could you please let me know if my last suggestion was helpful?

    I look forward to your reply.

    Best Regards,

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

You must be logged in to reply to this topic.