Right - drives of similar density will have to share a storage unit.  You'd
have to define some drives, artificially, as  a different density, like
hcart & hcart2.

You can then use a storage group to prioritize the selection of a storage
unit.  If you local drive unit is unavailable/full, then it'll roll to the
shared unit.

Unfortunately, the media in your library can only be hcart or hcart2 -
there's no overlap.  You'll have an artificial distinction made in your
library.  When you create your tapes, it'll have to be defined as one of the
two media types and it'll only be use for that storage unit and none other.

Doable - but a management headache.

Another thing you can do is define multiple storage units that have a lower
drive count than your total drive count.  Say you've got 8 drives and two
servers.  Create two STU's with a drive count of six each.  If you tell your
host1 to use STU1 and host2 to use STU2 then each host is guaranteed the use
of at least two drives.  They can fight for the other four.

Your media is all the same type and no media type split is necessary.

-M

-----Original Message-----
From: Douglas Ritschel [mailto:dritschel62 AT yahoo DOT com]
Sent: Monday, March 08, 2004 4:37 PM
To: Michael Miller; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Dedicated and SSO drives on same SAN media
server


If the dedicated and SSO drives were in different
Storage Units, you could use Storage Groups to control
which one is selected. NetBackup will select the
Storage Unit that is listed first and if it is down
select the next in the list. 

To put the SSO drive in a seperate Storage Unit, I
beleive that the density would have to be different
for the SSO drive (say hcart3) than for the dedicated
drive, (say hcart2).  

--- Michael Miller <mmlist AT mjmm DOT org> wrote:
> Hi,
> 
> I am looking after an enviroment where we have a
> number of STK FC drives
> in a silo connected to a SAN.  What we are trying to
> do is have a couple
> of "dedicated" FC drives on each media server and
> then have a couple of
> SSO drives shared between the media servers. So
> something like:
> 
> STK_Drive1 -> configured on Media_Server1
> STK_Drive2 -> configured on Media_Server2
> STK_Drive3 -> configured on Media_Server3
> STK_Drive4 -> configured on Media_Server3 (two
> drives on server3)
> 
> STK_Drive5 -> configured as SSO on all media
> servers.
> 
> This is all great and groovy.  However, what we are
> seeing, is that
> sometimes the media servers pick the SSO drive
> before picking their
> dedicated drive.  Basically we are trying to ensure
> that each media server
> can backup its data. If for some reason it downs its
> own drive there is
> still the SSO drive available.
> 
> Each Media server has a storage unit configured with
> a maximum of 1
> concurrent drives and policies direct backups to a
> particular media
> server.
> 
> So, is there a configuration option available to
> tell netback to always
> use the non-SSO drive unless the dedicated drive is
> unavailable?
> 
> Or is our best way forward to use SSO for ALL the
> drives and let them
> float around- the probelm we would face with that
> though is the IPC
> message size limit, requiring changes to
> /etc/system- these are Solaris
> media servers.  On this note, is anyone using the
> larger IPC message sizes
> for setups with more than 16 SSO drives confgured?
> 
> thanks for any hints and tips about this.
> 
> Thanks
> Mike
> 
> _______________________________________________
> Veritas-bu maillist  - 
> Veritas-bu AT mailman.eng.auburn DOT edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you're looking for faster
http://search.yahoo.com
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu