I had the same issue. I tired to work with support but no luck..I had to end up fining a work around, it is lised below.
- perform a full backup
- install the same version of nsm on a seperate server
- perform a restore of your full backup
- upgrade the seperate nsm to version 6
- uninstall version 5 on your main nsm
- install version 6 on your main nsm
- perform a full backup on your seperate nsm after upgrade is complete
- copy full backup and perform a restore on your main nsm
Just to confirm, I have also carried out the above. I did find a little more information out, however, before doing so. The NSM had been up and running successfully for a while, so I had naively assumed a few things. After noting that the packet logs download function wasnt working on real-time threat analyzer, *another* issue on the server resulted in the client removing AV and reinstalling. This fixed the packet log issue, and got me thinking. It turned out that the AV exceptions were not in place for the NSM app and MySQL directories. We also had other issues after the above upgrade relating to potential DB corruption issues (noted in ems.log).
When running the upgrade process on another box (offline, no AV), I also noted that the 6.1 installer advised that I had to run the offline SQL procedures (due to fact that client had > 1 million alerts) after the upgrade. During the initial upgrade, I did not receive this warning.
So in essence, I believe the main issue was related to the fact that I had not confirmed that the two directories above were configured as AV exceptions (using VSE 8.7i).
All up and running now, though! I hope this info from sthomas and myself helps others! (Although on my part, I had done the RTM part, just not the confirming!)
sthomas - just for completeness, could you confirm if AV exceptions were configured correctly on your NSM? If this wasnt the main cause, then obviously there may be something else out there that could end up catching people out!