As far as I know, once the db backup completes, the log utilization should
be clean to zero. But in the activity log, I did find it was not true. Can
anybody tell me why? Thanks in advance.
07/11/06 05:07:00 ANR0984I Process 391 for DATABASE BACKUP started in
the
BACKGROUND at 05:07:00. (PROCESS:
391)
07/11/06 05:07:00 ANR4552I Full database backup triggered; started
as
process 391. (PROCESS:
391)
07/11/06 05:15:55 ANR4550I Full database backup (process 391)
complete,
4216422 pages copied. (PROCESS:
391)
07/11/06 05:15:55 ANR0985I Process 391 for DATABASE BACKUP running in
the
BACKGROUND completed with completion state SUCCESS
at
05:15:55. (PROCESS:
391)
07/11/06 05:15:55 ANR4556W Attention: the database backup operation
did not
free sufficient recovery log space to lower
utilization
below the database backup trigger. The recovery
log size
may need to be increased or the database backup
trigger
parameters may need to be adjusted.
07/11/06 05:16:06 ANR2997W The server log is 80 percent full. The
server
will delay transactions by 3 milliseconds.
(SESSION:
12862)
*The first trigger, after db backup completed, the log was still 80% FULL.*
...............................................
The second trigger, after db backup completed, the log was still 25% FULL
07/11/06 06:28:13 ANR0984I Process 394 for DATABASE BACKUP started in
the
BACKGROUND at 06:28:13. (PROCESS:
394)
07/11/06 06:28:13 ANR4552I Full database backup triggered; started
as
process 394. (PROCESS: 394)
07/11/06 06:39:27 ANR4550I Full database backup (process 394)
complete,
4338380 pages copied. (PROCESS:
394)
07/11/06 06:39:27 ANR0985I Process 394 for DATABASE BACKUP running in
the
BACKGROUND completed with completion state SUCCESS
at
06:39:27. (PROCESS:
394)
07/11/06 06:39:27 ANR2996I The server log is 25 percent full. The
server is
no longer delaying transactions. (SESSION: 12957)
