Pre-v5 jobs not being taken over correctly

  • AndyHenderson

    (@andyhenderson)


    9 months ago

    In reply to another topic you said:

    Migration of old jobs: Your previous jobs have not been removed and remain accessible in read-only mode at:
    👉 admin.php?page=backwpupjobs
    While the new version introduces a different backup flow, your existing jobs should still function as before.

    But, for me there are two big issues with my custom jobs:

    • I run my backups from an external server to avoid issues with cron. However, in the new version of the old job the ‘Start job’ option has been changed to ‘manually only’ so my backup requests are ignored.
    • They all backup files and database in a single job, but in the new version of the old job the ‘Database backup’ option is not ticked and there is no database in the backup when run manually.

    Because the the jobs are read-only I can’t fix them through the UI.

    Can you help?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter AndyHenderson

    (@andyhenderson)

    9 months ago

    FWIW I fixed the job definition by directly altering option ‘backwpup_jobs’ in the options table. I added “DBDUMP” to the ‘type’ array and changed activetype from “” to “link”.

    For some reason, although I specified the full backup in my link using jobid=1, it ran both my jobs (I have a database only job for occasional use).

    Andy

    Plugin Support Plugin Support

    (@saranshwpm)

    9 months ago

    Hi Andy,

    Thank you for your follow-up and for sharing your solution. Regarding your note about the database backup:

    In one of the past updates, the option to set the database backup file name was removed. However, the database file is still included in the backup archive as a .sql file. It may appear hidden depending on your system settings, so enabling the option to view hidden files should help locate it.

    If you’d like to assign a name to the database file, you can follow this workaround:
    👉 DB-only backup SQL file is unnamed and hidden

    Let us know if you have any other questions!

    Best regards.

    Thread Starter AndyHenderson

    (@andyhenderson)

    9 months ago

    Thank you for getting back, but that’s not it. The database dump file was definitely missing from the backup zip file. Apart from not being visible in the zip list, the size of the backup was reduced by exactly the size of the database dump as recorded for previous backups (I installed v5 first on a very slow-moving web site). Also, the ‘Database backup’ option was unticked in the job details. Adding DBDUMP to the type array caused the database dump to be included and the backup size went back to normal.

    You don’t mention the ‘Start job’ option which was also changed. As it happens, it was just as well that it did, otherwise I might not have realised that I was no longer backing up my database.

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

The topic ‘Pre-v5 jobs not being taken over correctly’ is closed to new replies.