Hi,
In this Blog post i will describe some more about the Fling Horizon Daas Migration Tool https://labs.vmware.com/flings/horizon-daas-migration-tool
From the Fling website it’s clear what this does
Horizon DaaS Migration Tool helps migrating from earlier versions of Horizon DaaS (6.1.5, 6.1.6, 7.0.0) to the latest supported version (8.0.0). The tool can be used to move persistent desktop mappings from existing tenants to a newly provisioned tenant on 8.0.0.
The migration is not an in-place migration and does require a parallel setup of VMware Horizon DaaS 8.0.0 to be available. The tool is a command line tool that must be run from a separate Ubuntu virtual machine.
How does this work?
You need a Ubuntu Server , and install the Fling on it. The documentation from the website describes this.
How to export the source tenant configuration?
Login to your Ubuntu VM. Go to /vmware/daas/migration/bin . and run python export.py -v
Example output:
[email protected]:/vmware/daas/migration/bin# python export.py -v
You’ll be prompted to enter DaaS ServiceProvider and Tenant details now [Enter]:
Source service provider IP []: 10.100.10.10
Destination service provider IP []: 10.200.10.10
“Source service provider” password []:
Re-confirm “Source service provider” password []:
Source SP domain name []: SP
Source SP domain user []: adm-migratieuser
“Source SP domain” password []:
Re-confirm “Source SP domain” password []:
Provide source tenant, version no. from the list – [‘6.1.5’, ‘6.1.6’, ‘7.0.0’]. [Default: 6.1.6]: 6.1.5
Provide destination tenant, version no. from the list – [‘8.0.0’]. [Default: 8.0.0]:
Source tenant, org-Id []: 1021
Destination tenant, org-Id []: 1019
=== Input details validation ===
Source service provider Ip: “10.100.10.10”
Destination service provider Ip: “10.200.10.10”
Source SP domain name: “SP”
Source SP domain user: “adm-migratieuser”
Source tenant version: “6.1.5”
Destination tenant version: “8.0.0”
Source tenant org-Id: “1021”
Destination SP Ip: “10.200.10.10”
Destination tenant org Id: “1019”
Are the details correct ? [yes]:
DaaS Export: Progress [==================================================] 100.0% complete
DaaS Export – Done
[email protected]:/vmware/daas/migration/bin#
Howto Import into the destination Tenant:
First create a file named vms_to_be_migrated.txt , in to the imported directory. in this example /vmware/daas/migration/data/10.200.10.10/1019
When ready run python import.py -v , inside the /vmware/daas/migration-toolkit/v2.0/bin directory.
Example Import output:
[email protected]:/vmware/daas/migration-toolkit/v2.0/bin# python import.py -v
CA/SSL verification to be enabled [Options=yes|no, Default:yes]: no
You’ll be prompted to enter DaaS ServiceProvider and Tenant details now [Enter]:
Destination service provider IP [10.200.10.10]:
“Destination service provider appliance” password []:
Re-confirm “Destination service provider appliance” password []:
Destination SP domain name []: SP
Destination SP domain user []: adm-migratieuser
“Destination SP domain” password []:
Re-confirm “Destination SP domain” password []:
Source tenant, version no. [6.1.5]:
Destination tenant, version no. [8.0.0]:
Destination tenant, org-Id [1019]:
Require vCenter details for VM power management. What is your “destination desktop” vCenter hostname or Ip []: vc01.destinationvc.local
vCenter user []: adm-migratieuser
“vCenter password” password []:
Re-confirm “vCenter password” password []:
=== Input details validation ===
CA/SSL verification required: “False”
Fqdn: undef
Destination service provider Ip: “10.200.10.10”
Destination SP domain name: “SP”
Destination SP domain user: “adm-migratieuser”
Source tenant version: “6.1.5”
Destination tenant version: “8.0.0”
Destination tenant org Id: “1019”
vCenter host/Ip: “vc01.destinationvc.local”
vCenter user: “adm-migratieuser”
Are the details correct ? [yes]:
DaaS Import: Progress [==================================================] 100.0% complete
DaaS Import – Done
[email protected]:/vmware/daas/migration-toolkit/v2.0/bin#
Now your Done , check the Daas 8 portal and see the imported VM in the pool.
4,773 total views, 4 views today
