Support » Plugin: BackWPup - WordPress Backup Plugin » Backup not transferred to S3

Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Author Daniel Hüsken

    (@danielhuesken)

    Is the Bucket in EU ? We have found a Problem than and will release a fix asap.

    I’m experiencing the same issue – but my bucket is in the Oregon region.

    Thank you so much!

    No, my bucket is in Northern California.

    Plugin Author Daniel Hüsken

    (@danielhuesken)

    Can you test the development Version so we can see if it works.

    Hi, Daniel,

    Thanks for the quick reply; however, I’m afraid I got the same error as before with the new dev version. The bucket, as I noted, is in Oregon. Here’s the log (and again, thank you for your work on this):

    2013/01/11 15:13.17: [INFO]: BackWPup version 2.1.17; WordPress version 3.5; Copyright © 2013 Inpsyde GmbH Author: Daniel Hüsken
    2013/01/11 15:13.17: [INFO]: BackWPup comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions.
    2013/01/11 15:13.17: [INFO]: BackWPup job: 1. New; DB+FILE
    2013/01/11 15:13.17: [INFO]: BackWPup job started manualy
    2013/01/11 15:13.17: [INFO]: PHP ver.: 5.3.18; cgi-fcgi; Linux
    2013/01/11 15:13.17: [INFO]: MySQL ver.: 5.5.29-log
    2013/01/11 15:13.17: [INFO]: curl ver.: 7.24.0; OpenSSL/1.0.0
    2013/01/11 15:13.17: [INFO]: Temp folder is: /path-to-wp/wp-content/plugins/backwpup/tmp/
    2013/01/11 15:13.17: [INFO]: Backup file is: /path-to-wp/wp-content/plugins/backwpup/tmp/backwpup_1_2013-01-11_15-13-17.zip
    2013/01/11 15:13.17: 1. try for database dump...
    2013/01/11 15:13.17: Dump database table "wp_aec_event"
    2013/01/11 15:13.17: Dump database table "wp_aec_event_category"
    2013/01/11 15:13.17: Dump database table "wp_commentmeta"
    2013/01/11 15:13.17: Dump database table "wp_comments"
    2013/01/11 15:13.17: Dump database table "wp_links"
    2013/01/11 15:13.17: Dump database table "wp_ngg_album"
    2013/01/11 15:13.17: Dump database table "wp_ngg_gallery"
    2013/01/11 15:13.17: Dump database table "wp_ngg_pictures"
    2013/01/11 15:13.17: Dump database table "wp_options"
    2013/01/11 15:13.17: Dump database table "wp_postmeta"
    2013/01/11 15:13.17: Memory increased from 128M to 381M
    2013/01/11 15:13.17: Dump database table "wp_posts"
    2013/01/11 15:13.39: Dump database table "wp_term_relationships"
    2013/01/11 15:13.39: Dump database table "wp_term_taxonomy"
    2013/01/11 15:13.39: Dump database table "wp_terms"
    2013/01/11 15:13.39: Dump database table "wp_usermeta"
    2013/01/11 15:13.39: Dump database table "wp_users"
    2013/01/11 15:13.39: Database dump done!
    2013/01/11 15:13.39: Add database dump "myurl_wrd1.sql" with 58.91 MB to backup file list
    2013/01/11 15:13.39: 1. try for make list of files to backup....
    2013/01/11 15:13.41: 2751 files with 644.49 MB to backup
    2013/01/11 15:13.41: 1. try to create backup zip (PclZip) archive...
    2013/01/11 15:16.20: Backup zip archive create done
    2013/01/11 15:16.20: Archive size is 610.02 MB
    2013/01/11 15:16.20: 1. try sending backup file to Amazon S3...
    2013/01/11 15:16.20: Connected to S3 Bucket: www.myurl.org-backup
    2013/01/11 15:16.20: Upload to Amazon S3 now started...
    2013/01/11 15:16.21: Undefined index: Message
    2013/01/11 15:16.21: [ERROR] Can not transfer backup to S3! (301)
    2013/01/11 15:16.21: 2. try sending backup file to Amazon S3...
    2013/01/11 15:16.22: Connected to S3 Bucket: www.myurl.org-backup
    2013/01/11 15:16.22: Upload to Amazon S3 now started...
    2013/01/11 15:16.22: Undefined index: Message
    2013/01/11 15:16.22: [ERROR] Can not transfer backup to S3! (301)
    2013/01/11 15:16.23: 3. try sending backup file to Amazon S3...
    2013/01/11 15:16.23: Connected to S3 Bucket: www.myurl.org-backup
    2013/01/11 15:16.23: Upload to Amazon S3 now started...
    2013/01/11 15:16.23: Undefined index: Message
    2013/01/11 15:16.23: [ERROR] Can not transfer backup to S3! (301)
    2013/01/11 15:16.24: Job done in 187 sec.

    i get the same error

    2013/01/14 09:51.30: [ERREUR] Amazon API: cURL resource: Resource id #272; cURL error: necessary data rewind wasn't possible (cURL error code 65). See http://curl.haxx.se/libcurl/c/libcurl-errors.html for an explanation of error codes.
    2013/01/14 09:51.30: 2. tentative d'envoi du fichier sauvegarde vers Amazon S3...
    2013/01/14 09:51.31: Connecté au panier S: backup
    2013/01/14 09:51.31: Envoi vers Amazon S3 commencé...
    2013/01/14 09:51.31: [ERREUR] Amazon API: cURL resource: Resource id #281; cURL error: necessary data rewind wasn't possible (cURL error code 65). See http://curl.haxx.se/libcurl/c/libcurl-errors.html for an explanation of error codes.
    2013/01/14 09:51.31: 3. tentative d'envoi du fichier sauvegarde vers Amazon S3...
    2013/01/14 09:51.31: Connecté au panier S: backup
    2013/01/14 09:51.31: Envoi vers Amazon S3 commencé...
    2013/01/14 09:51.32: [ERREUR] Amazon API: cURL resource: Resource id #290; cURL error: necessary data rewind wasn't possible (cURL error code 65). See http://curl.haxx.se/libcurl/c/libcurl-errors.html for an explanation of error codes.
    2013/01/14 09:51.32: Opération effectuée en 8 sec.
    Plugin Author Daniel Hüsken

    (@danielhuesken)

    That seams a Problem with the offical S3 SDK i will lok that i build a update.

    Vielen Dank, Daniel – Ich schätze Ihre Arbeit.

    I’m receiving the same “Undefined Index” error on a new site. I have had no issues with other sites. The only difference with the current site is that I created the bucket through the BackWPup interface. I tried creating a new bucket through the AWS console but it still fails to backup and throws the same error. Additionally, I deleted the first bucket through the AWS console and it says “deleted” but it still is listed. Any buckets created through the AWS console delete immediately.

    Hopefully this can get resolved as it is an outstanding plugin. Thank you for all the time and effort involved to develop it.

    Plugin Author Daniel Hüsken

    (@danielhuesken)

    Where cames the Massage “Undefined Index”?

    with deleting buckest i have had never a problem.

    In the log, same as abullard above:

    2013/01/22 06:16.06: Upload to Amazon S3 now started…
    2013/01/22 06:16.06: Undefined index: Message2013/01/22 06:16.06: [ERROR] Can not transfer backup to S3! (301)
    2013/01/22 06:16.07: 2. try sending backup file to Amazon S3…
    2013/01/22 06:16.07: Connected to S3 Bucket: my.bucket2013/01/22 06:16.07: Upload to Amazon S3 now started…
    2013/01/22 06:16.07: Undefined index: Message2013/01/22 06:16.07: [ERROR] Can not transfer backup to S3! (301)
    2013/01/22 06:16.07: 3. try sending backup file to Amazon S3…
    2013/01/22 06:16.07: Connected to S3 Bucket: my.bucket2013/01/22 06:16.07: Upload to Amazon S3 now started…
    2013/01/22 06:16.08: Undefined index: Message2013/01/22 06:16.08: [ERROR] Can not transfer backup to S3! (301)

    As for the bucket deletion that is not a big issue. The bucket deletes eventually. Just wanted to mention it if it is related since it only happens with buckets created through BackWPup. It may just be Amazon’s way of doing things. Thanks again.

    Plugin Author Daniel Hüsken

    (@danielhuesken)

    ok i think that is the problem with eu buckets wher i hope i can fix it with a update.

    Plugin Author Daniel Hüsken

    (@danielhuesken)

    can u plase tet the deveopment version .

    Hi, Daniel,

    I am still getting the error with the latest dev version:

    2013/01/25 00:37.53: [INFO]: BackWPup version 2.1.17; WordPress version 3.5; Copyright © 2013 Inpsyde GmbH Author: Daniel Hüsken
    2013/01/25 00:37.53: [INFO]: BackWPup comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions.
    2013/01/25 00:37.53: [INFO]: BackWPup job: 1. New; DB+FILE
    2013/01/25 00:37.53: [INFO]: BackWPup job started manualy
    2013/01/25 00:37.53: [INFO]: PHP ver.: 5.3.20; cgi-fcgi; Linux
    2013/01/25 00:37.53: [INFO]: MySQL ver.: 5.5.29-log
    2013/01/25 00:37.53: [INFO]: curl ver.: 7.24.0; OpenSSL/1.0.0
    2013/01/25 00:37.53: [INFO]: Temp folder is: /path-to-wp/wp-content/plugins/backwpup/tmp/
    2013/01/25 00:37.53: [INFO]: Backup file is: /path-to-wp/wp-content/plugins/backwpup/tmp/backwpup_1_2013-01-25_00-37-52.tar.gz
    2013/01/25 00:37.53: 1. try for database dump...
    2013/01/25 00:37.53: Dump database table "wp_aec_event"
    2013/01/25 00:37.53: Dump database table "wp_aec_event_category"
    2013/01/25 00:37.53: Dump database table "wp_commentmeta"
    2013/01/25 00:37.53: Dump database table "wp_comments"
    2013/01/25 00:37.53: Dump database table "wp_links"
    2013/01/25 00:37.53: Dump database table "wp_ngg_album"
    2013/01/25 00:37.53: Dump database table "wp_ngg_gallery"
    2013/01/25 00:37.53: Dump database table "wp_ngg_pictures"
    2013/01/25 00:37.53: Dump database table "wp_options"
    2013/01/25 00:37.53: Dump database table "wp_postmeta"
    2013/01/25 00:37.53: Memory increased from 128M to 394M
    2013/01/25 00:37.53: Dump database table "wp_posts"
    2013/01/25 00:38.16: Dump database table "wp_term_relationships"
    2013/01/25 00:38.16: Dump database table "wp_term_taxonomy"
    2013/01/25 00:38.16: Dump database table "wp_terms"
    2013/01/25 00:38.16: Dump database table "wp_usermeta"
    2013/01/25 00:38.16: Dump database table "wp_users"
    2013/01/25 00:38.16: Database dump done!
    2013/01/25 00:38.16: Add database dump "mydbbackup.sql" with 61.62 MB to backup file list
    2013/01/25 00:38.16: 1. try for make list of files to backup....
    2013/01/25 00:38.17: 2108 files with 91.6 MB to backup
    2013/01/25 00:38.17: 1. try to create tar.gz archive file...
    2013/01/25 00:38.53: tar.gz archive creation done
    2013/01/25 00:38.53: Archive size is 57.44 MB
    2013/01/25 00:38.53: 1. try sending backup file to Amazon S3...
    2013/01/25 00:38.53: Connected to S3 Bucket: www.mysite.org-backup
    2013/01/25 00:38.53: Upload to Amazon S3 now started...
    2013/01/25 00:38.53: Undefined index: Message
    2013/01/25 00:38.53: [ERROR] Can not transfer backup to S3! (301)
    2013/01/25 00:38.54: 2. try sending backup file to Amazon S3...
    2013/01/25 00:38.54: Connected to S3 Bucket: www.mysite.org-backup
    2013/01/25 00:38.55: Upload to Amazon S3 now started...
    2013/01/25 00:38.55: Undefined index: Message
    2013/01/25 00:38.55: [ERROR] Can not transfer backup to S3! (301)
    2013/01/25 00:38.55: 3. try sending backup file to Amazon S3...
    2013/01/25 00:38.56: Connected to S3 Bucket: www.mysite.org-backup
    2013/01/25 00:38.56: Upload to Amazon S3 now started...
    2013/01/25 00:38.56: Undefined index: Message
    2013/01/25 00:38.56: [ERROR] Can not transfer backup to S3! (301)
    2013/01/25 00:38.57: Job done in 65 sec.

    I ran a backup to be transferred to Amazon S3. It got stuck at the “try to create backup zip archive” stage for a very long time, never proceeded forward. However, when I login to my Amazon S3 console, it appears to have backed up and transferred just fine. So the problem is that the message wasn’t getting back to my WordPress dashboard. My account resides in US, eastern region.

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Backup not transferred to S3’ is closed to new replies.