How to extend the disk size of a Safeguard for Privileged Sessions (SPS) virtual appliance (4287169)

How to extend the disk size of a Safeguard for Privileged Sessions (SPS) virtual appliance

By default Safeguard for Privileged Sessions (SPS) sends an email or SNMP alert to the administrator with the subject "Disk usage is above the defined ratio".

Connections through the appliance keep failing while the configuration web user interface is inaccessible.

Important to note:
Extending Disk Size of a virtual (VM) SPS might fail using this guide in case of an underlying 'legacy' filesystem, if the disk layout was inherited from an SPS version 4.x.x release.

If the above is true for your SPS setup, then we strongly recommend to plan with a migration procedure in order to sustain an up to date virtual SPS appliance. Our detailed migration guide is available at the following link: Migrating One Identity Safeguard for Privileged Sessions to a new appliance

SPS can only use a set disk space assigned to the virtual host.

The appliance can not write more data on the disk because there is no more free space.

WARNING!

The machine that runs SPS must be a virtual machine!
This procedure will not work on a physical machine.

RESOLUTION

Version check

- With SPS 6 LTS or 6 Feature version:

STEPS

1. Warning! Hazard of data loss!

Create a full system backup (configuration and data backup). For detailed instructions, see One Identity Safeguard for Privileged Sessions - Technical Documentation.

2. Power down the virtual machine.

3. Extend the storage size.

4. Power on the SPS virtual machine.

5. Login to SPS as root locally (or remotely using SSH) to access the Console menu.

6. Go to menu option #6 Troubleshooting -> #7 Extend core partition

This will add the extra disk space from the freshly grown virtual disk and reboot the appliance

7.  To validate this is completed, login to SPS locally (or remotely using SSH) as root and select the boot shell then run the command: df -h

This will display the extended size for /dev/mapper/vg--root-core

If upgraded to SPS 5 from an earlier version extend the disk manually using our internal script.
Open a support ticket and ask for the script and guide.

If unsure about the installation check it the following way.

• Log in to the boot shell
• Execute the following command

df -h /mnt/drbd

• Check "Filesystem" field
• If the device name is something like /dev/Xda4, the disk can be resized using this procedure.
  Letter X might vary on different systems. Usually it is 's' or 'v'.

Filesystem      Size  Used Avail Use% Mounted on

/dev/sda4        12G  8.9G  2.9G  76% /mnt/drbd

• If the device is /dev/drbd0, extend the disk using our script and guide.

STEPS

1. Warning! Hazard of data loss!

Create a full system backup (configuration and data backup). For detailed instructions, see One Identity Safeguard for Privileged Sessions - Technical Documentation.

2. Power down the virtual machine.

3. Extend the storage size.

4. Power on the SPS virtual machine.

5. Login to SPS as root locally (or remotely using SSH) to access the Console menu.

6. Select Shells > Boot Shell.

7. Issue the following command:

parted /dev/Xda resizepart

Letter X might vary on different systems. Usually it is 's' or 'v'. Check your system before issuing this command.

8. Answer the on-screen questions with the following answers:

• Fix/Ignore? > fix
• Partition number? > 4
• Warning: Partition /dev/sda4 is being used. Are you sure you want to continue? Yes/No? > yes
• End? > -0
• Fix/Ignore? > fix

For example:

(boot/master/ip99)root@sps1:~# parted /dev/sda resizepart
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 4194304 blocks) or continue with the current setting?
Fix/Ignore? fix
Partition number? 4
Warning: Partition /dev/sda4 is being used. Are you sure you want to continue?
Yes/No? yes
End?  [22.5GB]? -0
Information: You may need to update /etc/fstab.

9. Issue the following command

resize2fs /dev/Xda4

Letter X might vary on different systems. Usually it is 's' or 'v'. Check your system before issuing this command.