Thanks for your help . Regarding the nmsql document i create the backup command like this " nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL -R -H MSSQL:ABT " i have 8 gb tlogs in sql server and i expect that the backup only this 8 gb but the job runs 15 min. and backup 40gb data so it is not backing up only trans backups. Am i clear enough ? the command can not run as expected.
-R uses the NO_TRUNCATE option when backing up transaction logs, don't you want to truncate the logs?
-H uppercase -H uses the NORECOVERY option when backing up transaction logs. It leaves the database in Restoring state. Do you really want to leave the DB in that status?
You can check, once the backup completes, open NMSQL GUI and see what has been backed up.
the -h is used to skip specified DB, is not to skip DB and backup logs, so if you run -h DB_NAME that DB will be skipped in the backup, as well as its logs.
so what is the correct arrangement this is the last version of my backup command " nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL -h MSSQL:ABT " and still backing up all database
Incremental backups will backup ONLY the TLogs of SQL DB so, having this say I would suggest you to:
1.- Configure a client entry in NetWorker server for SQL client
2.- Configure a group, or include that client in a group with schedule full+Incrementals as you wish
3.- Run a backup (first one will be full) and then run a second one incremental level, or either check the box for the group configuration "Force Incremental". This backup should be incremental and backup ONLY the logs.
Running manual backup from command line can lead to this situation, NetWorker server not tracking the indexes hence all backups are being promoted to full.
Please try this option, it HAS TO WORK.
Hold on, how do you have the SQL DB configured? Is it Simple mode, full mode or bulk mode?
Please refer to the documentation for more information. You have to configure the DB in full mode.
ok here is the offical answer from emc networker engineer:
There is not such thing in Networker as transaction log backup
i am give up .
It would be interesting to see entire question and answer.
Anyway, as pointed out so far, you can do that though I do not see the point. First backup has to be full and it will backup database. This is simple MS requirement. Each time you make backup of DB outside NW transaction log backup will be also promoted to full DB backup too (again, this is SQL mechanism which keeps track of consistency). You can run from there only transaction logs, but I see no point of such approach. In case of restore, you would need to restore quite alot. If transaction logs are not needed, simply turn database model to simple then.
In workflow frequency you set it to run every 15 minutes. You use same module (NMM) for all SQL backups (DB and TLOG) where level of the backup determines the action performed.
we had been running nsrsqlsv -o with the saveset of mssql: on one SQL server to truncate logs at noon of every day. But after upgrading our server to v9.1, and the client and NMM module on this server to v9.1, the error that appears is:
157931:(pid 9988):Backup level 'mssql:' is obsolete. Change the backup level to logs only and restart the backup.
how do I modify the client to continue to truncate the logs ?
CarlosRojas
1.7K Posts
0
May 16th, 2012 21:00
Hello,
Yes indeed, with NMSQL you can only backup the transaction log, but not with NMM 2.3
I would suggest you to take a look at NMSQL documentation.
Anyway you have to bear in mind that, in order to have incremental or differential backups you will ALWAYS need a full backup
For TLogs there is some specific options though, pretty clearly defined in NMSQL docs.
Note that NMM 2.3 only supports full backups, so only NMSQL would be your option here.
Thank you.
Carlos.
ahmetkececiler
68 Posts
0
May 17th, 2012 06:00
Thanks for your help . Regarding the nmsql document i create the backup command like this " nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL -R -H MSSQL:ABT " i have 8 gb tlogs in sql server and i expect that the backup only this 8 gb but the job runs 15 min. and backup 40gb data so it is not backing up only trans backups. Am i clear enough ? the command can not run as expected.
ahmetkececiler
68 Posts
0
May 17th, 2012 06:00
Yes you are right i dont need -R and i have to use -h not -H i am trying now.
CarlosRojas
1.7K Posts
0
May 17th, 2012 06:00
Hi,
Remember that first backup will be always full.
Why are you using the -R and -H?
-R uses the NO_TRUNCATE option when backing up transaction logs, don't you want to truncate the logs?
-H uppercase -H uses the NORECOVERY option when backing up transaction logs. It leaves the database in Restoring state. Do you really want to leave the DB in that status?
You can check, once the backup completes, open NMSQL GUI and see what has been backed up.
Thank you.
Carlos.
CarlosRojas
1.7K Posts
0
May 17th, 2012 07:00
Hi,
the -h is used to skip specified DB, is not to skip DB and backup logs, so if you run -h DB_NAME that DB will be skipped in the backup, as well as its logs.
Thank you.
Carlos
ahmetkececiler
68 Posts
0
May 18th, 2012 07:00
so what is the correct arrangement this is the last version of my backup command " nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL -h MSSQL:ABT " and still backing up all database
CarlosRojas
1.7K Posts
0
May 21st, 2012 05:00
Hi,
If you run this command twice the first time should run full (DB+TLogs) and the second time should run incremental (Only TLogs).
If this doesn't work try the same from NetWorker server.
Command to run, for all DB's:
nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL MSSQL:
If you want to exclude Model and Master DB's then run:
nsrsqlsv -s 34istemcnwbck -l incr -b SAPPOOL -h model -h master MSSQL:
The name of the DB you want to exclude is like that, no need to add MSSQL:DB_NAME
Thank you.
Carlos.
ahmetkececiler
68 Posts
0
May 22nd, 2012 03:00
ok here is the offical answer from emc networker engineer:
There is not such thing in Networker as transaction log backup
i am give up .
CarlosRojas
1.7K Posts
1
May 22nd, 2012 05:00
Hi,
I don't agree with that answer, I'm sorry.
Incremental backups will backup ONLY the TLogs of SQL DB so, having this say I would suggest you to:
1.- Configure a client entry in NetWorker server for SQL client
2.- Configure a group, or include that client in a group with schedule full+Incrementals as you wish
3.- Run a backup (first one will be full) and then run a second one incremental level, or either check the box for the group configuration "Force Incremental". This backup should be incremental and backup ONLY the logs.
Running manual backup from command line can lead to this situation, NetWorker server not tracking the indexes hence all backups are being promoted to full.
Please try this option, it HAS TO WORK.
Hold on, how do you have the SQL DB configured? Is it Simple mode, full mode or bulk mode?
Please refer to the documentation for more information. You have to configure the DB in full mode.
Thank you.
Carlos.
ble1
4 Operator
•
14.4K Posts
0
May 28th, 2012 04:00
It would be interesting to see entire question and answer.
Anyway, as pointed out so far, you can do that though I do not see the point. First backup has to be full and it will backup database. This is simple MS requirement. Each time you make backup of DB outside NW transaction log backup will be also promoted to full DB backup too (again, this is SQL mechanism which keeps track of consistency). You can run from there only transaction logs, but I see no point of such approach. In case of restore, you would need to restore quite alot. If transaction logs are not needed, simply turn database model to simple then.
abhinet
2 Posts
0
June 12th, 2017 02:00
How to configure SQL transaction logs backup for every 15 minutes.
Networker server :- 9.1 and client Version :- 8.2
is there any Need to install separate module for transaction logs ??
abhinet
2 Posts
0
June 12th, 2017 02:00
How to configure SQL transaction logs backup for every 15 minutes.
Networker server :- 9.1 and client Version :- 8.2
ble1
4 Operator
•
14.4K Posts
0
June 20th, 2017 05:00
In workflow frequency you set it to run every 15 minutes. You use same module (NMM) for all SQL backups (DB and TLOG) where level of the backup determines the action performed.
mpezeur
40 Posts
0
July 28th, 2017 05:00
we had been running nsrsqlsv -o with the saveset of mssql: on one SQL server to truncate logs at noon of every day. But after upgrading our server to v9.1, and the client and NMM module on this server to v9.1, the error that appears is:
157931:(pid 9988):Backup level 'mssql:' is obsolete. Change the backup level to logs only and restart the backup.
how do I modify the client to continue to truncate the logs ?
ble1
4 Operator
•
14.4K Posts
0
September 4th, 2017 07:00
Change backup level. You probably use schedule called mssql and you should apply logs only.