01-24-2017 01:42 PM
Just wondering if anyone has gone through the upgrade to 3.0 yet? Tips? Hints? Gotchas?
01-26-2017 07:42 AM
Not yet, and I'm expecting it to be not that simple.
My advice might be to try to test it. If you create a VM with 2 x vCPU, 2GB vRAM, two vNICs, and four disks of 200, 20, 70, 70, and a virtual SATA DVD drive, then you should be able to boot / install from the v2.7.3 ISO, and then configure as a standalone master/media. Create another VM to be your Admin Console, use that to configure a catalog backup, and run that catalog backup. And then you shoud be ready to perform a test upgrade from v2.7.3.
But after all that effort you may well find that a dummy/demo/test virtual appliance simply cannot be upgraded due to internal restrictions/limitations.
02-02-2017 12:44 AM - edited 02-02-2017 11:56 AM
In version 2.6.1.2 to 3.0 upgrades, your vmware backups may fail.
NetBackup appliances upgraded to software version 3.0 (NetBackup 8.0):
All VMware backups will fail with status 6/23 regardless of the transport method with the following events in VxMS provider log:
01/05/2017 16:41:25 : connectToHost:VixGuest.cpp:957 <INFO> : Transport Modes available on this host: file:san:hotadd:nbdssl:nbd
01/05/2017 16:41:25 : vdCleanup:VixInterface.cpp:1286 <TRACE> : in
01/05/2017 16:41:25 : g_vixInterfaceLogger:libvix.cpp:1775 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .
01/05/2017 16:41:25 : g_vixInterfaceLogger:libvix.cpp:1775 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_Connect: Establish connection.
This is caused by this dynamic-link library file not removed by the installer during upgrade from 2.6.1.2 to 3.0:
/usr/openv/lib/map/libvix.so
This is currently being worked on in ETrack 3908353
( do we all have to contact support one by one?.... )
02-02-2017 07:17 AM
Done a few upgrades.
The mentioned issue "failing vmware backups" is only seen in 2.6.1.2 to 3.0 upgrades.
Upgrading from 2.7.x to 3.0 is OK.
This issue is now being tracked under Defect ET 3909204
In terms of fix, remove or move/rename the two files:
/usr/openv/lib/map/libvix.so
/usr/openv/lib/map/libvixST.so