04-27-2014 01:32 AM
04-28-2014 11:37 PM
As per Nicolai's excellent post, there is no 1:1 relationship between STUs and devices, merely device type (drive density) and location (robot number and media server).
So, some examples:
04-27-2014 03:37 AM
04-27-2014 04:31 AM
What is the point with this qustion ?
04-27-2014 05:03 AM
Nicolai, it wont hurt knowing how many storage units we can create having some number of drives at our disposal beforehand...also,its more of an inquisitiveness :)
04-27-2014 05:34 AM
04-27-2014 08:08 AM
Marriane,if you dont mind can you break it up with an example pls...
04-27-2014 10:31 PM
Hi nbuno,
First off, (Taken from NBU AdminGuide volume I) Storage Unit is a label that NetBackup associates with physical storage. The storage can identify a robot, a path to a volume, or a disk pool. A Storage units can be included as part of a storage unit group or a storage lifecycle policy.
Storage Unit types:
Now, to elaborate what Marianne answered:
# of STU = 1 STU/Media Server/STU Type/per robot
04-28-2014 12:39 AM
Since there is no 1:1 relation between physical devices and storage units you can create so many storage units that you can confuse the admin before Netbackup.
That does not provide a definite number - but try to keep a 1:1 ration as rule of thump. This does not always work - e.g if you do duplication where you may have two storage unit pointing to the tape tape devices but different "concurrent write drives".
04-28-2014 11:37 PM
As per Nicolai's excellent post, there is no 1:1 relationship between STUs and devices, merely device type (drive density) and location (robot number and media server).
So, some examples: