Forum Discussion

Claudio_Veronez's avatar
Claudio_Veronez
Level 6
16 years ago

NetBackup MSSQL not truncating log

Hello,

I'm running NB log policy over several mssql servers,

I'm having some problem because after log backup, the log is not truncated and I'm getting some space problems.

NB 6.5.3 
MSSQL client OK   6.5.3
files      OK
online  OK
diff        OK
full        OK
Log      OK  (but not truncate the log)

Does anyone had these problem?

Thanks.



7.1.x and Earlier
Agents
Backup and Recovery
Basics
Configuring
Database
NetBackup
  • Mouse's avatar
    Mouse
    16 years ago

    NetBackup for SQL Server completes successful (Status 0) backups and truncates SQL transaction logs but the amount of physical space on the SQL Server hard drive allocated to the transaction log does not decrease.

    http://seer.entsupport.symantec.com/docs/263890.htm


    3RD PARTY: Despite backing up and truncating the Microsoft SQL Server transaction logs with NetBackup, the size of the transaction log on the SQL server's hard disk drive does not get any smaller.


    http://seer.entsupport.symantec.com/docs/263631.htm

    This behavior is normal, and is the result of how SQL handles its transaction logs.  

  • Claudio_Veronez's avatar
    Claudio_Veronez
    Level 6
    16 years ago
    Man. you R greate, I 'll read it all

    I 'll test it and send the results here..


    THANKS A LOT



  • Mouse's avatar
    Mouse
    Moderator
    16 years ago

    NetBackup for SQL Server completes successful (Status 0) backups and truncates SQL transaction logs but the amount of physical space on the SQL Server hard drive allocated to the transaction log does not decrease.

    http://seer.entsupport.symantec.com/docs/263890.htm


    3RD PARTY: Despite backing up and truncating the Microsoft SQL Server transaction logs with NetBackup, the size of the transaction log on the SQL server's hard disk drive does not get any smaller.


    http://seer.entsupport.symantec.com/docs/263631.htm

    This behavior is normal, and is the result of how SQL handles its transaction logs.  

  • Claudio_Veronez's avatar
    Claudio_Veronez
    Level 6
    16 years ago
    I'll run today the backup and activate de log.


    I'll send it here tomorrow.

    That is crazy I'm trying end the MSSQL dude is telling me that there is nothing about truncate.


    Thakns for the help.
  • Mouse's avatar
    Mouse
    Moderator
    16 years ago
    Well, it can mean that problem is actually on SQL side and your backup is working properly.
    Ask your DBA to check why MSSQL does not truncate its log.
  • rj_nbu's avatar
    rj_nbu
    Level 6
    16 years ago
     
    You need to run DBCC SHRINKDATABASE or DBCC SHRINKFILE command in Query Analyzer (SQL Server) to reduce the PHYSICAL size of the log file.
     
    Netbackup backs up and truncates ONLY the logical part of the transaction log file, but the Actual shrinking part has to be done on the database itself.
     
     
    Here is a MSFT article explaining the process:
     
     
     
     

    Relevant snippet from the MSFT Article 873235:
     
    Shrink the transaction log file

    The backup operation or the Truncate method does not reduce the log file size. To reduce the size of the transaction log file, you must shrink the transaction log file. To shrink a transaction log file to the requested size and to remove the unused pages, you must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE Transact-SQL statement can only shrink the inactive part inside the log file.

    http://support.microsoft.com/kb/873235


    And, here is a technote as well: