SQL by default will promote incr to full whenever it finds that some other tool has done backup too of the database. This mechanism exists to make sure there is consistency. Check if there is schedule backup within SQL itself. Also, check if this happens after file system backup has run (in yes, try to disable SQL writer).
i just confuse about the last part of your message..we do not backup the file system.only the database.
thanks.
You can then ignore that part (in the past under certain conditions fs backup of the machine would trigger SQL Writer and the would trigger next SQL transaction log to be full DB backup - it was an issue which got fixed since long time, but you never said what your client version and module were nor if you have file system backup enabled too).
ble1
4 Operator
•
14.4K Posts
2
May 23rd, 2014 18:00
SQL by default will promote incr to full whenever it finds that some other tool has done backup too of the database. This mechanism exists to make sure there is consistency. Check if there is schedule backup within SQL itself. Also, check if this happens after file system backup has run (in yes, try to disable SQL writer).
ranstorm
1 Rookie
•
45 Posts
0
May 23rd, 2014 19:00
yah, you are right..there is another job that backup the mssql database..ill try to disable it..
i just confuse about the last part of your message..we do not backup the file system.only the database.
thanks.
ble1
4 Operator
•
14.4K Posts
1
May 24th, 2014 03:00
You can then ignore that part (in the past under certain conditions fs backup of the machine would trigger SQL Writer and the would trigger next SQL transaction log to be full DB backup - it was an issue which got fixed since long time, but you never said what your client version and module were nor if you have file system backup enabled too).
ranstorm
1 Rookie
•
45 Posts
0
May 25th, 2014 18:00
hi Hrvoje Crvelin, i got now incremental backup after disabling another running backup in the jobber..i just need to monitor this for few days.thanks.