|
|
|
date: Wed, 20 Feb 2008 11:43:52 -0800 (PST),
group: microsoft.public.exchange.clustering
back
RE: Exchange 2007 - SCR - Logs not Truncating on Target
I'm having the same issue, though only using 2 storage groups. I'd like to
achiever two things:
Truncate old logs on the SCR source server
Truncate old logs on the SCR target server
Incidentally, the source is a CCR clustered mailbox server - so in short, my
68GB mailbox database is in a folder totaling 191GB with the log files. That
191GB is then replicated twice - to the passive CCR node and to the SCR
target.
Talk about wasted disk space...
Any input?
"Paul" wrote:
> I had the same problem.
>
> We setup 1 SCR target with 14 Storage Groups. After a week I found the logs
> on the target continued to grow and grow.
>
> I manually deleted the target logs that were days and days old, and found
> they continued to accumulate.
>
> On a whim that I setup the replaylagtime or trunicate incorrectly, I stopped
> 1 of 14 storage groups from replicating to target. I then deleted target
> logs and database and started the replication over from the start, including
> re-seeding the DB.
>
> From that moment on, all 14 storage groups now trunicated logs as expected.
> Go figure?
>
>
> "braincandy@gmail.com" wrote:
>
> > I have a setup for 2 Exchange 2007 servers that are doing SCR. My
> > problem is that the Target machine is not truncating the logs, it is
> > however replaying the log file with any problems.
> >
> > I enabled SCR with the following command:
> >
> > Enable-StorageGroupCopy -identity "First Storage Group" -ReplayLagTime
> > 0.0:5:0 -TruncationLagTime 1.0:0:0 -StandbyMachine venus
> >
> > you can see that the TruncationLagTime is set to 1 Day, however it has
> > been over a week and the logs have not truncated.
> >
> > and Yes, the Source server is being backed up and having the logs
> > truncated over there. I have resorted to manually removing the older
> > log files. Should this not be automatic? Can i manually truncate
> > them? I've suspended the replication and have rebooted the target
> > machine with no luck, I have yet to do it on the source.
> >
> > Here is the current status:
> >
> > Name SummaryCopySt CopyQueueLeng ReplayQueueL
> > LastInspecte
> > atus
> > th ength dLogTime
> > ---- -------------
> > ------------- ------------ ------------
> > First Storage Group Healthy 0
> > 527 2/20/2008...
> >
> > Any help is appreciated it. Thank you
> >
date: Thu, 5 Jun 2008 13:12:02 -0700
author: Douglas
Re: Exchange 2007 - SCR - Logs not Truncating on Target
Have you taken a backup? You need to take a backup that truncates logs in
order to have truncation occur.
--
Regards,
Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
"Douglas" wrote in message
news:73D43DC2-6927-41B0-A0AD-6864D7803A73@microsoft.com...
> I'm having the same issue, though only using 2 storage groups. I'd like
> to
> achiever two things:
>
> Truncate old logs on the SCR source server
> Truncate old logs on the SCR target server
>
> Incidentally, the source is a CCR clustered mailbox server - so in short,
> my
> 68GB mailbox database is in a folder totaling 191GB with the log files.
> That
> 191GB is then replicated twice - to the passive CCR node and to the SCR
> target.
>
> Talk about wasted disk space...
>
> Any input?
>
> "Paul" wrote:
>
>> I had the same problem.
>>
>> We setup 1 SCR target with 14 Storage Groups. After a week I found the
>> logs
>> on the target continued to grow and grow.
>>
>> I manually deleted the target logs that were days and days old, and found
>> they continued to accumulate.
>>
>> On a whim that I setup the replaylagtime or trunicate incorrectly, I
>> stopped
>> 1 of 14 storage groups from replicating to target. I then deleted target
>> logs and database and started the replication over from the start,
>> including
>> re-seeding the DB.
>>
>> From that moment on, all 14 storage groups now trunicated logs as
>> expected.
>> Go figure?
>>
>>
>> "braincandy@gmail.com" wrote:
>>
>> > I have a setup for 2 Exchange 2007 servers that are doing SCR. My
>> > problem is that the Target machine is not truncating the logs, it is
>> > however replaying the log file with any problems.
>> >
>> > I enabled SCR with the following command:
>> >
>> > Enable-StorageGroupCopy -identity "First Storage Group" -ReplayLagTime
>> > 0.0:5:0 -TruncationLagTime 1.0:0:0 -StandbyMachine venus
>> >
>> > you can see that the TruncationLagTime is set to 1 Day, however it has
>> > been over a week and the logs have not truncated.
>> >
>> > and Yes, the Source server is being backed up and having the logs
>> > truncated over there. I have resorted to manually removing the older
>> > log files. Should this not be automatic? Can i manually truncate
>> > them? I've suspended the replication and have rebooted the target
>> > machine with no luck, I have yet to do it on the source.
>> >
>> > Here is the current status:
>> >
>> > Name SummaryCopySt CopyQueueLeng ReplayQueueL
>> > LastInspecte
>> > atus
>> > th ength dLogTime
>> > ---- -------------
>> > ------------- ------------ ------------
>> > First Storage Group Healthy 0
>> > 527 2/20/2008...
>> >
>> > Any help is appreciated it. Thank you
>> >
date: Thu, 5 Jun 2008 13:31:42 -0700
author: Scott Schnoll [MSFT]
Re: Exchange 2007 - SCR - Logs not Truncating on Target
What sort of backup is required?
My company uses Symantec BackupExec 12d, though we have not yet taken a
backup of Exchange, because we were considering it an added layer that we
would only put on after the Exchange configuration worked the way we want it
to.
Does this all hinge on the Archive Bit setting?
I assume the Exchange agent would be required for the backup to have the
desired effect?
-Douglas
"Scott Schnoll [MSFT]" wrote:
> Have you taken a backup? You need to take a backup that truncates logs in
> order to have truncation occur.
>
> --
> Regards,
>
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
> "Douglas" wrote in message
> news:73D43DC2-6927-41B0-A0AD-6864D7803A73@microsoft.com...
> > I'm having the same issue, though only using 2 storage groups. I'd like
> > to
> > achiever two things:
> >
> > Truncate old logs on the SCR source server
> > Truncate old logs on the SCR target server
> >
> > Incidentally, the source is a CCR clustered mailbox server - so in short,
> > my
> > 68GB mailbox database is in a folder totaling 191GB with the log files.
> > That
> > 191GB is then replicated twice - to the passive CCR node and to the SCR
> > target.
> >
> > Talk about wasted disk space...
> >
> > Any input?
> >
> > "Paul" wrote:
> >
> >> I had the same problem.
> >>
> >> We setup 1 SCR target with 14 Storage Groups. After a week I found the
> >> logs
> >> on the target continued to grow and grow.
> >>
> >> I manually deleted the target logs that were days and days old, and found
> >> they continued to accumulate.
> >>
> >> On a whim that I setup the replaylagtime or trunicate incorrectly, I
> >> stopped
> >> 1 of 14 storage groups from replicating to target. I then deleted target
> >> logs and database and started the replication over from the start,
> >> including
> >> re-seeding the DB.
> >>
> >> From that moment on, all 14 storage groups now trunicated logs as
> >> expected.
> >> Go figure?
> >>
> >>
> >> "braincandy@gmail.com" wrote:
> >>
> >> > I have a setup for 2 Exchange 2007 servers that are doing SCR. My
> >> > problem is that the Target machine is not truncating the logs, it is
> >> > however replaying the log file with any problems.
> >> >
> >> > I enabled SCR with the following command:
> >> >
> >> > Enable-StorageGroupCopy -identity "First Storage Group" -ReplayLagTime
> >> > 0.0:5:0 -TruncationLagTime 1.0:0:0 -StandbyMachine venus
> >> >
> >> > you can see that the TruncationLagTime is set to 1 Day, however it has
> >> > been over a week and the logs have not truncated.
> >> >
> >> > and Yes, the Source server is being backed up and having the logs
> >> > truncated over there. I have resorted to manually removing the older
> >> > log files. Should this not be automatic? Can i manually truncate
> >> > them? I've suspended the replication and have rebooted the target
> >> > machine with no luck, I have yet to do it on the source.
> >> >
> >> > Here is the current status:
> >> >
> >> > Name SummaryCopySt CopyQueueLeng ReplayQueueL
> >> > LastInspecte
> >> > atus
> >> > th ength dLogTime
> >> > ---- -------------
> >> > ------------- ------------ ------------
> >> > First Storage Group Healthy 0
> >> > 527 2/20/2008...
> >> >
> >> > Any help is appreciated it. Thank you
> >> >
>
>
date: Fri, 6 Jun 2008 06:33:03 -0700
author: Douglas
Re: Exchange 2007 - SCR - Logs not Truncating on Target
Typically folks take full backups, which truncate the logs. Your backup
application documentation should contain full information on how to take a
truncating backup.
Hope this helps.
--
Regards,
Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
"Douglas" wrote in message
news:14E53B38-6F63-421D-8E23-94E158C9F74E@microsoft.com...
> What sort of backup is required?
>
> My company uses Symantec BackupExec 12d, though we have not yet taken a
> backup of Exchange, because we were considering it an added layer that we
> would only put on after the Exchange configuration worked the way we want
> it
> to.
>
> Does this all hinge on the Archive Bit setting?
> I assume the Exchange agent would be required for the backup to have the
> desired effect?
>
> -Douglas
>
> "Scott Schnoll [MSFT]" wrote:
>
>> Have you taken a backup? You need to take a backup that truncates logs
>> in
>> order to have truncation occur.
>>
>> --
>> Regards,
>>
>> Scott Schnoll
>> Microsoft Corporation
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>>
>> "Douglas" wrote in message
>> news:73D43DC2-6927-41B0-A0AD-6864D7803A73@microsoft.com...
>> > I'm having the same issue, though only using 2 storage groups. I'd
>> > like
>> > to
>> > achiever two things:
>> >
>> > Truncate old logs on the SCR source server
>> > Truncate old logs on the SCR target server
>> >
>> > Incidentally, the source is a CCR clustered mailbox server - so in
>> > short,
>> > my
>> > 68GB mailbox database is in a folder totaling 191GB with the log files.
>> > That
>> > 191GB is then replicated twice - to the passive CCR node and to the SCR
>> > target.
>> >
>> > Talk about wasted disk space...
>> >
>> > Any input?
>> >
>> > "Paul" wrote:
>> >
>> >> I had the same problem.
>> >>
>> >> We setup 1 SCR target with 14 Storage Groups. After a week I found
>> >> the
>> >> logs
>> >> on the target continued to grow and grow.
>> >>
>> >> I manually deleted the target logs that were days and days old, and
>> >> found
>> >> they continued to accumulate.
>> >>
>> >> On a whim that I setup the replaylagtime or trunicate incorrectly, I
>> >> stopped
>> >> 1 of 14 storage groups from replicating to target. I then deleted
>> >> target
>> >> logs and database and started the replication over from the start,
>> >> including
>> >> re-seeding the DB.
>> >>
>> >> From that moment on, all 14 storage groups now trunicated logs as
>> >> expected.
>> >> Go figure?
>> >>
>> >>
>> >> "braincandy@gmail.com" wrote:
>> >>
>> >> > I have a setup for 2 Exchange 2007 servers that are doing SCR. My
>> >> > problem is that the Target machine is not truncating the logs, it is
>> >> > however replaying the log file with any problems.
>> >> >
>> >> > I enabled SCR with the following command:
>> >> >
>> >> > Enable-StorageGroupCopy -identity "First Storage
>> >> > Group" -ReplayLagTime
>> >> > 0.0:5:0 -TruncationLagTime 1.0:0:0 -StandbyMachine venus
>> >> >
>> >> > you can see that the TruncationLagTime is set to 1 Day, however it
>> >> > has
>> >> > been over a week and the logs have not truncated.
>> >> >
>> >> > and Yes, the Source server is being backed up and having the logs
>> >> > truncated over there. I have resorted to manually removing the
>> >> > older
>> >> > log files. Should this not be automatic? Can i manually truncate
>> >> > them? I've suspended the replication and have rebooted the target
>> >> > machine with no luck, I have yet to do it on the source.
>> >> >
>> >> > Here is the current status:
>> >> >
>> >> > Name SummaryCopySt CopyQueueLeng ReplayQueueL
>> >> > LastInspecte
>> >> > atus
>> >> > th ength dLogTime
>> >> > ---- -------------
>> >> > ------------- ------------ ------------
>> >> > First Storage Group Healthy 0
>> >> > 527 2/20/2008...
>> >> >
>> >> > Any help is appreciated it. Thank you
>> >> >
>>
>>
date: Fri, 6 Jun 2008 08:42:23 -0700
author: Scott Schnoll [MSFT]
|
|
