4

I would suggest you take a look at AcloudA that can be used as hardware gateway that presents cloud storage as local DAS to your server and offloads data to the cloud. It can be installed either in local server or NAS (it depends on hardware specifics that you use) as SATA/SAS HDD with connectivity to cloud (either Amazon or Azure) allowing to run backup ...


3

Did you run Cloudberry Backup service under the right service account? By default it uses Local System account.


2

It really depends on your file size and number of object Storage GW from AWS costs you on monthly basis and you have caching option which is good. CloudBerry Backup has block level backup where huge objects can be offloaded on incremental block level basis (basically changes goes to S3) what gives you another recovery point. There is also real time ...


2

You are probably doing incremental backups. The \20130202191902\ suggests there might be several modified versions of the same file backed up. Such backups are ment to be recovered using the same tool that created them, not by copying the files back.


2

As strange as this may seem the documentation appears to contain the answer to your question. -notification - specify to receive notification email when backup fails (errorOnly) or in all cases (on). Possible values: errorOnly (default) |on.


2

Our software runs forever incremental - that means, that after the first full backup we upload only the changed parts of files. However, we do not do the forever block level backup. Block level is available only in advanced mode. You should choose advanced mode and after that, from advanced settings, you should enable block level. To learn more about our ...


1

Apologies for writing a delayed answer: But in my script, change the condition in this way: "Condition":{"StringLike":{"s3:prefix":["home/David/*"]}} Thanks to ceejayoz, for pointing me this error.


1

I managed to fix this in the end by running the Consistency Check within Cloudberry against the Azure Storage Account. This found a lot of warnings of files the Cloudberry database didn't know about, either locally or remote. It fixed all of these warnings and the backup began working normally again.


1

you can try Veeam Agent for Linux. The link is right here https://www.veeam.com/linux-cloud-server-backup-agent.html


1

Hello and thanks for evaluating our product. For Linux we don't use direct upload to Glacier. Please go to edit | lifecycle policy and set archive to Glacier transition to 0 days. In that case, your files will be transferred automatically from S3 to Glacier with no additional costs.


1

In my opinion, it is better to use native S3 API for automating relatively simple tasks. I found Cloudberry's API being less reliable for such cases. Take a look here for more info: http://docs.aws.amazon.com/cli/latest/reference/s3api/get-object.html


1

Currently you can configure different retention policies in separate plans only. Thanks for the suggestion! We have added your vote to the feature request.


1

That was caused by some API changes on AWS side. However, in new release everything works fine again.


1

Seen such errors with various backup apps, usually it's a COM permission issue. Start > Run > dcomcnfg On the right-side of the newly-opened windows, expand the Component Services > Computers > My Computer nodes. Right-click on My Computer and select Properties from the contextual menu. In the newly-opened window, select the COM Security tab. look up for ...


1

I'm no s3 expert but have you tried giving it the ListAllMyBuckets privilege? I had this problem when trying to access s3 using s3cmd from an ec2 instance even though I granted all privileges with :* I had to explicitly give the ListAllMyBuckets privilege: "Sid": "Stmt1397683550000", "Effect": "Allow", "Action": [ "s3:ListAllMyBuckets" ], "...


Only top voted, non community-wiki answers of a minimum length are eligible