Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync backup to Amazon S3 #157

Closed
lushndm opened this issue Sep 25, 2018 · 6 comments
Closed

Sync backup to Amazon S3 #157

lushndm opened this issue Sep 25, 2018 · 6 comments
Assignees
Labels
bug

Comments

@lushndm
Copy link

@lushndm lushndm commented Sep 25, 2018

Hi!
Sync backup to Amazon S3 is interrupted with message:
"'InvalidArgumentException' with message 'File not found: phar:///usr/local/bin/phpbu/lib/aws-sdk/Endpoint/../data/endpoints_prefix_history.json'
in phar:///usr/local/bin/phpbu/lib/aws-sdk/functions.php:149"

@lushndm
Copy link
Author

@lushndm lushndm commented Sep 25, 2018

<phpbu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:noNamespaceSchemaLocation="http://schema.phpbu.de/5.0/phpbu.xsd">
  <backups>
    <backup name="xtra">
      <!-- create a json logfile -->
      <log type="json" target="/home/appuser/mybackups/log-xtrabackup.json"/>

      <adapter type="env" name="myEnv"></adapter>

      <!-- source xtrabackup -->
      <source type="xtrabackup">
        <option name="user" value="backup" />
        <option name="password" value="secretpassword" />
      </source>

      <target dirname="/backups/mysql-xtra"
              filename="xtra-%Y%m%d-%H%i"
              compress="bzip2"/>

      <!-- sync amazon s3 -->
      <sync type="amazons3">
        <option name="key" value="STRONGAMAZONKEY"/>
        <option name="secret" value="strongsecretvalue"/>
        <option name="bucket" value="bucketname"/>
        <option name="region" value="eu-west-3"/>
        <option name="path" value="/backup/"/>
      </sync>

      <!-- cleanup quantity: keep the last 3 backups -->
      <cleanup type="quantity">
        <option name="amount" value="3"/>
      </cleanup>

    </backup>
  </backups>
</phpbu>
@lushndm
Copy link
Author

@lushndm lushndm commented Sep 25, 2018


Runtime:       PHP 7.0.32-0ubuntu0.16.04.1
Configuration: /backups/mysql-xtra/phpbu-xtra.xml

backup: [xtrabackup] ******************************************************
(/usr/bin/innobackupex --no-timestamp --user='backup' --password='******' '/backups/mysql-xtra/dump' && /usr/bin/innobackupex --apply-log '/backups/mysql-xtra/dump')
(/bin/tar -jcf '/backups/mysql-xtra/xtra-20180925-1415.tar.bz2' -C '/backups/mysql-xtra' 'dump' && rm -rf '/backups/mysql-xtra/dump')
ok

sync: [amazons3] **********************************************************
exception: File not found: phar:///usr/local/bin/phpbu/lib/aws-sdk/Endpoint/../data/endpoints_prefix_history.json
failed

Time: 13 seconds, Memory: 6.00MB

Exception 'InvalidArgumentException' with message 'File not found: phar:///usr/local/bin/phpbu/lib/aws-sdk/Endpoint/../data/endpoints_prefix_history.json'
in phar:///usr/local/bin/phpbu/lib/aws-sdk/functions.php:149

backup xtra: FAILED
@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented Sep 25, 2018

oO

@sebastianfeldmann sebastianfeldmann self-assigned this Sep 25, 2018
@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented Sep 25, 2018

Will fix it directly

sebastianfeldmann added a commit that referenced this issue Sep 25, 2018
@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented Sep 25, 2018

Please update to version 5.1.4

The missing file should be there.
Sorry and thanks again for reporting this

@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented Sep 25, 2018

Can you please confirm that version 5.1.4 is working?
For me the AWS sync is working again.
If you confirm the fix I will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.