Secondary protection of Exchange

We have a DPM to DPM  scenario and this is struggling with the Exchange 
Backups as the recovery point creation keeps failing. We have it bandwidth 
throttled during the week and it keeps failing on the Exchange recovery point 
job. If it fails halfway through a recovery point job and transfers 10GB of 
Exchange data to the secondary server, will it need to transfer that 10GB 
again the next time a recovery point runs or will it continue from where it 

Simon,
If you search this newsgroup, you will see a lot of people had the same 
issue.  To solve it, I had create a script [available in newsgroup], then 
create a scheduled task to run on the secondary server shortly after an 
express full ran of Exchange on the primary dpm server.  This script runs a 
consistency check with certain perameters and checks that alleviates the 
express full that runs later on the secondary.  So, you will need to know 
when an express full for exchange runs and usually completes on the primary, 
then have the consistency check script run and complete on the secondary 
dpmserver before the secondary express full runs.

Hope this makes sense.  My primary runs express full for exchange at 6 PM.  
Usually completes within a half an hour.  My script runs on secondary at 7:15 
PM and usually a couple hours to complete.  Then the secondary runs express 
full at midnight which only transfers about 300 to 600 MB and completes.  My 
secondary express used to never complete until I got the script and all the 
timing running properly.

Rob

"Simon" wrote:

> We have a DPM to DPM  scenario and this is struggling with the Exchange 
> Backups as the recovery point creation keeps failing. We have it bandwidth

> throttled during the week and it keeps failing on the Exchange recovery
point 
> job. If it fails halfway through a recovery point job and transfers 10GB of

> Exchange data to the secondary server, will it need to transfer that 10GB 
> again the next time a recovery point runs or will it continue from where it

This is a known issue with DPM 2007 and we are actively considering this fix 
as a QFE release

-- 
Thanks
Madhan S

This posting is provided "AS IS" with no warranties, and confers no
rights
"robbied31" <robbied31@discussions.microsoft.com> wrote in
message 
news:AE1B7A17-D0E6-4997-8A68-1D0F254A8004@microsoft.com...
> Simon,
> If you search this newsgroup, you will see a lot of people had the same
> issue.  To solve it, I had create a script [available in newsgroup], then
> create a scheduled task to run on the secondary server shortly after an
> express full ran of Exchange on the primary dpm server.  This script runs 
> a
> consistency check with certain perameters and checks that alleviates the
> express full that runs later on the secondary.  So, you will need to know
> when an express full for exchange runs and usually completes on the 
> primary,
> then have the consistency check script run and complete on the secondary
> dpmserver before the secondary express full runs.
>
> Hope this makes sense.  My primary runs express full for exchange at 6 PM.
> Usually completes within a half an hour.  My script runs on secondary at 
> 7:15
> PM and usually a couple hours to complete.  Then the secondary runs 
> express
> full at midnight which only transfers about 300 to 600 MB and completes. 
> My
> secondary express used to never complete until I got the script and all 
> the
> timing running properly.
>
> Rob
>
> "Simon" wrote:
>
>> We have a DPM to DPM  scenario and this is struggling with the
Exchange
>> Backups as the recovery point creation keeps failing. We have it 
>> bandwidth
>> throttled during the week and it keeps failing on the Exchange recovery

>> point
>> job. If it fails halfway through a recovery point job and transfers
10GB 
>> of
>> Exchange data to the secondary server, will it need to transfer that
10GB
>> again the next time a recovery point runs or will it continue from
where 
>> it
>> got to?