Upgrade the Virtual Appliance in VMware

Upgrading the Virtual Appliance involves:

Backing up and deleting the hard disks of the existing virtual machines.
Deploying new virtual machines by using OVA image.
Restoring the backup to their hard disks.
Attaching the new hard disks to the older virtual machines

Splunk AppDynamics On-Premises Virtual Appliance provides the reference script that helps in upgrading the Virtual Appliance.

Note: This document contains links to VMware documentation. Splunk AppDynamics makes no representation as to the accuracy of VMware documentation because VMware controls its own documentation.

Back Up the Virtual Appliance Data

Follow these to back up the Virtual Appliance data:

Download the Virtual Appliance OVA file from the Downloads portal.
Note: The OVA file available in the downloads portal is used for both installation and upgrade procedures.

Shutdown the Splunk AppDynamics, Anomaly Detection, and Secure Application services.

appdcli stop secapp
appdcli stop aiops
appdcli stop appd
<<Wait for pods to terminate before deleting operators>>
appdcli stop operators

Run the backup command:
```
appdcli run backup
```
This command generates a <backup_tar> file with all the necessary data.
Copy and paste the backup file outside of the cluster.

Prepare to upgrade the Virtual Appliance

Complete the following steps to prepare the Virtual Appliance upgrade:

Power off the virtual machines that are running the Kubernetes cluster.
Rename the existing virtual machines to use their names for the new virtual machines.
Right click each virtual machine and select Edit Settings:
1. In Virtual Hardware, expand Hard Disk 2.
2. Note the Disk File name
Remove the data disk from the virtual machines.
1. Right click on each virtual machine and select Edit Settings.
2. In Virtual Hardware > Hard Disk2, select Remove Device from the more options.

Upgrade the Virtual Appliance with the OVA File

Complete the following steps to upgrade the Virtual Appliance by using an OVA file:

Deploy three virtual machines by using the upgrade OVA file.
Delete the data disk of the new virtual machine:
1. Go to Edit Settings.
2. Select Hard Disk 2.
3. Remove device
Attach the data disks of the previous virtual machines:
1. Go to Edit Settings.
2. Add a new device.
3. Select Existing Hard Disk and specify the disk file name that you have noted earlier.
Enable VMware tools in the virtual machines to configure OVF properties.
1. Select th eConfigure tab.
2. Select vApp Options and click Edit.
3. In Edit vApp Options > OVF Tools, select VMware Tools. See Edit OVF properties for a virtual machine.
Power on the new virtual machines.

Verify the Deployment Status

Verify the deployment of virtual machines:

Verify whether the deployment of virtual machines is successful:
```
appdctl show boot
```
Note: Ensure that the services in each node is active. If any service appears as Failed, restart that virtual machine. You might have to redeploy the virtual machine if it is still failing.
Create a three-node cluster:
1. Run the following command in the primary node and specify the IP address of the peer nodes:
```
appdctl cluster init <Node-2-IP> <Node-3-IP>
```
2. Run the following command to verify the node status:
```
appdctl show cluster
microk8s status
```
  Ensure that the output displays the Running status as true for the nodes that are part of the cluster.
  Sample Output
```
NODE           | ROLE  | RUNNING
----------------+-------+---------
10.0.0.1:19001 | voter | true
10.0.0.2:19001 | voter | true
10.0.0.3:19001 | voter | true
```
  Note: You must re-login to the terminal if the following error appears:
```
Insufficient Permissions to Access Microk8s
```

Restore Data in the Virtual Appliance

Copy the <backup_tar> file to one of the cluster nodes that is generated earlier. See Prerequisites.
Run the following command to restore the persistent volumes specifications:
```
appdcli run restore <backup_tar>
```
Verify that the PVC are in the Bound state by running the following command:
```
kubectl get pvc -A
```
Start the following services:
```
appdcli start appd [Profile]
```
Restore self-signed CA ingress certificates.A prompt is displayed "Do you want to restore self-signed ingress certificates?" Enter 0 for No or 1 for Yes".
- Choose 0 if you have configured the certificates for DNS.
- Choose 1 to configure the certificates.
Sometimes, MySQL Router pods might fail to start. In such cases, restart the services using the following commands:
1. Stop the Splunk AppDynamics services.
```
appdcli stop appd
```
  Wait for the pods to terminate.
2. Stop the operators:
```
appdcli stop opeartors
```
3. Start the Splunk AppDynamics services:
```
appdcli start appd <profile>
```

After the upgrade, the cluster uses the existing data disk and becomes functional.