*SM'rs

     FYI

     Not to long ago I posted a message explaining a problem concerning
     slow copy pool restores when the copy pool data resided in virtual
     volumes (the restore was a faktor 10-15 slower than expected).

     Well we finally received a useful tip from TSM support. It had
     everything to do with the setting of the TSM server option TCPnodelay.
     When this option is set to YES the virtual volume copy pool restore
     behaves in a manner expected of them (fast enough).

     This setting has only to be set at the target server, setting this
     value on the source server has no effect on the restores.


     regards Walter Ridderhof



-----------------------------------------------------------------
ATTENTION:
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
=========================================================================