Re: volumes in a collocation group?
I believe Paul meant to say: Nodes not assigned to a specific collocation group are treated as if *each* is in *its* own private collocation group (i.e., collocation by node.) -- jim.o...@yale.edu Paul Zarnowski wrote: Nodes not assigned to a specific collocation group are treated as if they were in their own private collocation group. At 12:15 AM 3/15/2009, Larry Clark wrote: Paul, A question occurred to me.. If you have a subset of nodes defined to collocation groups, but a number of nodes not defined to collocation groups, will TSM attempt to avoid putting files not in a collocation group on volumes that have collocation groups nodes...as distinct from your explanation of filling volumes for collocations group members? Larry Clark
Re: volumes in a collocation group?
On Mar 14, 2009, at 10:23 PM, Larry Clark wrote: What you say is curious..only nodes that are in a collocation group should have data on the volumes in that collocation group. At least that is my understanding. Your saying more than one collocation group can store data on the same volume? I know for collocation by node that would not be true Paul already mentioned the scenario in which TSM has to put a a collocation group member's data on a tape that has data from another group on it, due to resource constraints. You can get similar results if a node's collocation group membership changes from one group to another. In that case, data stays where it is, meaning the tapes now contain data from two groups on them, even though TSM behaved exactly as predicted. I keep wondering if there's a way to mix groups' data on a volume using MOVE DATA or MOVE NODEDATA, but since neither lets you specify a target more exactly than a storage group, I haven't seen how yet. Larry Clark Nick
Re: volumes in a collocation group?stg
Hi, All. The critical piece that Larry mentioned is that he's interested in a copypool. If your primary pool is collocated by anything, but your copypool is not collocated at all, then your copypool data will be mixed up with no regard for collocation groups. Nick, if you really want to mix data on tapes (I have no idea why you would want to, but the beautiful thing about TSM is you can do nearly anything you want), the first way I can think of is to temporarily reduce MAXSCRATCH (or temporarily disable collocation), set to Unavailable the volumes you do _not_ wish to write to, then issue move [node]data. Alex Alex Paschal Storage Solutions Engineer MSI Systems Integrators Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Sunday, March 15, 2009 5:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] volumes in a collocation group? On Mar 14, 2009, at 10:23 PM, Larry Clark wrote: What you say is curious..only nodes that are in a collocation group should have data on the volumes in that collocation group. At least that is my understanding. Your saying more than one collocation group can store data on the same volume? I know for collocation by node that would not be true Paul already mentioned the scenario in which TSM has to put a a collocation group member's data on a tape that has data from another group on it, due to resource constraints. You can get similar results if a node's collocation group membership changes from one group to another. In that case, data stays where it is, meaning the tapes now contain data from two groups on them, even though TSM behaved exactly as predicted. I keep wondering if there's a way to mix groups' data on a volume using MOVE DATA or MOVE NODEDATA, but since neither lets you specify a target more exactly than a storage group, I haven't seen how yet. Larry Clark Nick This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: volumes in a collocation group?stg
Hi Alex, Yes, this is related to improving restore times in a DR senario...so these are offsitevols from a copypool. Larry Clark (518) 712-5138 Home Office - Original Message - From: Alex Paschal apasc...@msiinet.com To: ADSM-L@VM.MARIST.EDU Sent: Sunday, March 15, 2009 2:37 PM Subject: Re: [ADSM-L] volumes in a collocation group?stg Hi, All. The critical piece that Larry mentioned is that he's interested in a copypool. If your primary pool is collocated by anything, but your copypool is not collocated at all, then your copypool data will be mixed up with no regard for collocation groups. Nick, if you really want to mix data on tapes (I have no idea why you would want to, but the beautiful thing about TSM is you can do nearly anything you want), the first way I can think of is to temporarily reduce MAXSCRATCH (or temporarily disable collocation), set to Unavailable the volumes you do _not_ wish to write to, then issue move [node]data. Alex Alex Paschal Storage Solutions Engineer MSI Systems Integrators Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Sunday, March 15, 2009 5:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] volumes in a collocation group? On Mar 14, 2009, at 10:23 PM, Larry Clark wrote: What you say is curious..only nodes that are in a collocation group should have data on the volumes in that collocation group. At least that is my understanding. Your saying more than one collocation group can store data on the same volume? I know for collocation by node that would not be true Paul already mentioned the scenario in which TSM has to put a a collocation group member's data on a tape that has data from another group on it, due to resource constraints. You can get similar results if a node's collocation group membership changes from one group to another. In that case, data stays where it is, meaning the tapes now contain data from two groups on them, even though TSM behaved exactly as predicted. I keep wondering if there's a way to mix groups' data on a volume using MOVE DATA or MOVE NODEDATA, but since neither lets you specify a target more exactly than a storage group, I haven't seen how yet. Larry Clark Nick This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: volumes in a collocation group?stg
On Mar 15, 2009, at 1:37 PM, Alex Paschal wrote: Nick, if you really want to mix data on tapes (I have no idea why you would want to, but the beautiful thing about TSM is you can do nearly anything you want), the first way I can think of is to temporarily reduce MAXSCRATCH (or temporarily disable collocation), set to Unavailable the volumes you do _not_ wish to write to, then issue move [node]data. Gee, and I was just trying to warn Larry not to be too sure about collocation groups never sharing tapes. Kids these days Alex Nick
Sap r/3
zone some drives to the SAP/R3 server, install tsm. Make it a libclient of the libmgr if you have one. that's what I see big pharma do. +-- |This was sent by a579...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
