---
title: "Installing CTERA Portal Instances"
slug: "installing-ctera-portal-instances-43-2"
tags: ["Portal", "8.3"]
updated: 2026-08-31T13:31:41Z
published: 2026-08-31T13:31:41Z
canonical: "kb.ctera.com/installing-ctera-portal-instances-43-2"
---

> ## 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.

# Installing CTERA Portal Instances

Use the following workflow to install CTERA Portal.

1. [Creating a Portal Instance](/v1/docs/installing-ctera-portal-instances-43-2) using a CTERA Portal image obtainable from [CTERA support](https://www.ctera.com/support/).
2. [Configuring Network Settings](/v1/docs/configuring-network-settings-6).
3. Optionally, if it is not set correctly, [configure a default gateway](/v1/docs/configuring-a-default-gateway-14).
4. [Additional Installation Instructions for Customers Without Internet Access](/v1/docs/additional-installation-instructions-for-customers-without-internet-access-10-2).
5. For the first server you install, follow the steps in [Configuring the Primary Server](/v1/docs/configuring-the-primary-server-5-2).
6. For any additional servers beside the primary server, install the server as described below and configure it as an additional server, as described in [Installing and Configuring Additional CTERA Portal Servers](/v1/docs/installing-and-configuring-additional-ctera-portal-servers-5-2).
7. Make sure that you replicate the database, as described in [Configuring the CTERA Portal Database for Backup](/v1/docs/configuring-ctera-portal-database-for-backup-and-restore-3).
8. Backup the server as described in [Backing Up the CTERA Portal Servers and Storage](/v1/docs/backing-up-the-ctera-portal-servers-and-storage-4).

**Note**

You can use block-storage-level snapshots for backup, but snapshots are periodical in nature, configured to run every few hours. Therefore, you cannot recover the metadata to any point-in-time, and can lose a significant amount of data on failure. Also, many storage systems do not support block-level snapshots and replication, or do not do so efficiently.

## Creating a Portal Instance

You can install the CTERA Portal on Red Hat OpenShift console. The installation requires the CTERA Portal qcow2 image, that you get from [CTERA support](https://www.ctera.com/support/) and save to the client computer.

**To install the CTERA Portal Server:**

1. Log in to the Red Hat OpenShift console.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-AGHM04SA.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
2. If necessary, change the view to **Administrator**, in the top left drop-down.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-31EOFP2C.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

The **Projects** page is displayed.
3. Click **Virtualization > Templates** in the navigation pane.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-OBKR0J1E.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

If the **VM from uploaded QCOW2 - UEFI + 1 disk** is displayed, continue with step 4, otherwise:
  1. Click **Create Template**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ALTU0VSW.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
  2. Replace the code with the following:

```
kind: Template
apiVersion: template.openshift.io/v1
metadata:
  name: vm-from-upload-uefi-plus1
  namespace: vmimported-user1
  uid: 21ddfbbf-1b4b-47eb-b9c6-d17c114946ba
  resourceVersion: '2149121'
  creationTimestamp: '2026-03-23T06:33:18Z'
  labels:
    os.template.kubevirt.io/other: 'true'
    template.kubevirt.io/type: vm
    workload.template.kubevirt.io/server: 'true'
  annotations:
    description: Create a VM with a disk that you upload manually (QCOW2)
    openshift.io/display-name: VM from uploaded QCOW2 - UEFI + 1 disk
  managedFields:
    - manager: Mozilla
      operation: Update
      apiVersion: template.openshift.io/v1
      time: '2026-03-23T06:33:18Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:description': {}
            'f:openshift.io/display-name': {}
          'f:labels':
            .: {}
            'f:os.template.kubevirt.io/other': {}
            'f:template.kubevirt.io/type': {}
            'f:workload.template.kubevirt.io/server': {}
        'f:objects': {}
        'f:parameters': {}
objects:
  - apiVersion: kubevirt.io/v1
    kind: VirtualMachine
    metadata:
      name: '${NAME}'
      labels:
        app: '${NAME}'
    spec:
      running: false
      dataVolumeTemplates:
        - apiVersion: cdi.kubevirt.io/v1beta1
          kind: DataVolume
          metadata:
            name: '${NAME}-rootdisk'
          spec:
            source:
              upload: {}
            storage:
              resources:
                requests:
                  storage: '${ROOTDISK_SIZE}'
        - apiVersion: cdi.kubevirt.io/v1beta1
          kind: DataVolume
          metadata:
            name: '${NAME}-datadisk1'
          spec:
            source:
              blank: {}
            storage:
              resources:
                requests:
                  storage: '${EXTRA1_SIZE}'
      template:
        metadata:
          annotations:
            vm.kubevirt.io/flavor: small
            vm.kubevirt.io/os: centos9
            vm.kubevirt.io/workload: server
          labels:
            kubevirt.io/domain: '${NAME}'
            kubevirt.io/size: small
        spec:
          architecture: amd64
          domain:
            cpu:
              cores: 1
              sockets: 1
              threads: 1
            devices:
              disks:
                - name: rootdisk
                  disk:
                    bus: virtio
                - name: datadisk1
                  disk:
                    bus: virtio
              interfaces:
                - name: default
                  masquerade: {}
                  model: virtio
              networkInterfaceMultiqueue: true
              rng: {}
            features:
              acpi: {}
              smm:
                enabled: true
            firmware:
              bootloader:
                efi:
                  secureBoot: false
            machine:
              type: q35
            resources:
              requests:
                memory: 2Gi
          evictionStrategy: LiveMigrate
          networks:
            - name: default
              pod: {}
          terminationGracePeriodSeconds: 180
          volumes:
            - name: rootdisk
              dataVolume:
                name: '${NAME}-rootdisk'
            - name: datadisk1
              dataVolume:
                name: '${NAME}-datadisk1'
parameters:
  - name: NAME
    description: VM name
    value: CTERA
    required: true
  - name: ROOTDISK_SIZE
    description: Must be >= qcow2 virtual size
    value: 32Gi
  - name: EXTRA1_SIZE
    description: Extra disk size
    value: 250Gi
```
  3. Click **Create**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-5ROGMCTK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
4. Click **Virtualization > VirtualMachines** in the navigation pane.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-HQLYXIHQ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
5. Click **Create > From template**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-PEL2Q1D1.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

The **Create new VirtualMachine** page is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-WMZVQ6QZ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
6. Click **User templates**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-L8TGP64R.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
7. Click the **VM from uploaded QCOW2 - UEFI + 1 disk** option.  

The **VM from uploaded QCOW2 - UEFI + 1 disk** blade is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-PFISRMKH.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
8. For **Disk source** select **Upload (Upload a new file to a PVC)**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-EL8VFX3X.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
9. Browse to the CTERA Portal qcow2 image file, `Portal_Image_<version>.qcow2` where *version* is the CTERA Portal version and select it.
10. Set the **Disk size** to `32` Gib.
11. Click **CPU | Memory** and set 8 vCPUs and 32GiB memory.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-K2SAEPKI.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
12. Click **Save**and then click **Optional parameters** in the **VM from uploaded QCOW2 - UEFI + 1 disk** blade.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-YX1K9I8T.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
13. Change the **ROOTDISK_SIZE** to `32Gi` and the **EXTRA1_SIZE** to 1% of the expected global file system size or a minimum of 200Gi.
14. Enter a name for the portal server in the **VirtualMachine name** field In the **VM from uploaded QCOW2 - UEFI + 1 disk** blade. The name must be only lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character.
15. Click **Customize VirtualMachine**.  

The upload of the qcow2 image starts.
16. When the upload finishes, click **Create VirtualMachine**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ATFC2TN8.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

The virtual machine is created.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-TCC7ZT8B.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
17. Click the YAML tab.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-7U3KSWTT.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
18. Add the following highlighted text under **Interfaces**.

```
- bridge: {}
  model: virtio
  name: ctera-vlan
```

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-74RNIJ2I.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

where `ctera-vlan` is the name of the vlan where the portal will run.
19. Add the following highlighted text under **networks**:

```
- multus:
    networkName: ctera-vlan
  name: ctera-vlan
```

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-5HLX7BGH.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

where `ctera-vlan` is the name of the vlan where the portal will run.
20. Click **Save**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ONMDKNP4.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
21. Click **Actions > Start**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-QVJ0ABQG.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
22. Click the **Console** tab or click the **Overview** tab and then **Open web console**.
**Note**

When opening the web console from the **Overview** tab, the console is displayed in a new brower tab.
23. If necessary, click **Connect**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-XKZWM4TU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
24. Log in as `root` using the default password `ctera321`.
25. You are promptd to change the password.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-YFR6CE7J.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
26. Navigate to `/etc/ctera` and open **portal.cfg**  configuration file for editing.
**Note**

You can also edit **portal.cfg** directly from any directory by entering `vi $portalcfg`

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-JYARJR23.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
27. Run the command `portal.sh restart` to restart the portal.
28. To make sure that the script to create the data pool completed successfully, run `docker images` to check that the docker images are available, including *zookeeper*, which is the last docker to load to the data pool.
**Note**

If the script to create the data pool does not successfully run, it will start on every boot until it completes. The script has a timeout which means it will exit if the data pool is not created within the timeout after boot time. If the data pool is not created, dockers required by the portal are not loaded to the data pool.

If all the dockers do not load you need to run the script `/usr/bin/ctera_firstboot.sh`

Also, refer to [Troubleshooting the Installation](/v1/docs/installing-ctera-portal-instances-42-2#troubleshooting-the-installation) if the script does not complete successfully.
29. Continue with [Create the Archive Storage](/v1/docs/installing-ctera-portal-instances-42-2#create-the-archive-storage).
30. You can assign a static IP, as described in [configure network settings](/v1/docs/configuring-network-settings-6).
**Note**

The VM is assigned an IP you can use, which is displayed in the VM **Overview** under the **Network** panel for the network name set up by the Red Hat OpenShift administrator and added to the YAML, in this screenshot, the `ctera-vlan` network. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-E0S96UL1.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
31. Start CTERA Portal services, by running the following command: `portal-manage.sh start`

**Note**

Do not start the portal until both the **sdconv** and **envoy** dockers have been loaded to the data pool. You can check that these dockers have loaded in `/var/log/ctera_firstboot.log` or by running `docker images`

## Create the Archive Storage

You need to create the archive pool on the primary database server and when PostgreSQL streaming replication is required, also on the secondary, replication database, server. See [Using PostgreSQL Streaming Replication](/v1/docs/using-postgresql-streaming-replication-3-2) for details about PostgreSQL streaming replication.

**To create the archive pool:**

1. Log in to the Red Hat OpenShift console.
2. Click **Virtualization > VirtualMachines** in the navigation pane and select the CTERA Portal VM.  

The **Overview** panel for the VM is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-VAW92TCA.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
3. Scroll down to display the **Storage** panel.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-0WCOMI9T.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
4. Click **Storage (2)**.  

The **Configuration > Disks** panel is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-6DFXG61C.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
5. Click **Actions > Stop**.
6. Click **Add disk**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-K5RHD2GD.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
7. Select **Empty disk (blank)**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-A47KPTZU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
8. Specify the **Disk size**.
**Note**

The minimum archive pool should be 200GB but it should be sized around 2% of the expected global file system size. For more details, see [Requirements](/v1/docs/planning-general-and-port-requirements-3#general-requirements).
9. Speify the **StorageClass** and click **Save**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-V49KYGL4.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
10. Click **Actions > Start**.
11. Click the **Console** tab or click the **Overview** tab and then **Open web console**.
**Note**

When opening the web console from the **Overview** tab, the console is displayed in a new brower tab.
12. If necessary, click **Connect**.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-XKZWM4TU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)
13. Log in as `root`.
14. Run `lsblk` or `fdisk -l` to identify the disk to use for the archive pool.
15. Run the following command to create the archive pool: `portal-storage-util.sh create_db_archive_pool Device`  

where *Device* is the **device name**  of the disk to use for the archive pool.  

For example: `portal-storage-util.sh create_db_archive_pool vdc`  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-TT2VC328.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A18%3A47Z&se=2026-11-11T05%3A18%3A47Z&sr=c&sp=r&sig=Gv4M1IrD2XuleINV0fMgKf7l%2FvCNOOM2INP%2BKzH6Jsk%3D)  

This command creates both a logical volume and an LVM volume group using the specified device. Therefore, multiple devices can be specified if desired. For example: `portal-storage-util.sh create_db_archive_pool vdc vdd vde`

## Troubleshooting the Installation

You can check on the progress of the docker loads in one of the following ways to ensure that all the dockers are loaded: The last docker to load is called *zookeeper*:

- In `/var/log/ctera_firstboot.log`
- By running `docker images` to check that the docker images are available.
- By checking if `/var/lib/ctera_firstboot_completed` is present with the date and time when the installation was performed.

If all the dockers do not load you need to run the script `/usr/bin/ctera_firstboot.sh`