We have been running DPM 2007 SP1 for over a year.  It is running on a 
Windows 2008 R2 Enterprise machine called STORAGE1.  A couple weeks ago, we 
did an inplace upgrade to DPM 2010RC.  The upgrade went fine, and everything 
has been working as normal since the upgrade.  The only thing strange I 
noticed at the time was that each computer item under each protection group 
said "Protection-Switched" after the upgrade.  Everything was working, so I 
didn't look into it at the time.

Today we installed a second brand new server with 2008 R2 and DPM 2010RC 
called DPMBACKUP, in an attempt to setup a seconday DPM server.  When I went 
to create a protection group on the secondary server, I couldn't expand and 
any of the servers listed under "protected servers" on STORAGE1...when I try, 
I get the following message:

"DPM was unable to get the list of data sources on serverx that are 
protection by the primary DPM server storage1.cashn.on.ca.  Make sure that 
storage1 is protecting the data sources for which you want to set this DPM 
server as the secondary server.  If the problem persists, restart the 
DPMWriter service on STORAGE1 ID: 3119"

I tried restarting the DPMWriter service on storage1, but it didn't make any 
difference.  I then tried figuring out why each item on storage1 says 
"protection-switched" and right clicked on one of the protected resources and 
clicked "Switch Disaster Protection" and was presented with the following 
message:

"The selected data sources were previously protected by the primary DPM 
server CSVTEST.Hyper-V_Cluster.domain.name.  Performing this operating will 
resume their secondary protection and run a consistencty check between the 
data on primary DPM server and secondary DPM server.  If some other data 
sources from the production servers of selected data sources are still 
directly protected on this DPM server, jobs for such data sources will fail 
untill their protection is switched back to primary DPM server.  Do you want 
to switch back protection of selected data sources to 
CSVTEST.hyper-V_Cluster.domain.name?  ID: 31159"

Storage1 is one of two members in a test cluster called 
"hyper-V_Cluster.domain.name" we setup to test hyper-v live migration, and 
CSVTEST is a test hyper-v guest machine that we have setup on the cluster, 
but it has never had DPM installed on it.  For some unknown reason, the 
upgrade seems to have caused my my storage1 DPM setup to think it is a 
secondary server and that CSVTEST was the primary.  I'm guessing that this is 
also the root of my problems trying configure the new secondary DPM server, 
but I have no idea what to do to correct the problem?

Anyone??

Other issues I notcied post upgrade to DPM 2010 RC.

- I couldn't upgrade the DPM agent on any of my remote servers after the 
upgrade using the "update available" link in the agents tab in the DPM 
console.  I had to manually run the update on each of the servers directly.

- Even though it appears to be configured correctly end user recovery for 
file based resources never worked in DPM 2007 and it still doesn't work in 
2010

- When I configure a protection group on Storage1, and I look under the 
STORAGE1\All SQL Servers I now see "Storage1\MS$DPM2007$" and 
"Storage1\MSDPM2010RCEVAL".    There are MDF and LDF files in "C:\program 
files\microsoft dpm]dpm\dpmdb" for each database, and they are both the same 
size.  Should both databases still exist...should I be backup both up?

Hi Chris,

We appreciate your feedback on DPM 2010 RC.
For Connected Agent Upgrade,  what did the upgrade fails with? You can look 
at Error and Warning level alerts in Alerts tab and find the issue.
Also, what's is the DPM 2007 version you upgraded from? Connected Agent 
Upgrade will work only if you upgraded from DPM : 2.0.8861.0 or later.

We will find out about your other issues and will respond quickly.

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


"Chris Smout" <ChrisSmout@discussions.microsoft.com> wrote in message 
news:DFAD8A83-6BFD-4360-AFC0-5BADB36BD72D@microsoft.com...
> We have been running DPM 2007 SP1 for over a year.  It is running on a
> Windows 2008 R2 Enterprise machine called STORAGE1.  A couple weeks ago, 
> we
> did an inplace upgrade to DPM 2010RC.  The upgrade went fine, and 
> everything
> has been working as normal since the upgrade.  The only thing strange I
> noticed at the time was that each computer item under each protection 
> group
> said "Protection-Switched" after the upgrade.  Everything was working, so 
> I
> didn't look into it at the time.
>
> Today we installed a second brand new server with 2008 R2 and DPM 2010RC
> called DPMBACKUP, in an attempt to setup a seconday DPM server.  When I 
> went
> to create a protection group on the secondary server, I couldn't expand 
> and
> any of the servers listed under "protected servers" on STORAGE1...when I 
> try,
> I get the following message:
>
> "DPM was unable to get the list of data sources on serverx that are
> protection by the primary DPM server storage1.cashn.on.ca.  Make sure that
> storage1 is protecting the data sources for which you want to set this DPM
> server as the secondary server.  If the problem persists, restart the
> DPMWriter service on STORAGE1 ID: 3119"
>
> I tried restarting the DPMWriter service on storage1, but it didn't make 
> any
> difference.  I then tried figuring out why each item on storage1 says
> "protection-switched" and right clicked on one of the protected resources 
> and
> clicked "Switch Disaster Protection" and was presented with the following
> message:
>
> "The selected data sources were previously protected by the primary DPM
> server CSVTEST.Hyper-V_Cluster.domain.name.  Performing this operating 
> will
> resume their secondary protection and run a consistencty check between the
> data on primary DPM server and secondary DPM server.  If some other data
> sources from the production servers of selected data sources are still
> directly protected on this DPM server, jobs for such data sources will 
> fail
> untill their protection is switched back to primary DPM server.  Do you 
> want
> to switch back protection of selected data sources to
> CSVTEST.hyper-V_Cluster.domain.name?  ID: 31159"
>
> Storage1 is one of two members in a test cluster called
> "hyper-V_Cluster.domain.name" we setup to test hyper-v live migration, and
> CSVTEST is a test hyper-v guest machine that we have setup on the cluster,
> but it has never had DPM installed on it.  For some unknown reason, the
> upgrade seems to have caused my my storage1 DPM setup to think it is a
> secondary server and that CSVTEST was the primary.  I'm guessing that this 
> is
> also the root of my problems trying configure the new secondary DPM 
> server,
> but I have no idea what to do to correct the problem?
>
> Anyone??
>
> Other issues I notcied post upgrade to DPM 2010 RC.
>
> - I couldn't upgrade the DPM agent on any of my remote servers after the
> upgrade using the "update available" link in the agents tab in the DPM
> console.  I had to manually run the update on each of the servers 
> directly.
>
> - Even though it appears to be configured correctly end user recovery for
> file based resources never worked in DPM 2007 and it still doesn't work in
> 2010
>
> - When I configure a protection group on Storage1, and I look under the
> STORAGE1\All SQL Servers I now see "Storage1\MS$DPM2007$" and
> "Storage1\MSDPM2010RCEVAL".    There are MDF and LDF files in "C:\program
> files\microsoft dpm]dpm\dpmdb" for each database, and they are both the 
> same
> size.  Should both databases still exist...should I be backup both up? 

There is nothing in the alerts tab in DPM related to the agent upgrade 
failing.  However, if the remote agent must be 2.0.8861.0 or higher, that may 
be my problem, as the current version I am trying to upgrade from on the 
remote servers is 2.0.8844.0.

Also, just to let you know, I did get end user recovery working by running 
the DPM 2010RC version of c:\Program Files\Microsoft Data Protection 
Manager\DPM\End User 
Recovery\DPMADSchemaExtension.exe on one of our domain controllers, so that 
problem is solved.  (thanks to Daniel Segel for his post on this issue)

Looking forward to any insight you can come up with on the other issues...

"Anurag[MSFT]" wrote:

> Hi Chris,
> 
> We appreciate your feedback on DPM 2010 RC.
> For Connected Agent Upgrade,  what did the upgrade fails with? You can look 
> at Error and Warning level alerts in Alerts tab and find the issue.
> Also, what's is the DPM 2007 version you upgraded from? Connected Agent 
> Upgrade will work only if you upgraded from DPM : 2.0.8861.0 or later.
> 
> We will find out about your other issues and will respond quickly.
> 
> Thanks
> Anurag [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> 
> 
> "Chris Smout" <ChrisSmout@discussions.microsoft.com> wrote in message 
> news:DFAD8A83-6BFD-4360-AFC0-5BADB36BD72D@microsoft.com...
> > We have been running DPM 2007 SP1 for over a year.  It is running on a
> > Windows 2008 R2 Enterprise machine called STORAGE1.  A couple weeks ago, 
> > we
> > did an inplace upgrade to DPM 2010RC.  The upgrade went fine, and 
> > everything
> > has been working as normal since the upgrade.  The only thing strange I
> > noticed at the time was that each computer item under each protection 
> > group
> > said "Protection-Switched" after the upgrade.  Everything was working, so 
> > I
> > didn't look into it at the time.
> >
> > Today we installed a second brand new server with 2008 R2 and DPM 2010RC
> > called DPMBACKUP, in an attempt to setup a seconday DPM server.  When I 
> > went
> > to create a protection group on the secondary server, I couldn't expand 
> > and
> > any of the servers listed under "protected servers" on STORAGE1...when I 
> > try,
> > I get the following message:
> >
> > "DPM was unable to get the list of data sources on serverx that are
> > protection by the primary DPM server storage1.cashn.on.ca.  Make sure that
> > storage1 is protecting the data sources for which you want to set this DPM
> > server as the secondary server.  If the problem persists, restart the
> > DPMWriter service on STORAGE1 ID: 3119"
> >
> > I tried restarting the DPMWriter service on storage1, but it didn't make 
> > any
> > difference.  I then tried figuring out why each item on storage1 says
> > "protection-switched" and right clicked on one of the protected resources 
> > and
> > clicked "Switch Disaster Protection" and was presented with the following
> > message:
> >
> > "The selected data sources were previously protected by the primary DPM
> > server CSVTEST.Hyper-V_Cluster.domain.name.  Performing this operating 
> > will
> > resume their secondary protection and run a consistencty check between the
> > data on primary DPM server and secondary DPM server.  If some other data
> > sources from the production servers of selected data sources are still
> > directly protected on this DPM server, jobs for such data sources will 
> > fail
> > untill their protection is switched back to primary DPM server.  Do you 
> > want
> > to switch back protection of selected data sources to
> > CSVTEST.hyper-V_Cluster.domain.name?  ID: 31159"
> >
> > Storage1 is one of two members in a test cluster called
> > "hyper-V_Cluster.domain.name" we setup to test hyper-v live migration, and
> > CSVTEST is a test hyper-v guest machine that we have setup on the cluster,
> > but it has never had DPM installed on it.  For some unknown reason, the
> > upgrade seems to have caused my my storage1 DPM setup to think it is a
> > secondary server and that CSVTEST was the primary.  I'm guessing that this 
> > is
> > also the root of my problems trying configure the new secondary DPM 
> > server,
> > but I have no idea what to do to correct the problem?
> >
> > Anyone??
> >
> > Other issues I notcied post upgrade to DPM 2010 RC.
> >
> > - I couldn't upgrade the DPM agent on any of my remote servers after the
> > upgrade using the "update available" link in the agents tab in the DPM
> > console.  I had to manually run the update on each of the servers 
> > directly.
> >
> > - Even though it appears to be configured correctly end user recovery for
> > file based resources never worked in DPM 2007 and it still doesn't work in
> > 2010
> >
> > - When I configure a protection group on Storage1, and I look under the
> > STORAGE1\All SQL Servers I now see "Storage1\MS$DPM2007$" and
> > "Storage1\MSDPM2010RCEVAL".    There are MDF and LDF files in "C:\program
> > files\microsoft dpm]dpm\dpmdb" for each database, and they are both the 
> > same
> > size.  Should both databases still exist...should I be backup both up? 
> 
> .
> 

Hi Chris,

Connected Agent Upgrade is not supported from 2.0.8844.0. Minimum agent 
version should be 2.0.8861.0 for connected agent upgrade to work.

For your Hyper-V cluster where your DPM server becomes secondary after 
upgrading from V2 to RC, I request you to open a case with Microsoft 
Support.
It requires investigation including the collection of additional diagnostic 
data. The Microsoft Support team is equipped to deal gather this data and 
perform initial triage on the problem.

You can do so via a phone call or an e-mail. The details are available here:
http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=11802&gprid=530712
If you have any issues with this process or if Microsoft Support is unable 
to resolve your issue feel free to follow-up with me.

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


"Chris Smout" <ChrisSmout@discussions.microsoft.com> wrote in message 
news:4A49F46F-A26B-447E-AD48-03C03552BDAF@microsoft.com...
> There is nothing in the alerts tab in DPM related to the agent upgrade
> failing.  However, if the remote agent must be 2.0.8861.0 or higher, that 
> may
> be my problem, as the current version I am trying to upgrade from on the
> remote servers is 2.0.8844.0.
>
> Also, just to let you know, I did get end user recovery working by running
> the DPM 2010RC version of c:\Program Files\Microsoft Data Protection
> Manager\DPM\End User
> Recovery\DPMADSchemaExtension.exe on one of our domain controllers, so 
> that
> problem is solved.  (thanks to Daniel Segel for his post on this issue)
>
> Looking forward to any insight you can come up with on the other issues...
>
> "Anurag[MSFT]" wrote:
>
>> Hi Chris,
>>
>> We appreciate your feedback on DPM 2010 RC.
>> For Connected Agent Upgrade,  what did the upgrade fails with? You can 
>> look
>> at Error and Warning level alerts in Alerts tab and find the issue.
>> Also, what's is the DPM 2007 version you upgraded from? Connected Agent
>> Upgrade will work only if you upgraded from DPM : 2.0.8861.0 or later.
>>
>> We will find out about your other issues and will respond quickly.
>>
>> Thanks
>> Anurag [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>>
>> "Chris Smout" <ChrisSmout@discussions.microsoft.com> wrote in message
>> news:DFAD8A83-6BFD-4360-AFC0-5BADB36BD72D@microsoft.com...
>> > We have been running DPM 2007 SP1 for over a year.  It is running on a
>> > Windows 2008 R2 Enterprise machine called STORAGE1.  A couple weeks 
>> > ago,
>> > we
>> > did an inplace upgrade to DPM 2010RC.  The upgrade went fine, and
>> > everything
>> > has been working as normal since the upgrade.  The only thing strange I
>> > noticed at the time was that each computer item under each protection
>> > group
>> > said "Protection-Switched" after the upgrade.  Everything was working, 
>> > so
>> > I
>> > didn't look into it at the time.
>> >
>> > Today we installed a second brand new server with 2008 R2 and DPM 
>> > 2010RC
>> > called DPMBACKUP, in an attempt to setup a seconday DPM server.  When I
>> > went
>> > to create a protection group on the secondary server, I couldn't expand
>> > and
>> > any of the servers listed under "protected servers" on STORAGE1...when 
>> > I
>> > try,
>> > I get the following message:
>> >
>> > "DPM was unable to get the list of data sources on serverx that are
>> > protection by the primary DPM server storage1.cashn.on.ca.  Make sure 
>> > that
>> > storage1 is protecting the data sources for which you want to set this 
>> > DPM
>> > server as the secondary server.  If the problem persists, restart the
>> > DPMWriter service on STORAGE1 ID: 3119"
>> >
>> > I tried restarting the DPMWriter service on storage1, but it didn't 
>> > make
>> > any
>> > difference.  I then tried figuring out why each item on storage1 says
>> > "protection-switched" and right clicked on one of the protected 
>> > resources
>> > and
>> > clicked "Switch Disaster Protection" and was presented with the 
>> > following
>> > message:
>> >
>> > "The selected data sources were previously protected by the primary DPM
>> > server CSVTEST.Hyper-V_Cluster.domain.name.  Performing this operating
>> > will
>> > resume their secondary protection and run a consistencty check between 
>> > the
>> > data on primary DPM server and secondary DPM server.  If some other 
>> > data
>> > sources from the production servers of selected data sources are still
>> > directly protected on this DPM server, jobs for such data sources will
>> > fail
>> > untill their protection is switched back to primary DPM server.  Do you
>> > want
>> > to switch back protection of selected data sources to
>> > CSVTEST.hyper-V_Cluster.domain.name?  ID: 31159"
>> >
>> > Storage1 is one of two members in a test cluster called
>> > "hyper-V_Cluster.domain.name" we setup to test hyper-v live migration, 
>> > and
>> > CSVTEST is a test hyper-v guest machine that we have setup on the 
>> > cluster,
>> > but it has never had DPM installed on it.  For some unknown reason, the
>> > upgrade seems to have caused my my storage1 DPM setup to think it is a
>> > secondary server and that CSVTEST was the primary.  I'm guessing that 
>> > this
>> > is
>> > also the root of my problems trying configure the new secondary DPM
>> > server,
>> > but I have no idea what to do to correct the problem?
>> >
>> > Anyone??
>> >
>> > Other issues I notcied post upgrade to DPM 2010 RC.
>> >
>> > - I couldn't upgrade the DPM agent on any of my remote servers after 
>> > the
>> > upgrade using the "update available" link in the agents tab in the DPM
>> > console.  I had to manually run the update on each of the servers
>> > directly.
>> >
>> > - Even though it appears to be configured correctly end user recovery 
>> > for
>> > file based resources never worked in DPM 2007 and it still doesn't work 
>> > in
>> > 2010
>> >
>> > - When I configure a protection group on Storage1, and I look under the
>> > STORAGE1\All SQL Servers I now see "Storage1\MS$DPM2007$" and
>> > "Storage1\MSDPM2010RCEVAL".    There are MDF and LDF files in 
>> > "C:\program
>> > files\microsoft dpm]dpm\dpmdb" for each database, and they are both the
>> > same
>> > size.  Should both databases still exist...should I be backup both up?
>>
>> .
>>