October 28, 2009 at 2:49 pm
I've always avoided using third-party sql server backup agents (veritas, symantec, etc). Vendors and internal backup admins always question why I don't use them. I guess I'm working on the keep it simple principle. Any horror stories out there about scary third-party backup agents? Anyone having success with these?
October 28, 2009 at 3:20 pm
I have used Veritas, LiteSpeed, and RedGate Backup (in addition to native sql backup).
If ranking them, I would rank them RedGate, LiteSpeed, Veritas, Native Backup as far as speed, compression, and problems factor into the backups.
The only scary stories I could come up with, however, actually relate to tape devices and not the actual agent.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 28, 2009 at 3:33 pm
I've used SQL Safe and LiteSpeed and have had very positive results with both doing backups directly to database disk files.
The only horror stories I've ever had related to this is when third party tools do database backups directly to tape. Anytime we had to do a restore, the task went to a network administrator who had no concept of how to do point in time recoveries, or restoring multiple transaction logs to a full restore. It essentially takes the backup and restore process out of the hands of the DBA's who tend to be experts in that arena.
October 28, 2009 at 5:40 pm
Don't listen to anyone who is not a DBA about database backups. They won't be responsible for recovery, you will. I would agree the tools you should be wary of are those that backup direct to tape and require an 'agent' to work. these tend to do things like 'freeze' and 'thaw' the database whilst backing it up and are not good for anything more than full backups. As a DBA I would not be comfortable if those were the only backups I had. Tools such as veritas are only good for getting backups to disk off to tape IMHO.
Other than that if you don't require backup compression or encryption native is always the way to go. I agree with the KISS principal. Why have a level of obfuscation between you and the backup strategy. A DBA does not need an all singing and dancing GUI with its own esoteric error messages to build a backup and recovery strategy, Microsoft supply all the tools and support you need and on the web you will find all the scripts and support you could ever want. Most important there will be tons of documentation on how to recover from any Disaster scenario.
If you need compression or encryption I would consider Hyperbac. You can still use standard maintenance plan or backup scripts. For all intents and purposes its the same as if you were doing SQL native backups. I have no axe to grind here its just the tool I would use for its simplicity.
One thing though, for system databases only native backups will do for me, but then I am ultra conservative when it comes to anything that affects my ability to recover SQL.
---------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply