Is this definitely correct? I was under the impression that it would
join the storage unit unless there were already 4 streams from that
schedule already, i.e. that it would mpx higher than the schedule limit
so long as it was with streams from other policies.
I guess I should test this all out again, I have to admit that I did
test it once until I understood it but it's got muddled in my mind again
:-(
> i.e. a schedule with an mpx setting of 4 will not join a storage unit
> with Max Drives = 1 and Max MPX = 10 that's got 5 streams running,
even
> though the storage unit can take 5 more streams.
cheers, Phil
Phil Weber MBCS CITP
Storage Technical Services - Senior UNIX Technologist
Business Technology
Phone: 01384 26 4136
Egg Banking plc
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Tharp,
Trey
Sent: 29 April 2008 04:46
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Storage unit groups are not understood -
yesI'mpuzzeld
What's the multiplexing # set to on the schedule? Also, "Allow multiple
data streams" is checked on the policies, right?
You can have an unlimited number of policies using a storage unit group
as far as I know. We've got well over 100 policies using a storage unit
group with 2-4 storage units in it and we run over 1000 active jobs to
this storage units.
There are many enablers and limits for multiplexing and multistreaming
that all have to be turned on and turned up for it to work. The lowest
denominator is on the schedule itself, so if a new stream starts, it
will not join a mpx group that's got more jobs active than what it's set
to.
i.e. a schedule with an mpx setting of 4 will not join a storage unit
with Max Drives = 1 and Max MPX = 10 that's got 5 streams running, even
though the storage unit can take 5 more streams.
-Trey
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of fred
fred
Sent: Saturday, April 26, 2008 4:22 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Storage unit groups are not understood - yes
I'mpuzzeld
In the relms of the Top 20 (or so) misunderstood ....specifically #2.
Storage unit groups are not understood. (version = 6.5.1)
I'm still puzzled..... If you have policies pointing to the same storage
group with two policies running with the a couple of streams each. Then
a third starts it ends up by queueing. The only difference being its
not NT Windows but a Standard Unix policy.
Rentetion time and media pool the same.
Can only a limited number of Policies actually use the storage group at
any one time, even if the retention time and tape pool the same?
Does the same apply for storage units?
If you have a stroage unit like below I would expect you could have two
policies writng to it at the same time (with no queueing ) as long as
there less than a total of 10 streams. Policies with media multiplexing
of 10 and same retention and pool.
Storage Unit:
Multiplexing enabled
Maximum concurrent write drives: 1
Maximum streams per drive: 10
I have set it to one as I don't what to multistream to more that two
tapes drives in the storage unit group.
Storage Unit Group (set to "balance load" ) has two storage units of the
above i.e a max of 20 streams i.e it will do twice the work load
of my example I'm assuming each stream is a "job". In the manuals
what is a "job" seems to change with context.
Max client streams = 24 (for slow backups of small servers)
Am I missing anything?
Cheers Fred
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
-----------------------------------------
Egg is a trading name of the Egg group of companies which includes:
Egg Financial Intermediation Ltd (reg no 3828289) and Egg Banking
plc (reg no 2999842). Egg Banking plc and Egg Financial
Intermediation Ltd are authorised and regulated by the Financial
Services Authority (FSA) and are entered in the FSA register under
numbers 205621 and 309551 respectively. These members of the Egg
group are registered in England and Wales. Registered office:
Citigroup Centre, Canada Square, London E14 5LB.
This e-mail is confidential and for use by the addressee only. If
you are not the intended recipient of this e-mail and have received
it in error, please return the message to the sender by replying to
it and then delete it from your mailbox. Internet e-mails are not
necessarily secure. The Egg group of companies do not accept
responsibility for changes made to this message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission
of viruses, it is the responsibility of the recipient to ensure
that the onward transmission, opening or use of this message and
any attachments will not adversely affect its systems or data. No
responsibility is accepted by the Egg group of companies in this
regard and the recipient should carry out such virus and other
checks as it considers appropriate.
This communication does not create or modify any contract.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
