Other Changes

It is important to note changes that occur following an upgrade from prior versions. If upgrading from 3.4*, some of these may already be applied during that upgrade.

•

Portal: Portal introduces many enhancements including enabling x-drive, bandwidth throttling, ability to enroll Linux for recovery node creation, ability to stop backup and RN updates while in progress, resume recovery node build, suspending self-tests temporarily, and improved status report with tool tips. To see these changes, you must refresh your browser using CTRL-F5.

•	Winpy: For legacy systems (G11) and newer systems (G12) that are upgraded from supported 3.2SP2 levels, a Xen6 version of the winpy will be received automatically during each upgrade and will be installed by the installer utility.

•	Linpy: Support for RN creation requires a Linpy VM that is installed on the hypervisor similar to winpy, one per onQ tenant.

•	ISO SR: A new storage repository for storing winpy and linpy ISO images is created upon upgrading to 3.6 from any prior versions, except 3.4HF2 as 3.4HF2 is already configured with the new storage repository.

•

Repo: For systems upgraded from onQ version 3.2* to 3.6, all /opt/BCVdata/BCVServer/current/repo/snapshots/<pn-name>/block_sums.db databases on the onQ will be deleted. This is done as a part of repo initialization when protection is started first time after the upgrade. The process is run in the background and hence does not hold up protection start.

•

Sync Monitor: During the upgrade from 3.2* to 3.6, the schema for BCV.workloadConfig table will be upgraded to add two new columns to store snapshot information. Also, during the intermediate upgrade to 3.4HF1, a folder ‘.mysql’ will be created under /current and should not be removed once in place.

•	Pmdb database cleanup cronjobs: For system being upgraded from 3.2*, two new cronjobs created: one for daily cleanup of records and another for weekly cleanup of backups, etc. These jobs run in the background on a daily basis with a moving retention period of 90 days.

•

Licensing: Due to introduction of linpy VM on hypervisor to build Linux recovery nodes, upgrading to 3.6 might require regenerating the license for the onQ Appliance with higher node count in certain cases where node count allowed is equal to enrolled count. This step is required for AV regardless of node count.

v3.6