joe90bass Posted May 4, 2010 Posted May 4, 2010 When installing, some time back, SQL 2008 onto one of our Servers I never checked whether backup Exec 12 supported SQL 2008 After many months of minor niggles such as not being able to edit a job without having a stack exception error, the niggles which I thought a reinstall during half term would cure have turned into bigger issues such as restore problems and the time has come to look into this. I have now discovered that backup Exec 12 does not like, at all, SQL 2008 on the same box Having no money in our budget for IT this year, the chances of getting an upgrade are pretty slim. Has anyone on here managed to get a workaround?
danrhodes Posted May 5, 2010 Posted May 5, 2010 This is a solution I have found. -Give the backup account "db_datareader" "db_datawriter" and "sysadmin" rights to the master database -Make sure backup account was added to "logon as a batch job right" through local security policy -Update Remote Agent by copying the RAWS folder to SQL server and running the setupaax64.cmd -RestartRemote Agent services as well as Backup Exec services And try your backup! D
joe90bass Posted May 5, 2010 Author Posted May 5, 2010 (edited) Thanks for the suggestions. Just tried it, but still no luck. The problem is I can actually take a backup, but can't amend the backup job, I'm now, recently, also unable to restore work. I don't have any real alternative servers to migrate SQL server to either, and I don't know if I did if that would solve the issue - is the damage already done to the server as far as BE is concerned! Edited May 5, 2010 by joe90bass typo's
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now