[PCA 2.x] How to Increase Repository Capacity in the Oracle Private Cloud Appliance
(Doc ID 1938558.1)
Last updated on DECEMBER 01, 2024
Applies to:
Private Cloud Appliance - Version 1.0.1 and laterPrivate Cloud Appliance X5-2 Hardware - Version All Versions and later
Private Cloud Appliance X8-2 - Version All Versions and later
Oracle VM - Version 3.4.6 to 3.4.6 [Release OVM34]
Linux x86-64
Oracle's Private Cloud Appliance ships with an internal ZFS storage appliance intended as a "system disk" for the entire appliance, This includes a default Oracle VM repository named Rack1-Repository, sized at 300GB or 3TB depending on PCA version. This document shows how to add additional space by enlarging the repository's iSCSI LUN, or by creating a repository on an NFS mountpoint available on the internal ZFS appliance, or by creating a new iSCSI LUN on the internal ZFS appliance.
It is important to leave residual disk capacity for other functions. If the PCA multi-tenant feature will be used, then disk capacity must be kept available for each tenant group's repository and pool file systems. The internal ZFS appliance on PCA X5 InfiniBand based PCA systems is a small capacity device, so repository capacity should be enlarged to no more than 8TB. The ZS7-2 appliance in a PCA X8 default capacity is much larger, and can be expanded with additional storage trays.
On PCA X5 and earlier, the recommendation is to use external storage such as an InfiniBand connected ZFS appliance.
It is important to leave residual disk capacity for other functions. If the PCA multi-tenant feature will be used, then disk capacity must be kept available for each tenant group's repository and pool file systems.
Goal
This note shows how to expand repository capacity in the Private Cloud Appliance (PCA) beyond the default repository allocation.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |