Resize existing VAs in ISC

Hi all,

We are considering resizing our existing Azure-hosted VAs. Is that an option? If so, do you have a step-by-step process for scaling them without impacting the existing configuration (e.g., ISC registration)? Also, since we have two VAs, should they be resized one at a time?

Standard_D8s_v5

x86 Processors: 4
Memory: 32 GB
Storage: 128 GB

===== Our Virtual Appliance Specs =====

CPU(s): 4
On-line CPU(s) list: 0-3
Model name: Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
CPU(s) scaling MHz: 125%
NUMA node0 CPU(s): 0-3
Mem: 15Gi 3.8Gi 7.6Gi 1.1Mi 4.5Gi 11Gi
Filesystem Size Used Avail Use% Mounted on
/dev/sda9 122G 8.9G 108G 8% /

my recommendation would be creating new VAs as per your desired config and it is the best choice

You should talk to your systems/network admin guys as you will have to reconfigure the Virtual Machine itself.

And, I do not think creating a new VAs and deleting old ones that @HussainshaSyed001 suggested is a good idea. Sorry to disagree

I have resized my Azure VAs in the test-environment multiple times. It’s pretty simple, you just need to deallocate the VM, resize the machine and start. This bash script is what I would use, with the Azure CLI. Perhaps it helps.

I’d recommend you see how it works in your test-environment first, in case my script is bad after all. Haven’t used it in over a year now.

#!/bin/bash

# ======================================
# Define all necessary variables here
# ======================================
RESOURCE_GROUP="my-resource-group"   # Replace with your Resource Group name
VM_NAME="sailpoint-va01"             # Replace with your VM name
LOCATION="eastus"                    # Region where your VM is deployed
NEW_SIZE="Standard_B2ms"             # Desired VM size: 

# ======================================
# Begin the resize process
# ======================================
echo "Starting the resize process for VM '$VM_NAME' in Resource Group '$RESOURCE_GROUP' located in '$LOCATION'..."

# Step 1: Deallocate the VM (required for resizing)
echo "Deallocating the VM..."
az vm deallocate --resource-group "$RESOURCE_GROUP" --name "$VM_NAME"

# Step 2: Resize the VM to the new size
echo "Resizing the VM to size '$NEW_SIZE'..."
az vm resize --resource-group "$RESOURCE_GROUP" --name "$VM_NAME" --size "$NEW_SIZE"

# Step 3: Start the VM after resizing
echo "Starting the VM..."
az vm start --resource-group "$RESOURCE_GROUP" --name "$VM_NAME"

echo "Resize process completed. The VM '$VM_NAME' is now set to '$NEW_SIZE'."

@iamnithesh when you say re-configure, existing configurations will be lost like registration/FW and all other stuff?

No, I meant to say reconfigure the “VM” itself. Not the VA. There should not be any changes to the VA.

Response from @othornewill seems like what you need

Hi @othornewill Thanks for the response. I’ll test this in our TEST environment and see how it works. I’ll post an update here. Thanks

Yes,

Existing Azure-hosted SailPoint VA can be resized without redeploying them. Stop the VM, resize it, and start it again. In a 2-VA cluster, resize one VA at a time to avoid downtime. Existing VA registration and configuration remain intact because the VM disk is preserved during the resize operation. Always validate the change in a test environment before applying it to production.

@Prashanth1812

Follow the below steps

  • Work with devops to build those new servers
  • Create a new cluster
  • Connect your new virtual appliances to that cluster
  • Migrate all the apps to the new cluster
  • Decomission the old VA and cluster once all apps are migrated

Thanks