You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 165356b
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: content/admin/backing-up-and-restoring-your-instance/configuring-elasticsearch-snapshots.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ This feature is opt-in. If you don't configure a snapshot repository, {% data va
33
33
34
34
Configure the following settings using `ghe-config` over SSH. For more information, see [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh).
35
35
36
-
You'll apply the configuration to register the snapshot repository with Elasticsearch. The repository is named `search_index_snapshots-VERSION`, where `VERSION` is the current {% data variables.product.prodname_ghe_server %} release version.
36
+
You'll apply the configuration to register the snapshot repository with Elasticsearch. The repository is named `search_index_snapshots-vVERSION`, where `VERSION` is the current {% data variables.product.prodname_ghe_server %} release version.
37
37
38
38
### Azure Blob storage
39
39
@@ -106,7 +106,7 @@ You'll apply the configuration to register the snapshot repository with Elastics
106
106
After configuration apply completes, confirm the snapshot repository was registered.
If a required secret is missing, configuration apply fails while registering the repository. Update the secrets and rerun `ghe-config-apply` to retry.
@@ -137,9 +137,9 @@ You can manage Elasticsearch snapshots directly using the following commands. Ru
137
137
138
138
| Command | Description |
139
139
| --- | --- |
140
-
|`ghe-es-create-snapshot`| Creates a new snapshot in the configured repository. |
141
-
|`ghe-es-list-snapshots`| Lists snapshot repositories, or snapshots within a repository. |
142
-
|`ghe-es-restore-snapshot`| Restores search indices from a snapshot. |
140
+
|`/usr/local/share/enterprise/ghe-es-create-snapshot`| Creates a new snapshot in the configured repository. |
141
+
|`/usr/local/share/enterprise/ghe-es-list-snapshots`| Lists snapshot repositories, or snapshots within a repository. |
142
+
|`/usr/local/share/enterprise/ghe-es-restore-snapshot`| Restores search indices from a snapshot. |
143
143
144
144
> [!TIP]
145
145
> For routine backups and restores, use {% data variables.product.prodname_enterprise_backup_utilities %} or {% data variables.product.prodname_enterprise_backup_service %} instead of these commands directly. The backup tooling coordinates Elasticsearch snapshots with the rest of your instance's data to ensure a consistent backup or restore. Use the manual commands only when you need to manage search index snapshots independently of a full instance backup or restore.
@@ -151,13 +151,13 @@ You can restore a snapshot created by an earlier {% data variables.product.prodn
151
151
1. List available snapshots for the earlier version.
Copy file name to clipboardExpand all lines: content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,6 @@ The following features are currently unavailable on {% data variables.enterprise
23
23
| Feature | Details | More information |
24
24
| :- | :- | :- |
25
25
| Dependency insights | Organization-level and enterprise-level dependency insights are unavailable and display no data. |[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization)|
26
-
| License and package metadata in the dependency graph | License and package details are not currently populated in the dependency graph. This can result in empty license fields in software bill of materials (SBOM) exports and missing license information from the {% data variables.dependency-review.action_name %}. |[AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/establish-provenance-and-integrity/export-dependencies-as-sbom)<br>[AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-dependency-review-action)|
27
26
| macOS runners for {% data variables.product.prodname_actions %} | Currently unavailable. |[AUTOTITLE](/actions/concepts/runners/github-hosted-runners)|
28
27
| Maven and Gradle support for {% data variables.product.prodname_registry %} | Currently unavailable. |[AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)|
29
28
| {% data variables.product.prodname_marketplace %} | {% data variables.product.prodname_marketplace %}, as a means of searching for, purchasing, and directly installing apps and actions, is unavailable. Ecosystem apps and actions can still be discovered and installed from their source, but they may require modification to work on {% data variables.enterprise.data_residency_site %}. |[{% data variables.product.prodname_actions %} workflows from {% data variables.product.prodname_marketplace %}](#github-actions-workflows-from-github-marketplace)|
0 commit comments