With the release of update rollup 4 for Data Protection Manager 2012 R2 , it is now supported to protect a remote SQL server running SQL 2014 (about time)
http://blogs.technet.com/b/dpm/archive/2014/10/29/protect-sql-server-2014-using-dpm-2012-r2.aspx
There are still some features that isnt supported to test and verify , v.next will support/require SQL 2014 as DPM database target but in 2012 R2 UR4 its protected data only
Install is pretty straight forware as usual
Push the agent , will require a reboot due to updated filter driver
After server have been reboottet verify that SYSTEM have sysadmin rights on the SQL server you want to protect
Create new protection group
Select Servers
browse the SQL instance , and select auto to ensure that all databases will be added
Name the protection protectoin group , in the demo setup there is no tape libarary so short term only
And a hourly backup
Sucess !
and a few minutes later we now have a valid backup , ready for first restore test