Does NMM2.4 Support SQL Truncate Log?

Question

Dears: I test the NMM 2.4 by using SQL 2005 、SQL 2008 and SQL 2012. Backup command is nsrsqlsv -T or nsrsqlsv -G. Only SQL 2005 can work with truncate only and no log. It looks NMM 2.4 not support truncate log on SQL 2008 and SQL2012. Please give me a suggestion for truncate log before backup. Thanks. BR Danny SQL 2008 & SQL 2012 are messages as below: savegrp: suppressed 8 lines of output.53085 1345785546 1 0 0 2248 1744 0 sql-2 (pid1744) 27 Backing up of %s succeeded. 1 0 6 master70857 1345785546 2 0 0 2248 1744 0 sql-2 (pid1744) 73 The -T option will be ignored, TRUNCATE_ONLY is not supported in SQL 2008 053085 1345785548 1 0 0 2248 1744 0 sql-2 (pid1744) 27 Backing up of %s succeeded. 1 0 5 model70857 1345785548 2 0 0 2248 1744 0 sql-2 (pid1744) 73 The -T option will be ignored, TRUNCATE_ONLY is not supported in SQL 2008 053085 1345785548 1 0 0 2248 1744 0 sql-2 (pid1744) 27 Backing up of %s succeeded. 1 0 4 msdb43709 1345785550 1 0 0 2248 1744 0 sql-2 (pid1744) 13 Stop time: %s 1 35 25 Fri Aug 24 13:19:10 2012 The -T option will be ignored, TRUNCATE_ONLY is not supported in SQL 2008 savegrp: suppressed 11 lines of output.53085:(pid 4428):Backing up of ReportServer succeeded.70858:(pid 4428):The -G option will be ignored, NO_LOG is not supported in SQL 200853085:(pid 4428):Backing up of ReportServerTempDB succeeded.70858:(pid 4428):The -G option will be ignored, NO_LOG is not supported in SQL 200853085:(pid 4428):Backing up of master succeeded.70858:(pid 4428):The -G option will be ignored, NO_LOG is not supported in SQL 200853085:(pid 4428):Backing up of model succeeded.70858:(pid 4428):The -G option will be ignored, NO_LOG is not supported in SQL 200853085:(pid 4428):Backing up of msdb succeeded.43709:(pid 4428):Stop time: Fri Aug 24 13:45:12 2012

CarlosRojas · Accepted Answer

Hi Danny,

In order to truncate the logs you just need to run an incremental backup, no need for the -T option.

When running incremental backup with the nsrsqlsv command, and set level to incremental then only TLogs will be backed up and, if you have the SQL DB's in Full recovery mode then the logs will be automatically truncated after a successful incremental backup.

Please let me know if you need any further information.

Thank you.

Carlos.

Vincent01011 · Answer

Dear Carlos: Thanks for your kindly reply and give more informations for me. I follow your tip to setup the backup job,and will monitor it for a few days. Thanks a lot. BR Danny

ble1 · Answer

Truncate calls in SQL are actually not recommended by MS.  Having normal TLOG backup will address your issue.

NetWorker

Was this post helpful?