As mentioned earlier, when the backup is written it is the SQL Server service that is writing it, not the agent. The agent will log into SQL with the domain...

I have also seen this error occur when a server backup agent, such as NetBackup, is accessing the live database files in order to copy them to tape.

I don't know...