|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > transaction log backup problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
transaction log backup problem
|
|
| David 2002-11-06, 11:24 am |
| I checked and indeed the databases are set to "simple"
instead of "full". What other effects would changing this
setting cause?
This database is critical to our business and I don't want
to change anything that may have negative effects or cause
downtime.
Thanks for your help! I appreciate it.
-David Price
>-----Original Message-----
>Check the Database options settings through properties.
>Make sure that 'Truncate log on checkpoint' is checked
off
>(SQL Server 7.0) or 'Full' recovery mode is selected (SQL
>Server 2000).
>
>
>
>
>>-----Original Message-----
>>I am in charge of maintaining a SQL server with about 40
>>databases. The one or two databases that are absolutely
>>critical are in use all the time. The transaction log
>>backups are failing every time. full backups seem to
work
>>just fine. Can anyone tell me what I may need to do to
>the
>>database to allow the transaction logs to run?
>>
>>The transaction-log backup log:
>>Microsoft (R) SQLMaint Utility (Unicode), Version Logged
>>on to SQL Server 'SQL' as 'sa' (non-trusted)
>>Starting maintenance plan 'DB Maintenance Plan' on */2002
>>Backup can not be performed on database 'xxxx'. This sub
>>task is ignored.
>>
>>Thanks,
>>David Price
>>.
>>
>.
>
| |
| Flicker 2002-11-06, 3:23 pm |
| If it is SIMPLE then you can't do trans. backup.
If you think the database is critical you must do log backup, unless you can
live with the fact that the latest restore you can do is from the last full
backup. Anything after that is gone.
"David" <davidp@blackhole.com> wrote in message
news:52e701c285b7$ac58df10$39e
f2ecf@TKMSFTNGXA08...
> I checked and indeed the databases are set to "simple"
> instead of "full". What other effects would changing this
> setting cause?
>
> This database is critical to our business and I don't want
> to change anything that may have negative effects or cause
> downtime.
>
> Thanks for your help! I appreciate it.
> -David Price
>
> >-----Original Message-----
> >Check the Database options settings through properties.
> >Make sure that 'Truncate log on checkpoint' is checked
> off
> >(SQL Server 7.0) or 'Full' recovery mode is selected (SQL
> >Server 2000).
> >
> >
> >
> >
> >>-----Original Message-----
> >>I am in charge of maintaining a SQL server with about 40
> >>databases. The one or two databases that are absolutely
> >>critical are in use all the time. The transaction log
> >>backups are failing every time. full backups seem to
> work
> >>just fine. Can anyone tell me what I may need to do to
> >the
> >>database to allow the transaction logs to run?
> >>
> >>The transaction-log backup log:
> >>Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> >>on to SQL Server 'SQL' as 'sa' (non-trusted)
> >>Starting maintenance plan 'DB Maintenance Plan' on */2002
> >>Backup can not be performed on database 'xxxx'. This sub
> >>task is ignored.
> >>
> >>Thanks,
> >>David Price
> >>.
> >>
> >.
> >
|
|
|
|
|