09-05-2013 12:04 PM
Background:
NetBackup 7.5.0.1
Windows 2008 R2
In the last month we moved our software from Windows 2003 to Window 2008 R2. The import was a success and we were able to resume our backup policies. The last two weeks have had issues were the iSCSI target has lost connectivity. To resolve this we rebooted and redetected our storage devices. We took a look at our previous install and added a file called MAX_FILES_PER_ADD, with a value of 25000, in Program Files\Veritas\Netbackup folder. I suspect that won't resolve our issues. During the second fail, the mapped drives remained but Netbackup had already failed.
Is there a setting in Netbackup to have a longer timeout period? Or maybe something I could do with the services?
09-05-2013 02:23 PM
You need to fix the issue of iSCSI loosing connectivity.
A longer timeout is just like taking a pain killer but what you really need is surgery to have the rust nail removed from the foot.
There is a description of what MAX_FILE_PER_ADD do her:
http://www.symantec.com/docs/TECH183788
09-06-2013 04:33 AM
Checkpoint re-start is probably the only really useful thing here until you get your systems fixed.
At least after a failure it will try and re-start and / or allow you to resume the backup from where it had got to
Hope this helps