Upgrading
Configured settings from Sun VDI 2.0, including a VMware vCenter and its corresponding virtual machines and pools, can be stored and used once again after Sun VDI 3.0 has been installed and configured.
Sun VDI 3.0 provides a command line tool to preserve the data and settings from Sun VDI 2.0.
 | Sun VDI 2.0 = Sun VDC 1.0 Sun VDI 2.0 is also known as Sun VDC 1.0 - this can cause confusion. VDI refers to the complete layered software solution, while VDC refers to only the management software component. If you are currently running the Sun VDI 2.0 software, release in March 2008, you can upgrade to VDI 3.0 using the following procedure. |
Steps
- Extract data and settings from Sun VDI 2.0.
If Sun VDI 2.0 is still installed and configured, and the Sun VDI 3.0 bits are already available, use vda-migrate to export the data:<MEDIA-DIR>/Supplemental/vda-migrate -e </path/to/directory>
The data will be exported to the specified directory.
Sun VDI 2.0 was found on the server. + Storing data... Data exported to directory '/var/opt/SUNWvda/backup'A log file is created with detailed information. When vda-migrate finishes it indicates the location of the log file. In Solaris platforms it can be located at '/var/adm/log/vda-migrate.<date and time>.log'.
For more information about the vda-migrate command see its usage page.
- Remove Sun VDI 2.0.
Refer to the Sun Virtual Desktop Connector 1.0 Installation and Administration Guide.
- Install Sun VDI 3.0.
Refer to Step 4: Install and Configure the VDI Core in the Installing information.
- Import the data and settings into Sun VDI 3.0.
Later on, the exported data should be imported with the vda-migrate command, this time called in the Sun VDI 3.0 installation directory.
VDI must be configured before the data can be imported. In order to import data, Sun VDI 3.0 must have been previously installed and configured.
It's also recommended to import the data before any other action takes place on a Sun VDI host, (i.e. before adding a desktop provider, or performing another administrative task)./opt/SUNWvda/sbin/vda-migrate -i </path/to/directory>
Import data from Sun Virtual Desktop Infrastructure 2.0 ([y]/n)? Creating Desktop Providers + virtual.center... Enter port for VC host virtual.center [443]: Creating Pools + pool.A... Restoring Pool Assignments + Importing desktop /datacenter/vm/vda-dyn-pool.A/vmA01... + Importing desktop /datacenter/vm/vda-dyn-pool.A/vmA02... + pool.B... Restoring Pool Assignments + Importing desktop /neid.Datacenter/vm/vmB11... Restoring non-assigned Desktops + Creating Personal pool for 'virtual.center'... + Importing desktop /datacenter/vm/vmC31... + Importing desktop /datacenter/vm/vmD41... The data from Sun Virtual Desktop Infrastructure 2.0 has been imported into Sun VDI 3.0.A log file is created with detailed information and can be used to track eventual errors. The log file can be located at '/var/adm/log/vda-migrate.<date and time>.log'.
For more information about the vda-migrate command see its usage page.
- Upgrade the VDI Tools.
The VDI tools are installed on the desktop guest OS and are necessary for recycling to work properly and to handle RDP connections when the guest OS enters standby. VDI 3.0 introduces some improvements which are incompatible with previous versions of the tools. If you are importing desktops from a previous version of VDI, the tools need to be upgraded.- Go Control Panel > Add or Remove Programs. Remove 'Sun Virtual Desktop Connector Tools'.
- Install the new version of the VDI tools. Instructions can be found here.