Skip to content

Commit 7b7bbaf

Browse files
isaacmbrownheiskrjules-p
authored
Docs for local storage migrations option (#56145)
Co-authored-by: Kevin Heis <[email protected]> Co-authored-by: Jules <[email protected]>
1 parent 36c3a04 commit 7b7bbaf

File tree

3 files changed

+32
-19
lines changed

3 files changed

+32
-19
lines changed

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

Lines changed: 15 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -69,27 +69,25 @@ To migrate your repositories from {% data variables.product.prodname_ghe_server
6969

7070
## Step 3: Set up blob storage
7171

72-
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.
73-
74-
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 %}.
72+
{% data reusables.enterprise-migration-tool.blob-storage-intro %}
7573

7674
> [!NOTE]
7775
> 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).
7876
>
7977
> 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.
8078
81-
### Setting up blob storage with a supported cloud provider
82-
83-
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
84-
85-
#### Setting up an AWS S3 storage bucket
79+
### Setting up an AWS S3 storage bucket
8680

8781
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
8882

89-
#### Setting up an Azure Blob Storage account
83+
### Setting up an Azure Blob Storage account
9084

9185
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
9286

87+
### Using local storage (GHES 3.16+)
88+
89+
{% data reusables.enterprise-migration-tool.local-storage-steps %}
90+
9391
### Configuring blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}
9492

9593
{% data reusables.enterprise-migration-tool.blob-storage-management-console %}
@@ -330,25 +328,23 @@ For {% data variables.product.pat_generic %} requirements, see [AUTOTITLE](/migr
330328

331329
## Step 4: Set up blob storage
332330

333-
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.
331+
{% data reusables.enterprise-migration-tool.blob-storage-intro %}
334332

335-
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 %}.
336-
337-
### Setting up blob storage with a supported cloud provider
338-
339-
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
340-
341-
#### Setting up an AWS S3 storage bucket
333+
### Setting up an AWS S3 storage bucket
342334

343335
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
344336

345-
#### Setting up an Azure Blob Storage storage account
337+
### Setting up an Azure Blob Storage storage account
346338

347339
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
348340

341+
### Using local storage (GHES 3.16+)
342+
343+
{% data reusables.enterprise-migration-tool.local-storage-steps %}
344+
349345
### Configuring your blob storage credentials
350346

351-
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 %}:
347+
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 %}:
352348

353349
* If you use {% data variables.product.prodname_ghe_server %} 3.8 or higher, configure your credentials in the {% data variables.enterprise.management_console %}.
354350
* If you use {% data variables.product.prodname_ghe_server %} 3.7 or lower, configure the credentials in the {% data variables.product.prodname_cli %}.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
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.
2+
3+
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 %}.
4+
5+
{% data reusables.enterprise-migration-tool.supported-blob-storage-providers %}
6+
* Local storage on the GHES instance (GHES **3.16** and later)
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
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 %}.
2+
3+
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" %}.
4+
{% data reusables.enterprise_site_admin_settings.management-console %}
5+
1. Sign in to the {% data variables.enterprise.management_console %}.
6+
1. In the left sidebar, click **Migrations**.
7+
1. Click **Enable {% data variables.product.company_short %} Migrations**.
8+
1. Under "Migrations Storage", click **Local Storage**.
9+
1. Click **Save settings**.
10+
11+
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).

0 commit comments

Comments
 (0)