Occassional EXCEPTION_ACCESS_VIOLATION after a standard translog backup

  • Hi,

    I'm getting an "EXCEPTION_ACCESS_VIOLATION" occasionally after a fairly standard hourly translog backup on 4 databases. The databases are not very big and there is plenty of space on the box.

    SQL Version: Microsoft SQL Server 2014 - 12.0.2000.8 (X64)

    Feb 20 2014 20:04:26

    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

    This has happened before and after we bounced the box it was fine but we can't do that again when we go live. I'm including the stack dump with this post as I hope it will help.

    I would really appreciate any comments/suggestions/user-experience you would like to share. Help.

    J.

    Incl. Sql Stack Dump

  • Have you logged a call with MS support?

  • No, not as yet. I thought I would try this forum first. There is nothing exotic here - its a fairly standard hourly translog backup that appears to fail occasionally. I used the maintenance plan wizard to create the thing.

    The T-SQL is below. It runs fine from inside SSMS - provided that I bounce the "SQL Server" service. It just that occasionally the maintenance plan appears to fail:

    T-SQL From Maintenance Plan

    EXECUTE master.dbo.xp_create_subdir N'D:\SQL2014\Backups\Live Systems\GAMMA_1_0'

    GO

    EXECUTE master.dbo.xp_create_subdir N'D:\SQL2014\Backups\Live Systems\DELTA'

    GO

    EXECUTE master.dbo.xp_create_subdir N'D:\SQL2014\Backups\Live Systems\Alpha_LIVE_1_0'

    GO

    EXECUTE master.dbo.xp_create_subdir N'D:\SQL2014\Backups\Live Systems\BETA_LIVE_2_0'

    GO

    BACKUP LOG [GAMMA_1_0] TO DISK = N'D:\SQL2014\Backups\Live Systems\GAMMA_1_0\GAMMA_1_0_backup_2015_06_17_102938_6078468.bak' WITH NOFORMAT, NOINIT, NAME = N'GAMMA_1_0_backup_2015_06_17_102938_6078468', SKIP, REWIND, NOUNLOAD, STATS = 10

    GO

    declare @backupSetId as int

    select @backupSetId = position from msdb..backupset where database_name=N'GAMMA_1_0' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'GAMMA_1_0' )

    if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''GAMMA_1_0'' not found.', 16, 1) end

    RESTORE VERIFYONLY FROM DISK = N'D:\SQL2014\Backups\Live Systems\GAMMA_1_0\GAMMA_1_0_backup_2015_06_17_102938_6078468.bak' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND

    GO

    BACKUP LOG [DELTA] TO DISK = N'D:\SQL2014\Backups\Live Systems\DELTA\DELTA_backup_2015_06_17_102938_6088469.bak' WITH NOFORMAT, NOINIT, NAME = N'DELTA_backup_2015_06_17_102938_6088469', SKIP, REWIND, NOUNLOAD, STATS = 10

    GO

    declare @backupSetId as int

    select @backupSetId = position from msdb..backupset where database_name=N'DELTA' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'DELTA' )

    if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''DELTA'' not found.', 16, 1) end

    RESTORE VERIFYONLY FROM DISK = N'D:\SQL2014\Backups\Live Systems\DELTA\DELTA_backup_2015_06_17_102938_6088469.bak' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND

    GO

    BACKUP LOG [Alpha_LIVE_1_0] TO DISK = N'D:\SQL2014\Backups\Live Systems\Alpha_LIVE_1_0\Alpha_LIVE_1_0_backup_2015_06_17_102938_6088469.bak' WITH NOFORMAT, NOINIT, NAME = N'Alpha_LIVE_1_0_backup_2015_06_17_102938_6088469', SKIP, REWIND, NOUNLOAD, STATS = 10

    GO

    declare @backupSetId as int

    select @backupSetId = position from msdb..backupset where database_name=N'Alpha_LIVE_1_0' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'Alpha_LIVE_1_0' )

    if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''Alpha_LIVE_1_0'' not found.', 16, 1) end

    RESTORE VERIFYONLY FROM DISK = N'D:\SQL2014\Backups\Live Systems\Alpha_LIVE_1_0\Alpha_LIVE_1_0_backup_2015_06_17_102938_6088469.bak' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND

    GO

    BACKUP LOG [BETA_LIVE_2_0] TO DISK = N'D:\SQL2014\Backups\Live Systems\BETA_LIVE_2_0\BETA_LIVE_2_0_backup_2015_06_17_102938_6088469.bak' WITH NOFORMAT, NOINIT, NAME = N'BETA_LIVE_2_0_backup_2015_06_17_102938_6088469', SKIP, REWIND, NOUNLOAD, STATS = 10

    GO

    declare @backupSetId as int

    select @backupSetId = position from msdb..backupset where database_name=N'BETA_LIVE_2_0' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name=N'BETA_LIVE_2_0' )

    if @backupSetId is null begin raiserror(N'Verify failed. Backup information for database ''BETA_LIVE_2_0'' not found.', 16, 1) end

    RESTORE VERIFYONLY FROM DISK = N'D:\SQL2014\Backups\Live Systems\BETA_LIVE_2_0\BETA_LIVE_2_0_backup_2015_06_17_102938_6088469.bak' WITH FILE = @backupSetId, NOUNLOAD, NOREWIND

  • are you on 2014 RTM?

  • No. SQL server standard

    select @@Version: Microsoft SQL Server 2014 - 12.0.2000.8 (X64)

    Feb 20 2014 20:04:26

    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

  • I am sure Microsoft SQL Server 2014 - 12.0.2000.8 = RTM (you probably do have standard edition). I know RTM has caused these violations when doing backups.

    I don't have the ability to decipher these dump files, I have tried in the past and failed miserably. I would still suggest to contact MS support, either way they will probably tell you to apply 2014 updates.

  • Ok - thanks for the suggestions. I'm nearly sure we are using standard and are up-to-date with updates. Anyone else out there with anything to offer? Any suggestions.....

  • jellybean (6/17/2015)


    No. SQL server standard

    select @@Version: Microsoft SQL Server 2014 - 12.0.2000.8 (X64)

    Feb 20 2014 20:04:26

    Copyright (c) Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

    Hi

    BL0B_EATER is right. Your version is 12.0.2000.8 which is RTM. (You are indeed on Standard edition, but this is irrelevant now)

    Check these links to get a better understanding on patch levels and try to update to a more up to date one after testing your applications compatibility.

    http://sqlserverbuilds.blogspot.hu/

    http://sqlserverupdates.com/

    @edit: Added relevant article about higher patch level needed from 2014 RTM

    http://sqlserver-help.com/2015/03/25/solution-sql-server-backup-failing-with-exception_access_violation/

    ________________________________________________________________
    "Accept conditions as they exist, or accept the responsibility for changing them."

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply