Morning! I was wondering what some feedback was on SQL backup practices and what is the best. Currently I run a full backup using SSMS Maintenance Job which needs to complete before Backup Exec Symantec product. I rely solely on the Backup Exec system to backup TLOGs every hour after the full back through BAckUp Exec is complete. It seems a bit redundant for me to run a full back up using SSMS at 10:30PM and then Symantec Backup Exec runs at 1130PM with full back up but with the TLOGs after that. If I run a full backup using SSMS and the backup completes then Backup Exec fails with TLOGs because of the SSMS full backup and this does not catch up until 1130PM. There is a break in the backup process on our end that I would like to resolve and actually review. Any feedback, shared links on this topic will be greatly appreciated.
[EMS SQL Backup] has built-in templates for different types of servers. Each template includes different types of backups and different schedules according to optimal maitenance practices. The template can be easily transformed to the maintenance policy on real servers. :
There are some useful "SQL backup Practices": 1.Backups should not be on the same physical storage as your database files 2.Set up schedules to automate your backups 3.Use a test server to verify the restore procedure of your backups 4.Test your recovery strategies 5.Use all available verification options during backup process I found it out in an short article [(here)], hope would be useful :
In my experience after working in a high online transaction processing environment, we were administering just under 50 SQL server instances. The backups were being done either with Redgate sql backup, and for the not so critical servers we used maintenance plans. But not both on one server. Depending on how busy the database server is, you need to find out when is a suitable time to schedule a full backup to run once a week. Find a suitable time to run a differential backup once a day. And depending how busy the individual database is, schedule transaction logs to run every 15 minutes. That way you should be able to restore a database to a reasonable time in case of emergency.