Question in regards to the Infrastructure/setup.

[cfemr]

Did anyone with this issue ever resolve this issue?

We have the same problem. Direct SAN backup working great for all machines with native vmdk's but fails for vRDM with the below error :

Error: Unknown element format: 'NAA:50002ac197f32138565620202020/00119' Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}

We can snapshot all machines with vRDM within VMware with no problem.

Call has been logged with support but response time and feedback has been very poor - literally use network mode and move on.

[Vitaliy S.]

Hi Chris,

Could your issue be related to one that is discussed in this thread > Direct SAN access and vRDMs.

Thanks!

[cfemr]

Thanks Vitaliy but I don't think this applies to us.

We're using Veeam to backup LUNs on 3PAR storage and using storage integration so we don't present LUNs to the backup proxy but instead rely on Veeam taking a storage snapshot then presenting the snapshot to the proxy.

From what I can see the snapshot is created in VMware but then Veeam is unable to identify which LUNs to snapshot on the 3PAR so and fails at this point.

[foggy]

Chris, backup from storage snapshots is not supported for VMs with vRDM disks.

[cfemr]

Is lack of storage integration support with vRDM documented anywhere as i've not seen anything saying this? This is a real surprise given I've had a support call logged for 4 days to investigate the issue and our design and implementation was conducted with 2 days on site from a Veeam SE!

[foggy]

There used to be a note in the user guide in previous version, I'm currently verifying why it is not there for v8.