I've just found this...

http://seer.support.veritas.com/docs/281629.htm

...which suggests that you can install BE on a SQL 2005 server, which implies the BEDB would be fine running on SQL 2005.

Can someone explain this contradictory information?

http://forums.veritas.com/discussions/thread.jspa?...

I'm not 100% sure what that support article refers to, but while 10d can't use SQL2005 for its database, this is now possible with 11d.

I hear what you're saying, but we've already paid a fortune to implement 10d, and as it came out while SQL 2005 was around, and the the adjustment needed is TINY (let's bear in mind here that's it STILL SQL; it's not as if it's got to sit on Linux), one would expect better compatibility for an Enterprise product like Backup Exec.

Surely you're not suggesting that they force their customers to part with more money to upgrade to 11d, rather than provide a Hotfix for the many users of 10d? That's reckless, unfair capitalism, isn't it?Message was edited by:
Al Wilson

While I can understand your disappointment, BE10 came out in Jan 2005. SQL 2005 didn't come out until November 2005. So support for SQL would have to be added with a hotfix.
You can't add a hotfix until you have BE installed. You can't install BE without the hotfix (unless you are going to install to MSDE then move the database). SO there's a kind of catch 22 situation.
I personally am in favour of installing SQL to a local MSDE instance. MSDE is "good enough" for BE, it's very well supported, and you than have your disaster recovery covered for your backup server. With a remote database, in the event of a disaster you have to recover the DB before you can recover BE. But you'd also need to recover BE before you could recover SQL...

We found MSDE couldn't handle the volume of backup operations that we do. We therefore have a DR plan to cover our current setup. I see what you mean about the catch-22 though.

It could still be done by Hotfix for existing and new installations.For existing installations, apply the hotfix, then move the DB using BEUtility. Pretty straightforward. For a fresh install (if you only own 10.x) the process of making 10d SQL 2005-compatible may be a little protracted, but it's also a lot cheaper than testing and upgrading to 11d. In my opinion a lot of organisations would prefer that route.

VERITAS have already done the work for 11d. It would show some customer care if VERITAS packaged up their efforts in a Hotfix to retrofit 10d.