Versions Compared

Version Old Version 13 New Version Current
Changes made by

shachar greenberg (Unlicensed)

Hanan Kenan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The DPODs DPOD's Big Data Store is located on a dedicated hard drive. From time to time there is a need to extended the amount of disk space that is Occasionally, the disk space allocated for the Store .The reasons could be needs to be increased. Reasons for that include an increase in TPS, or a requirement to keep retain history for longer periods of time.

Increasing the amount of The process to increase the disk space allocated to DPODs Store involves DPOD's Store entails the two stages detailed below:

Anchor
Increase Data Disk
Increase Data Disk
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.

Virtual appliance

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

Anchor
Extend Existinf Disk
Extend Existinf Disk
Extend the existing

...

Virtual Disk

Use the VMware vSphere Client in order to edit the

...

DPOD virtual machine
  1. Stop the DPOD virtual machine.

...

  1. Select Edit virtual machine

...

  1. settings

...

  1. Select the 3rd hard drive (which is the data disk, as described in

...

  1. the Hardware and Software Requirements page).
  2. Increase the

...

  1. Provisioned size of the hard drive and press OK.
  2. Wait for the increase process to finish.
  3. Start the DPOD virtual machine.

...


  1. Image Modified

Anchor
configure extended disk
configure extended disk
Configure the extended disk

...

at the OS level

...


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

    Code Block
    df -h /data

    The system output should resemble the following:
    Image Modified

...

  1. Verify the new disk size:

    Code Block
    fdisk -l |grep /dev/sdc

    The system output should resemble the following:

    Image Modified

...

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

    Code Block
    fdisk /dev/sdc

     and perform the following steps:

    1. Press p to print the partition table to identify the number of partitions

...

    1. :
      Image Added
      If this is the first

...

    1. time the disk is extended, you should only see sdc1. If this is

...

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

...

    1. When the system prompts for a partition number, enter the next number depending on the output of the partition table print

...

    1. .
      If this is the first extension and you see only one row of output - enter 2. If this is the second disk

...

    1. extension then the partition number will be 3

...

    1. , and so on.
    2. Press Enter

...

    1. twice
      Image Modified
    2. Press t to change the system's partition ID.
    3. Press 2 to select the newly

...

    1. created partition (Remember: if this is a subsequent disk extension - the number will be 3 or higher)
    2. Type 8e to change the Hex Code of the partition for Linux LVM.

    3. Press w to write the changes to the partition table.

      Image Modified

      Note

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


    4. Reboot the system:

      Code Block
      reboot

...


    2. When the system is back up,

...

    1. ensure the new partition is available:

      Code Block
      fdisk -l | grep /dev/sdc

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

...

    1. Stop the application

...

    1. by running app-util.sh

...

    1.  and selecting option 2 (stop all)

...

    1. Note

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


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

      Code Block
       pvcreate /dev/sdc2

...


    1.  Extend the LVM Volume Group (VG):

      Code Block
      vgextend vg_data /dev/sdc2

...


    2. Extend the LVM

...

    1. Logical Volume (LV):

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

...


    2.  Identify the /data file system type (for CentOS 7.2 based

...

    1. appliances the type is xfs):

      Code Block
      cat /etc/fstab |grep /data

      The system output should resemble the following:
      Image Modified

...

    1.  Resize the file system

...

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

      Code Block
      titleext4

...

    1. resize2fs /dev/vg_data/lv_data


      Code Block
      titlexfs

...

    1. xfs_growfs /dev/vg_data/lv_data

      The system output should resemble the following:
      Image Modified

...

    1. To display the new

...

    1. size of the /data mount point

...

    1. :

      Code Block
      df -h /data

...


 Anchor
Add New Disk
Add New Disk
Add new virtual disk
Use the VMware vSphere Client in order to edit the DPODs virtual machine
  1. Stop the DPOD virtual machine.
...
  1. Select Edit virtual machine 
...
  1. settings
  2. Select Add > Hard Drive
  3. Ensure to configure the new hard drive as 
...
  1. Thick Provision Eager 
...
  1. Zeroed
...
  1.  Wait for the increase process to finish.
...
  1. Start the DPOD virtual machine
...

  1. Image Added

 Anchor
configure new disk
configure new disk
Configure the new disk 
...
at the OS 
...
Level
...

  1. Verify the current size of the /data mount point
...
  1. :
     Code Block
    df -h /data
    The system output should resemble the following:
    Image Modified
...
  1. Verify the new disk size:
     Code Block
    fdisk -l |grep /dev/sdd
    The system output should resemble the following:
    Image Modified
  2. Create a new partition 
...
  1. with the new size:
     Code Block
    fdisk /dev/sdd

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

    2. When the system is back up, 
...
    1. ensure the new partition is created:
       Code Block
      fdisk -l |grep /dev/sdd
       The system output should resemble  the following:
      Image Modified
...
    1. Stop the application 
...
    1. by running app-util.sh
...
    1.  and selecting option 2 (stop all)
...
    1. Create a new LVM 
...
    1. Physical Volume (PV):
       Code Block
      pvcreate /dev/sdd1
...

    2. Extend the LVM 
...
    1. Volume Group (VG):
       Code Block
      vgextend vg_data /dev/sdd1
...

    2.  Extend the LVM logical volume (LV): 
       Code Block
      lvextend -l +100%FREE /dev/vg_data/lv_data
...

    2.  Identify the /data file system 
...
    1. type (for CentOS 7.2 based 
...
    1. appliances the type is xfs): 
       Code Block
      cat /etc/fstab |grep /data
       The system output should resemble the following:
      Image Modified
...

    2.  Resize the file system
...
    1. . Select the correct command below for your file system type:
       Code Block
      titleext4
...
    1. resize2fs /dev/vg_data/lv_data

       Code Block
      titlexfs
...
    1. xfs_growfs /dev/vg_data/lv_data
      The system output should resemble the following:
      Image Modified
...

    2. To display the new 
...
    1. size of 
...
    1. the /data mount point:
       Code Block
      df -h /data
      The system output should resemble the following:
      Image Modified
 
 Anchor
Update Configuration File
Update Configuration File
Update the Store Configuration File
Update Starting with v1.0.4, 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:
 Code Block
languagebash
themeMidnight
 /app/scripts/update_store_allocation.sh  

 Info
The script is available on DPOD v1.0.4 
...
 and above. If you are using earlier version please contact DPOD support and the script will be provided.
...

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