SQL Backup Set Issue

[drdc]

Good Day All,

I have created a SQL backup set and am experiencing errors.

The backup sets are set to use the sa user and password and have been verified by the customer as current active accounts.

Please let me know if there is something i am missing, I have never seen these error before a SQL backup.

Thank you

Error Log:

01:00:20 E 3201 Cannot open backup device 'C:\taylor_test.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (taylor_test)
01:00:20 E 3201 Cannot open backup device 'C:\kba_eseries_cv.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (kba_eseries_cv)
01:00:20 E 3201 Cannot open backup device 'C:\kba_sitefinity.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (kba_sitefinity)
01:00:20 I 1073742926 'taylor_test' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...
01:00:20 I 1073742926 'kba_eseries_cv' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...
01:00:20 I 1073742926 'kba_sitefinity' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...
01:00:20 E 3201 Cannot open backup device 'C:\msdb.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (msdb)
01:00:20 I 1073742926 'msdb' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...
01:00:20 E 3201 Cannot open backup device 'C:\model.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (model)
01:00:20 I 1073742926 'model' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...
01:00:20 E 3201 Cannot open backup device 'C:\master.2'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
SQL:declare @dbName nvarchar(255), @device nvarchar(512), @sqlstring nvarchar(1024) set @dbName = ? set @device = ? select @sqlstring = N'backup database [' + @dbName + N'] to ' + @device + N' with init ' exec (@sqlstring) (master)
01:00:20 I 1073742926 'master' database is in 'SIMPLE' recovery mode. Skipping transaction log backup ...

[terrydavis]

SQL Version?
OS Version of SQL Server?

This error says that SQL cannot write to the C:\ drive. I can't say I have ever used the sa account to perform backup operations, always windows credentials. Not sure how sa translates to a local server account for permissions. Try making your dump path of C:\Windows\Temp before making any other changes. Any user can write to that location typically.

[drdc]

Windows 2008 SP2

SQL 2008 R2

[terrydavis]

Could be hitting some user account control security issues as well. Try my suggestion of using C:\Windows\Temp as dump location. There will also be errors in the SQL log but likely they will be the same as what you see in the DS-Client event log.

[Grunt]

What user is the sql service utilizing. Changing it to "local Service" might help you out here.

[caseyd58]

Are the files in question actually being created in the dump file folder? If so, do they remain in the folder AFTER the job fails?
I have occasionally seen these errors when an SQL job does not complete successfully and never removes these temporary files, leaving them locked and inaccessible. Deleting these files and re-running the job fixed the problem each time.

If the files are never actually written to the dump folder, then it is a very strong possibility it is permissions related.