I have 2 backup scripts:

master..sqlbackup N'-SQL "BACKUP DATABASE [db_Import]
TO DISK = ''E:\<AUTO>'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', VERIFY, ERASEFILES = 3, COMPRESSION = 3"'

master..sqlbackup N'-SQL "BACKUP DATABASE [db_Import]
TO DISK = ''E:\Backups\ITSVPKSR02\<AUTO>'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', VERIFY, ERASEFILES = 3, COMPRESSION = 3"'


These are being run from SQL Query Analyser, the first one works, the second one doesn’t. The second script has been running for quite some time (SQL Server Agent Scheduled) but since upgrading to Version 4 I get the following errors:


Backing up db_Import (full database) to:
E:\Backups\ITSVPKSR02\FULL_ITSVPKSR02_db_Import_20060209 121725.sqb

Failed to create backup folder : E:\Backups\ITSVPKSR02SQL Backup exit code: 500

And

exitcode 500
sqlerrorcode 0
filename01 E:\Backups\ITSVPKSR02\FULL_ITSVPKSR02_db_Import_20060209 121725.sqb

I am also getting the following in the event log:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 09/02/2006
Time: 11:36:40
User: N/A
Computer: ITSVPKSR02
Description:
18210 :
BackupVirtualDeviceSet::AllocateBuffer: failure on backup device 'SQLBACKUP_D77F982C-058E-417C-9C9E-26B82FA4595D'. Operating system error 995(error not found).


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 47 00 00 10 00 00 00 "G......
0008: 0b 00 00 00 49 00 54 00 ....I.T.
0010: 53 00 56 00 50 00 4b 00 S.V.P.K.
0018: 53 00 52 00 30 00 32 00 S.R.0.2.
0020: 00 00 00 00 00 00 ......


AND


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 17055
Date: 09/02/2006
Time: 11:36:40
User: N/A
Computer: ITSVPKSR02
Description:
3041 :
BACKUP failed to complete the command sp_executesql;1


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: e1 0b 00 00 10 00 00 00 á.......
0008: 0b 00 00 00 49 00 54 00 ....I.T.
0010: 53 00 56 00 50 00 4b 00 S.V.P.K.
0018: 53 00 52 00 30 00 32 00 S.R.0.2.
0020: 00 00 00 00 00 00 ......


This is happening across all databases and affects logs and full backups.
Can someone please help to resolve this?
SinclairSpeccy
0

Comments

3 comments

  • SinclairSpeccy
    This script is now working.


    Regards,

    Darren France
    SinclairSpeccy
    0
  • petey
    Was it an error with regards to the SQL Backup Agent service user rights?
    petey
    0
  • SinclairSpeccy
    It was, thanks to Daniel for the fix.

    Changed the service to run under the same domain account as the SQL Server Agent and backups have resumed.
    SinclairSpeccy
    0

Add comment

Please sign in to leave a comment.