Unsolved

This post is more than 5 years old

27035

January 7th, 2009 15:00

How do I backup MS SQL databases and their transaction logs with Networker

How do I properly backup MS SQL databases and their transaction logs with Networker?

I'm currently running scheduled daily backups with Networker using the "nsrsqlsv.exe -T" backup command. The SQL server's dbs are set to 'Full' for their recovery model.

This seems to back up all the databases, but Enterprise manager reports that the transaction logs aren't backed up. I have to use NTbackup in order to see the logs being backed up.

How do I setup Networker to backup all the SQL databases and their transaction logs?
Should I be using the "nsrsqlsv.exe -R" command in conjunction with the "nsrsqlsv.exe -T" command?

4 Operator

 • 

14.3K Posts

June 18th, 2015 00:00

Yes.

2 Intern

 • 

136 Posts

June 20th, 2015 10:00

In my case, I am doing incremental backup for weekdays. But still Transactional logs are not getting cleaned up.

Means, it not archiving.. right?

4 Operator

 • 

14.3K Posts

June 20th, 2015 11:00

TLOG lives in single file and that file grows unless you do TLOG backup.  When TLOG backup is made, file won't shrink, but rather SQL will reuse the space in existing file.  To shrink the file, you must truncate it from SQL itself.  Check MS SQL pages which have details on this.

2 Intern

 • 

136 Posts

June 20th, 2015 12:00

I am not able to get your points.

If I do TLOG backup, the file size will not grow. But again in second point, I am confused again. asking me to do truncate the TLOG file from SQl?

Can you get me to the doc, if possible?

4 Operator

 • 

14.3K Posts

June 20th, 2015 13:00

Yes... so, TLOG lives in some file X.  This file will grow as transaction are committed.  When you do TLOG backup, transaction in file X are marked as backed up and space they have been using will be reused (overwritten) by new transactions.  If there are more transactions than current size of X, it will grow.  If you wish to shrink it, the way it is done these days, is to place DB into simple model and then truncate it.  Then put it back into full recovery model and do DB backup and have those TLOG backups running.  I personally run them every 1h 24/7.

2 Intern

 • 

136 Posts

June 20th, 2015 15:00

Perfect.. Let me try this.. So grateful..

No Events found!

Top