Backup Exec upgrade - Exec 12 to Exec 2010

[mo_vigilante]

Hello all,

In the next week or so I will be intending to perform a upgrade on Backup Exec 12 to 2010. This will be one of my first BIG jobs from my point of view and experience and I thought I'd never learn unless I try to carry it out myself rather than a company.

Just wondered if anyone else has gone through this upgrade? And if so, what problem did you encounter if you had any?

From what I've read online on Symantec it seems straightforward, but got a feeling it isn't!

Just hope the remote agents upgrade goes smoothly as well.

Thanks.
Mo

[Shielder]

Surprisingly, my 12 to 2010 upgrade seemed to go alright when I did it, was expecting all sorts of things to go wrong given how frustratingly broken the software always seems! I had to input new product keys as one would expect to, but it was pretty much incident free. Of course with anything like this, Your Mileage May Vary.

Right now however, I'm doing an upgrade from 2010 RTM to R3 (to fix some exchange backup issues I hope), should be as straightforward as 12 to 2010 but I won't hold my breath.

[Hawkeyez]

What issues are you having with Exchange?

I have done a new install to a fresh media server (BE2010 R2), and added a couple of new Win2008 servers.
They went fine, so moved over two Win2003 servers over, one being Exchange (2003), which is kicking back some VSS Writer errors. They other (runs Moodle) is fine also.

I'm just rebooting Exchange after another attempt at a fix. Fingers crossed it works.

"Luckily" I didnt move over the 3 DC's and Sims Server, so are still being backed up without issues on the BE11d setup.

[mo_vigilante]

Cheers guys for your inputs. I've been away but hopefully will go smooth like your upgrade. Just a random question - with the existing job setups that are already, can you keep the existing job setups or you do you have to start from scratch to create jobs?

Thanks.
Mo

[spc-rocket]

Hi Guys,

I'm about to upgarde to BE 2010 R3 from 11d SP5, any issues to look out for?

Thanks,

Ash.