Increasing storage capacity

You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.

In this article

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

Warning: The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "Monitoring your GitHub Enterprise Server appliance."

As more users join your GitHub Enterprise Server instance, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.

Requirements and recommendations

Note: Before resizing the user storage volume, put your instance in maintenance mode. For more information, see "Enabling and scheduling maintenance mode."

Minimum requirements for an instance with beta features enabled are bold in the following table. For more information, see "Beta features in GitHub Enterprise Server 2.22."

User licensesvCPUsMemoryAttached storageRoot storage
Trial, demo, or 10 light users2
or 4
16 GB
or 32 GB
100 GB
or 150 GB
200 GB
10 to 3,0004
or 8
32 GB
or 48 GB
250 GB
or 300 GB
200 GB
3,000 to 50008
or 12
64 GB500 GB200 GB
5,000 to 800012
or 16
96 GB750 GB200 GB
8,000 to 10,000+16
or 20
128 GB
or 160 GB
1000 GB200 GB

Beta features in GitHub Enterprise Server 2.22

If you enable beta features in GitHub Enterprise Server 2.22, your instance requires additional hardware resources. For more information about the beta features, see the release notes for the 2.22 series on the GitHub Enterprise website.

Increasing the data partition size

  1. Resize the existing user volume disk using your virtualization platform's tools.
  2. SSH into your GitHub Enterprise Server instance.
    $ ssh -p 122 admin@HOSTNAME
  3. Put the appliance in maintenance mode. For more information, see "Enabling and scheduling maintenance mode."
  4. Reboot the appliance to detect the new storage allocation.
  5. Run the ghe-storage-extend command to expand the /data filesystem:
    $ ghe-storage-extend

Increasing the root partition size using a new appliance

  1. Set up a new GitHub Enterprise Server instance with a larger root disk using the same version as your current appliance. For more information, see "Setting up a GitHub Enterprise Server instance."
  2. Shut down the current appliance.
  3. Detach the data disk from the current appliance using your virtualization platform's tools.
  4. Attach the data disk to the new appliance with the larger root disk.

Increasing the root partition size using an existing appliance

  1. Attach a new disk to your GitHub Enterprise Server appliance.
  2. Run the parted command to format the disk:
    $ sudo parted /dev/xvdg mklabel msdos
    $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
    $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
  3. Run the ghe-upgrade command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as github-enterprise-2.11.9.hpkg, will not work as expected.
    $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
  4. Shut down the appliance.
  5. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
  6. Start the appliance.

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.