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
Copy file name to clipboardExpand all lines: content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
+15-19Lines changed: 15 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,27 +69,25 @@ To migrate your repositories from {% data variables.product.prodname_ghe_server
69
69
70
70
## Step 3: Set up blob storage
71
71
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 %}
75
73
76
74
> [!NOTE]
77
75
> 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).
78
76
>
79
77
> 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.
80
78
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
86
80
87
81
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
88
82
89
-
####Setting up an Azure Blob Storage account
83
+
### Setting up an Azure Blob Storage account
90
84
91
85
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
92
86
87
+
### Using local storage (GHES 3.16+)
88
+
89
+
{% data reusables.enterprise-migration-tool.local-storage-steps %}
90
+
93
91
### Configuring blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}
94
92
95
93
{% data reusables.enterprise-migration-tool.blob-storage-management-console %}
@@ -330,25 +328,23 @@ For {% data variables.product.pat_generic %} requirements, see [AUTOTITLE](/migr
330
328
331
329
## Step 4: Set up blob storage
332
330
333
-
Because many {% data variables.product.prodname_ghe_server %} instances sit behind firewalls, we use blobstorage 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 %}
334
332
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
342
334
343
335
{% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
344
336
345
-
####Setting up an Azure Blob Storage storage account
337
+
### Setting up an Azure Blob Storage storage account
346
338
347
339
{% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
348
340
341
+
### Using local storage (GHES 3.16+)
342
+
343
+
{% data reusables.enterprise-migration-tool.local-storage-steps %}
344
+
349
345
### Configuring your blob storage credentials
350
346
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 %}:
352
348
353
349
* If you use {% data variables.product.prodname_ghe_server %} 3.8 or higher, configure your credentials in the {% data variables.enterprise.management_console %}.
354
350
* If you use {% data variables.product.prodname_ghe_server %} 3.7 or lower, configure the credentials in the {% data variables.product.prodname_cli %}.
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)
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