Speed througput for Snap server

[cgwillard]

I am using ArcServe 2000, on a Win NT 4.0 SP5 server, to backup to an Exabyte EZ17 tape drive. Currently, it takes 30 hours to backup 62 Gb. In ArcServe's Activity Log, these are the entries I see:
8/18 11:23 Connect to snap server...
8/19 10:11 Start backup session...
8/19 17:57 Disconnect from snap server...

Does anybody know what could be happening during the 11 hours between connection and starting the backup?
I have been struggling with this issue for months now (since we got the Snap server), and I can't imagine that everyone else is getting such slow backups with a Snap server.

ANY advice would be appreciated. Also, please share positive experiences with backing up a Snap server. Thank you.

 

[jimpames]

Did you install the QSS patch?:
---------------------

http://support.ca.com/Download/patches/asitnt/LO91823.html

-----------------------
PRODUCT: ARCserve 2000 AE/WG Edition RELEASE: 7.0

APAR #: LO91823 DATE: 5 APR 2001

PROBLEM DESCRIPTION: NT -SLOW DOWN WHEN BACKING UP A NAS DEVICE
----------------------------------------------------
>>> ATTN: THIS FIX IS FOR NT 4.0/W2K ONLY <<<

ARCserve would experience a slow down when backing
up a NAS device, specifically Quantum Snap Server.

PREREQS: LO82875
----------------------
Arcserve must be COMPLETELY patched or it can give you trouble.

http://support.ca.com/Download/patches/arcserve2000.html

Let me know what you think...

jimpames@hotmail.com Jim P. Ames

http://www.jimpames.com

 

[cgwillard]

Good thinking - I did install patches LO82875 and LO91823. I saw that LO91823 was intended to speed up NAS backups, but it hasn't made a bit of difference.

I have everything on the snap server in one root directory, and I back up only that root directory. I thought that might help because ArcServe would only have to verify permission one time. It isn't any faster or slower than backing up each folder separately, though.

Any other suggestions?

 

[jimpames]

Use the Arcserve Server Admin, tape engine, config wheel, debug to screen and file.
This will create a log of all activity and we will get a better idea of what is going on.
Then, fire off a QSS backup-
I'll help you read the log... It will be full of SCSI commands...
Sincerely,
jimpames@hotmail.com Jim P. Ames

http://www.jimpames.com