In the SQL Server logs there was an error event when it attempted to backup a transaction log to a file to a non existent path. The thing is, we don't know what triggered the backup attempt. Poured over the maintenance logs and SQL Agent Jobs and cannot find anything. Is there a way to track down what triggered this backup request? If not for this one, then something to set up in case it happens again? Everyone who has access to the server insists they didn't do it. It is possible that it is a stored procedure or something that is programmed to backup the log to a file when triggered (maybe for troubleshooting) but I don't know how to track that sort of thing down. The path it attempted to use is very unique so if there is a way I could do some sort of comprehensive search that would work.