Backup Error - SQL 2005

Hi there!
I just posted a question about my Backup Plan 2005 SQL and I got very good
answers!, but now, I'm getting other problem, I'm checking the event viewer
and I see this error 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"
- I'm using Management Studio to configure the backups
- All my databases are Full Recovery Model.
- I run Full Backup of my databases every day. (1:00am)
- I run every 15 minutes backup of the LOG files
I read something on the MS website (KB 818202) and they say :
"This warning message may be logged because the NO_LOG and TRUNCATE_ONLY
options of the BACKUP statement truncate the transaction log files, and you
might need transaction logs for the full recovery of the database."
So, my doubt is:
- The error is because I'm running the backup of the logs every 15 minutes
and THAT is truncating the LOG file, so, what I have to do? When I'v created
the job on the Management Studio, I havent had the option to set "NO_LOG"
and "TRUNCATE_ONLY"...'
Can somebody give me a hand with this' please..
What I really want is recovery the full database in case something
happens...at least the most actual data...
Thanks you!
JoseCheck again the options of your log backup maintenance plan. Maybe another
administrator/job/process is doing the truncates. ¿Can you set a profiler
trace to search for "suspicious" log backups with "truncate_only" or
"no_log"?
--
Rubén Garrigós
Solid Quality Mentors
"Jose" <Jose@.discussions.microsoft.com> wrote in message
news:293D0F53-7004-4889-AF52-396116DDCF07@.microsoft.com...
> Hi there!
> I just posted a question about my Backup Plan 2005 SQL and I got very good
> answers!, but now, I'm getting other problem, I'm checking the event
> viewer
> and I see this error 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"
> - I'm using Management Studio to configure the backups
> - All my databases are Full Recovery Model.
> - I run Full Backup of my databases every day. (1:00am)
> - I run every 15 minutes backup of the LOG files
> I read something on the MS website (KB 818202) and they say :
> "This warning message may be logged because the NO_LOG and TRUNCATE_ONLY
> options of the BACKUP statement truncate the transaction log files, and
> you
> might need transaction logs for the full recovery of the database."
> So, my doubt is:
> - The error is because I'm running the backup of the logs every 15 minutes
> and THAT is truncating the LOG file, so, what I have to do? When I'v
> created
> the job on the Management Studio, I havent had the option to set "NO_LOG"
> and "TRUNCATE_ONLY"...'
> Can somebody give me a hand with this' please..
> What I really want is recovery the full database in case something
> happens...at least the most actual data...
> Thanks you!
> Jose|||I fully agree. *Somebody* is doing BACKUP LOG dbname WITH TRUNCATE_ONLY (or NO_LOG). You need to
hunt that down.
A regular log backup (where you actually do a backup) will not produce that message in the event
log.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Rubén Garrigós" <novalidaddress@.none.com> wrote in message
news:A6546FF2-01BB-48C4-BBDA-535B58B89019@.microsoft.com...
> Check again the options of your log backup maintenance plan. Maybe another
> administrator/job/process is doing the truncates. ¿Can you set a profiler trace to search for
> "suspicious" log backups with "truncate_only" or "no_log"?
> --
> Rubén Garrigós
> Solid Quality Mentors
> "Jose" <Jose@.discussions.microsoft.com> wrote in message
> news:293D0F53-7004-4889-AF52-396116DDCF07@.microsoft.com...
>> Hi there!
>> I just posted a question about my Backup Plan 2005 SQL and I got very good
>> answers!, but now, I'm getting other problem, I'm checking the event viewer
>> and I see this error 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"
>> - I'm using Management Studio to configure the backups
>> - All my databases are Full Recovery Model.
>> - I run Full Backup of my databases every day. (1:00am)
>> - I run every 15 minutes backup of the LOG files
>> I read something on the MS website (KB 818202) and they say :
>> "This warning message may be logged because the NO_LOG and TRUNCATE_ONLY
>> options of the BACKUP statement truncate the transaction log files, and you
>> might need transaction logs for the full recovery of the database."
>> So, my doubt is:
>> - The error is because I'm running the backup of the logs every 15 minutes
>> and THAT is truncating the LOG file, so, what I have to do? When I'v created
>> the job on the Management Studio, I havent had the option to set "NO_LOG"
>> and "TRUNCATE_ONLY"...'
>> Can somebody give me a hand with this' please..
>> What I really want is recovery the full database in case something
>> happens...at least the most actual data...
>> Thanks you!
>> Jose
>|||You may want to set up a profiler trace, and filter on BACKUP in the
TextData.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:O53r9x9YIHA.1204@.TK2MSFTNGP03.phx.gbl...
I fully agree. *Somebody* is doing BACKUP LOG dbname WITH TRUNCATE_ONLY (or
NO_LOG). You need to
hunt that down.
A regular log backup (where you actually do a backup) will not produce that
message in the event
log.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Rubén Garrigós" <novalidaddress@.none.com> wrote in message
news:A6546FF2-01BB-48C4-BBDA-535B58B89019@.microsoft.com...
> Check again the options of your log backup maintenance plan. Maybe another
> administrator/job/process is doing the truncates. ¿Can you set a profiler
> trace to search for
> "suspicious" log backups with "truncate_only" or "no_log"?
> --
> Rubén Garrigós
> Solid Quality Mentors
> "Jose" <Jose@.discussions.microsoft.com> wrote in message
> news:293D0F53-7004-4889-AF52-396116DDCF07@.microsoft.com...
>> Hi there!
>> I just posted a question about my Backup Plan 2005 SQL and I got very
>> good
>> answers!, but now, I'm getting other problem, I'm checking the event
>> viewer
>> and I see this error 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"
>> - I'm using Management Studio to configure the backups
>> - All my databases are Full Recovery Model.
>> - I run Full Backup of my databases every day. (1:00am)
>> - I run every 15 minutes backup of the LOG files
>> I read something on the MS website (KB 818202) and they say :
>> "This warning message may be logged because the NO_LOG and TRUNCATE_ONLY
>> options of the BACKUP statement truncate the transaction log files, and
>> you
>> might need transaction logs for the full recovery of the database."
>> So, my doubt is:
>> - The error is because I'm running the backup of the logs every 15
>> minutes
>> and THAT is truncating the LOG file, so, what I have to do? When I'v
>> created
>> the job on the Management Studio, I havent had the option to set
>> "NO_LOG"
>> and "TRUNCATE_ONLY"...'
>> Can somebody give me a hand with this' please..
>> What I really want is recovery the full database in case something
>> happens...at least the most actual data...
>> Thanks you!
>> Jose
>|||Thank you!! all of you!
I will tracert the "suspicious" man!
Have a nice day!
Jose
"Tom Moreau" wrote:
> You may want to set up a profiler trace, and filter on BACKUP in the
> TextData.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:O53r9x9YIHA.1204@.TK2MSFTNGP03.phx.gbl...
> I fully agree. *Somebody* is doing BACKUP LOG dbname WITH TRUNCATE_ONLY (or
> NO_LOG). You need to
> hunt that down.
> A regular log backup (where you actually do a backup) will not produce that
> message in the event
> log.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Rubén Garrigós" <novalidaddress@.none.com> wrote in message
> news:A6546FF2-01BB-48C4-BBDA-535B58B89019@.microsoft.com...
> > Check again the options of your log backup maintenance plan. Maybe another
> > administrator/job/process is doing the truncates. ¿Can you set a profiler
> > trace to search for
> > "suspicious" log backups with "truncate_only" or "no_log"?
> > --
> >
> > Rubén Garrigós
> > Solid Quality Mentors
> >
> > "Jose" <Jose@.discussions.microsoft.com> wrote in message
> > news:293D0F53-7004-4889-AF52-396116DDCF07@.microsoft.com...
> >> Hi there!
> >> I just posted a question about my Backup Plan 2005 SQL and I got very
> >> good
> >> answers!, but now, I'm getting other problem, I'm checking the event
> >> viewer
> >> and I see this error 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"
> >>
> >> - I'm using Management Studio to configure the backups
> >> - All my databases are Full Recovery Model.
> >> - I run Full Backup of my databases every day. (1:00am)
> >> - I run every 15 minutes backup of the LOG files
> >>
> >> I read something on the MS website (KB 818202) and they say :
> >> "This warning message may be logged because the NO_LOG and TRUNCATE_ONLY
> >> options of the BACKUP statement truncate the transaction log files, and
> >> you
> >> might need transaction logs for the full recovery of the database."
> >>
> >> So, my doubt is:
> >> - The error is because I'm running the backup of the logs every 15
> >> minutes
> >> and THAT is truncating the LOG file, so, what I have to do? When I'v
> >> created
> >> the job on the Management Studio, I havent had the option to set
> >> "NO_LOG"
> >> and "TRUNCATE_ONLY"...'
> >>
> >> Can somebody give me a hand with this' please..
> >> What I really want is recovery the full database in case something
> >> happens...at least the most actual data...
> >>
> >> Thanks you!
> >>
> >> Jose
> >
> >
>
>