Change deployment profile on VMware

Use the apicup command and deploy new VMs to change your deployment profile.

For information about the available deployment profiles, see Planning your deployment topology and profiles.
Note:

The procedures to change deployment profile do not permit the endpoints to be changed.

If you want to change a one replica deployment to a three replica deployment, and you used the hostname of your original VM in your endpoints, you cannot change these endpoints. In this scenario, you must configure load-balancers and logical DNS records so that your original VM hostname routes to the new VMs of your three replica deployment.

If you want to change endpoints, you can use the form-factor migration process.

Moving to a profile that has the same number of VMs

Complete the following steps to change your deployment profile:
  1. Take backups of your analytics configuration and database: VMware analytics backup.
  2. Shutdown your analytics VMs.
  3. Update the CPU and memory resources for your analytics VMs in your VMware console, as required for your new profile.
  4. Restart your VMs.
  5. In your project directory, update your deployment profile:
    apicup subsys set <subsystem name> deployment-profile=<new profile>
  6. Apply the new profile:
    apicup subsys install <subsystem name>
If for any reason you are not able to change the CPU or memory on your VMs, redeploy them following the disaster recovery process: Recovering from a disaster.

Moving from a one replica to a three replica deployment profile

  1. Take backups of your analytics configuration and database: VMware analytics backup.
    Note: You do not need to take VMware snapshots, since your existing VM is deleted and replaced when you change deployment profile.
  2. In your project directory, update your deployment profile:
    apicup subsys set <analytics subsystem name> deployment-profile=<three replica profile>
  3. Define the hostname and network interfaces for the two new analytics VMs. Use the apicup hosts create and apicup iface create commands. For more information, see Preparing the analytics subsystem for deployment.
  4. Shutdown your existing analytics VM.
  5. Follow the disaster recovery steps: Recovering from a disaster, but note that you must create a new ISO file for your original single analytics VM. Do not attempt to reuse the previous ISO file in your new three replica deployment.
  6. When disaster recovery steps are complete and your new deployment is verified, delete your original VM (which you shutdown in step 4).

Moving from a three replica to a one replica deployment profile

  1. Take backups of your analytics configuration and database: VMware analytics backup.
    Note: You do not need to take VMware snapshots, since your existing VMs are deleted and replaced when you change deployment profile.
  2. In your project directory, update your deployment profile:
    apicup subsys set <subsystem name> deployment-profile=<one replica profile>
  3. Delete two of your three VMs from your configuration with the apicup hosts delete command.
  4. Shutdown your existing API Connect VMs.
  5. Follow the disaster recovery steps: Recovering from a disaster, but note that you must create a new ISO file for your analytics VM. Do not attempt to reuse a previous ISO file in your new one replica deployment.
  6. When disaster recovery steps are complete and your new deployment is verified, delete your original VMs (which you shutdown in step 4).