Unsolved
This post is more than 5 years old
27 Posts
0
3053
August 7th, 2014 23:00
SQL Incremental backups are promoting to full
Hi,
We have Networker 8.x backup server and taking backup of SQL databases. Some of the SQL Hourly incremental backups (transaction log) are promoting to full with the below message.
Mar 21 00:04:23 :MSSQL:config 37785:(pid 3836):Last backup of database 'config' was not created using NMSQL Module.
Mar 21 00:04:23 MSSQL:config Promoting the backup level to full. NSR_BACKUP_LEVEL: full;
SQL DBA has native SQL backups configured in addition to Networker online backups.
Does anyone know what could be the reason why it is promoting to full? Can native SQL backups affect Networker backups?
Thanks
Sreekanth
Fenglin1
4 Operator
•
2.1K Posts
0
September 17th, 2014 01:00
Hi Sreedama,
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "Networker Support Forum" which would be the most relevant for this question.
crazyrov
4 Operator
•
1.3K Posts
1
September 18th, 2014 03:00
Sreedama,
Yes the any other backups(might be maintenance jobs or any other 3rd party tools) other than NetWorker affect the incremental backups. The backups are forcefully promoted fully if NetWorker detects a backup from other than itself done on the same SQL instance.
ShubhamMishra
40 Posts
0
September 19th, 2014 08:00
Hi Sreekanth
What is the recovery mode of the MSSQL database.
If this is set to Simple recovery model from database end, then all Networker MSSQL online backups shall be full.
SQL DBA need to put the database in Full recovery mode, then Networker Online module for MSSQL Backup shall be able to take the incremental backups.
Thanks
ble1
4 Operator
•
14.3K Posts
0
September 19th, 2014 10:00
The message is quite clear - the solution too - see what crazyrov said.
Sreedama
27 Posts
0
September 22nd, 2014 09:00
Hi all,
Thanks for your reply. Database recovery is model is set to full. As per the DBA, the native SQL backups are done as "copy only" that should not change LSN numbers. Why Netwoker has to promote the backup to full when LSN is not changed. Can someone provide the technical details about this behaviour? This is the question from customer and they states Networker logic has to be changed to ignore "copy only" backups as it is not affecting LSN number. please suggest.
Thanks
Sreekanth
ble1
4 Operator
•
14.3K Posts
0
September 22nd, 2014 11:00
I don't know the details, but if I had to guess, I would say that NW doesn't check LSN if it is changed or not, but rather if previous backup is owned by NW or not. If NW is not "author" it assume it has to run full ignoring options likes Copy-Only scenarios. If so, NMM would need to check also is_copy_only flag and that might not be the case. Pure guess from my side so I would suggest to open a ticket with official support and engineering.