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
Mehdi
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
Hello,
I would like to know if someone has experience using the Simultaneous
Write feature of TSM 5.4?
We are thinking about creating a copy_pool on a remote site tape library
and enable this feature to see if we can create the copy tapes at a
remote site directly.
Has anybody done this?
Thanks
I have a 5.3.4.0 TSM server and am using simultaneous write for one client
with a huge DB to backup. Like 300+ GB DB dump.Backing up over
Gig Ethernet direct to LTO2 tape drives in local IBM 3584 Library.
Onsite and offsite tape pool. Works well.
I do not have a remote site, so don't know
: Simultaneous Write
Hello,
I would like to know if someone has experience using the Simultaneous
Write feature of TSM 5.4?
We are thinking about creating a copy_pool on a remote site tape library
and enable this feature to see if we can create the copy tapes at a
remote site directly.
Has anybody
Is anyone out there doing this? :-) Thanks!
God bless you!!!
Chip Bell
Network Engineer I
IBM Tivoli Certified Deployment Professional
Baptist Health System
Birmingham, AL
-
Confidentiality Notice:
The information contained in this email
Greetings, all. I'm dipping my toes into the simultaneous-write
regime with server-to-server volumes. I'm seeing a behavior I'd like
to confirm.
I've got a few boxes which do small backups every few minutes of the
day. I'd been hoping to get them all doing simultaneous-write to my
remote
Hi,
Are there any messages anyone has picked up which relate to the success or
failure of simultaneous primary and copy pool writes?
I'll be trawling through the messages manual for a while so any hints
would be greatly appreciated.
Thanks,
Matthew
Aviva plc
Registered Office: St. Helen's, 1
configured to use simultaneous write may leave orphaned
rows in database tables.
Problem: TSM servers configured