March 28, 2015 at 10:30 am
I just inherited 43 SQL Servers.
Maintenace plans are not being used and I know that that is not the most flexible method of doing backups and T-SQL Scripts are prefered.
All of backups are performed using cmdexe or sqlcmd. They are not using T-SQL to perform the backups.
What is the best practice to perform backups?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 28, 2015 at 10:50 am
Go to http://ola.hallengren.com and check out his solution for backing up your databases and logs. I've been using it for years and it has saved me countless hours. It even integrates with third party tools like Idera and redgate through a common proc-interface.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 28, 2015 at 10:59 am
PS regarding your question about best practices I was not sure if you meant tools or strategy so focused on toos in my last post since you mentioned Maintenance Plans (MPs). The tools you use (MPs, Ola's scripts, something else) to invoke the database backups is not nearly as important (relatively unimportant actually) as your backup and recovery strategy. The frequency with which you take a full database backup, differential database backups (if at all) and transaction log backups (if in full or bulk logged recovery) will be dictated by the data owners (usually a business owner) so your DR plan's RPO needs to line up with their expectations. That is the important thing to nail down when taking over these new instances. Do not assume that the previous schedules were correct, ask, and implement accordingly.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 28, 2015 at 11:01 am
Orlando Colamatteo (3/28/2015)
Go to http://ola.hallengren.com and check out his solution for backing up your databases and logs. I've been using it for years and it has saved me countless hours. It even integrates with third party tools like Idera and redgate through a common proc-interface.
Thanks! 🙂
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 28, 2015 at 11:08 am
Orlando Colamatteo (3/28/2015)
PS regarding your question about best practices I was not sure if you meant tools or strategy so focused on toos in my last post since you mentioned Maintenance Plans (MPs). The tools you use (MPs, Ola's scripts, something else) to invoke the database backups is not nearly as important (relatively unimportant actually) as your backup and recovery strategy. The frequency with which you take a full database backup, differential database backups (if at all) and transaction log backups (if in full or bulk logged recovery) will be dictated by the data owners (usually a business owner) so your DR plan's RPO needs to line up with their expectations. That is the important thing to nail down when taking over these new instances. Do not assume that the previous schedules were correct, ask, and implement accordingly.
I know what to do with respect to backup and recovery strategy.
I was unsure of the best method to backup.
I do not like sqlcmd and cmdexe. I do not want to prose moving away from that without a valid justification.
Thanks!
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply