- Upgrade to the latest revision of flexVDI 2.2. Upgrade the distribution on all your hosts, and the flexVDI Manager, to their latest version.
- Plan your local storage layout. If you installed flexVDI 2.2 with its default partitioning options, you will have a /boot partition and three LVM volumes: /home, swap and the root filesystem. The best way to upgrade is to either remove everything and make a fresh install, or keep /home, so you already have guest images in place. The later option is best suited if you have files that you want to keep using, but make sure to back up all important files before going on with the reinstallation. Files to back up include, but are not limited to:
- /flexvdi/volatile: volatile images you do not want to remove.
- /flexvdi/local: sysprep answer files, etc.
- /home: guest images and templates.
- /flexvdi/media_servers/cifs: Files served by the optional CIFS/SMB server hosted by a flexVDI Host.
- Other files you may have stored in the system.
- Plan your network layout. This usually means just repeating your flexVDI 2.2 network layout. Make sure to create the same virtual bridges in the same subnets, or or you will have to reconfigure the network of every Guest.
- Stop all your virtual machines and prevent users from connecting to the platform. Remember stopping clones, and setting the number of precreated desktops to "0" in Desktop Policies.
- Back up your flexVDI Manager Database, as explained in flexVDI Manager Backup and keep it somewhere safe; /flexvdi/backup will disappear during the upgrade.
- You have to create the same virbrx virtual bridges that existed in the 2.2 installation, as the guests will need them to create their network interfaces.
- You have to use the same IP address and hostname for your servers. Otherwise the Manager will identify them as new hosts and mark the old ones as down, and Pools and storage objects will keep referencing the original host names.
- You have to mount your external volumes in the same mount point, or they will not be found.