cancel
Showing results for 
Search instead for 
Did you mean: 

2 storage units pointing to the same robot

RichardXClark
Level 4

Setup
****
Netbackup 6.0 MP4 on AIX 5.3

1 x Robot - IBM3494
10 drives - IBM3592
Drive speed native 104MB/s
Allow Multiplexing = 4

***

I have 2 storage units pointing to the same robot.
This is just legacy, inherited, both storage units are configured the same.

When all drives are spinning, but not flat out, some queued jobs are waiting for storage unit 1.
I know that there is spare capacity, with multiplexing I can get 40 jobs at the same time.
If I kill a job waiting for storage unit 1 and start it manually, it is able to use a multiplex slot on storage unit 2.

I was thinking of collpsing these 2 storage units into 1, hoping to reduce the wait times.
I figured that storage unit 2 would need storage unit 2 to be finished with a drive before it could be re-allocated.

True?

Are there any other know issues with how we have it?

Does collapsing into 1 storage unit sound like a good idea?

Soon, I intend to change development & non business critical servers to a higher multiplexing factor.
I have a Priority1, P2, P3 list that the business has given me.
I will also change priorities and naming conventions.

With such high speed drives & many wintel servers that write at 5 - 10 MB/s, I figured I would need to multiplex quite high to reduce shoe shine.

I had in mind...

P1 = MPX 4
P2 = MPX 8
P3 = MPX 12

I figured i would go for 1 storage unit with MPX12, then setting MPX4, 8 or 12 at the policy level.

Does this sound like a good approach?
Or would 3 storage units be better?


thx
Rich
 

7 REPLIES 7

FrSchind
Level 5
Partner
do it with 1 storage unit, the way you intend to configure mpx is fine. more than 1 storage unit for 1 robot is only necessary when you have multiple media servers or media types in this robot.

RichardXClark
Level 4
Thx Frerk,

I'll set the unneeded storage unit as 'on demand only', pending deletion in the near future.

For policies that are set to use 'any available' unit no changes are needed.

For policies that specify the unneeded unit, I will change to 'any available'.

However, when I have multiple copies enabled, the 'any available' drop down is missing.

Any idea why it is missing? Just a mistake by Veritas?

Since I have lots like this, I may need a scripting solution.

In the meantime, the 'on-demand only' will buy me the time to figure this out.


thx
Rich

RichardXClark
Level 4
Update...

Missing from Fat client only
Java Client is fine!

FrSchind
Level 5
Partner
to change the storage unit in a script you can use these commands:

bppllist  - lists all the policies
bpplinfo - to change the storage unit of the policy (use -modify, or all other attributes of your policy will be set to the default!)
bpplschedrep - to change the storage unit(s) of a schedule.

look at the -h output to get the correct syntax.

RichardXClark
Level 4
thx :)

quebek
Moderator
Moderator
   VIP    Certified
Keep in mind that having MPX factor on 12 will slow down restore process a lot!!

RichardXClark
Level 4
Yes, I know, this is why i have asked for Priority 1 2 & 3 categories for our servers
P3 (MPX 12) are mainly development servers which rarely require a restore & have no set SLA on recovery.