I have been using BE9.1 forever to back up our Exchange 2003 server running on Windows 2003 Server Standard 32 bit. All was well. We just virtualized our environment and we virtualized Exchange as well as the backup server. This gave me oportunity to upgrade.
I installed a fresh install of BE12.5 on the lone physical server we have now which also runs vCenter if that makes a difference, uninstalled the 9.x backup client from the Exchange box and pushed the new client to the Exchange box from the BE console. I thought all was ok until...
I tried run a job and was getting a C++ Runtime Error. When I click the error, beremote.exe stopped responding and the client service would stop. Not a huge problem because the service would start back up fine but would fail if you ran the backup again. This occurred as soon as BE tried to talk to the agent...ie, no data would back up before the error.
I needed to backup Exchange, so I did the worst possible thing you could do in this situation and I called Symantec support. He had me run some cmd on the Exchange server in the BE folder that uninsatlled the pushed client. After a reboot, he had me copy the RAWS32 folder to the exchange server and install it locally. I did that.
Now, when I try the backup, I still get the runtime error but with the added bonus of when I click OK the clear the error, my server blue screens and spontaneously reboots itsself. The most worrysome thing about this is the last time it did so, it was stuck on the Windows splash screen (the windows 2003 screen between the POST and the Windows is starting box) for about 10 minutes before it finally came back online. With users screaming for email, you can imagine I was sweating. Anyway, I told support that they were unhelpful and decided not to try another backup until I had some insight from someone who know what they are talking about.
Anyone out there that can help????? Please.