Not within DPM.   This is known as an "Off Host Backup"  or "server less backup"    Programs such as Backup Exec do.  (Called ADBO)   Netbackup and Commvault also support this, but not DPM.    DPM can't just "login" it has to be told the IP address and complete IQN name to use.     Generically, to do this, the backup sw, calls Volume Shadow Service (VSS) to quiet the filesystem and flush cache.  When VSS goes to do that, if our HW provider is there, it will connect to the vss-control volume on the array, select the volume, create snapshot and return (in XML format) the volume name and IP address.    This information can be used to tell the CLI version of  MS iSCSI initiator (msiscli) where to, and what volume to log into.   DPM lacks this capability.  Also MS changed the XML format in W2K8, so the backup server must be same OS as server being backed up.  W2K3 or W2K8, you can't mix them for off host backups.  So DPM would have to build software to handle this processing of the XML file and tell the iSCSI initiator to login.  Then put the snapshot offline and delete it when done.   So not a simple task by any means. 
We have a Hyper-V cluster connecting to an Equallogic PS6000e using CSV over iSCSI and recently have begun to setup Hyper-V virtual machine protection. The issue we are seeing involves the backup timing out (VSSADMIN list writers shows time out) and event logs show iSCSI cannot connect to target volumes. When I look at the iSCSI initiator in Windows (2008 R2) we see all targets communicating successfully. The HIT tools are installed on each Hyper-V host and we have configured the iSCSI targets to use CHAP authentication and IP restriction for the iSCSI network. If I disable the Equallogic VSS writer (DPM attempts to use this as a hardware VSS writer) then backup of Hyper-V virtual machines succeeds using the default software Hyper-V VSS writer. Our option is to use only IP restrictions for iSCSI access but would we need to provide the DPM server with an interface on the iSCSI network. What I would like to know is what are the adverse effects of disabling the Equallogic VSS writer using the eqlvss /unregserver command on each Hyper-V node and reverting to the Hyper-V software VSS writer (other than performance impact).Is there a component of the Equallogic SAN on a windows environment that expects the Equallogic VSS writer to be functioning?
DPM Backup of CSV storage on Equallogic