Hi,
I am running Netbackup Datacenter on a win2k MSCS cluster environment running it's data off a SAN
I have urgent restores to a new SAN and am running restores via scripts as this is quicker than fighting with the GUI on netbackup 3.4.1_... Some of the restores bomb out with a bpcr timeout(socket error, status code 25). Does the "CR" stand for "Client read" timeout as this is what our vendors have assumed and this timeout has been increased. It now fails after the same amount of time (well under the timeout limit)Any ideas???????? COULD IT BE A CLEAN REQUEST TIMEOUT?? or am I on the wrong track entirely.
Thanks
Magrat
I am running Netbackup Datacenter on a win2k MSCS cluster environment running it's data off a SAN
I have urgent restores to a new SAN and am running restores via scripts as this is quicker than fighting with the GUI on netbackup 3.4.1_... Some of the restores bomb out with a bpcr timeout(socket error, status code 25). Does the "CR" stand for "Client read" timeout as this is what our vendors have assumed and this timeout has been increased. It now fails after the same amount of time (well under the timeout limit)Any ideas???????? COULD IT BE A CLEAN REQUEST TIMEOUT?? or am I on the wrong track entirely.
Thanks
Magrat