OK, well that answers a lot of my questions, but is this still the case when your copy storage pool tapes are usually offsite? I tried to do a move nodedata in our test domain for the copy pool and it gave me errors stating that it could not move the data in the storage pool for that particular node, because the tapes were "offsite", which they are. So will the data in the copy storage pools still collocate over time even if the tapes are offsite in a vaulting location?
Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-108 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, January 03, 2006 5:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Collocation Questions Yes, you can collocate the copy pool and not the primary pool, no problem. Yes, it will decrease the number of tapes per node. However, If you are sending the copy pool tapes offsite with a manual pull/courier process, it will increase the number of tapes for your courier run (which is why most sites don't collocate the copy pools). In TSM 5.3, you can do collocation by a group of nodes. If you have just a handfull of very important clients, for example, you could put them all in the same collocation group, and just collocate those nodes. As far as doing MOVE NODEDATA, that's up to you. When you turn collocation on, any newly written output is collocated. Any old data stays where it is. So as migration and reclamation occur, the data will gradually, over time, all get collocated, even if you don't do MOVE NODEDATA. So the situation will gradually get better by itself, but not necessarily quickly. An appropriate strategy might be to do MOVE NODEDATA for your most critical clients, and leave the less important ones alone. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: Tuesday, January 03, 2006 4:46 PM To: ADSM-L@VM.MARIST.EDU Subject: Collocation Questions I am doing server recovery exercises at all of our sites that have TSM servers (TSM 5.3.2.0 on W2K3). Part of the recovery process is to recall back tapes in our copy storage pools that belong to the node that is being recovered. One of the things I have noticed is that we are not using collocation at our sites, and because of this, I am having to call back a large amount of tapes for just one node. If I turn on collocation on the copy storage pools, will this decrease the number of tapes that are used per node? Do I have to do a move nodedata command after turning collocation on for collocation to work? The reason why I don't want to turn collocation on the primary storage pools is space (we have a small library at most of the sites) and so I just want the copy storage pools to be collocated. Will this work, without having the primary storage pools collocated as well? Mel Dennis