Hi,
identify your bottleneck.
It is not obvious what it is.
Your backup times were sub-standard even a couple years ago.
Some tips:
- check using FTP your network
- check the perform,ance of your SAN drives
- copy a part of your NT drive either into NUL or on another SAN
drive, how long will it take?,
- look at the drive lights when backing-up, by this speed they
should only occasionaly light
- look at the CPU on you file server during the backup, at this
speed it should be well under 10%
- if CPU is near 100%, disable compressing
- check your server, even with 4 CPU´s the database performance could be
the bottleneck
- copy a part of your NT file system on a drive local to TSM server
n back it up from there,
how long will it take?
If long, the database might be the bottleneck,
in this case add spindles to your server and spread the database among
them
and check whether the physical and logical drives on your scsi
controller have caching on
(WRITE-BACK, not WRITE-THROUGH)
- ressourceutilisation 10 -- if you have more NT drives to backup, using
this setting they will be backed up in paralell,
maybe this kills your ressources
- TCPWindowsize 63 -- setting it larger could improve network speed if this
is the bottleneck, have a look at older postings
- etc.
good luck
Juraj
> -----Original Message-----
> From: Steve Harris [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 01, 2002 1:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Backup of Win2`K Fileserver
>
>
> Hi Guillaume
>
> RENAME FILESPACE may help here
>
> Rename the new filespace to some "temporary" name
> Rename the old filespace to the new name
> Run incremental backup
>
> After a suitable period, delete the "temporary" filespace.
>
> Regards
>
> Steve Harris
> AIX and TSM Admin
> Queensland Health, Brisbane Australia
>
> >>> [EMAIL PROTECTED] 01/08/2002 6:30:35 >>>
> Hello
>
> I have a BIG performance problem with the backup of a win2k
> fileserver. It used to be pretty long before but it was
> managable. But now the sysadmins put it on a compaq
> storageworks SAN. By doing that they of course changed the
> drive letter. Now it has to do a full backup of that drive.
> The old drive had 1,173,414 files and 120 GB of
> data according to q occ. We compress at the client. We have
> backup retention set to 2-1-NL-30. The backup had been
> running for 2 weeks!!! when we cancelled it to try to
> tweak certain options in dsm.opt. The client is at 4.2.1.21
> and the server is at 4.1.3 (4.2.2.7 in a few weeks). Network
> is 100 mb. I know that journal backups will help
> but as long as I don't get a full incremental in it doesn't
> do me any good. Some of the settings in dsm.opt :
>
> TCPWindowsize 63
> TxnByteLimit 256000
> TCPWindowsize 63
> compressalways yes
> RESOURceutilization 10
> CHAngingretries 2
>
> The network card is set to full duplex. I wonder if an FTP
> test with show some Gremlins in the network...?? Will try it..
>
> I'm certain the server is ok. It's a F80 with 4 processors
> and 1.5 GB of RAM, though I can't seem to get the cache hit %
> above 98. my bufpoolsize is 524288. DB is 22 GB
> 73% utilized.
>
> I'm really stumped and I would appreciate any help
>
> Thanks
>
> Guillaume Gilbert
>
>
>
> **********************************************************************
> This e-mail, including any attachments sent with it, is confidential
> and for the sole use of the intended recipient(s). This
> confidentiality
> is not waived or lost if you receive it and you are not the intended
> recipient(s), or if it is transmitted/ received in error.
>
> Any unauthorised use, alteration, disclosure, distribution or review
> of this e-mail is prohibited. It may be subject to a
> statutory duty of
> confidentiality if it relates to health service matters.
>
> If you are not the intended recipient(s), or if you have
> received this
> e-mail in error, you are asked to immediately notify the sender by
> telephone or by return e-mail. You should also delete this e-mail
> message and destroy any hard copies produced.
> **********************************************************************
>
