Backup on Share NFS fails - Windows Server 2008 R2
Backups over the network are risky as network connectivity is not redundant.  While you can setup your server to have multiple Network Interface Cards (NICs), if one were to fail while sending the stream of data establishing a connection from the secondary NIC would still cause a disruption to the original stream, which in this case, will cause a backup failure.

There are 2 things I can readily suggest you do, as follows:


Backup Locally: Make a local backup first and then use a secondary job such as robocopy, PowerShell, etc. to copy these backups over to your network share.
Stripe your backups: Make use of backup striping.  This will often times speed up the backup process significantly.  I still think you should backup locally, but striping your backup over the network may help you beat whatever network traffic is likely causing your latency issues.  Even Ola's solution supports striping in the event you're using that.


Backing up locally is most important for your TLog backups.  If enough of those fail in a row and your Tlogs fill the drive, you can run into a database halt situation which will be a service outage.  I'm not a fan of outages, nor should you be, which is why I really think you should make a backup locally, then offload a copy of those files to your network share.