Forum Discussion

Claudio_Veronez's avatar
Claudio_Veronez
Level 6
15 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
    15 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.  

19 Replies

Sort By
  • Mouse's avatar
    Mouse
    Moderator
    15 years ago
    Check your script once again.

    Follow this article and make sure that you have "- "Backup and truncate transaction log" backs up and truncates the transaction logs." selected

    DOCUMENTATION: Step-by-step configuration of NetBackup 6.0 for SQL 2000/2005 transaction log backups
    http://seer.entsupport.symantec.com/docs/287788.htm
  • Claudio_Veronez's avatar
    Claudio_Veronez
    Level 6
    15 years ago
    The problem is..

    that was the first thing I look for.

    I tried to run from de client (not save, exec etc.)

    I 've selected "Backup and truncate transaction log" 

    Ahhh..

    thanks a lot.


  • Mouse's avatar
    Mouse
    Moderator
    15 years ago
    If it works - let everyone know what was the solution
  • Claudio_Veronez's avatar
    Claudio_Veronez
    Level 6
    15 years ago

    The MSSQL dude here told me that he will need to run a script for shrink right after the backup end.

    If I ĺl have to use a script I can truncate after that too...

    that is correct?


  • Claudio_Veronez's avatar
    Claudio_Veronez
    Level 6
    15 years ago

    Ahh thanks Mouse.

    I've just tested the log.. and no truncating a at all.

    what else should it be? maybe something about the mssql?

  • Mouse's avatar
    Mouse
    Moderator
    15 years ago
    You have to use either backup - MSSQL built-it or NetBackup but not both of them.

    Otherwise you will not be able to recover your database! (check this article)
    http://seer.entsupport.symantec.com/docs/241513.htm
    This problem occurs because some software other than NetBackup, including the native SQL backup utility, has backed up and truncated the transaction logs.  To restore the database, either restore only the full backup and any transaction logs prior to the other software's backup and truncate, or restore only the full backup.  

    However if your shrink operation does not touch transaction logs, it's ok


  • Mouse's avatar
    Mouse
    Moderator
    15 years ago
    When you running your job from the NBU for MSSQL client gui you can see progress there.

    By the way, when was your last full backup?