ADSM-L

Re: Co-location

2002-10-23 01:07:55
Subject: Re: Co-location
From: Chris Gibes <gibes AT BERBEE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 23 Oct 2002 00:06:35 -0500
Matt,

You are absolutely correct.  Co-location is by storage pool, not by
management class.  So yes, you would need to carve your disk up into
multiple storage pools to selectively use co-location, or you could set
up a tape pool that was co-located and go directly to tapes but
<caution!> you would need to have enough drives to accomplish this.  I
would also add the old, "disk is so cheap," but my guess is that it's
not viable to add more disk (or you're on one of those platforms where
disk is not "cheap"...)

I guess one thing to consider is that while you may be carving your disk
up into smaller pools, the total amount of disk and the total amount
being backed up are going to be the same regardless of how many pools
you have, so carving one big pool up, shouldn't be that big of an issue,
as long as you put some planning into the size of the disk pools.

Chris Gibes
Tivoli Certified Consultant
IBM Certified System Administrator
gibes AT berbee DOT com



We'd really like to avoid carving up our disk space into more smaller
pools.  But, as far as I can tell, that's the only way to use
colocation selectively.  Am I missing something, or is that the way
it works?
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge
obsolete
profits for their obsolete shareholders.  And this year's run twice as
fast
as last year's.

<Prev in Thread] Current Thread [Next in Thread>