Would other backup tools suffer the same problem then? If this is a
filesystem problem I would expect so.
To the original poster: how long does it take Barfserve to restore a 60 GB
filesystem with 10M files?
As you can tell, I'm no fan of Arcserve.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (719) 260-5991
Email: [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Nicholas Cassimatis/Raleigh/IBM
Sent: Wednesday, September 20, 2000 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Slow restore for large NT client outcome.. appeal to Tivoli
Development/Support
Jeff,
One thing to show your NT Admins is just how much overhead NTFS has. The
way I've done this before is to copy a drive, either locally or over the
network. If you take one of the drives with a lot of small files, can copy
it, the performance will drop as the copy goes on. The more files you
stick on an NTFS partition, the higher the overhead becomes. The way the
NTFS allocation tables work, the more files you put in, the more complex
the tables become.
Here's the test I did, in basic form:
On a system with a large drive, net use (NT speak - "Map Network Drive") to
an empty drive on an adjacent machine.
Copy a 20GB directory (from the command line - no NT speak) to this drive.
Measure performance.
Delete data on target system.
Copy entire drive to target. Measure performance.
Laugh as NT Admins realize how bad the performance gets with the larger
drive.
(If you can't tell from the above, I'm not much of an NT fan)
Nick Cassimatis
[EMAIL PROTECTED]
"I'm one cookie away from happy." - Snoopy (Charles Schulz)
