What are the challenges you face when working across database platforms? Take the survey
Options

Error during backup

appwrightappwright Posts: 62
edited August 18, 2005 10:38AM in SQL Backup Previous Versions
I am having a strange error during backups. I backup a couple hundred databases every night and this is sporadic. It seems to happen when I am logged into the SQL Server remotely and then logout. When I logout, it seems to cause this error best I can tell:

4/27/2005 10:24:23 PM: SQL Backup 3.1.0, (c) Red Gate Software Ltd 2004 - 2005
4/27/2005 10:24:23 PM:
4/27/2005 10:24:23 PM: Backing up MPOWERMEDIA (full database) on TAHOE instance to \\Servwatch\@Backups\TAHOE_MPOWERMEDIA_db_(full)_200504272224.sqb ...
4/27/2005 10:24:23 PM:
4/27/2005 10:24:23 PM: BACKUP DATABASE [MPOWERMEDIA] TO DISK = '\\Servwatch\@Backups\TAHOE_MPOWERMEDIA_db_(full)_200504272224.sqb' WITH NAME = 'Database (MPOWERMEDIA) Full', DESCRIPTION = '', PASSWORD = 'XXXXXXXXXX', ERASEFILES_ATSTART = 2, MAILTO = 'xxx', COMPRESSION = 3
4/27/2005 10:24:23 PM:
4/27/2005 10:24:27 PM: Deleting old backup file: \\Servwatch\@Backups\TAHOE_MPOWERMEDIA_db_(full)_200504242313.sqb
4/27/2005 10:24:27 PM: Warning 161: ERASEFILES error: Failed to delete file: \\Servwatch\@Backups\TAHOE_MPOWERMEDIA_db_(full)_200504242313.sqb. Error code: 158 (The segment is already unlocked).
4/27/2005 10:24:30 PM: osql -S TAHOE\TAHOE -Q "BACKUP DATABASE [MPOWERMEDIA] TO VIRTUAL_DEVICE = 'SQLBACKUP_88112141' WITH BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = 'Database (MPOWERMEDIA) Full', DESCRIPTION = '', FORMAT" -b -w 120 -U sa -P XXXXXXXXXX
4/27/2005 10:24:52 PM: Thread 0 error: Failed to service command. Error code: -2139684860 Process terminated unexpectedly. Error code: -2139684860

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Do you have any maintenance jobs that might be running during that time blocking the backup?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Nope - the only thing that makes this happen is if I am logged into the machine remotely while the RG SQL Backup is running, open the EM, close it, log off the computer.
  • Options
    peteypetey Posts: 2,358 New member
    Could you pls check the vdi.log file (found in the SQL Server Log folder) and SQL Server log file for any other errors that may have been raised at the time of the backup? Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Here is the VDI log:

    2005/04/25 22:06:53 pid(1060) tid(1292)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/25 22:06:53 pid(300) tid(484)
    Error on SQLBACKUP_191761517
    Error at CVD::GetCommand: AbortDetected

    2005/04/25 22:06:53 pid(1060) tid(1292)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/25 22:06:53 pid(300) tid(484)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/25 22:06:53 pid(1060) tid(1292)
    Error on SQLBACKUP_191761517
    Error at SVDS::CloseDevice: Abort detected

    2005/04/25 22:06:53 pid(300) tid(2324)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/25 22:06:53 pid(1060) tid(1292)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/25 22:06:53 pid(1060) tid(1596)
    Error on SQLBACKUP_191761517
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(1060) tid(1292)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(1060) tid(1292)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(1060) tid(1292)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(516) tid(2784)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(1060) tid(1292)
    Error on SQLBACKUP_88112141
    Error at SVDS::CloseDevice: Abort detected

    2005/04/27 22:24:52 pid(516) tid(3644)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:52 pid(1060) tid(1292)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked

    2005/04/27 22:24:53 pid(1060) tid(1500)
    Error on SQLBACKUP_88112141
    Error at TriggerAbort: invoked
  • Options
    peteypetey Posts: 2,358 New member
    Which remote connectivity app are you using? I tried using RDC but could not reproduce your error.

    Is the sequence of events as follows?

    - sqb is backing up database A
    - you log in to server, open EM, connect to server, log out
    - sqb finishes backing up database A, starts to backup database B
    - sqb fails to backup database B, reporting the error you described
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Yes along those lines. I haven't done it again since I want it to backup :)

    I have a couple hundred DB's that backup. It does some of them, I log into it, open Explorer and Enterprise Manager. Close everything, log off the machine. Then I get the error in email.
  • Options
    peteypetey Posts: 2,358 New member
    How are you logging in? Terminal Services, VNC etc?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    see PM
  • Options
    I can pretty much repeat this on demand now.
  • Options
    peteypetey Posts: 2,358 New member
    I am still trying to reproduce the error using the software you are using. Also, which versions of Windows and SQL Server are you using?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    I am using Windows 2000 with all the service packs and updates (according to Windows Update).

    @version results this:
    I am using Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
  • Options
    You need to make sure that the virus checker is not scanning you backup location. Or the temp red-gate location.
  • Options
    No virus checkers doing anything. This has to do purely with GotoMyPC and terminal services.
Sign In or Register to comment.