jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Docs for local storage migrations option (#56145)

Browse Source 
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
Co-authored-by: Jules <19994093+jules-p@users.noreply.github.com>
This commit is contained in:
Isaac Brown
2025-07-24 17:18:34 +01:00
committed by GitHub
parent 36c3a048f4
commit 7b7bbafe13
3 changed files with 32 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
View File

@@ -69,27 +69,25 @@ To migrate your repositories from {% data variables.product.prodname_ghe_server
## Step 3: Set up blob storage
Because many {% data variables.product.prodname_ghe_server %} instances sit behind firewalls, for {% data variables.product.prodname_ghe_server %} versions 3.8 or higher, we use blob storage as an intermediate location to store your data that {% data variables.product.prodname_dotcom %} can access.
You must first set up blob storage with a supported cloud provider, then configure your settings in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}.
{% data reusables.enterprise-migration-tool.blob-storage-intro %}
> [!NOTE]
> You only need to configure blob storage if you use {% data variables.product.prodname_ghe_server %} versions 3.8 or higher. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, skip to [Step 4: Set up a migration source in {% data variables.product.prodname_ghe_cloud %}](#step-4-set-up-a-migration-source-in-github-enterprise-cloud).
>
> Blob storage is required to migrate repositories with large Git source or metadata. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, you will not be able to perform migrations where your Git source or metadata exports exceed 2GB. To perform these migrations, update to {% data variables.product.prodname_ghe_server %} versions 3.8 or higher.
### Setting up blob storage with a supported cloud provider
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
#### Setting up an AWS S3 storage bucket
### Setting up an AWS S3 storage bucket
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
#### Setting up an Azure Blob Storage account
### Setting up an Azure Blob Storage account
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
### Using local storage (GHES 3.16+)
{% data reusables.enterprise-migration-tool.local-storage-steps %}
### Configuring blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}
{% data reusables.enterprise-migration-tool.blob-storage-management-console %}
@@ -330,25 +328,23 @@ For {% data variables.product.pat_generic %} requirements, see [AUTOTITLE](/migr
## Step 4: Set up blob storage
Because many {% data variables.product.prodname_ghe_server %} instances sit behind firewalls, we use blob storage as an intermediate location to store your data that {% data variables.product.prodname_dotcom %} can access.
{% data reusables.enterprise-migration-tool.blob-storage-intro %}
First, you must set up blob storage with a supported cloud provider. Then, you must configure your credentials for the storage provider in the {% data variables.enterprise.management_console %} or {% data variables.product.prodname_cli %}.
### Setting up blob storage with a supported cloud provider
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
#### Setting up an AWS S3 storage bucket
### Setting up an AWS S3 storage bucket
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
#### Setting up an Azure Blob Storage storage account
### Setting up an Azure Blob Storage storage account
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
### Using local storage (GHES 3.16+)
{% data reusables.enterprise-migration-tool.local-storage-steps %}
### Configuring your blob storage credentials
After you set up blob storage with a supported cloud provider, you must configure your credentials for the storage provider in {% data variables.product.prodname_dotcom %}:
If you set up blob storage with a **cloud provider** (as opposed to local storage), you must configure your credentials for the storage provider in {% data variables.product.prodname_dotcom %}:
* If you use {% data variables.product.prodname_ghe_server %} 3.8 or higher, configure your credentials in the {% data variables.enterprise.management_console %}.
* If you use {% data variables.product.prodname_ghe_server %} 3.7 or lower, configure the credentials in the {% data variables.product.prodname_cli %}.

6
data/reusables/enterprise-migration-tool/blob-storage-intro.md Normal file
View File

@@ -0,0 +1,6 @@
You must store your repository data in a place that {% data variables.product.prodname_dotcom %} can access. If your {% data variables.product.prodname_ghe_server %} instance is behind a firewall, you may need to set up blob storage with an external cloud service.
First, you must set up blob storage with a supported provider. Then, if you're using a cloud provider, you must configure your credentials for the storage provider in the {% data variables.enterprise.management_console %} or {% data variables.product.prodname_cli %}.
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
* Local storage on the GHES instance (GHES **3.16** and later)

11
data/reusables/enterprise-migration-tool/local-storage-steps.md Normal file
View File

@@ -0,0 +1,11 @@
When you run a migration with local storage, archive data is written to the disk on {% data variables.location.product_location_enterprise %}, without the need for a cloud storage provider. {% data variables.product.prodname_importer_proper_name %} will automatically retrieve the stored archive from {% data variables.product.prodname_ghe_server %}, unless you have blocked egress traffic from {% data variables.product.prodname_ghe_server %}.
1. From an administrative account on {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click {% octicon "rocket" aria-label="Site admin" %}.
{% data reusables.enterprise_site_admin_settings.management-console %}
1. Sign in to the {% data variables.enterprise.management_console %}.
1. In the left sidebar, click **Migrations**.
1. Click **Enable {% data variables.product.company_short %} Migrations**.
1. Under "Migrations Storage", click **Local Storage**.
1. Click **Save settings**.
When you perform the migration, monitor your disk space on {% data variables.product.prodname_ghe_server %}. Migration archives are automatically deleted after 7 days. To free up space, you can delete an archive using the [AUTOTITLE](/rest/migrations/orgs#delete-an-organization-migration-archive).