Thanks Neil, it works if copystg is set to blank.
But what I understand from the following excerpt is that autocopy=none
should be enough:
(Reference: TSM 6.2 Problem Determination Guide)
"*If the storage pool is set for simultaneous-write operations*, the
“Copy Storage Pool(s):” value references one or more other storage pool
and Tivoli Storage Manager interprets the simultaneous-write operation to
higher priority than the LAN-free data transfer. Because simultaneous-write
operations are considered a higher priority operation, this storage pool is
reported as LAN-free enabled and as such, the client will send the data
the server. The storage agent does not support simultaneous-write
On Thu, May 10, 2012 at 8:45 PM, <neil.schofield AT yorkshirewater.co DOT
> It may be worth blanking out the COPYSTGPOOL value for the storage pool as
> well as changing the AUTOCOPY value.
> I know that in TSM prior to 6.x, the AUTOCOPY property of the storage pool
> did not exist - simultaneous write was determined by whether or not
> COPYSTGPOOL was defined for the storage pool. It's possible the validate
> lanfree code is still using this as the basis for deciding whether a pool
> is lanfree-capable.
> Neil Schofield
> Technical Leader
> Yorkshire Water
> Spotted a leak?
> If you spot a leak please report it immediately. Call us on 0800 57 3553
> or go to http://www.yorkshirewater.com/leaks
> Get a free water saving pack
> Don't forget to request your free water and energy saving pack, it could
> save you money on your utility bills and help you conserve water.
> The information in this e-mail is confidential and may also be legally
> privileged. The contents are intended for recipient only and are subject to
> the legal notice available at http://www.keldagroup.com/email.htm
> Yorkshire Water Services Limited
> Registered Office Western House, Halifax Road, Bradford, BD6 2SZ
> Registered in England and Wales No 2366682