01-05-2012 07:53 AM
NBU 7.0.1, running on RH LInux with a Quantum i2000 robot - 12 drives (8 LTO3 and 4 LTO4).
I've searched Google but couldn't find the answer to my question. I've only got a few months experience with this setup. When I look at the robot, only 3 drives are being used and I have jobs queued up that say "drives are in use". The policies are set to "Use multiple streams" and the Storage Units are set up to allow 8 "Maximum concurrent write drives". So what have I missed?
Also there is 1 Master server and 2 Media servers.
Mike
Solved! Go to Solution.
01-06-2012 06:05 AM
Well - 208 only has 4 drives in it and you say only three are being used ......
That is because the others are all DOWN
You need to UP the drives (and find out why there were down to get this sorted out)
01-05-2012 12:45 PM
You should have multiple Storage Units in this setup, right?
Please post output of the following:
bpstulist -U
How are Storage Units assigned to policies - specific STU's or STU groups?
Are jobs queueing for one specific STU or more than one STU?
01-05-2012 01:12 PM
yes, I have multiple storage units. I'm focused on the NDMP-based storage units especially. Specific STUs are assigned to policies - I am not using STU groups at the moment (willing to change, however). NDMP jobs are queued for these 2 specific STUs.
[root@master ~]# bpstulist -U Label: master-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: master Number of Drives: 5 On Demand Only: no Max MPX/drive: 6 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB Label: media03-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media03 Number of Drives: 2 On Demand Only: yes Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media04-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media04 Number of Drives: 2 On Demand Only: yes Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media05-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media05 Number of Drives: 2 On Demand Only: yes Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media01-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media01 Number of Drives: 7 On Demand Only: no Max MPX/drive: 10 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB Label: media06-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media06 Number of Drives: 2 On Demand Only: yes Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB Label: media02-hcart3-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media02 Number of Drives: 1 On Demand Only: no Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB Label: master-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: master Number of Drives: 4 On Demand Only: no Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media03-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media03 Number of Drives: 4 On Demand Only: yes Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media04-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media04 Number of Drives: 4 On Demand Only: yes Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media05-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media05 Number of Drives: 4 On Demand Only: yes Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media06-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media06 Number of Drives: 4 On Demand Only: yes Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media01-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media01 Number of Drives: 4 On Demand Only: no Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: media02-hcart-robot-tld-0 Storage Unit Type: Media Manager Host Connection: media02 Number of Drives: 4 On Demand Only: no Max MPX/drive: 4 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB Label: master-hcart3-robot-tld-0-208 Storage Unit Type: NDMP Host Connection: master Number of Drives: 8 On Demand Only: no Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB NDMP attach host: 192.168.123.75 Label: master-hcart-robot-tld-0-208 Storage Unit Type: NDMP Host Connection: master Number of Drives: 2 On Demand Only: no Max MPX/drive: 1 Density: hcart - 1/2 Inch Cartridge Robot Type/Number: TLD / 0 Max Fragment Size: 1048576 MB NDMP attach host: 192.168.123.75 Label: master-hcart3-robot-tld-0-208_copy Storage Unit Type: NDMP Host Connection: master Number of Drives: 8 On Demand Only: no Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB NDMP attach host: 192.168.123.75 Label: master-hcart3-robot-tld-0-208_copy2 Storage Unit Type: NDMP Host Connection: master Number of Drives: 8 On Demand Only: no Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB NDMP attach host: 192.168.123.75 Label: media01-hcart3-robot-tld-0-208 Storage Unit Type: NDMP Host Connection: media01 Number of Drives: 4 On Demand Only: no Max MPX/drive: 1 Density: hcart3 - 1/2 Inch Cartridge 3 Robot Type/Number: TLD / 0 Max Fragment Size: 1048575 MB NDMP attach host: 192.168.123.75 Label: backup_to_disk Storage Unit Type: Disk Storage Unit Subtype: Basic (1) Host Connection: master Concurrent Jobs: 15 On Demand Only: yes Max MPX: 1 Path: "/usr/openv/netbackup/backup2disk" Max Fragment Size: 524287 MB Stage data: yes Block Sharing: no High Water Mark: 85 Low Water Mark: 60 Ok On Root: yes
01-05-2012 02:13 PM
in NB there are a number of things that can cause a job to queue up.
The easy way for us to help is to find out why they are queued up.
If you go to the gui and
either look at the column that says "State Details" of the job that is queue
or look at the details of the job that is queued
it will tell you why it is waiting -
With that info we can get closer to why are are not using all the drives.
01-05-2012 09:51 PM
What is the reason for having 2 STU's for the same device parameters?
The only difference is the number of drives. Maybe this is 'confusing' NBU?
To really see what is in use, assigned and allocated, compare output of all of the following on the master:
vmoprcmd -d
vmdareq
nbrbutil -dump (check the bottom section of output with allocation info).
01-06-2012 04:15 AM
In addition to the helps and requests above can i ask if all of your Media Servers have had the Shared Storage Option license registered on them?
Run /usr/openv/netbackup/bin/admincmd/get_license_key on each one to make sure it has been added.
Hope this helps
01-06-2012 05:52 AM
@J.Hinchcliffe - Here is the last bit of the Detailed Status for one of the queued jobs:
Jan 5, 2012 1:34:17 PM - awaiting resource master-hcart3-robot-tld-0-208. Waiting for resources.
[root@master ~]# vmoprcmd -d
PENDING REQUESTS
01-06-2012 06:05 AM
Well - 208 only has 4 drives in it and you say only three are being used ......
That is because the others are all DOWN
You need to UP the drives (and find out why there were down to get this sorted out)
01-06-2012 07:27 AM
@Mark_Solutions -- I've reset the drives to UP and enabled the necessary paths. I'm checking the Scalar i2000 to see what errors are on the drives - one drive at least needs cleaning, but at least all of the drives are being utilized.
I would still like to understand how to correct the config of STUs.
01-06-2012 07:44 AM
Glad this has helped
In general each media server will have a single storage unit that relates to the number of drives of the same denisty in a library
So in your case, assuming all drives are shared, then each media server should have hcart3 storage unit with 8 drive and a hcart storage unit with 4 drives
You only tend to have additional ones with less drives if you want to restrict a particular media sevrer or policy from using all of the drive, in which case you can take a copy of it and reduce its drive count.
Do check all of your policies and schedules (and disk staging / SLPs if you use them) before deleting any to make sure that they are not specified somewhere which would revert the policy to fail or use "any available"
Hope this helps
01-06-2012 11:23 AM
I think I have a problem setting up the STUs correctly, but I'll move that to another thread.