• Resolved eftcolumbus

    (@eftcolumbus)


    Hi, over the past month my email alert says it was apparently unsuccessful. I’ve been doing a weekly backup to S3 for years and it has been failing every week for about month. My hosting and S3 accounts have not changed. When I click Test S3 Settings it says:

    S3 settings test result: Success: Region: us-east-2: We accessed the bucket, and were able to create files within it. The communication with Amazon S3 was encrypted.

    Currently it is now saving most of my backup to my /backup folder on my server. When I check S3 the last one is from January 17. I am having no other issues with my S3 account in other usages.

    On the backup I just tried today, it always says “moving on” at the end of each line until I get to this (NOTE: I replaced the domain name with “mydomain”)

    3744.307 (12) The final database file (/home/nginx/domains/mydomain.com/public/wp-content/backup/backup_2021-02-15-1258_mydomain_4aeb53402275-db.gz) exists, but was apparently not modified within the last 30 seconds (time_mod=1613415341, time_now=1613415667, diff=326). Thus we assume that another UpdraftPlus terminated; thus we will continue.
    3744.353 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_options.table.gz (1/279): adding to final database dump
    3744.665 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_users.table.tmpr4920.gz (2/279): adding to final database dump
    3744.716 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_users.table.gz (3/279): adding to final database dump
    3744.720 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_usermeta.table.gz (4/279): adding to final database dump
    3745.119 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_actions.table.tmpr105359.gz (5/279): adding to final database dump
    3745.145 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_actions.table.gz (6/279): adding to final database dump
    3745.149 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_claims.table.tmpr26909.gz (7/279): adding to final database dump
    3745.151 (12) backup_2021-02-15-1258_mydomaine_4aeb53402275-db-table-hp_actionscheduler_claims.table.gz (8/279): adding to final database dump
    3745.153 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_groups.table.tmpr6.gz (9/279): adding to final database dump
    3745.155 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_groups.table.gz (10/279): adding to final database dump
    3745.158 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_logs.table.tmpr85448.gz (11/279): adding to final database dump
    3745.192 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_actionscheduler_logs.table.gz (12/279): adding to final database dump
    3745.195 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_commentmeta.table.tmpr122727.gz (13/279): adding to final database dump
    3745.203 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_commentmeta.table.gz (14/279): adding to final database dump
    3745.206 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_comments.table.gz (15/279): adding to final database dump
    3745.444 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_links.table.tmpr0.gz (16/279): adding to final database dump
    3745.448 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_links.table.gz (17/279): adding to final database dump
    3745.451 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_ms_snippets.table.tmpr0.gz (18/279): adding to final database dump
    3745.454 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_ms_snippets.table.gz (19/279): adding to final database dump
    3745.456 (12) backup_2021-02-15-1258_mydomain_4aeb53402275-db-table-hp_postmeta.table.gz (20/279): adding to final database dump
    4103.885 (13) Opened log file at time: Mon, 15 Feb 2021 19:07:06 +0000 on https://mydomain.com
    4103.888 (13) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.16.47 WP: 5.6.1 PHP: 7.3.11 (fpm-fcgi, Linux ngx.mydomain.com 2.6.32-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK 2018 x86_64) MySQL: 10.1.48-MariaDB WPLANG: en_US Server: nginx/1.17.5 safe_mode: 0 max_execution_time: 900 memory_limit: 800M (used: 32.5M | 18.5M) multisite: N openssl: OpenSSL 1.0.2k 26 Jan 2017 mcrypt: Y LANG: ZipArchive::addFile: Y
    4103.890 (13) Free space on disk containing Updraft’s temporary directory: 6745 MB
    4103.893 (13) Requesting backup semaphore lock (4aeb53402275)
    4103.895 (13) [Lock (updraft_lock_4aeb53402275, hp_options) acquired] info
    4103.898 (13) Backup run: resumption=13, nonce=4aeb53402275, file_nonce=4aeb53402275 begun at=1613411922 (4104s ago), job type=backup
    4103.901 (13) [Updraftplus] The backup is being aborted for a repeated failure to progress.
    4103.903 (13) An error condition has occurred for the first time during this job
    4103.905 (13) [Lock option (updraft_lock_4aeb53402275, hp_options) released] info
    4103.908 (13) An email has been scheduled for this job, because we are in debug mode
    4103.910 (13) Fetching RSS news feed
    4104.011 (13) Fetched RSS news feed; result is a: SimplePie
    4104.061 (13) Sending email (‘Files (database backup has not completed) (Full backup)’) report (attachments: 1, size: 556.2 KB) to: busin…
    4105.174 (13) The backup attempt has finished, apparently unsuccessfully

Viewing 8 replies - 16 through 23 (of 23 total)
  • Thread Starter eftcolumbus

    (@eftcolumbus)

    No, because it’s on manual now because they are filling up my server and making my site slow down, so I can’t run them. Last one on there is from Feb 14. I have done some test runs since then on a manual basis but none were on Sunday. My last successful normal backup was Jan 17 btw.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Hi, wondering if you had any more ideas? I confirmed that I wasn’t running any other backups when I did the new one. The regular scheduled backups on Jan 24, 31, Feb 7, and 14 all had the same problems (I gave you logs from the 14th). Then I canceled the scheduled backups because they were clogging up my server so there were no more Sunday attempts.

    I also tested it manually 3 times since Feb 14, all were unsuccessful.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    So…no other ideas?

    Plugin Contributor bcrodua

    (@bcrodua)

    Hi,

    Apologies for the late reply.

    Please could you send us a copy of the latest full backup log?
    This can be found in the UpdraftPlus Existing Backups tab.
    The contents will be too long to post here directly, but you can use an online service such as Dropbox or Pastebin, and post the link here.

    Regards,
    Bryle

    Thread Starter eftcolumbus

    (@eftcolumbus)

    I had previously provided the full log and we didn’t get anywhere. I just want to make sure since you are new to this thread that you have read everything already asked/responded to.

    Earlier this week i:

    1) Wiped Settings
    2) Deleted Plugin and Reinstalled
    3) Set up a new key with S3 even though my original one was testing successfully

    Then I tested in pieces and I was able to get it to backup just the files when I excluded the database, but I am unable to get it to backup the database.

    Here is a log from unsuccessful attempt just now. This is database only.

    https://1ty.me/4M1q6if

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Hi it’s been a couple weeks since I provided you the requested information. Do you have any suggestions?

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Hi, it’s now been 3 weeks since I responded to your request for the log again. Should I just assume you aren’t going to answer this? If I don’t hear back by end of day I will assume so.

    Thread Starter eftcolumbus

    (@eftcolumbus)

    Well it’s entirely disappointing that you asked me to repeat steps you had already asked me to do and then never respond in 4 weeks – I could tell nobody had read the log I posted because it shows the access date/time and nobody had accessed it since i posted it nearly 4 weeks ago. And then you marked it resolved. So I guess I will leave a negative review.

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Now backups unsuccessful after years successful’ is closed to new replies.