Transaction log backup fails with Recovery MS SQL

Discussion in 'Other Acronis Products' started by TAC, Apr 22, 2008.

Thread Status:
Not open for further replies.
  1. TAC

    TAC Registered Member

    Joined:
    Sep 13, 2006
    Posts:
    6
    Hi Folks,

    when I create a backup plan with the new Acronis product, I can build a full database backup without any problem. After that I could create three successful transaction log backups:

    Transactional Backup-Operation erfolgreich abgeschlossen. Sourcen: /Microsoft SQL Server/(local)/tac_gmbh. Speicherort: \\ServDE07\SQLRecovery\ServDE03\. Startzeit: 13:00:07. Ende: 13:00:20.

    With the fourth this error happens and it won't stop with every following process:

    Transactional Backup-Operation fehlgeschlagen. Sourcen: /Microsoft SQL Server/(local)/tac_gmbh. Speicherort: \\ServDE07\SQLRecovery\ServDE03\. Startzeit: 14:00:05. Fehler: Mitgliederaufruf fehlgeschlagen (0xE000B) token = "Backup.BackupArchive.Append.Apply" Tag = 0x298D61E7C0088C93 Cannot back up '(local).tac_gmbh' Microsoft SQL database transaction log: There is no information about the previous backup or there is a gap between it and the existing transaction log. (0x574000) Tag = 0xE4F164619BEC8BEFCannot back up '(local).tac_gmbh' Microsoft SQL database transaction log: There is no information about the previous backup or there is a gap between it and the existing transaction log. (0x574000) Tag = 0xE4F164619

    I know that this is the german version, but most messages are in english. Maybe someone understands, what is happening here.
    I stopped the SQL server from doing any maintainance, I have left everything to Acronis Recovery for MS SQL Server.

    Thanks for help,
    any questions, just ask.

    Thanks,
    Gunnar @ TAC
     
  2. jeremyotten

    jeremyotten Registered Member

    Joined:
    Feb 9, 2005
    Posts:
    684
    Set your recovery model to FULL (on SQL server) and try again
     
  3. TAC

    TAC Registered Member

    Joined:
    Sep 13, 2006
    Posts:
    6
    Hi Jeremy,

    I have taken a look into my settings. The recovery model was set to "Full" already.
    Now since the system is running for a few days, I have a few successful transaction backups and then a few errors follow. o_O
    This repeats day by day.
    My backup plan does the transactional every hour and I am sure, that there is enough user action in between.

    Are there any other ideas?

    Shall I post some entries from the logs?

    Thanks,
    Gunnar
     
  4. TAC

    TAC Registered Member

    Joined:
    Sep 13, 2006
    Posts:
    6
    o.k., no one asked me, but I am doing it anyway :)
    (means: posting an error log message)

    This is the newest error message. Some "Unknown Win32 error".

    Transactional Backup-Operation fehlgeschlagen. Sourcen: /Microsoft SQL Server/(local)/tac_gmbh. Speicherort: \\ServDE07\SQLRecovery\ServDE03\. Startzeit: 17:00:08. Fehler: Mitgliederaufruf fehlgeschlagen (0xE000B) token = "Backup.BackupArchive.Append.Apply" Tag = 0x298D61E7C0088C93 Failed to create backup of database 'tac_gmbh' from Microsoft SQL Server '(local)'. (0x57100E) Tag = 0x120B5C319F646E80 MSSQL_ClientVirtualDeviceSet::GetConfig fails. (0x572000) Tag = 0x38930F7709E76260 Unknown Win32 error (0xFFF0) code = 80770004) Tag = 0xBD28FDBD64EDB8ABFailed to create backup of database 'tac_gmbh' from Microsoft SQL Server '(local)'. (0x57100E) Tag = 0x120B5C319F646E80 MSSQL_ClientVirtualDeviceSet::GetConfig fails. (0x572000) Tag = 0x38930F7709E76260 Unknown Win32 error (0xFFF0) code = 80770004) Tag = 0xBD28FDBD64EDB8ABMSSQL_ClientVirtualDeviceSet::GetConfig fails. (0x572000) Tag = 0x38930F7709E76260 Unknown Win32 error (0xFFF0) code = 80770004) Tag = 0xBD28FDBD64EDB8ABUnknown Win32 error (0xFFF0) code = 80770004) Tag = 0xBD28FDBD64EDB8AB.

    Does not so very stable right now ?!?!
     
  5. jeremyotten

    jeremyotten Registered Member

    Joined:
    Feb 9, 2005
    Posts:
    684
    Update to build 117 and try again ;-)
    hey I am sounding like Acronis tech support ;-)
     
Thread Status:
Not open for further replies.