← Back to Articles
Migrate VTM 1.6 to VTM 2.1
Last Updated: July 07, 2026
Important: In order to upgrade VTM systems running VTM 1.x versions on vManager platforms, it must first upgrade or be at VTM 1.6 on the vManager platform, then migrate/upgrade to VTM 2.1 on the Domain Manager platform. Once at VTM 2.1 on the Domain Manager platform, the VTM upgrade procedures can be followed to upgrade to later VTM versions.

You can migrate a VTM 1.6.0.n vManager configuration to Domain Manager VTM 2.1 using the existing Arango Database backup and restore utilities.

You must perform a backup for VTM migration in order to migrate your VTM configuration to Domain Manager.
  1. Log in to the master KVM node on Domain Manager.
  2. Copy the VTM 1.6.0 ArangoDB archive to the worker KVM node.
  3. Extract the contents of the archive: tar xf <VTM 1.6.0 ArangoDB archive file name>
  4. Copy the arangoDB_Dump directory to the /cluster/backup directory on the worker KVM node.
  5. Secure Shell into the master KVM node.
  6. Open the /home/labuser/install directory
  7. Extract the "deploy_services.sh" script:
    "./deploy_services.sh –x
  8. Execute the arango-restore.sh script to start the restore process:
    ./arango-restore.sh <Directory of the backup location on the worker KVM node>
    The backup directory location is the date of the backup on the worker node in /cluster/backup. The restore script looks for backups in /cluster/backup by default. The full path to the Arango backup directory starting from backup date folder must be specified as an argument to the arango-restore.sh script.
  9. Optionally, monitor the restore process:
    This command allows you to view the status of the restore: labuser@master-halo:~/install$ kubectl -n csdm get jobs | grep -i backup-arango-restore

    Output:

    backup-arango-restore-20220303222811 1/1 2s 3m7s
    This command generates a log on the restore process: kubectl -n csdm logs jobs/backup-arango-restore-20220303222811 --all-containers
  10. Restart the VTM POD:
    kubectl get pods -A | grep vtm
    kubectl -n csdm delete pod <VTM POD ID>
    NOTE: If you want RxDs to be managed by VTM, you must delete RxDs from VTM and re-add them to Domain Manager and then re-sync with VTM. Otherwise, RxDs on the VTM inventory have their ownership reset to “RxD Manager.”