September 12, 2010 at 8:38 am
We are currently implementing NetBackup as our SQL Server backup solution and I was hoping people in the SQLServerCentral community who are using (or have used) Netbackup as a backup solution could provide feedback on how they implemented it, why it was implemented that way and what challenges were faced in the process.
Right now we have it set up in such a way that the NBU server would first write the backup to disk and then it would go from disk to tape at a later time.
Our reasons for not using the NBU server for kicking off the job is the inability to kick off a pre-script to run a consistency check before the weekly full. There are other ways to schedule the checkDB, but we would really like the operations packaged together. NBU offers something that they were initially calling a 'pre-script', but it turns out it's really referred to as a 'pre-notify' and its main purpose is to notify when a database has started backing up. So by the time the checkDB would execute, the backup threads have already been triggered.
So my immediate goal is to gather the pros and cons between kicking the job off from the NBU server vs. kicking it off from the client. My long term goal is to make sure I have consistent, valid backups that I can easily restore from within the agreed upon time to recovery 🙂
Thank you for any input you can provide!
Kim
September 12, 2010 at 9:18 am
It sounds like you are using the same methodology I would use. Pros - checkdb and multi-layer protection in case of failure (copied to NBU and then to tape is a good thing over direct to tape).
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply