cancel
Showing results for 
Search instead for 
Did you mean: 

Error 213 and 2074

Stanleyj
Level 6
The appliance had been up and running for a couple of weeks and I am now starting to recieving error 213 (no storage unit available) and error 2074 (disk volume is down) during some of the backups. I have been working with support but they seem to be stumped by this (mainly because of the appliance thing) and really dont have a clue how to proceed. This error seems to mainly appear with my sql jobs but there have been situations where it appeared on the jobs just before the sql backups start. So that kinda rules out it being a paticular policy. The 2074 errors are related to my duplication jobs but the robots are attached to the appliance as well so i thought i would post them in here also. The 2074 errors started appearing the same time the 213 errors poped up but they happen several minute later. The jobs do not retry after these errors happen so some things are not getting backup and at this point it happens on random policies so i dont know from day to day what is not going to get backup. Thank you for any assistance offered.
1 ACCEPTED SOLUTION

Accepted Solutions

Stanleyj
Level 6

Following the unix instructions solved the over commitment issue,

 

I also found the following in the 7.1 Release Notes under Operational Notes -> NetBackup Media Server DeduplicationOption:

■ 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.

View solution in original post

1 REPLY 1

Stanleyj
Level 6

Following the unix instructions solved the over commitment issue,

 

I also found the following in the 7.1 Release Notes under Operational Notes -> NetBackup Media Server DeduplicationOption:

■ 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.