Creating and Configuring an additional disk for VMware Identity sva

Products

• VMware Aria Suite
• VMware

Issue/Introduction

VMware Identity Manager documentation recommends the utilization of an external instance of vPostgres when setting up a high availability (HA) environment. However, since the release of VMware Identity Manager documentation, standalone vPostgres is EOA and no longer available as a standalone product. To address customers’ needs, VMware developed a way to utilize the vPostgres instance located in the VMware Identity Manager appliance in a HA mode without having to incur additional licensing costs. Now, customers with large deployments may require more disk space to support large internal databases.

Applicable to Photon and SLES

Environment

VMware Identity Manager 3.3.x

Resolution

This article provides information on creating and configuring an additional disk for VMware Identity Manager SVA virtual machine to support large internal databases.

Create an additional disk for the VMware Identity Manager SVA virtual machine.

1. Log in to vSphere client.
2. Shut down the Identity Manager SVA virtual machine.
3. Right-click the Identity Manager SVA virtual machine and click Edit Settings.
4. Click the Hardware tab and click Add.
5. Click Hard Disk for the device type and click Next.
6. Click the Create a new virtual disk tab and click Next.
7. Set the disk size and storage options appropriate for your environment and click Next.
   Determine the appropriate disk size based on your deployment. You can change the disk size at any time after deployment.
8. Go to the Advanced Options page, accept the default settings, and click Next.
9. Go to the Ready to Complete page and click Finish.
10. Power on the Identity Manager sva virtual machine.
11. Log in to the Identity Manager SVA machine as root.
12. Run the list command to show the contents of the directory, /dev/sd*.
    
    ls –lat /dev/sd*
    
    When you run the list command, all the Workspace drives show in the list. The newest drive is listed last, in this case, sde.
     
13. Record the newest directory name. You need the name in a later step.
     
14. Run these commands in the following order:
    
    pvcreate /dev/sde
    vgextend db_vg /dev/sde
    lvextend /dev/mapper/db_vg-db /dev/sde
    resize2fs -p /dev/mapper/db_vg-db
     
15. Run the pvdisplay command to confirm that the disk was created. 
    
    pvdisplay
    df –kmh

 

The name of the partitioned drive and the free disk space displays. The new disk space is available for use by your internal database.

Note : you can run the following if the drive does not display
 ls /sys/class/scsi_host
echo "- - -" > /sys/class/scsi_host/hostx/scan

Additional Information

vIDM DB partition is full or nearly out of space