Backup SQL2000 and SQL2005 with Agent very slow

[linkeloetje]

Since a while and I can't figure out what caused the probem, the Backup of a Remote SQL2000 and a remote SQL2005 server through a SQL-agent is very very slow. About 50 MB/Min. to 100MB/Min. Before the speed was about 900 MB/min
Both servers have lots of databases ranging from 100MB to 50GB so you can figure out how long it takes before a backup Job finishes. This wasn't a problem before.
In the meantime i've updates Brightstore from 11.5 SP1 to SP2 but without any results.

I've tried a new backup-job, backup directly to tape without diskstaging. What parameters can be changed so I can try something new? Disable latest mcafee virusscanner?
Can anyone give me some suggestions what to look for?

 

[n018737]

Normaly slow backup with BrightStor SQLServer Agent is a network problem.

We have a lot of SQLServers (2000/2005) and the backup output ratio is very high.
Also we have SQLServer 2000 over Virutal (VMWare ESX) MS Windows 2000 and it's run very fast.

This is a log of our SQL Server databases over LTO Drive and conected to LAN 1 GBytes

Job No....................... 2
Job ID....................... 11928
Workstation.................. DATABASESRV1123
Source....................... dbasql@MSSQLSERVER\P_CONT_0233
Target....................... 11/17/06 1:00 PM, ID C0D8, Sequence #2, S/N 000088
Session...................... 6
Start Time................... 11/17/06 7:42 PM
Session Method............... Backup Agent - Database (Full)
Total Database(s)............ 1
Total Skip(s)................ 0
Total Size (Disk)............ 1 KB
Total Size (DB).............. 1,896.87 MB
Total Size (Media)........... 1,896.93 MB
Elapsed Time................. 46s
Average Throughput........... 2,474.26 MB/min
Session Status............... Finished

 

[linkeloetje]

Thanks for your reply, but...
Making a backup that takes only 1 minute for about 2 GB is quit good but doesn't give an accurate "avarage throughput"
My backupjob from 1 database looks like the one below, which has a lousy throughput. Because we use Disk-staging, I made a Backup, directly to tape, of one database when everything on the network was quit. But with the same result.
Making a backup with a script, to a file on the staging disk, takes 20 minutes for a 37GB database, that's 1850MB/Min. So I thing that Arcserve is the problem. It might be what's running on the backup server, or what's running on the SQL server. Al other backup's from different servers run smoothly. So I expect it has something to do with de agents, the sql-agent in particular. Even the backup of all the other files from the sql-server has good performance.

What can be done.

Job No....................... 18
Job ID....................... 7356
Workstation.................. MYSERVER
Source....................... dbasql@SQL2000\MYDATABASE
Target....................... 3/31/06 11:04 AM, ID 0C5C, Sequence #1
Session...................... 165
Start Time................... 11/21/06 5:49 AM
Sequence..................... 1
Workstation.................. MYSERVER
Path......................... dbasql@SQL2000\MYDATABASE
Owner Name................... caroot
Session Type................. Backup Agent
Session Method............... Backup Agent - Database (Full)
No Registry
Directories Backed Up
Description.................. STAGING [JOB 7] SUBJOB 16, Source [MYSERVER ( 10.0.0.243 )], Backup Job
Total Database(s)............ 1
Total Skip(s)................ 0
Total Size (Disk)............ 1 KB
Total Size (DB).............. 21.212,31 MB
Total Size (Media)........... 21.222,68 MB
Elapsed Time................. 6h 8m 4s
Average Throughput........... 57,65 MB/min
Session Status............... Finished

 

[linkeloetje]

The Problem is resolved:

The Microsoft SQL Agent Configuration, "Max VDI Transfer" was set to default “2097152”. By trying different settings, and because of other problems, this setting was changed. So now this problem is resolved.

Nevertheless I've still got a problem when making a backup of several SQL servers in combination with diskstaging, for which i will start a new threat.

 

[n018737]

Where do you change the "Max VDI Transfer"?

 

[linkeloetje]

I changed the "Max VDI Transfer" in the "Microsoft SQL Agent Configuration"-Tool from cheyenne on both SQL servers.