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

Question

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?

dpinink_silva · Answer

If you are running full everyday, have you tried to run an incremental backup? This should backup the transaction logs.

mtaylor-lfcu.co · Answer

Do I run the incremental job using the 'nsrsqlsv.exe -T' command? With some other switch or no switch at all?

amediratta · Answer

You can create the schedule for incremental for the day and apply the schedule on the client/group resource.

mtaylor-lfcu.co · Answer

Yes, but what about the switch for the nsrsqlsv.exe? Do I need a switch or not? If so which one?

amediratta · Answer

-T is meant only for Full backups. -R woul backup transaction logs in a NO_TRUNCATE mode. for levels, -l is the option but to be used only if you are running a client-initiated backup using the command line.

You can set incremental backup for SQL which backs up all transaction log changes since the last full, differential or transactional log backup. For SQL 2005, EMC also suggests using -H to backup transaction logs prior to database restore or primary filegroup restore.

Tomi · Answer

I myself use a 3 group system for backuping MS SQL databases and transaction logs. One for full (in which I do 2 incr backups after the full), incr and diff which are run on different days. As for the backup command I use the savepnpc since I want to shrink the transaction logs after the backups are done and as for the backup command inside the scripts I use "nsrsqlsv.exe -l level -b pool MSSQL:" and osql command to shrink.

This has worked for me but there might be other "easier" ways to do it.

dgreggs1 · Answer

Dont use the switch, just the command. If you have not done so already create two schedules, one for Full's and one for Incremental aka Tlog to SQL. Create at least two clients for your SQL backups. On client A, select "Full" as the backup level, "MSSQL:" as the saveset and "nsrsqlsv" as the Backup Command.

When the backup starts Networker builds the environment for the job. It reads all the properties of the client and the group that the client is in to build the backup command.

Read the app log and you can see how this is done.

FlyEagles · Answer

When you specify -T, it means truncate the logs hence it runs a full backups. I wouldn't use any flags at all and just let the Schedule take care of the backup level, Incremental backup will only backup Tlogs. Also, if you run any NTbackups in between, Legato loses track of the transaction logs and it forces a full backup so, make sure you are only using one application for backup.

HTH

thstein · Answer

Hi,you can set the 'force incremental' flag in the group definition and set the interval time.The first backup in the 24h interval is the scheduled backup, the other backups are incremental.thorsten

col999 · Answer

New to the Networker SQL module (NSM),

but just to confirm that if NSM is doing a Full backup @ 1800 after a SQL Maintenance Plan (SQLMP) completes a Full bkup @ 1600, then every hour, the SQLMP does a Trn Bkup, then the backups are going to be out of sync for restore purposes

Would I be correct in saying that if you had to restore @ 2200 after the NSM backup you would have to use the NSM and then the Trn Logs from the SQLMP? Appreciate any feedback

joka2 · Answer

Has this been answered? I was reading through and I don't fine the conclusion.

I'm having problem doing small incremental backups of some SQL servers with NMSQL 5.2, but not all. The recovery model is always Full, and no other backup application is interfering NetWorker.

In one case, the incremental bakcup is always 14GB, but level 1 backup with nsrsqlsv is only 300MB.

Should level 1 backup (differential) be used instead of Incremental?

regards,

Johannes

ble1 · Answer

joka wrote:Has this been answered? I was reading through and I don't fine the conclusion.I'm having problem doing small incremental backups of some SQL servers with NMSQL 5.2, but not all. The recovery model is always Full, and no other backup application is interfering NetWorker.In one case, the incremental bakcup is always 14GB, but level 1 backup with nsrsqlsv is only 300MB.Should level 1 backup (differential) be used instead of Incremental?regards,Johannes Level backup goes against database.  Incremental is doing transaction logs.

tsamuel0905 · Answer

Incremental will do transaction logs backup. That's fine. Do i need to alter command? Anyway to archive the logs? Many Thanks, Samuel Thomas

ble1 · Answer

No, schedule is enough.

tsamuel0905 · Answer

Archiving the logs?

NetWorker

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

Was this post helpful?