05-03-2011 06:05 AM
Solved! Go to Solution.
05-26-2011 09:01 AM
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.
05-26-2011 09:01 AM
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.