September 1, 2011 at 6:50 am
(sql2005EE sp3)
Someone just launched BACKUP LOG WITH TRUNCATE_ONLY for his database.
( I know, I shouldn't have provided dbo auth, but you know how that goes )
Apparently the default trace doesn't record this event 🙁
In the instances errorlog file it only states:
Message
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
[msdb].[dbo].[backupset] Doesn't record this breach :angry:
Of course, regular scheduled log backups fail after this event because of the lack of a valid full backup.
For now I've launched a trace to capture "audit backup/restore events", so I'll know the origin by tomorrow 😎
The question is: Where and how could I have discovered / prevented this ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply