Restore Data in the Virtual Appliance

  1. Copy the <backup_tar> file to one of the cluster nodes that is generated earlier. See Prerequisites.
  2. Run the following command to restore the persistent volumes specifications:
    appdcli run restore <backup_tar>
  3. Verify the PVC are in theBound state by running the following command:
    kubectl get pvc -A
  4. Start the following services:
    appdcli start appd [Profile]
    1. Splunk AppDynamics Services.
    2. Anomaly Detection Service.
    3. Cisco Secure Application Service.
  5. 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.
  6. 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.