Re: Backup Exec cancel job pruning logs?
- From: UselessUser <UselessUser@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Aug 2008 01:07:01 -0700
Hi,
I cancelled it approx 15 minutes in to the job whilst it was backing up the
stores I believe... in Backup Exec, I have the backup method set as Full -
Database and logs (Flush committed logs), and enable the restore of
individual mail messages and folders from the information store backup (Which
I assume is the brick method, I thought this was called Granular Restore or
something?)...
I have just checked the logs on the box vs what was backed up on the tape
and it looks like it has done the "sensible" thing, ie successfully backed up
a store then truncated its committed log files, I found it confusing because
I stopped the backup in between store backup so whilst we have 4 stores I
cancelled it after the 2nd store, hence only 2 stores had their logs
truncated.
My final weird issue is that this whole problem basically came about as our
Exchange backup is set to start at 00:00, and there was no tape in the drive,
I put one in at 15:00 yesterday for the midnight backup of Tuesday, and lo
and behold it started backing up to it. I had to cancel this job. Now when I
look at the logs on Tuesday at - EDIT I have just rechecked everything and it
all now makes sense!
So in the backup process, are the logs pruned after succesful backup of the
store, or before?
"Mark Arnold [MVP]" wrote:
On Tue, 26 Aug 2008 08:25:02 -0700, UselessUser.
<UselessUser@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
We have backup exec 11d with the remote exchange agent on our 2k3 Sp2 server.
I had to cancel a backup job, and when I did this and reviewed the log file
on the Exchange server, I noticed several logs relating to the shadow copy
including a 224 log telling me its deleting log files, followed by a 9616
event id stating that log truncation is succesful?
Is this a problem considering I am actually cancelling the backup? Or does
it mean that these log files have already been comitted to the database (as
in the checkpoint file has gone past them) and they are subsequently not
needed for backup/roll forward?
In which case if my exchange databases were to die right now, I could not in
fact restore the database from last night and roll forward because it has
deleted some necessary log files?
Almost sounds like you are running the IS level and then the Bricks
level. If BE thinks the IS level is secured and OK it certainly will
truncate. At what point did you cancel and were you running an IS,
Bricks or both?
- References:
- Re: Backup Exec cancel job pruning logs?
- From: Mark Arnold [MVP]
- Re: Backup Exec cancel job pruning logs?
- Prev by Date: Re: admin rights to mailboxes
- Next by Date: Appropriate changes for Message size limits
- Previous by thread: Re: Backup Exec cancel job pruning logs?
- Next by thread: Exchange 2007 > mailbox security group question
- Index(es):
Relevant Pages
|
