The following procedure is applicable to All-in-One DPOD appliance mode installation only.

In non-appliance installations, the operating system and file system configuration is under the responsibility of the customer, so the following procedure can only be used as an example, since the actual existing file system configuration might not match the one created in the appliance mode installation.

For details about the Store space in a Cell environment, see Setup a Cell Environment.

DPOD's Big Data Store is located on a dedicated mount point. Occasionally, the disk space allocated for the Store needs to be increased. Reasons for that include an increase in TPS, or a requirement to retain history for longer periods of time. Follow the steps below to increase the Store space.

Note: You may choose between extending the existing data disk (option 1), or adding additional disks (option 2).
Since DPOD uses fdisk utility for creating partitions in the data disk during installation, it only supports extending the existing data disk (option 1) up to 2TB. However, additional disks (option 2) can be larger than 2TB.

Option 1: Extending the Existing Data Disk

Extending the Disk in a Physical Server

For physical servers, use the server vendor's RAID management software to extend the existing RAID Disk (LUN) in order to increase the data disk.

Extending the Disk in a Virtual Machine

Use the VMware vSphere Client in order to edit the DPOD virtual machine settings:

Stop the DPOD virtual machine.
Select Edit virtual machine settings
Select the 3rd hard drive (which is the data disk, as described in the Hardware and Software Requirements page).
Increase the Provisioned size of the hard drive and press OK.
Wait for the increase process to finish.
Start the DPOD virtual machine.

Configuring the File System after Extending the Disk

Verify the current size of mount point /data:
```
df -h /data
```
The system output should resemble the following:
Verify the new disk size:
```
fdisk -l | grep /dev/sdc
```
The system output should resemble the following:
Use fdisk to create a new partition for the new size:
```
fdisk /dev/sdc
```
1. Press p to print the partition table to identify the number of partitions:
  
  If this is the first time the disk is extended, you should only see sdc1. If this is a subsequent extension - you will see additional sdcX listed (e.g. sdc2 for the second extension).
2. Press n to create a new primary partition.
3. Press p for primary.
4. When the system prompts for a partition number, enter the next number depending on the output of the partition table print.
  If this is the first extension and you see only one row of output - enter 2. If this is the second disk extension then the partition number will be 3, and so on.
5. Press Enter twice
6. Press t to change the system's partition ID.
7. Press 2 to select the newly created partition (Remember: if this is a subsequent disk extension - the number will be 3 or higher).
8. Type 8e to change the Hex Code of the partition for Linux LVM.
9. Press w to write the changes to the partition table.
  
  The following warning is valid, the system reboot will fix the issue:
  “WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8)”
Reboot the system:
```
reboot
```
When the system is available again, ensure the new partition is available:
```
fdisk -l | grep /dev/sdc
```
The system output should resemble the following (note the new sdcX added):
Stop the application by running app-util.sh and selecting option 2 (stop all).
Configure the new partition:

If the new partition is not sdc2, substitute sdc2 for the right qualifier in all the following commands
```
pvcreate /dev/sdc2
vgextend vg_data /dev/sdc2
lvextend -l +100%FREE /dev/vg_data/lv_data
```
Identify the /data file system type (for CentOS 7.2+ based appliances the type is xfs):
```
cat /etc/fstab | grep /data
```
The system output should resemble the following:
Resize the file system. Select the correct command below for your file system type:
For ext4
```
resize2fs /dev/vg_data/lv_data
```
For xfs
```
xfs_growfs /dev/vg_data/lv_data
```
The system output should resemble the following:
Display the new size of the /data mount point:
```
df -h /data
```
Update the Store configuration file (see below).

Option 2: Adding an Additional Data Disk

Adding an Additional Disk in a Physical Server

For physical servers, use the server vendor's RAID management software to add new RAID Disk (new LUN), in order to increase the data disk.

Adding an Additional Disk in a Virtual Machine

Use the VMware vSphere Client in order to edit the DPOD virtual machine settings:

Stop the DPOD virtual machine.
Select Edit virtual machine settings
Select Add > Hard Drive
Ensure to configure the new hard drive as Thick Provision Eager Zeroed
Wait for the increase process to finish.
Start the DPOD virtual machine.

Configuring the File System after Adding the Disk

Verify the current size of the /data mount point:
```
df -h /data
```
The system output should resemble the following:

Identify the new disk:

lsblk

[ Note: Example output below is filtered to show only sdd disk information, but should include many more entries of sda, sdb and sdc disks ]

NAME                    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sdd                       8:32   0  200G  0 disk

Stop the application by running app-util.sh and selecting option 2 (stop all)
Execute the following commands. Replace the name of data disk if it is different in your environment.
```
pvcreate -ff /dev/sdd
vgextend vg_data /dev/sdd
lvextend -l +100%FREE /dev/vg_data/lv_data
```
Identify the /data file system type (for CentOS 7.2+ based appliances the type is xfs):
```
cat /etc/fstab | grep /data
```
The system output should resemble the following:
Resize the file system. Select the correct command below for your file system type:
For ext4
```
resize2fs /dev/vg_data/lv_data
```
For xfs
```
xfs_growfs /dev/vg_data/lv_data
```
The system output should resemble the following:
Display the new size of the /data mount point:
```
df -h /data
```
The system output should resemble the following:
Update the Store configuration file (see below).

Update the Store Configuration File

Execute the following script to update the Store configuration file with the new file system size:
```
/app/scripts/update_store_allocation.sh -l 1
```
Start the application by running app-util.sh and selecting option 1 (start all).

Browser not supported