Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Secondary Protection System State Backup Failing

4 views
Skip to first unread message

t_v

unread,
Nov 27, 2009, 3:18:07 AM11/27/09
to
The secondary PG for SS fails with every sync (24h @ 00.00). The primary PG
works fine without any problems. Production servers are a mix of WS2K3 x64
and x86 R2 SP2 and WS2K8 x64 SP2. The failure involves all versions.

The error:"DPM failed to communicate with the protection agent on XX because
the agent is not responding. (ID 43 Details: Internal error code:
0x8099090E)". The Primary Agent Status is OK under the Agents tab and it is
accessible from all other PGs.

Both Pr and Sec have the recent hotfixes installed (all up to KB976542).Both
are WS2K8 x64 SP2 residing in different sites.

Any advice would be welcome.

Hitesh Sharma[MSFT]

unread,
Nov 30, 2009, 4:50:59 AM11/30/09
to
Hi,

Please help me understand the scenario a little better: Are you trying to
protect system state of primary DPM server in the secondary DPM Server?
Unfortunately this particular scenario does not work right now and the issue
is being fixed in DPM V3.

--
Thanks,
Hitesh Sharma [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.

Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm
"t_v" <t...@discussions.microsoft.com> wrote in message
news:ECCCE013-F61B-408A...@microsoft.com...

Narendran Gunasekaran[MSFT]

unread,
Nov 30, 2009, 5:23:46 AM11/30/09
to
Hi,
If you are doing secondary protection of system state, is this error
occuring only for System state? Do you have any other datasource that is
secondary protected, and see this issue for that datasource as well? Can you
also please let me know how many datasources have been secondary-protected?

--
Narendran[MSFT]


This posting is provided "AS IS" with no warranties, and confers no rights.

"Hitesh Sharma[MSFT]" <hish...@online.microsoft.com> wrote in message
news:#yrdgKac...@TK2MSFTNGP02.phx.gbl...

0 new messages