Skip to content

Commit

Permalink
3.12.2 release
Browse files Browse the repository at this point in the history
  • Loading branch information
@release-controller
release-controller[bot] authored and release-controller[bot] committed Apr 19, 2024
1 parent eb96f07 commit b072922
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 8 deletions.
2 changes: 1 addition & 1 deletion docs/getting-started.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Getting started

1. [Download the latest version of backup-utils][1] and extract the repository using `tar`:
1. [Download the latest release version][1] and extract the repository using `tar`:

`tar -xzvf /path/to/github-backup-utils-vMAJOR.MINOR.PATCH.tar.gz`

Expand Down
18 changes: 11 additions & 7 deletions docs/requirements.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,10 @@ However, if your rsync package has backported the CVE fix without backporting th

Option #3 is required if your operating system's package manager does not have access to rsync v3.2.5 or later (e.g. Ubuntu Focal).

Please note that some operating systems have their own versioning scheme for packages (including `rsync`).
If your backup host is using one of these operating systems, you will not be able to rely on a version check to determine whether you are
affected by the `rsync` performance degredation described above.

## Storage requirements

Storage requirements vary based on current Git repository disk usage and growth
Expand Down Expand Up @@ -65,23 +69,23 @@ Please avoid using an NFS mount for the data directory (where backup data is sto
Starting with Backup Utilities v2.13.0, version support is inline with that of the
[GitHub Enterprise Server upgrade requirements][8] and as such, support is limited to
three versions of GitHub Enterprise Server: the version that corresponds with the version
of Backup Utilities, and the two versions prior to it.
of Backup Utilities, and the two releases prior to it.

For example, Backup Utilities v2.13.0 can be used to backup and restore all patch
versions from 2.11.0 to the latest patch version of GitHub Enterprise Server 2.13.
releases from 2.11.0 to the latest patch release of GitHub Enterprise Server 2.13.
Backup Utilities v2.14.0 will be released when GitHub Enterprise Server 2.14.0 is released
and will then be used to backup all versions of GitHub Enterprise Server from 2.12.0
to the latest patch version of GitHub Enterprise Server 2.14.
and will then be used to backup all releases of GitHub Enterprise Server from 2.12.0
to the latest patch release of GitHub Enterprise Server 2.14.

Backup Utilities v2.11.4 and earlier offer support for GitHub Enterprise Server 2.10
and earlier versions up to GitHub Enterprise Server 2.2.0. Backup Utilities v2.11.0 and earlier
and earlier releases up to GitHub Enterprise Server 2.2.0. Backup Utilities v2.11.0 and earlier
offer support for GitHub Enterprise Server 2.1.0 and earlier.

**Note**: You can restore a snapshot that's at most two feature versions behind
**Note**: You can restore a snapshot that's at most two feature releases behind
the restore target's version of GitHub Enterprise Server. For example, to restore a
snapshot of GitHub Enterprise Server 2.11, the target GitHub Enterprise Server appliance must
be running GitHub Enterprise Server 2.12.x or 2.13.x. You can't restore a snapshot from
2.10 to 2.13, because that's three versions ahead.
2.10 to 2.13, because that's three releases ahead.

**Note**: You _cannot_ restore a backup created from a newer version of GitHub Enterprise Server to an older version. For example, an attempt to restore a snapshot of GitHub Enterprise Server 2.21 to a GitHub Enterprise Server 2.20 environment will fail with an error of `Error: Snapshot can not be restored to an older release of GitHub Enterprise Server.`.

Expand Down

0 comments on commit b072922

Please sign in to comment.