So far one of the big issues with Data Protection Manager 2012 R2 is the lack of support for Windows 2003 Workloads , Yes 2003 is close to slipping out of patching and support but NOT as of writing , so people still need to protect their workloads.
If people are still on 2003 there is a reason , ISV being annoying , workloads being retired and 100 different options so its critical that we are able to protect it.
So if you plan to upgrade to 2012 R2 consider the impact of the 2003 servers , either leave the 2003 workload on a downlevel DPM server , or plan to upgrade to use Hyper-V integration
Trying to add a older agent result in Error 307 and is unsupported.
And trying to browse the 2003 agent says the same , dont work and isnt supported
But through the Hyper-V integration we can select our 2003 VM and add it to a protection group
At least we can add the server to a protection group
And after a few minutes we can see the 2003 server being protected through the Hyper-V integration
And from a recovey point of view we recover the whole VM
And browse down though the VHD and select single files to recover.
So we can protect 2003 servers if the workload is on Hyper-V and we dont need transaction backup SQL/Sharepoint/Exchange.
So its better than nothing but not much , hopefully Microsoft will reverse on this and add 2003 support to Data Protection Manager 2012 R2