SQL 2K5 EE VLDB backing up issue | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL 2K5 EE VLDB backing up issue

Folks, for VLDB sizing around 2T, some ideas about the backup schedules considering the backup time and performance. ——————
Bug explorer/finder/seeker/locator
——————
Obviouslyhttp://www.sql-server-performance.com/backup_restore_tuning.asp is a good one to refer,http://www.microsoft.com/sql/prodinfo/previousversions/scalabilityfaq.mspx too. http://www.microsoft.com/sql/prodinfo/previousversions/scalability.mspx on the scalability, before that I would suggest to audit the hardware whether it can cope up the load. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
quote:Originally posted by xiebo2010cx Folks, for VLDB sizing around 2T, some ideas about the backup schedules considering the backup time and performance. ——————
Bug explorer/finder/seeker/locator
——————

If your company is willing spend money, disk backup (HW) solution (snap/snap clone technology) is best approach instead of using native backup solution with multiple files and filegroup backups…
Most of the SAN vendors provide this technology.
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

I don’t think my company will purchase the disk backup solution at least this year. We are currently backing up DBs to 3 different disks with 2 backup files each at the same time. One full db backup contains 6 different backup files located in 3 different physical disks. Also we have hourly TransLog backup to one dedicated SAN drive. Any potential problems with this kind of backup method?
quote:Originally posted by MohammedU
quote:Originally posted by xiebo2010cx Folks, for VLDB sizing around 2T, some ideas about the backup schedules considering the backup time and performance. ——————
Bug explorer/finder/seeker/locator
——————

If your company is willing spend money, disk backup (HW) solution (snap/snap clone technology) is best approach instead of using native backup solution with multiple files and filegroup backups…
Most of the SAN vendors provide this technology.
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

——————
Bug explorer/finder/seeker/locator
——————
Have you looked at the links posted above as there are few counters up there, the current setup you have suitable at present. But you have to monitor the backup/restore performance by taking help of PERFMON counts. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Along with Sayta links you can also take a look third party backup solutions LiteSpeed and Red-Gate ect…which will reduce your backup size upto 80% and improve backup time… MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

]]>