on Collocation
Content preview: Hi Jennifer, While there is a COLLOCGROUP option to MOVE
NODEDATA,
it sounds like you just want to move one node's data. Any kind of data
movement
operation will try to respect the collocation setting you provide at the
node level, assuming you have
Thanks Marc! Very helpful!!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Marc
Lanteigne
Sent: Thursday, November 09, 2017 8:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Question on Collocation
Hi Jennifer,
> I removed the n
Content preview: Hi Jennifer, While there is a COLLOCGROUP option to MOVE
NODEDATA,
it sounds like you just want to move one node's data. Any kind of data
movement
operation will try to respect the collocation setting you provide at the
node level, assuming you have the storage pool
Hi Jennifer,
> I removed the node from the collocation group and added it to the new
collocation group
The way you did it, or just not part of a group gives the same result. So
your way was good, I wasn't trying to say it wasn't, just that you could
have saved a few steps and get the same
Marc,
I removed the node from the collocation group and added it to the new
collocation group - where it resides by itself. Will the move nodedata command
move the data from the tapes in the old collocation group to tapes in the new
collocation group? Also, do you know how to initiate
PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Question on Collocation
>
> Hi Jennifer,
>
> Do you have client-side compression enabled? I'm not familiar with what the
> GUI reports, but dsmc will show this in the "Objects compressed by"
> line.
>
> On 1
] Question on Collocation
Hi Jennifer,
Do you have client-side compression enabled? I'm not familiar with what the GUI
reports, but dsmc will show this in the "Objects compressed by"
line.
On 11/03/2017 02:06 PM, Drammeh, Jennifer C wrote:
> I use collocation and I have a node whe
Hi Jennifer,
The backup always only applies to the filesystem backup, not systemstate.
You’ll have to change the mode of the systemstate backup to get a full.
Or use move nodedata to move it all together.
BTW, you would just have needed to remove the node from the collocation group.
Nodes
Hi Jennifer,
Do you have client-side compression enabled? I'm not familiar with what
the GUI reports, but dsmc will show this in the "Objects compressed by"
line.
On 11/03/2017 02:06 PM, Drammeh, Jennifer C wrote:
> I use collocation and I have a node where the System Admin
I use collocation and I have a node where the System Admin has requested that
his data from a particular node be isolated on tapes by itself. I created a
collocation group and have associated this one node with the new group. This
node had previously been backing up to a different collocation
as 6 times during a single migration, something is not right. Not
only is this rather slow, but it is wearing out the tapes.
Group collocation is set for both the DEVTYPE=FILE disk stgpool, and the
next one in the heirarchy which is tape. The collocation groups are
sensibly-sized - total size of each
requirement of your
infrastructure to maintain scratch availability, and do new acquisitions
when scratch levels fall below foo.
Frankly, I like that TSM will override collocation preferences when
its at MAXSCR for volumes in a pool.
Me too.
I have a script, which I think I've bandied about here
it was implemented.
I view collocation as a tool to Keep data from a given node in physical
proximity, to reduce mount latency at restore time. Any of you who have
attempted to service restores from a large pool of uncollocated data
(raises hand) would see this as the primary purpose of the tool
Hi Grant,
I used to track collocation group spill overs when my servers were version 5
and used tapes. Now I am on v6 and almost all disk, so I don't do that anymore.
Anyway, I used a mysql database on my desktop system. I would dump data from
the tsm servers and load it into mysql where I
vu.node_name=nd.node_name -
group by vu.stgpool_name, vu.volume_name -
order by Groups desc, Nodes desc, FSpaces desc
We assign all nodes to collocation groups, even if it is only one node.
Good luck.
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU
Hello
We use collocation to segment data into collocation groups and nodes,
but recently found that collocation is on a best efforts basis and
will use any tape if there is not enough space.
I understand the theory behind this but it does not help with compliance
requirements. I know that we
If you absolutely need for nodes to be isolated on their own media, why aren't
they in their own individual domains which point to their own storage pools,
all of which might share a library?
Frankly, I like that TSM will override collocation preferences when its at
MAXSCR for volumes
log that it has had to resort to non collocation.
Does that make sense?
I will need to look at the implications of splitting it out based on
domains, thanks for the heads up.
Grant
On 17/04/13 10:15, Nick Laflamme wrote:
If you absolutely need for nodes to be isolated on their own media, why
belongs.
Report those volumes as candidates for move nodedata.
Richard
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grant
Street
Sent: Tuesday, April 16, 2013 7:40 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Collocation anomaly report
Hello
pool backups with 'maxproc=4', but occasionally use 'maxproc=5'.
Backup storage pool operations do not seem to be following the documented
rules for collocation. The server currently has 7 collocation groups.
Yesterday morning, the copy pool had 25 volumes in filling status, with
one collocation
I have observed that for primary storage pools where the tape volumes have been
DEFINEd to belong to that pool, MOVE DATA to consolidate tapes belonging to the
same collocation group has unexpected results. The database reliably selects
the volume copied FROM as the primary candidate
.
You cannot dedup on DISK stgpools.
DISK implies random access disk - e.g., devclass DISK.
FILE implies serial access disk - e.g., devclass FILE.
But I think there is still an open question about collocation and
deduplication. Deduplication must be done using FILE stgpools, but FILE
stgpools CAN
Deschner
Sent: Wednesday, June 22, 2011 9:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
Back to client side dedupe, which we're about to deploy for a branch
campus 90 miles away in Rockford IL.
The data is sent from the clients in Rockford via tin cans
@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
Back to client side dedupe, which we're about to deploy for a branch
campus 90 miles away in Rockford IL.
The data is sent from the clients in Rockford via tin cans and string to
the TSM server in Chicago already dedpued. We're using
Zarnowski
Sent: Wednesday, June 22, 2011 7:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
This is my understanding as well. I'm almost certain this is the case, though
we have not yet used source dedup.
..Paul
On Jun 22, 2011, at 3:34 AM, Grigori Solonovitch
FILE.
But I think there is still an open question about collocation and
deduplication. Deduplication must be done using FILE stgpools, but FILE
stgpools CAN use collocation. I don't know what happens in this case.
..Paul
At 02:38 PM 6/21/2011, Prather, Wanda wrote:
If it is a file device class
Hello,
I had a student ask me today What happens if you have collocation turned on
for a storage pool that you are deduplicating? I did not know what to answer
because in my mind I thought well, if the data is collocated then I need to
have a copy of that data on that client's tape, otherwise
Tape pools are not de-duped, so that is not a consideration.
On Tue, Jun 21, 2011 at 13:17, Mark Mooney mmoo...@aisconsulting.net wrote:
Hello,
I had a student ask me today What happens if you have collocation turned on
for a storage pool that you are deduplicating? I did not know what
] Deduplication and Collocation
Hello,
I had a student ask me today What happens if you have collocation
turned on for a storage pool that you are deduplicating? I did not
know what to answer because in my mind I thought well, if the data is
collocated then I need to have a copy of that data on that client's
: Tuesday, June 21, 2011 8:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deduplication and Collocation
Tape pools are not de-duped, so that is not a consideration.
On Tue, Jun 21, 2011 at 13:17, Mark Mooney mmoo...@aisconsulting.net wrote:
Hello,
I had a student ask me today What happens if you have
Dedup only works in TSM storage pools that reside on disk (specifically
devtype=FILE pools).
If you have data that goes to a dedup pool, then gets migrated off to tape, it
is reduped (rehydrated, reinflated, whatever you want to call it.)
So collocation will still be in effect for that pool
If it is a file device class with dedup turned off, yes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark
Mooney
Sent: Tuesday, June 21, 2011 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
So data
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, June 21, 2011 12:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
Dedup only works in TSM storage pools that reside on disk (specifically
, then gets migrated off to tape, it
is reduped (rehydrated, reinflated, whatever you want to call it.)
So collocation will still be in effect for that pool.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark
Mooney
Sent: Tuesday, June 21, 2011
@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deduplication and Collocation
Cool, Thanks :) I have questions about client dedup. Do you know of any
redbook detail on that?
Thanks,
Mooney
Prather, Wanda wprat...@icfi.com wrote:
Dedup only works in TSM storage pools that reside on disk (specifically
- e.g., devclass FILE.
But I think there is still an open question about collocation and
deduplication. Deduplication must be done using FILE stgpools, but FILE
stgpools CAN use collocation. I don't know what happens in this case.
..Paul
At 02:38 PM 6/21/2011, Prather, Wanda wrote
Thank you Wanda! Much Appreciated!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, June 21, 2011 9:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deduplication and Collocation
https://www-304.ibm.com/support
of that will increase my h/w costs or administration time?
If you are planning for collocation by filespace for a copy storage
pool with volumes shipped to an offsite vault, your are correct
about the 30+ scratch tapes per night. In addition, I think your
offsite reclamation processing will end up moving far
Does anyone have an real world example of moving from a single storage
pool to collation by filespace?
TSM 5.5, AIX 5.3
I'm backing up a 200TB server (solaris) with 1TB of new/changed files
per day. There are about 30 volumes (filespaces) and I am thinking of
changing to collation to improve
Hi Bill,
Migration and backup stgpools shall take some extra time as there are more
volumes te mount/dismount.
If you have to migrate small amounts during backupperiod because you don't
have enough diskpool, the backup period could be much much longer.
If you define the collocation groups, don't
In a collocated world, the number of concurrent operations you can run
are limited by the number of tape drives you have.
Evans, Bill bev...@fhcrc.org 11/12/2010 12:26 PM
Does anyone have an real world example of moving from a single storage
pool to collation by filespace?
TSM 5.5, AIX 5.3
I'm weeding my collocgroups, and I decided my management script is
getting smooth enough that I'd consider exposing it for you-all to
take and beat upon if you desire. Throw tomatoes, kibitz, fix my
bustedness, whatever. :)
http://nersp.osg.ufl.edu/~asr/media/cg/
In there are:
the script
Hi,
I have some Collocation Group in my TSM and I need know
how many tapes I have on each Collocation Group.
Does anyone has this select?
thanks
---
Anderson
You might look at the q nodedata command, as you can define the collocation
group as an option
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Anderson Douglas da Silva
Sent: Thursday, March 18, 2010 11:14 AM
To: ADSM-L@VM.MARIST.EDU
[mailto:ads...@vm.marist.edu] On Behalf Of
Wolfgang J Moeller
Sent: Monday, March 15, 2010 6:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Collocation Groups Reclamation and Restore
Fred Johanson writes:
Once a tape has been mounted for a collocation group's data,
all nodes in that group
--
Warm regards,
Michael Green
On Tue, Mar 9, 2010 at 9:01 PM, Francisco Molero fmol...@yahoo.com wrote:
2.- When TSM restores files from these tapes. Does it restore all files in
a sequential way ?. I mean TSM is reading the tape from the beginning and if
it finds files to belong to this
, 2010 00:07
Asunto: Re: Collocation Groups Reclamation and Restore
Fred Johanson writes:
Once a tape has been mounted for a collocation group's data,
all nodes in that group are migrated.
At least when the source pool is of type DISK, I'd guess
that files will still be ordered by filespace
Fred Johanson writes:
Once a tape has been mounted for a collocation group's data,
all nodes in that group are migrated.
At least when the source pool is of type DISK, I'd guess
that files will still be ordered by filespace and node,
just like they are by filespace in the case
Francisco Molero writes:
[...] I have some questions about Collocation Groups Reclamation and restore.
First, my environment I have a Tape STGpool with 3 Collocation Groups and 10
nodes per Group.
1.- When one volume is reclaimed in this pool. How TSM does the reclamation?
moving files
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Wolfgang J Moeller
Sent: Friday, March 12, 2010 8:51 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Collocation Groups Reclamation and Restore
Francisco Molero writes:
[...] I have some
Hi TSMers,
I have some questions about Collocation Groups Reclamation and restore.
First, my environment I have a Tape STGpool with 3 Collocation Groups and 10
nodes per Group.
1.- When one volume is reclaimed in this pool. How TSM does the reclamation?
moving files from one node from
Indeed you are correct. Though isn't that collocation going to go out of
the window on the 2nd days migrations? The daily chunks of data will be
together, but all node data would be on the same tape until it gets
filled.
I cannot agree more on you last sentence! :)
Steven
Steven Langdale
We are using an IBM3584 and don't use any kind of collocation. We have found
the migration process from diskpool to tape collocates data by node and
therefore already does a decent job of grouping node data together.
The only time you may see better performance with collocation
In that case you must be using collocation (albeit by accident).
You may want to look at group collocation as it sounds like your tapes are
probably underutilised. Unless that is you have manly fewer, bigger
clients.
Steven Langdale
Global Information Services
EAME SAN/Storage Planning
On Dec 17, 2009, at 5:31 PM, Steven Langdale wrote:
In that case you must be using collocation (albeit by accident).
Not really... Remember that, within Migpr, migration operates
serially by node, and thus you get a certain amount of same-node data
clumped together on sequential media
Depending on how you set up your collocation (File Systems, Server or Server
Group). If you chose collocation by file system then you would mount a tape
for each file sys, if you set by server then a mount per server etc ...
Hope that helps
Gardenia?
Collocation directs TSM to store the data for a particular group of
nodes, node, or filespace on as few volumes as possible. As Medhi
Salehi noted, it keeps tape mounts to a minimum for restores, but it
opens many more tapes.
In primary pools if you collocate by Node, each Client
I am not sure if collocating a copy pool is beneficial. It seems like the
copy pool as a disaster recovery pool would be ideal to collocate, but
if you send off tapes every day you end up with a fragmented set of
tapes for each collocation unit anyway. To clean that up would require
bringing
, then it would make more sense, but our
average is about 40% utilized. We are required to send off tapes every
workday. Many tapes are so underutilized that they reclaim in a day or
two.)
Collocation does reduce tape contention between nodes and overall tape
mounts during a disaster. If TSM is your only
Hi,
I find by applying collocation concept, the no.of tape mount increases while
taking backup...
Could anyone justify it or explain me why it is so?
+--
|This was sent by subhashinipanchaksha...@gmail.com via Backup Central
The benefit of collocation is in restore time, because tape mounts will be
reduces for restoring each client. If there are not enough tape drives
defined in TSM server, more tape mount during backup is natural.
Does anyone have a script that will show the volumes associated with a
collocation group?
I'm trying to run this but receive an error;
select distinct vu.volume_name, cg.collocgroup_name from volumeusage vu,
collocgroup cg where vu.node_name=cg.node_name and vu.stgpool_name='DRMC'
group
Does anyone have a script that will show the volumes associated with a
collocation group?
select distinct vv.volume_name from nodes nn, volumeusage vv -
where nn.collocgroup_name=upper('$1') and vv.node_name=nn.node_name
You DON'T want to use the collocgroup table.
Wolfgang J
I do it this way.
select distinct COLLOCGROUP_NAME,VOLUME_NAME from COLLOCGROUP,VOLUMEUSAGE
where STGPOOL_NAME='LOCALTAPE' and COLLOCGROUP.NODE_NAME=VOLUMEUSAGE.NODE_NAME
group by COLLOCGROUP_NAME,VOLUME_NAME
To generate a list of volumes by collocation group.
I actually combine
12:30:01
tsm: BKMEmove nodedata collocggroup=LPAR07_GROUP from=daily_2
ANR4877E MOVE NODEDATA: Collocation group LPAR07_GROUP is not defined.
ANS8001I Return code 11.
tsm: BKME
Could somebody
Grigori:
LPAR07_GROUP is not a collocggroup. It is a nodegroup.
To view the Collocation group, run q COLLOCGROUP
On Wed, Aug 26, 2009 at 6:51 AM, Grigori Solonovitch g.solonovi...@bkme.com
wrote:
Dear TSMAdmins,
I have faced next problem in TSM Server 5.5.3 under AIX 5.3:
tsm
consider the environment before printing this Email
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of TSM
User
Sent: Wednesday, August 26, 2009 1:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Collocation node group question
Grigori
, 2009 11:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 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
15, 2009 11:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 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
Of Larry
Clark
Sent: sábado, 14 de Março de 2009 22:13
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] volumes in a collocation group?
Hi,
Would someone have a query that returns all the volumes in a particular
collocation group (within a copypool)?
-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] volumes in a collocation group?
Hi Larry,
I thing that my TSM Server do not have this DB record (version 5.2) , but I
will try to help you or give you some ideas.
Try sommething similarlike this:
select volume_name from volumeusage where stgpool_name
, 2009 12:34 PM
Subject: Re: [ADSM-L] volumes in a collocation group?
Q noded col=name-of-collocpool stg=name-of-stgpool
Fred Johanson
TSM Administrator
University of Chicago
773-702-8464
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
: [ADSM-L] volumes in a collocation group?
Thanks Fred. That was mentioned previously, but it does not show if other
servers not in the colloc group are stored on those volumes.
Larry Clark
(518) 712-5138 Home Office
- Original Message -
From: Fred Johanson f...@uchicago.edu
To: ADSM-L
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
collocation, which is not cheating but using the features of TSM to
address
volume contention and wait times on mounts. A mechanical mount that takes 3
minutes is a lot of time if your data is spread across 30 volumes versus 10:
20 x 3 x #number of servers.
Larry Clark
- Original Message -
From
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] volumes in a collocation group?stg
Yes, the underlying problem is they are not collocated and they have
experienced delays because of:
- multiple platforms requesting the same volumes concurrently
- multiple servers on the same platform requesting
That's what collocation does.
Without collocation when migrating the data from primary storage to storage
pools TSM will just right to the current tape, fill it up, mount another.
With collocation it writes to tapes in the collocation group (if space is
available), or mounts a scratch tape
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
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
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
: 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
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
Hi,
Would someone have a query that returns all the volumes in a particular
collocation group (within a copypool)?
On Mar 14, 2009, at 5:13 PM, Larry Clark wrote:
Hi,
Would someone have a query that returns all the volumes in a
particular
collocation group (within a copypool)?
QUERY NODEDATA COLLOCG=grpname STG=stgname
I suspect your mental model of how collocation works is a bit tangled,
because other
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
From looking at the command I think
q nodedata collocg=collocation group name
would return all the members and volumes in a collocation group.
Larry Clark
(518) 712-5138 Home Office
- Original Message -
From: Nick Laflamme dplafla...@gmail.com
To: ADSM-L@VM.MARIST.EDU
Sent: Saturday
Larry,
This would only be true if you had sufficient tapes so that each
collocation group always has a tape in empty or filling status. Otherwise,
TSM will start doubling up and putting more than one collocation group on a
tape volume.
When TSM is writing data to a collocated storage pool
Thanks Paul. When I collocated by node I never saw any shared, so perhaps we
either had sufficient tapes or those rules didn't apply to collocation by
node. It would make sense if there were no empty tapes available there would
be some way of satisfying the backup/migration requirement.
Larry
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
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
:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: karel@atosorigin.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lepre,
James
Sent: maandag 19 januari 2009 20:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Collocation
Hello
Hello Everyone
I have a question regarding collocation
I have a VTL and would like to start using collocation for various
reasons. My question is and I cant remember the answer what is it. If
I collocate the pool and start a backup each node will get their own
tape, however
Don't forget collocation by group.
All of our nodes belong to one group or another and we can then be pretty
sure that collocation will do what we need. Mostly, our tape pools are
collocated by group. Some nodes are in a group all by themselves and some
(e.g. workstations) have many nodes
Levad
Sent: Friday, January 16, 2009 7:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to figure collocation overhead
Don't forget collocation by group.
All of our nodes belong to one group or another and we can then be
pretty
sure that collocation will do what we need. Mostly, our tape
Is there a guide or rule of thumb for determining what collocation will
do to library space? It is being considered for improving restore
speeds.
I'm backing up 80TB in 30 volumes(filespaces) on a solaris server.
Currently there is no collocation set, all data goes to a long-term
management
You can easily determine how many lines of tapes you will initially
break out into, based upon which of the multiple types of collocation
you ultimately decide upon and how many nodes or filespaces are
active, sending data to TSM storage. I would double that number to
account for tape leak
Collocation consumes as much of the library as you tell it to.
When you set MAXSCRATCH on a storage pool, TSM will confine the pool to that
number of tapes. If you have less tapes available than you have clients,
you get a do the best you can collocation.
There are plenty of sites who have more
.
On Thu, Jan 15, 2009 at 11:53 AM, Wanda Prather wanda.prat...@jasi.comwrote:
Collocation consumes as much of the library as you tell it to.
When you set MAXSCRATCH on a storage pool, TSM will confine the pool to
that
number of tapes. If you have less tapes available than you have clients
Hi Farren ,
you can have it all. If you set the stg to group-collocation and
want a group or even a single node to be collocated then you set
up the collocation groups with the number of members as needed.
We only use group-collocation and if a single node should be collocated then
we just define
Hi Farren,
As per the Admin Guide Configuring and Managing Server Storage Chapter
10 Keeping a Client's Files Together Planning for and Enabling
Collocation, located here:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmcw.doc/anrwgd55330.htm#colplan
you are correct
1 - 100 of 291 matches
Mail list logo
