Have you checked borgbackup docs, FAQ, and open Github issues?

Yup.

Is this a BUG / ISSUE report or a QUESTION?

ISSUE / feature request.

System information. For client/server mode post info for both machines.

Your borg version (borg -V).

1.1.10

Operating system (distribution) and version.

Manjaro Linux 18.1.1

Hardware / network configuration, and

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

What steps did you take and what happened:
Create two backups A and B one after the other:

velero backup create A 
velero backup create B

Get the jobs:

velero backup get
# ...
# A                            InProgress
# B                            New

While A is running, delete B:

velero backup delete B

After A is finished B gets exec

Dear Guillaume,
There is a tiny error in your documentation here: http://gmvault.org/in_depth.html
This line:

You can renew a saved oauth token with the option --renew-oauth-tok

should read:

You can renew a saved oauth token with the option --renew-oauth2-tok

The 2 is missing. The missing 2 causes an error when a user tries to renew the Oauth token. Would be great if you co

I need a clarification on this for auditing and compliance purposes.
The wal-e docs don't seem to mention what is the default cipher used, or if it simply uses gpg's defaults (which seems to have changed since gpg 2.1)?
Does wal-e enforce a particular cipher?
I would suggest this info be added to the documentation as well...
Thanks!

I suggest documenting the flags, and their usage, in the readme file.
They can be found in main.go or via "timeliner -help"

For example:

timeliner -repo /Volumes/XDrive get-all google_photos/me@gmail.com

Hi there,

I advised of an issue with the expiration strategy, however the issue was closed when the branch was merged to the master: laurent22/rsync-time-backup#105

Because the expiration strategy uses an absolute timestamp value to calculate the age between backups, it deletes backups that don't match the exact durations required.

The 2 examples below show diffe

General information

• App version: 0.6.3.1-play
• App source: Google Play
• Android Version: 9
• Custom ROM: Samsung OneUI 1.0

Request

Add an icon for Bugcrowd, as their accounts support 2FA.

Recent merges to add GCS and file support didn't completely update the readme, which now appears to single-out S3.

When uploading backups to S3

Although Config::Root is correctly set to $OXIDIZED_HOME when it exists, the config file is not read from this location. Oxidized will only find a config in either /etc/oxidized/config or $HOME/.config/oxidized/config (which I believe is due to Asetus only looking in those locations).

Expected behavior is that setting OXIDIZED_HOME would cause the confi

It’d be super nice if libarchive aka libCVE had proper, human-readable changelogs with references to security fixes. Right now the NEWS file is so incomplete as to be useless, and the release notes page on the wiki hasn’t been updated in ages.

It would be useful for others to have some information how they can create offsite backups without storing the configuration anywhere (at least not on the server).

At least I miss some best practice information ;-)

In unyson builder (block editor for wordpress) if setting a checkbox "multiple choice" and enabled as mandatory it let post the form anyway even if the check is not checked

I just wanted to mention a possible error in the FAQ.

In the section How to move snapshots to a new hard drive, the command line indicated in solution 3:
cd /DESTINATION; tar cf - /SOURCE/* | tar xf -
might have to be replaced by:
cd /SOURCE; tar cf - * | tar -C /DESTINATION/ -xf -

Otherwise o

Documentation should cover the followings:

• Logical Backup (feasible for small databases)
  • Using mysqldump+restic
• Physical Backup (feasible for large databases)
  • File system backup (using sidecar+restic)
  • Snapshot (using VolumeSnapshot)
• Offline Backup (Use hook to pause database server)
• Customizing backup process
  • Provide additional flags (i.e. --single-transaction

The main first point of contact for new users is https://github.com/dpc/rdedup - and the rendering of the README.md which is automatically shown. Adding some content from https://github.com/dpc/rdedup/wiki/My-original-use-case-(old-README.md) would get the message over more clearly, e.g. the unique features of rdedup such as the ability to securely backup multiple hosts with compression and de-du

The following statement in the manual is confusing: "It is important, however, that you use the same version of the xtrabackup binary that you used to create the backup to do the prepare."

It might be a remnant from the times when we had multiple xtrabackup binaries. Or it might mean that the same XtraBackup release should be used on both backup and prepare stages.

In any case the statement is i

Please provide the following information when submitting an issue (feature requests or general comments can skip this):

1. pgBackRest version:
   2.22

2. PostgreSQL version:
   9.4.2

3. Operating system/version - if you have more than one server (for example, a database server, a repository host server, one or more standbys), please specify each:
   Ubuntu 12.04.5 LTS x86_64 server

4. Did yo