DPOD's Big Data Store is located on a dedicated hard drive. 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.

The process to increase the disk space allocated to DPOD's Store entails the two stages detailed below:

• Increasing the data disk and file system.
• Updating the application Store configuration file

Increase the Data Disk and File System

Physical Server

Use the server vendor's RAID management software to extend the existing RAID Disk (LUN) or add new RAID Disk (new LUN), in order to increase the data disk and file system sizes for the physical server.

Select the correct OS level configuration procedure below, based on whether you selected to extend or add a disk.

• Extend existing disk
• Add new Disk

Virtual appliance

With a virtual deployment, there are two options available for increasing DPOD's Store disk space:

• Extend the existing data hard drive
• Add new data hard drive

Extend The Existing Virtual Disk

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

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

Configure the extended disk at the OS level

1. Verify the current size of mount point /data:

   df -h /data

   The system output should resemble the following:
   

2. Verify the new disk size:

   fdisk -l |grep /dev/sdc

   The system output should resemble the following:

   

3. Use fdisk to create a new partition for the new size:

   fdisk /dev/sdc

    and perform the following steps:

   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)”

      
      

   10. Reboot the system:

       reboot

       
       

   11. When the system is back up, ensure the new partition is available:

       fdisk -l | grep /dev/sdc

       The system output should resemble the following (note the new sdcX added)
       

   12. Stop the application by running app-util.sh and selecting option 2 (stop all)

       If the new partition is not sdc2, substitute sdc2 for the right qualifier in all the following commands

       
       

   13. Create a new LVM Physical Volume (PV):

       pvcreate /dev/sdc2

       
       

   14.  Extend the LVM Volume Group (VG):

       vgextend vg_data /dev/sdc2

       
       

   15. Extend the LVM Logical Volume (LV):

       lvextend -l +100%FREE /dev/vg_data/lv_data

       
       

   16.  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:
       

   17.  Resize the file system. Select the correct command below for your file system type:

       resize2fs /dev/vg_data/lv_data

       
       

       xfs_growfs /dev/vg_data/lv_data

       The system output should resemble the following:
       

   18. To display the new size of the /data mount point:

       df -h /data

       
       

Add new virtual disk

Use the VMware vSphere Client in order to edit the DPODs virtual machine

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

Configure The New disk at the OS Level

1. Verify the current size of the /data mount point:

   df -h /data

   The system output should resemble the following:
   

2. Verify the new disk size:

   fdisk -l |grep /dev/sdd

   The system output should resemble the following:
   

3. Create a new partition with the new size:

   fdisk /dev/sdd

   
   

   1. Press p to print the partition table and ensure there are no existing partitions. 
      
   2. Press n to create a new primary partition.
   3. Press p for primary.
   4. Press 1 for the partition number
   5. Press Enter twice
      
   6. Press t to change the system's partition ID.
   7. Type 8e to change the Hex Code of the partition for Linux LVM.
   8. Press w to write the changes to the partition table.
      

   9. Reboot the system:

      reboot

      
      

   10. When the system is back up, ensure the new partition is created:

       fdisk -l |grep /dev/sdd

        The system output should resenble the following:
       

   11. Stop the application by running app-util.sh and selecting option 2 (stop all)

   12. Create a new LVM Physical Volume (PV):

       pvcreate /dev/sdd1

       
       

   13. Extend the LVM Volume Group (VG):

       vgextend vg_data /dev/sdd1

       
       

   14.  Extend the LVM logical volume (LV) : 

       lvextend -l +100%FREE /dev/vg_data/lv_data

       
       

   15.  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:
       
       
       

   16.  Resize the file system. Select the correct command below for your file system type:

       resize2fs /dev/vg_data/lv_data

       
       

       xfs_growfs /dev/vg_data/lv_data

       The system output should resemble the following:
       
       
       

   17. To display the new  size of the /data mount point:

       df -h /data

       The system output should resemble the following:
       

 Update the Store Configuration File

Starting with v1.0.4.0, DPOD is shipped with a script that performs all the necessary steps to update the Store configuration file.

You may use this script by running:

 /app/scripts/update_store_allocation.sh  

When the script has completed, restart the application by running app-util.sh and selecting option 1 (start all)