I was wondering about this restore.
1. Was any 'active' virus scanning running at the time of the restore?
I have seen alot of performance improvements with TSM restores by
disabling the virus scanning temorarily during the large restore, and then
running a manual virus scan afterwards. (some security people don't like
this idea though)
2. Was this data compressed by the TSM client?
If it was and the Win2K server had really slow CPU's that could
have caused this restore to take along time. (Combine that with the virus
scanning and things are really slow).
3. What was the situation of the file system/disk array that the restore
was done to?
Various things happening on the disks slow stuff down. Raid-5
parity checking running at the same time as the restore, (especialy on
freshly setup array). Also various file system defragmentations running
at the same time as a large restore slow things down. Some paranoid
windows admins run defrags on their arrays every day, some large very full
arrays that defrage takes all day just to run, thus they are defragmenting
24x7. Combine that with slow cpu's, TSM compression and active virus
scanning and things are all ready for a painful TSM restoration.
I hope one of those things will help you get more performance out of this
configuration.
Matthew Glanville
Eastman Kodak
"Kelly J. Lipp" <lipp AT STORSOL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/25/2002 01:06 PM
Please respond to lipp
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Windows 2000 Restore Example
Gang,
Environment: TSM Server V5.1.1.4 on Win2K, TSM Client 5.1.1.0 on Win2K
Fileserver drive.
Data Restoration Statistics:
233,002 Objects
52.54 GB
Elapsed Time: 12:57:01
Other stats appeared quite normal, i.e., Network Data transfer rate.
resourceutilization = 4, Maxnummp = 4
Four tapes/drives used at least at the beginning, tapering down to one as
time wore on.
No judgment about the overall performance of this test. Just information
for all of you.
I believe this is a file create issue on the Win2K server rather than
anything in TSM. Anybody have any ideas how to increase the performance
of
this type of restore in this environment? Frankly, I was not surprised by
this. I would like to have seen a three hour restore rather than 13, but
it
is what it is.
Thanks
Kelly J. Lipp
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
lipp AT storsol DOT com or kelly.lipp AT storserver DOT com
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175
|
