Even worse, the transaction log of this database has grown to such a size
that any action on the database gives an error saying that the transaction
log is full. Even attempts to expand or add to the transaction logs gives
this error. The sys.databases table for the database says that the reason
why the transaction log cannot be reused is 2 - backup.
backup log <database_name> with no_log will clear the log. try a
backup to disk using the native SQL tools and then DPM again
--
Thanks,
C.Prashanth [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
"Alen Teplitsky" <alen...@gmail.com> wrote in message
news:9e79d6f4-3993-4ba4...@m3g2000yqf.googlegroups.com...
Have you scheduled incremental backups for the concerned database? By taking
log backups, the incremental backups at regular intervals will make sure
that logs get truncated.
Thanks,
Hitesh Sharma [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.
Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm
"Innovations" <Innov...@discussions.microsoft.com> wrote in message
news:854176B5-5309-47ED...@microsoft.com...