After 6.5 update - no more san mode in jobs

[ori]

case #00151863

I've updated to 6.5 yesterday, since the update all backup and replication jobs do not use san access mode anymore to access the source data, it uses nbd for backup jobs and hotadd for replication. It significantly impacts jobs performance.
Any ideas how to solve it?

[Vitaliy S.]

Hi Ori,

Make sure that everything is still proper configured (LUNs are seen in Windows Disk Management, iSCSI initiator is running etc.) to work in direct SAN mode and continue working with our support team.

Thanks!

[ori]

Thanks Vitaly.
Nothing has changed in my backup proxies configuration (except that after the installation the backup server sent its updates to all of the other infrastructure servers), yesterday everything worked just fine.
Anyway, I am waiting for the support to contact me.

[stevecuk]

I have exactly the same issue after upgrading to 6.5 today.

All my jobs worked perfectly using Direct SAN mode before today, a couple of backups I tried now only run in NBD mode, and there is an additional message under actions for each guest relating to not having a proxy on the ESX management network. This is true but has never stopped the Direct SAN mode before.

Any ideas.

Regards,
Steve

[Gostev]

Hi Steve, please also work with support to troubleshoot (include your support case ID here as well for me please). At this time, there are no known issues regarding this functionality - but it also could be because this version was just released. Although we already had over 15'000 downloads, so I would expect any big issue to be reported by dozens of users by now...

[stevecuk]

Thanks Gostev. I'll open a support case.

Regards,
Steve

[Gostev]

Also, at least a few users report direct SAN access mode working fine in 6.5, see the adjacent topic > Direct SAN access failure troubleshooting

[stevecuk]

I've just opened a support case No.00152038.

[ori]

Something weird.. I didn't speak with support yet, but all the jobs that ran today used san access mode, without any configuration change on my side.
Will check again tomorrow and update.

[tsightler]

The system scans for attached volumes every 24 hours or so, perhaps for some reason one scan pass failed to detect the SAN attached volumes, and then worked properly on the scan the next day.