Backups are failing with 213

[PhaniKumar82]

Team 

I need the solution that we have DD as storage unit and it has Max capacity is 180 I/O so it mean it will accept only 180 jobs at that time .

OR is it allow 180 I/O per each storage unit on same DD ? becasue recently we are facing jobs are failing with 213 error and that time storage unit is busy with other jobs 

Regards

Kumar

[mph999]

DOes it only fail when there are other jobs running ?

How many jobs are running ?

When did the failures start ?

Just before the failures started, what changes were made, for example, did the number of runnning jobs increase ?

Martin

[PhaniKumar82]

Because we are keep on adding the clients and we have 14 hr backup window ( 6PM to 8 AM ) 

almost 500 clients backups need to run so which one should be do when we add new client in future 

Master server is 7.1.0.3 

clients are same version 

Max concurrent jobs are 180 per each storage units 

[PhaniKumar82]

Yes it is failing when there are other jobs are running 

almost 300 + active jobs are running 

we have not changed any on increasing jobs number and we have set the limt jobs per policy has 150 

Regards,

Kumar

[Marianne]

Max jobs setting in NBU can range from 0 to 256.

Do you have a single master/media server to manage all these jobs?

Is 180 a recommendation/limitation from DD?

What is your DD plugin version?

[Marianne]

See the following in NBU 7.1 Release Notes  http://www.symantec.com/docs/DOC3643  :

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.

Also see this TN which points to DDOS problem: http://www.symantec.com/docs/TECH128433

[PhaniKumar82]

we have One Master server &  two media servers but storage unit allocated from single DD only 

DD os is 5.1.0.9

DD recommendation limit is 180 but my question is it for each storage unit or entire DD ?

Regards,

Kumar 

[Marianne]

DD recommendation limit is 180 but my question is it for each storage unit or entire DD ?

Since it is their recommendation, you need to ask them... By the sounds of it - probably entire DD.

Please also have a look at the Release Notes mentioned above.

[Nicolai · Accepted solution]

It's 180 streams per entire DD! -  That means you need to ensure the total amount of concurrent streams do not exceed 180. 

The best way to control the number of streams is  on the pool level. Check mark "Limit I/O streams per pool" and make sure the combined value of the disk pool for the DD device do not exceed 180.

A example:

DD_diskpool1 "Limit I/O per pool" = 50

DD_diskpool2 "Limit I/O per pool" = 50

This is OK combined value this single DD box is 100. 

DD2_diskpool1 "Limit I/O per pool" = 180

DD2_diskpool2 "Limit I/O per pool" = 200

NO GO. The combined value is 380 - it can only do 180.