Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
 Posted - 2005-10-01 : 09:21:54
|
| trying to narrow this down...I just upgrade from SQL 7.0 to SQL 2000 on my win 2k server machine.I notice now that backup exec SQL Server agent is no longer functioning following the upgrade.I'm running backup exec v. 8.6 which is said to support sql server 2000. in the backup exec log, where the agent usually does its work, I now see "unable to attach" "item not found" when the attempt is made by backup exec sql agent to do its job.If I attempt to setup a one-time backup, the tab for sql server backup options is completely grayed out.My SQL server is properly registered in EM, but it does not show up as an item that is backup-able in the backup exec window.I'm suspecting I somehow have to put this SQL 2000 installation back on the radar so backup exec can see it. any ideas?thanks |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-10-01 : 09:54:41
|
Or, reinstall Backup Exec on that server.  Or, IMHO an even better idea, drop Backup Exec entirely and do regular SQL Server backups.  Or, IMNSHO the BEST idea, get SQL LiteSpeed and use that for your backups.     Although I've got limited experience with things like Arcserve and Backup Exec, they always seem to play havoc with SQL Server backups, and we were always happier when we got rid of them. SQL LiteSpeed has been absolutely flawless on the other hand, easily worth every penny. |
 |
|
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2005-10-01 : 10:43:20
|
| thx Rob, I haven't looked into the sql virtual device backup option in awhile, but now that I think about it:if I set up a virtual device on my server and backup to it every three hours, the regular TAPE backup routine will back up this virtual device to tape each evening, no issues about it being in use b/c it's not an active MDF.So, the above solution would seem to be at least as good as the backup exec agent, and SQL Backup might give me more current data with the every-three-hours transaction log backups.Worst case scenario is I have to restore from tape. If so, I just restore the virtual device from tape and then restore dbs from the virtual device. Again, I'm assuming the virtual device would be backed up to tape and not skipped like the live databases -- I would make sure not to backup to the virtual device during tape backup window. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-10-01 : 11:53:49
|
| I agree completely with everything Rob said of course. We have SQL LiteSpeed and swear by it. When you did the setup on this new server, did you remember to install the open file agent? If not, I don't believe it will be able to tie into SQL Server. The best thing to do is just run SQL Server backups and backup those to tape though. The best thing to do is just run SQL Server backups and backup those to tape though. The best thing to do is just run SQL Server backups and backup those to tape though. The best thing to do is just run SQL Server backups and backup those to tape though. Oh, and buy SQL LiteSpeed if you can afford it.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
backup exec SQL agent FAILS post- SQL 2000 upgrade