I'm really new into silo configuration, so any info would help me, and sorry about anything stupid I might say.
If I use jbconfig on the second storage node, I'm going to configure a second jukebox in my datazone, am I right? We did that, but of course it was created without any slots, and we should add them using NMC, but we didn't know if it would add the same slots used by the first storage node. In other words, they would share the same slots?
There is thread on this subject (element address and jbedit so just check it via search... you will need to use sji commands for that if I remember correctly). Not sure about jbedit and silo (as in the past jbedit didn't support silo - it might have changed since 7.3.x - I know it was planned), but I usually use jbconfig for silo.
In this case, we would need a second license for jukebox, but EMC people told me that the license we have, "Silo, Unlimited Slots", should be enough to configure all storage nodes we would use....
If I use jbconfig on the second storage node, I'm going to configure a second jukebox in my datazone, am I right?
Correct.
We did that, but of course it was created without any slots, and we should add them using NMC, but we didn't know if it would add the same slots used by the first storage node. In other words, they would share the same slots?
No, with silo is a bit different. You must allocate slots via nsrjb command. The number of volumes you allocate the number of slots you get.
For example, let's say in ACSLS silo that you have 500 slots. Now, for first jukebox you have 100 slots and for second 400. You run nsrjb -a -T .. command for those slots (actually volumes as silo works with volumes and not slots!) and there you go. Check nsrjb command for examples (same rule applies to silos and AS libraries). I say to check that as there is really nice way to define ranges with -T option for volumes you wish to allocates.
I did a search against past threads and I'm a bit worried about the next steps. I see that people have to remove the library and configure it again when adding a new storage node. As I'm going to have 4 to 6 new ones in the next months, it would be painful to do that, isn't there any other way to do this?
In that case run jbconfig once and define all your storage nodes from one single silo. I'm not sure if silo license goes against physical silo or virtual libraries define so I can't say who is right here.
dpinink_silva
2 Intern
•
724 Posts
0
November 24th, 2006 09:00
If I use jbconfig on the second storage node, I'm going to configure a second jukebox in my datazone, am I right? We did that, but of course it was created without any slots, and we should add them using NMC, but we didn't know if it would add the same slots used by the first storage node. In other words, they would share the same slots?
Regards,
ble1
4 Operator
•
14.4K Posts
0
November 24th, 2006 09:00
dpinink_silva
2 Intern
•
724 Posts
0
November 24th, 2006 10:00
ble1
4 Operator
•
14.4K Posts
0
November 24th, 2006 10:00
going to configure a second jukebox in my datazone,
am I right?
Correct.
without any slots, and we should add them using NMC,
but we didn't know if it would add the same slots
used by the first storage node. In other words, they
would share the same slots?
No, with silo is a bit different. You must allocate slots via nsrjb command. The number of volumes you allocate the number of slots you get.
For example, let's say in ACSLS silo that you have 500 slots. Now, for first jukebox you have 100 slots and for second 400. You run nsrjb -a -T .. command for those slots (actually volumes as silo works with volumes and not slots!) and there you go. Check nsrjb command for examples (same rule applies to silos and AS libraries). I say to check that as there is really nice way to define ranges with -T option for volumes you wish to allocates.
dpinink_silva
2 Intern
•
724 Posts
0
November 24th, 2006 11:00
ble1
4 Operator
•
14.4K Posts
0
November 24th, 2006 11:00
ble1
4 Operator
•
14.4K Posts
0
November 24th, 2006 15:00