Increasing the Data or Archive Pool Size
- 1 Minute to read
- Print
- PDF
Increasing the Data or Archive Pool Size
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Note
CTERA recommends changing the storage with the help of CTERA support CTERA Support.
To increase the storage:
- For each CTERA Portal instance you have installed, stop CTERA Portal services, by doing the following:
- Open an SSH session to the CTERA Portal instance.
- Log in as
root
user. - Run the command to stop the CTERA Portal services:
portal-manage.sh stop
- In the vSphere Client console, right-click the CTERA Portal virtual machine and click Edit Settings.
The virtual machine settings are displayed. - In the Virtual Hardware tab, click select Hard Disk under ADD NEW DEVICE.
A new hard disk is added to the settings. - Specify the disk size you want for the new disk.
- Expand the New Hard disk item and for Location browse to the datastore you want to use for either the data pool or archive pool.
- Select the disk to use.
- Click OK.
The new VMDK hard disk is added. - Log in as
root
over SSH to the CTERA Portal server with the archive pool to increase. - Run the following command to identify the name of the device you attached:
fdisk –l
- Locate the device name according to its size and usage information.
- Run the following command to extend the data pool:
portal-storage-util.sh extend_storage deviceName
where deviceName is the device name identified when you ranfdisk -l
. - Run the following command to extend the archive pool:
portal-storage-util.sh extend_db_archive_pool deviceName
where deviceName is the device name identified when you ranfdisk -l
.
For example:portal-storage-util.sh extend_db_archive_pool sde
- For each CTERA Portal instance, starting from the CTERA Portal main database and proceeding to the application servers, start CTERA Portal services.
- Log in as
root
user to each CTERA Portal server over SSH. - Run the following command to start the portal services:
portal-manage.sh start
- Log in as
Was this article helpful?