Add extra capacity to InfiniMetrics versions prior to 2.2

Follow

Introduction

This page provides instructions for InfiniMetrics versions earlier than 2.2

The InfiniMetrics virtual appliance requires, by default, a 30GB virtual hard disk that suits most environments.
For large environments (multiple InfiniBox systems with many monitored counters), more capacity might  be required.
The following guide explains how to add extra capacity to an existing InfiniMetrics system and how to migrate the data to that added capacity.

Step-by-step guide

  1. Using VMware VI client or VMware web client add additional Hard Disk to the InfiniMetrics VM with the required capacity
  2. SSH to the InfiniMetrics VM as root, password is nfinidat1
  3. Rescan the added disk:

     echo "- - -" > /sys/class/scsi_host/host2/scan
  4. Create a new partition: fdisk /dev/sdb , type n enter, p enter, 1 enter, enter,enter, w enter (see example below)

    root@localhost:~# fdisk /dev/sdb
    Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
    Building a new DOS disklabel with disk identifier 0xec6deb86.
    Changes will remain in memory only, until you decide to write them.
    After that, of course, the previous content won't be recoverable.
    
    Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
    
    WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
             switch off the mode (command 'c') and change display units to
             sectors (command 'u').
    
    Command (m for help): n
    Command action
       e   extended
       p   primary partition (1-4)
    p
    Partition number (1-4): 1
    First cylinder (1-3916, default 1):
    Using default value 1
    Last cylinder, +cylinders or +size{K,M,G} (1-3916, default 3916):
    Using default value 3916
    
    Command (m for help): w
    The partition table has been altered!
    
    Calling ioctl() to re-read partition table.
    Syncing disks.
  5. Create a filesystem: 

    mkfs.ext3 /dev/sdb1
  6. Create a mount point: 

    mkdir /data
  7. Note the new disk UUID: 

    blkid /dev/sdb1
    (example output:) /dev/sdb1: UUID="0a6fe8d0-2f05-4dc6-8d85-9a9439fe0fc9" TYPE="ext3"
  8. Add an entry to the filesystem table (use the UUID returned at step 7) 

    echo "UUID=0a6fe8d0-2f05-4dc6-8d85-9a9439fe0fc9 /data ext3  defaults  0 0" >> /etc/fstab
  9. Mount the new filesystem:

    mount /data
  10. Verify that the added capacity mounted correctly:

    df -h /data
    (example output:)
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/sdb1        59G  306M   56G   1% /data
  11. Stop InfiniMetrics services:

    manage infinimetrics_services stop
    service gunicorn stop
    service postgresql stop
  12. Verify that the postgresql service is down: (if not, repeat the service postgresql stop command)

    service postgresql status
    (example output:) 9.3/main (port 5432): down
  13. Migrate the InfiniMetrics Data to the new FileSystem:

    mv /var/lib/postgresql/9.3/main /data/
  14. Create a symbolic link to the new data:

    ln -s /data/main /var/lib/postgresql/9.3/main
  15. Reboot the InfiniMetrics 

    reboot
  16. Wait until the InfiniMetrics finishes to boot and verify that it is working as expected  

Comments

Powered by Zendesk