This is my setup.
I have a three computers with Hyper-V 2012 R2 called DC1, DC2, and DC3.
I have two computers for backup Proxies and Repositories called, backup1, backup2 with hyper-v 2012 R2.
We are using HP P2000 G3 10GB as our storage and they are connected from the DC1, DC2, and DC3 via Broadcom BCM57800 iSCSI HBA 10GB.
The issue is we try to backup. Regarding Microsoft VSS Software and using Veeam's On-host solution. We can complete the backup without any problems.
The issue starts if we try to use Backup1 and Backup2 off-site Proxy instead of the on-host proxy service. We are using Microsoft iSCSI to connect to HP P2000 G3 10GB Storage unit and we have HP CAPI Proxy, HP VDS, and HP Hardware VSS provider installed on all machines.
there is no error that shows up in Backup2.
If i monitor the HP P2000 G3 storage, it does generate the VSS. I do see it. The issue that I think is that either the backup2 doesn't see that the VSS was generated and doesn't grab it, or dc that the machine is on, doesn't realized and detect the VSS has been created on the HP P2000 G3 because of the Broadcom iSCSI HBA doesn't detect it. While the HP P2000 G3 VSS snapshot is active, the HP P2000 G3 doesn't have any LUN attached to the VSS.
Futhermore my configuration is as follows
LUN 1 is for dc1
LUN 2 is for dc2
LUN 3 is for dc3
LUN 99 is for Quorum Disk
LUN 100 is for Cluster Data
LUN 101 is for Cluster Data
LUN 110 is for Cluster Data
LUN 111 is for Cluster Data
The Volume that is being VSS has as a snap-pool that is greater then 20% of the volume, so there shouldn't be any reason why there will not be enough space to generate a VSS Snapshot.
Any help will be greatly appreciated.