I then go to the SQL Server logs and view the current log.
At the same time when I received the email that the job failed I am able to find this:
Source: spid69
BackupDiskFile::RequestDurableMedia: failure on backup device \\xxxxx. Operating system error 64(The specified network name is no longer available.).
When I go to the location of where the backup file is there are transactional logs there (whether they are complete or not is another question but data was written to the network locations).
Things have been going fine until today. Nothing on the network has changed. A few months back I had to move the backups from our SAN to our NAS due to storage issues, migrations, etc. The hop count hasn't changed and it's the same millsecond response time when doing a ping and tracert.
You stated that you moved the backups from the SAN to the NAS. Were backups working after that move and just recently fail, or have they been failing since the move? Have you tried accessing the network location from the account the SQL Server service is using? It will need permissions to the network share.
Joie Andrew
"Since 1982"