none
Error creating backup SQL Bases RRS feed

  • Question

  • Добрый день!

    Есть сервер Blade G1 460 под управлением Windows 2003 Server R2 x32 подключенный по SAN к EVA 4000 к луну на 500Гб. Установлен так же SQL 2005 SP3 x32 с порядка 6 рабочими базами (от 30 до 190 Гб размерами)

    На сервере стоит агент DPM  2010  x32

    Сервер бекапов на базе Windows 2008 r2  + DPM 2010 подключен так же к SAN к EVA 4000 и MSL 2024. так же к серверу по SCASI подключены две корзины по 5 Тб.

     

    Ситуация следующая.

    не снимается recovery point с скуль сервера с ошибкой :

    Affected area:    1C_SQL\SQL2005\Upp81_hq
    Occurred since:    16.02.2011 4:17:49
    Description:    Recovery point creation jobs for SQL Server 2005 database 1C_SQL\SQL2005\Upp81_hq on 1c_sql.xxxxx.local have been failing. The number of failed recovery point creation jobs = 1.
     If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
        DPM encountered an error while performing an operation for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\1c_data\DataDB\Upp81_hq.mdf on 1c_sql.xxxxxxx.local (ID 2033 Details: The request could not be performed because of an I/O device error (0x8007045D))
        More information
    Recommended action:    1) Refer to the detailed error code in the description above. Retry this operation after the issue has been fixed.
    2) If the error was due to insufficient resources, then it could be a transient failure and you should retry this operation after some time.
        Create a recovery point...
    Resolution:    To dismiss the alert, click below
        Inactivate alert

     

    Type:    Recovery point
    Status:    Failed
    Description:    DPM encountered an error while performing an operation for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\1c_data\DataDB\Upp81_hq.mdf on 1c_sql.ххххх.local (ID 2033 Details: The request could not be performed because of an I/O device error (0x8007045D))
        More information
    End time:    16.02.2011 2:54:29
    Start time:    16.02.2011 2:30:05
    Time elapsed:    00:24:23
    Data transferred:    13 236,56 MB
    Cluster node    -
    Recovery Point Type    Express Full
    Source details:    1C_SQL\SQL2005\Upp81_hq
    Protection group:    1C SQL Backup

    такая ошибка только с одной базой на сервере, все остальные ( 5 штук) снимаются без сбоев.

    Иногда помогает решение : "Остановка скуля, детач базы, перезагрузка сервера, атач базы, перезагрузка". Т.к. было подозрение что какая то транзакция мешает  бекапу. Но данное решение помогает в 1 из 10 случаев.

    Что интересно, бекап начинается  и всегда прерывается на обьеме где то 11-13 Гб.

    Хотел бы отметить, что файл базы копируется и перезаписывается по сети без ошибок. база рабочая, в ней работают пользователи и никаких ошибок внутри базы с данными нет.

    На скуль сервере стоят ПОСЛЕДНИЙ драйвера stoport для адаптера SAN  и последний обновления для скуля и системы.

    Подскажите как решить проблему ?

    Спасибо заранее.

    __________________________________

     

    Good day!

    There is a server Blade G1 460 running Windows 2003 Server R2 x32 connected to SAN EVA 4000 to a partition on a 500GB. Is set as SQL 2005 SP3 x32 with about 6 working database (from 30 to 190 GB in size)

    The server is an agent DPM 2010 x32

    Server backups based on Windows 2008 r2 + DPM 2010 is connected as a SAN to EVA 4000 and MSL 2024. as a server connected to SCASI two repositories to 5 terabytes. each.

     

    The situation is as follows.

    fails to make a recovery point to the SQL server error :

    Affected area:    1C_SQL\SQL2005\Upp81_hq
    Occurred since:    16.02.2011 4:17:49
    Description:    Recovery point creation jobs for SQL Server 2005 database 1C_SQL\SQL2005\Upp81_hq on 1c_sql.xxxxx.local have been failing. The number of failed recovery point creation jobs = 1.
     If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
        DPM encountered an error while performing an operation for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\1c_data\DataDB\Upp81_hq.mdf on 1c_sql.xxxxxxx.local (ID 2033 Details: The request could not be performed because of an I/O device error (0x8007045D))
        More information
    Recommended action:    1) Refer to the detailed error code in the description above. Retry this operation after the issue has been fixed.
    2) If the error was due to insufficient resources, then it could be a transient failure and you should retry this operation after some time.
        Create a recovery point...
    Resolution:    To dismiss the alert, click below
        Inactivate alert

     

    Type:    Recovery point
    Status:    Failed
    Description:    DPM encountered an error while performing an operation for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\1c_data\DataDB\Upp81_hq.mdf on 1c_sql.ххххх.local (ID 2033 Details: The request could not be performed because of an I/O device error (0x8007045D))
        More information
    End time:    16.02.2011 2:54:29
    Start time:    16.02.2011 2:30:05
    Time elapsed:    00:24:23
    Data transferred:    13 236,56 MB
    Cluster node    -
    Recovery Point Type    Express Full
    Source details:    1C_SQL\SQL2005\Upp81_hq
    Protection group:    1C SQL Backup

    this error is only one database on the server, all the rest (5 pieces) is copied without error

    Sometimes it helps the decision: "
    Stop SQL , detach database, restart the server, atach database, reboot server." Because there was a suspicion that what prevents the backup of the transaction. However, this solution helps in 1 out of 10 cases.

    What is interesting, backup starts and always stops at the volume where it 11-13 GB.


    I would like to note that the database file is copied and rewritten over the network without errors . base of working, it employs users and no errors in the data base there .
    On the server are the latest drivers for the adapter stopport SAN and the last update for whining and systems.

    Tell me how to fix it?

    Thanks in advance.


     

    • Edited by tarzan2000 Thursday, February 17, 2011 11:35 AM
    Wednesday, February 16, 2011 5:59 AM

All replies

  • Hi

    Could you please post your question in English?

     

    BR

    Robert Hedblom



    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Wednesday, February 16, 2011 9:51 AM
    Moderator
  • Yeah, sorry . Fixed the first post .
    Wednesday, February 16, 2011 11:03 AM
  • I would begin by looking at the SQL server for any possible device or volume corruption type errors.  You can also check for the same on the DPM server, but if colocation is enabled this is likely not the cause. 

    Finally, are you saying that this happens often and that detaching the database and reattaching works to correct the error sometimes?  If so, it really sounds like a problem with the SQL database and I would also start looking into SQL to see if there are any problems reported with that particular database.


    Thanks, Chris Bu - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, March 2, 2011 4:10 PM
    Moderator
  • Hi Tarzan2000,

     

    Was this issue addressed?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, May 26, 2011 9:29 PM
    Moderator
  • Здесь хорошо написано про backup: Резервное копирование базы данных MS SQL Server
    • Edited by dimetra2008 Saturday, December 17, 2011 11:34 AM
    Saturday, December 17, 2011 11:32 AM
  • Hi Dimetra2008, would it be possible for you to translater your last post in english?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Saturday, December 17, 2011 7:31 PM
    Moderator
  • Для бэкапа баз SQL использую Handy Backup. Простая и удобная программа, советую
    Monday, September 10, 2012 8:01 AM