---
title: "KVM Specific Management"
slug: "openstackkvm-specific-management-5-1-1"
tags: ["Portal"]
updated: 2026-04-12T10:33:07Z
published: 2026-04-12T10:33:07Z
canonical: "kb.ctera.com/openstackkvm-specific-management-5-1-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# KVM Specific Management

## Increasing the Data or Archive Pool Size

          **Note**

          

CTERA recommends changing the storage with the help of CTERA support [CTERA Support](https://ctera.com/support).

**To increase the storage:**

1. For each CTERA Portal instance you have installed, stop CTERA Portal services, by doing the following:
  1. Open an SSH session to the CTERA Portal instance.
  2. Log in as `root` user.
  3. Run the command to stop the CTERA Portal services: `portal-manage.sh stop`
2. On the primary database server, or the replication, secondary, server, create a new disk using the following command: `qemu-img create -f qcow2 /<path>/<newdisk>.qcow2 <diskSize>` where *path* is the path to the new disk image, *newdisk* is the name for the disk and *diskSize* is the size of the disk.  

The volume is created. This can take a few minutes.
3. Change the permissions for the disk using the following command: `chmod 777`
4. Run `fdisk -l` to identify the device for the new disk.
5. Attach the new disk to the portal server using the following command: `virsh attach-disk <name> /<path>/<newdisk>.qcow2 <vdc> --cache none --persistent`  

where:  

*name* is the name assigned to the CTERA Portal server VM.  

*path* is the path to the new dis image.  

*newdisk* is the name of the new disk.  

*vdc* is the free device for the disk, identified by fdisk.  

*--cache none* is the disk cache mode and is optional.  

*--persistent* ensures that the disk remains attached after the VM is rebooted.
6. Extend the storage, by doing the following:
  1. Run the following command to extend the data pool: `portal-storage-util.sh extend_storage <deviceName>`  

where *device* is the device name identified when you ran `fdisk -l`
  2. Run the following command to extend the archive pool: `portal-storage-util.sh extend_db_archive_pool <device>`  

where *device* is the device name identified when you ran `fdisk -l`
7. For each CTERA Portal instance you installed, starting from the CTERA Portal main database and proceeding to the application servers, start CTERA Portal services by doing the following:
  1. Log in as `root` user to each CTERA Portal server over SSH.
  2. Run the following command to start the portal services: `portal-manage.sh start`