Prolonged backup in sql

Question

Hi guys,We have a sql server and we backup the it using MS Windows type of backup.Would like to inquire our recurring prolonged backup on sql server. A prolonged backup is considered when the allotted backup window exceeds running&nbsp;24hours.&nbsp;The&nbsp;Master/Media server and the&nbsp;Client server are already both on&nbsp;10GB&nbsp;Backup LAN.&nbsp;&nbsp;The files that are backed-up are SQL DB files.&nbsp;Currently the backup size of the weekly and monthly backup is around&nbsp;1.8TB&nbsp;(from&nbsp;3.5TB&nbsp;to&nbsp;4.8TB, to lessen backup time 1 Database backup was relocated to another drive during weekly and monthly backup). Backup time was reduced from around 200hours to 48hours but still&nbsp;prolonged&nbsp;backup is still encountered.&nbsp;*Noticed that the KB/SEC speed is quite slow eventhough it is on 10GB LAN. Any thoughts.

marianne · Answer

I would firstly look at resources on the SQL server during backup - CPU, Memory, disk.
Please also have a look at this section in the manual:
https://www.veritas.com/support/en_US/doc/17221771-129889660-0/id-SF930816798-129889660

raek · Answer

There is a bottleneck somewhere from client to server, you have to check all your chain links while backup is running : CPU, memory, disks, switches, routers/firewalls, tape drives, SAN, ... etc. And this requires some knowledge and experience in all these fields.

Forum Discussion

Prolonged backup in sql

2 Replies

Related Content

Legacy SQL backup policy

SQL backup query

SQL Backup error

Full backup executed after DIFF (SQL backup)

NBUITA - Connecting with Oracle SQL Developer

Recent Discussions

setup Malware Scanning

Data migration for LTR images of 3 clients

Installing a New Media Server and Transferring the Media Server Role

Silent Uninstall Switch for Veritas NetBackup Client

How to update netbackup agent java version?