none
in DPM 2012 what is the minimum required free space on disk to backup SQL transaction logs? RRS feed

  • Question

  • On our main SQL server we started getting alerts that recovery point creation jobs began to fail due to "not enough space on the disk" (see complete error below). Currently the size of the disk for t-logs is: 235GB. Free space is 77.8GB and used space is at 158GB. The size of the largest t-log (for DB MainDataStore, about which the error below is complaining) is 95.5GB.

    Question: Does the free space size need to be larger than the size of the largest t-log for successful recovery point creation?


    --- error from dpm ---
    Affected area: sqlserver1\MainDataStore
    Occurred since: 8/28/2017 3:47:45 AM
    Description: Recovery point creation jobs for SQL Server 2012 database sqlserver1\MainDataStore on sqlserver1.thecompany.com have been failing. The number of failed recovery point creation jobs = 11.
     If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)
    Execution of SQL command failed for SQL Server 2012 database sqlserver1\MainDataStore on sqlserver1.thecompany.com with reason : BACKUP LOG is terminating abnormally.
    Write on "H:\Prod-Logs\DPM_SQL_PROTECT\sqlserver1\MainDataStore_log.LDF\Backup\Current.log" failed: 112(There is not enough space on the disk.)
    Write on "H:\Prod-Logs\DPM_SQL_PROTECT\sqlserver1\MainDataStore_log.LDF\Backup\Current.log" failed: 112(There is not enough space on the disk.)
    . (ID 30173 Details: Internal error code: 0x80990D18)
    More information
    Recommended action: Check the Application Event Viewer logs on the SQL Server for entries posted by the SQL Server service to find out why the SQL command may have failed. For more details, look at the SQL Server error logs.



    Monday, August 28, 2017 4:30 PM