Running CCR Exchange 2007 on Windows Server 2008 with ArcServe backup
software configured to backup Exchange database (mailbox-level backup).
After backup finished successfuly the transaction log files on Exchange
server don't get deleted, so we have for more that 6 monts log files that
needs to be deleted.
Any ideas what to check or how to solve this problem? As I know, log files
have to be deleted after full backup, or are there any other options in CCR
environment?
Regards,Miha
The log files on the active server have to be successfully replicated
to the inactive server before they can be removed. And, if you're
doing a streaming backup, you have to back up the active databases,
not the inactive ones.
---
Rich Matheisen
MCSE+I, Exchange MVP
Thank you for answer. What exactly did you mean with
> The log files on the active server have to be successfully replicated
> to the inactive server before they can be removed
Doesn't backup software (ArcServe) automatically do this? We're doing full
backup of active databases via ArcServe exchange backup agent.
Do we need to to configure anything else, or use any other approach?
Regards,Miha
"Rich Matheisen [MVP]" <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:hrri065761mgs7le7...@4ax.com...
>Hi Rich,
>
>Thank you for answer. What exactly did you mean with
>> The log files on the active server have to be successfully replicated
>> to the inactive server before they can be removed
The inactive database is updated by the active node shipping log files
to the inactive node. On the inactive node the transactions in the log
files are applied to the database. When those transactions are
successfully committed to the inactive database the inactive node
conveys that information to the active node. Once the active node
knows the log files have been committed to both copies of the database
it notes that fact and will allow those log files to be removed.
>Doesn't backup software (ArcServe) automatically do this?
Well, no, not really. It asks the System Attendant service to do this.
The result looks the same, though.
>We're doing full
>backup of active databases via ArcServe exchange backup agent.
>Do we need to to configure anything else, or use any other approach?
When you look at the replication state of each database, are they all
"Healthy"?