Netbackup 7.1 - Error nbjm(pid=5592) NBU status: 213, EMM status: Storage units are not available

[rsakimoto]

Hi,

Need help on error on our Netbackup.

9/28/2012 12:51:09 AM - Info nbjm(pid=5592) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=6885, request id:{79E3A819-C744-4482-9C30-BD693A9547A6}) 
9/28/2012 12:51:09 AM - requesting resource stu_nbu4
9/28/2012 12:51:09 AM - requesting resource nbu2.NBU_CLIENT.MAXJOBS.BDOWBS0138
9/28/2012 12:51:09 AM - requesting resource nbu2.NBU_POLICY.MAXJOBS.Branch
9/28/2012 12:51:09 AM - awaiting resource stu_nbu4 - Maximum job count has been reached for the storage unit
9/28/2012 1:02:21 AM - Error nbjm(pid=5592) NBU status: 213, EMM status: Storage units are not available  
no storage units available for use(213)

Had this error 213 on alot of clients enrolled in our policy. Is there a max clients that one policy can cater? Does the On Demand option should really be unchecked for case on our policy that has several clients?

Thanks

[Marianne]

We need more info...

What kind of STU is stu_nbu4?
If disk, is 'On Demand Only' selected? (default for DSU)

Does your policy specify STU or is it set to 'Any Available'?

If STU is set to 'On Demand Only', you need to select the STU in the policy.

Amount of jobs that can be generated for a policy is determined by 'Limit Jobs' in Policy attributes. The default is unlimited.

[rsakimoto]

Hi Marianne, pls see in bold font for additional info.

What kind of STU is stu_nbu4? - It is MSDP
If disk, is 'On Demand Only' selected? (default for DSU) - Yes

Does your policy specify STU or is it set to 'Any Available'? - Where using SLP wherein storage destination backup is set tou our STU (stu_nbu4).

If STU is set to 'On Demand Only', you need to select the STU in the policy. - STU is selected on SLP.

Amount of jobs that can be generated for a policy is determined by 'Limit Jobs' in Policy attributes. The default is unlimited. - Yes it is in default unlimited.

Our setup on our master server, the policy we are using has 150 clients. Maximum concurrent jobs set on our STU is 30. Our backup window is from 1:30 AM to 7:00 PM (5hrs 30mins duration).

Before, we do not encounter this error code 213. We add 20 clients in our policy each day. Our projected number of clients is around 300. Can NBU handle this setup?

Thanks for your response. :)

[V4]

hope this helps

http://www.symantec.com/docs/HOWTO50974

Yes there is limit max client a policy can cater, you can change it depending upon your STU configuration of how much concurrent jobs it can accept

simply increase count under policy attibute of jobs per policy.

You can also enable multi streamin from same client with multiple selections.

Add new stream from directives

increase max jobs per client under master server host properties Global settigs

[rsakimoto]

Hi captain jack sparrow,

Yes there is limit max client a policy can cater, you can change it depending upon your STU configuration of how much concurrent jobs it can accept

simply increase count under policy attibute of jobs per policy. - already set to unlimited

You can also enable multi streamin from same client with multiple selections. - is this possible with our setup..? this will increase jobs per client right..?

Add new stream from directives. - ..?

increase max jobs per client under master server host properties Global settigs - Set to 3

We are currently using "always use client-side deduplication" under client attributes. Is this counted as job count..?

Thank you very much for your response..

[falti_manullang]

Maximum job count has been reached for the storage unit <------- Just Increase the Maximum concurrent jobs setting.

The Maximum concurrent jobs setting uses and dependencies are as follows:

• Can be used to balance the load between disk storage units. A higher value (more concurrent jobs) means that the disk may be busier than if the value was set for fewer jobs.

  The media server load balancing logic considers all storage units and all activity. A storage unit can indicate three media servers. If Maximum concurrent jobs is set to three and two of the media servers are busy or down, the third media server is assigned all three jobs.

• Depends on the available disk space and the server's ability to run multiple backup processes. Where disk pools are used, the setting also depends on the number of media servers in the storage unit.

  If multiple storage units reference the same disk pool, the number of concurrent jobs that can access the pool is the sum of the Maximum concurrent jobs settings on all of the disk storage units. The setting applies to the storage unit and not to the disk pool. Therefore, the job load is automatically spread across the media servers that the storage unit configuration indicates.

[rsakimoto]

Hi falti.Manullang,

We already increased the max concurrent jobs from 20 to 40, same problem encountered.

Heres our setup, we have around 150 client on master server, created 1 policy for these clients. Policy storage is set to SLP wherein SLP is configured to backup to 1 STU (MSDP) and duplicates to Tape (HCART2) robot. Max concurrent job is set to 40. Client deduplication is set to "always use client-side deduplication".

Thank you for your response..

[Marianne]

Thanks for letting us know this is MSDP.

See the following extract from NBU 7.1 Release Notes:

■ Deduplication backup jobs may fail with status code 213 or status code 2074.

Deduplication backup jobs may fail with status code 213 or 2074 even though

a suitable storage unit exists. The deduplication servers usually must be under

heavy load for that to occur.

To work around this issue, add the following touch file to the deduplication

storage server and to any load balancing servers:

UNIX: /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO

Windows:

install_path\Veritas\NetBackup\db\config\DPS_PROXYDEFAULTRECVTMO

The file content must be the integer 800. No other file content is required.

[rsakimoto]

Hi Marianne,

I already added the file DPS_PROXYDEFAULTRECVTMO and is set to 800 integer. But still the same 213 code error.

Thank You.

[Marianne]

If you tell us these things, we won't waste eveyone's time by telling you stuff that you have already done.

You never mentioned your 7.1 patch level. There have been fixes for status 213 in various 7.1 patches, e.g. http://www.symantec.com/docs/TECH167950