CyberHosting

Bug in Incremental Backup?

AWS Incremental backup is not working in my server.

OS : Centos 7
OLS 1.5.7


Will first initiate backup repo..
sh: restic: command not found

Domains matching query does not exist.. [warning:179:prepMeta]
Meta data is ready..
Backing up data..
sh: restic: command not found

Data for mydomain.com backed to s3:s3.amazonaws.com/XXXXXXXXXXXXXXX.
Backing up databases..
sh: restic: command not found

Backing up emails..
sh: restic: command not found

Emails for mydomain.com backed to s3:s3.amazonaws.com/XXXXXXXXXXXXXXX.
Backing up meta..
sh: restic: command not found

Meta for mydomain.com backed to s3:s3.amazonaws.com/XXXXXXXXXXXXXXX.
Completed

Comments

  • So restic installation failed, it was fresh installation or upgrade?
  • edited October 19
    Sorry to hijacking the post but same bug here.

    It was an upgrade for me.

    Edit:

    Got it working by installing restic:

    yum -y install yum-utils-1.1.31-52.el7.noarch

    yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/copart/restic/repo/epel-7/copart-restic-epel-7.repo

    yum install restic
  • So restic installation failed, it was fresh installation or upgrade?

    Upgrade
  • @Luke007 you can install restic using @trifo13 comments, it should be fine then.
  • @CyberPanel S3 incremental backup is still not working

    Will first initiate backup repo..
    Fatal: create repository at s3:s3.amazonaws.com/mydomain.com failed: client.BucketExists: The difference between the request time and the current time is too large.


    Domains matching query does not exist.. [warning:179:prepMeta]
    Meta data is ready..
    Backing up data..
    Fatal: unable to open config file: Stat: The difference between the request time and the current time is too large.
    Is there a repository at the following location?
    s3:s3.amazonaws.com/mydomain.com

    Data for mydomain.com backed to s3:s3.amazonaws.com/XXXXXXXXXXXXXXXXXXXX.
    Backing up databases..
    Fatal: unable to open config file: Stat: The difference between the request time and the current time is too large.
    Is there a repository at the following location?
    s3:s3.amazonaws.com/mydomain.com

    Backing up meta..
    Fatal: unable to open config file: Stat: The difference between the request time and the current time is too large.
    Is there a repository at the following location?
    s3:s3.amazonaws.com/mydomain.com

    Meta for mydomain.com backed to s3:s3.amazonaws.com/XXXXXXXXXXXXXXXXXXXX.
    Completed

  • Go to your AWS account and open S3, do you see any domains folder there? Make sure you delete those folder and try again.
  • Go to your AWS account and open S3, do you see any domains folder there? Make sure you delete those folder and try again.

    There is no domain folder or bucket.
  • edited November 3
    The error says otherwise
    Will first initiate backup repo..
    Fatal: create repository at s3:s3.amazonaws.com/mydomain.com failed: client.BucketExists: The difference between the request time and the current time is too large.
    For every domain there will be a bucket in S3. On your logs it is saying client.BucketExists
  • The error says otherwise

    Will first initiate backup repo..
    Fatal: create repository at s3:s3.amazonaws.com/mydomain.com failed: client.BucketExists: The difference between the request time and the current time is too large.
    For every domain there will be a bucket in S3. On your logs it is saying client.BucketExists
    I don't know why the log reads so. There is no such bucket in my S3 account.
Sign In or Register to comment.
CyberPanel Discord

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!