I have a client who is still at BigFix 9.2.5 (as part of a deployment of the IBM License Metric Tool). The client wants to upgrade.
Is it “better” at this point to upgrade to 9.2.18 or 9.5.13? Can I perform a manual upgrade of the server and console directly from 9.2.5 to either version, or do I have to go through interim steps for all of the versions that required manual upgrades (if memory serves, 9,5 and 9.5.5)?
Be prepared for the database to grow quite a bit - the conversion to UNICODE in 9.5 consumes roughly double the database space, and the update can take quite a while to complete depending on your deployment size and age.
Have you read through the feature set in 9.5? In particular the audit trail cleaner and computer remover tools are now integrated into besadmin, be sure to check those out.
Hi Jason … yes, I am familiar with the integration of the audit trail cleaner and computer remover tools. Thanks for pointing out the growth in the database size; I’ll be sure to check available space before the upgrade begins. And yes, I also plan to RTFM before starting anything
Given that the database size could double with the 9.2.5 to 9.5.13 Linux upgrade, is there a minimum or recommended size for the DB2 transaction log? The documentation is silent on this question.
Also, when the documentation says “perform the manual upgrade if your database is remote” that simply means that databases BFENT and BESREPOR are not on the same server as BigFix, correct?
I’m not sure whether there is specific guidance for tempdb or the transaction log; as usual, the recommendation is to perform a full backup first.
And yes your understanding on the “manual upgrade” path is correct. When the database is remote, you will likely be prompted for DB credentials during the upgrade and the fixlet upgrade doesn’t accommodate that.