none
DPM 2007 64 bit with 32bit DPM 2007 secondary storage RRS feed

  • Question

  • I have Windows 2008 R2 64bit DPM 2007 on the Primary and Windows 2003 R2 32bit on secondary. Both have the same DPM build number. I read that someone was doing it, but I am getting an error when trying to enable protection of the primary.

    Can this be done?

     

     

    Protection agent version: 2.0.8861.0
    Error: Data Protection Manager Error ID: 372
     The agent operation failed because DPM detected a more recent version of the DPM protection agent (version 2.0.8868.0) on DPM.server.com.
    Recommended action: Install the updated version 2.0.8868.0 of the protection agent on the DPM server.


    Bret
    Tuesday, November 16, 2010 5:03 PM

Answers

  • A re-install of dpm seemed to work. So yes, you can have a mixed 32 and 64bit DPM configuration. someting I learned along the way. install base product, then SP1, then ONLY the latest rollup. don't bother with all the other hotfixes/rollups. Thats what I think messed up the install on my secondary DPM server.
    Bret
    Tuesday, November 16, 2010 9:35 PM

All replies

  • I just noticed that the agent version id falsly reported as 8861. but in fact it is 8868 on both servers. I tried doing a manual install, but I dont see how you can do a manual install on a Primary DPM server.
    Bret
    Tuesday, November 16, 2010 5:53 PM
  • ok, so the issue may be that the secondary server is pushing out the wrong version of the agent. I tried it on another server from the secondary and it pushed out 8861 even though 8868 is installed.

     


    Bret
    Tuesday, November 16, 2010 6:05 PM
  • I love this. it looks like 2.0.8868.0 did not install 100% on the secondary server. in the DPMDB under dbo.tbl.AM_Agent patch, there is nothing for 2.0.8868.0. I dont see a way to force a reinstall of the patch either. so looks like a DPM re-install.
    Bret
    Tuesday, November 16, 2010 7:06 PM
  • A re-install of dpm seemed to work. So yes, you can have a mixed 32 and 64bit DPM configuration. someting I learned along the way. install base product, then SP1, then ONLY the latest rollup. don't bother with all the other hotfixes/rollups. Thats what I think messed up the install on my secondary DPM server.
    Bret
    Tuesday, November 16, 2010 9:35 PM