8.0 Upgrade - Who's done it?

[hutchingsp]

We're on 7.0 SP5 and our upgrade kit has arrived.

Our CommServe is a VM so I can do a DR backup and a VM snapshot prior to the upgrade, but of course I'd like to get a feel for how people have found the upgrade process to have gone?

 

[cabraun]

I would like to know people's experiences with upgrading to 8 as well. But please be specific in detailing your experiences. To say "We upgraded and everything was fine" just to later find out that you are running a CommServe, 1 Media Agent, and 3 Windows File System iDAs well I would expect that type of vanilla environment to upgrade without much problem.

We are running
1 CommServe (7 w/ SP2)
4 Media Agents (7 w/ SP2) 2 on the same network and 2 separated by firewalls through which traffic passes only 1 direction and the other 2 are fiber SAN attached and utilize Gridstor
130 Windows (NT4, 2000 and 2003) iDAs (Most are 7 w/SP2) but the NT4 and the one on our SharePoint Portal Server are 6.1 w/ SP4
15 Oracle iDAs for 9i and 10g (7 w/ SP1 and SP2 mixed)
8 SQL iDAs for 2000 and 2005 (7 w/ SP1 and SP2 mixed)
1 SharePoint Docs and Database iDAa (6.1 w/ SP4)
1 Active Directory iDA (7 w/ SP2)
2 Exchange Mailbox iDAs (7 w/ SP2)
2 Exchange Database iDAs (7 w/ SP2)
2 Exchange Mailbox Archiver iDAs (7 w/ SP2)
2 Windows File System Data Archiver iDAs (7 w/ SP2)
2000 Windows desktops with the 6.1.14 Outlook Add-In for E-mail stub recovery.

So needless to say, what might be a simple upgrade in a vanilla environment might not be so easy in a larger / more complex environment. So rather than just posting here that you upgraded and it went fine, please give some detail about your environment.

Thanks

 

[theravager]

I've done the upgrade in a very large environment. There were numerous issues after the upgrade.

1. Exchange mailbox archiver is bugged is causes the mapi profiles to continually reset. Easy to fix but its a pain in ar*e. No resoulution.

2. Windows file agent has a bug tjat ifind process crashes when there are multiple paths/luns and exclusions. Theres a hotfix for this that you can get via cv if you have the issue.

3. Aux copies sometimes decide to use all possible streams on a media agent which make all jobs come to a screaming halt. This has been under investigation for a while but no resolution.

Other then that the upgrade itself was fairly effortless. I'd reckon i would hold out for sp2 unless you have a need to go to v8.

 

[hutchingsp]

OK issues encountered so far:

Backups to an LTO4 library gave an error of "Unable to disable hardware encryption" (that we don't want to use) - a hotfix/patch 11606 fixed that.

This may not be specific to the upgrade but because of the above, I quickly moved a storage policy copy to use a different LTO3 library, and when I came to do an incremental backup it insisted on doing a full but only for one client that uses that copy - and typically it was all 7tb of our primary file server, and Commvault say there's no way to change that behaviour.

We're also finding on one of our LTO3 libraries that media either imported via mail slot, or loaded in magazines, shows in Galaxy in the libraries "Slots" view, but doesn't show in the media pools until you do a right-click and discover/import/full scan or "something" to nudge it - that's waiting for support to do a webex.

 

[cbwfq]

I did the upgrade over this long holiday and had no trouble with the upgrade. In doing this upgade my suggestion is to FOLLOW the information when it comes to the DB upgrade.