That's 'one' way to do it, not the best IMO.
 
BE does have a SQL Agent that will talk to SQL directly.  The advantages
of this are that you can backup just the Transaction Logs, or do a Full
Database backup.  You can also restore to certain transaction point and
DR is a lot easier.  It also keeps all your backup plans in one central
management tool.
 
They way you are doing takes up a lot of space and the master database
restore is a little more tedious.
 
Depending on your RPO, you may want to do log backups every few hours of
so.
 
I use BOTH the BE Agent AND the Maint. Plan for backups.
 
-Sam

________________________________

From: James Kerr [mailto:[email protected]] 
Sent: Tuesday, September 29, 2009 10:09 AM
To: NT System Admin Issues
Subject: Am I backing up SQL correctly?


I have an MS SQL 2003 database that I backup by having it run its own
backup of the databases and it creates .bak files. Then later on in the
evening I have BE backup those .bak files to tape. These .bak files
should allow me to restore a database right?
 
James

 

 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to