Mainly VMware things
When upgrading NSX manager you might encounter an error for ‘large database table’ or ‘insufficient disk space’ or ‘database disk usage’. These errors can either be because the log directory in /common/logs is full or you actually have a valid database full problem.
Cloud Director specifically requires devices to be gracefully removed from itself prior to removing the devices from the vCenter or physically removing them from the DC. If you have this issue then it’s best to see if you can power back on devices or restore the VMs and then remove them in Cloud Director properly as that is the best method and does not require database manipulation. If you do not have that option then you will need to raw edit the postgres DB.
When upgrading from NSX 6.4.2, 6.4.3, or 6.4.4 you might receive the error message “Upgrade target version 6.4.10.17626462 is same or less than the current version 6.4.4.”
Our configuration at the start of this process is vCloud Director 9.5 installed and successfully running on CentOS7 VM using an external MS SQL database. By the end of this process we will be running Cloud Director on the self-contained appliance with a single external NFS share. I highly advise you create a cloned environment and run through these steps to ensure they work correctly in your environment as this is a highly complex process. If you run multiple cells then I suggest you perform this work on a single cell, upgrading it to the very end, remove all additional cells and simply deploy new cells once the primary is successfully working. This method assumes isolation from direct access to download updates, due to this the article is written around creating ISOs, mounting CDs, etc. With Cloud Director 10 the old flex UI has been completely deprecated. There are many new items in Cloud Director 10.1 which I have summarized in my article [vCloud Director 10.1 Release].
Our configuration at the start of this process is vCloud Director 9.5 installed and successfully running on CentOS7 VM using an external MS SQL database. By the end of this process we will be running Cloud Director on the self-contained appliance with a single external NFS share. I highly advise you create a cloned environment and run through these steps to ensure they work correctly in your environment as this is a highly complex process. If you run multiple cells then I suggest you perform this work on a single cell, upgrading it to the very end, remove all additional cells and simply deploy new cells once the primary is successfully working. This method assumes isolation from direct access to download updates, due to this the article is written around creating ISOs, mounting CDs, etc. With Cloud Director 10 the old flex UI has been completely deprecated. There are many new items in Cloud Director 10.1 which I have summarized in my article vCloud Director 10.1 Release.