Hi All,
Is anyone using a Synology running DSM 7 as an iSCSI target and having issues with [san] mode? We have 2 Synologies as ESX share storage iSCSI LUNs. One runs DMS6 and works in san mode, and we just added another same device but with DSM 7 and it will only operate in nbd mode. The disks are presented to the Proxyt in the same way and show as "offline shared". We do have a case (07200983) but I was wondering if anyone one else has seen this? The difference is host masking in DMS 6 and & might be causing it but Synology support are not clued up on Veeam and say Windows and ESX should not access the same lun.
Thanks,
Matt
-
- Service Provider
- Posts: 211
- Liked: 21 times
- Joined: May 30, 2012 11:58 am
- Full Name: Matt Peek
- Contact:
iSCSI SAN mode using Synology
Matt Peek
VMCE 2021
VMCE 2021
-
- Service Provider
- Posts: 211
- Liked: 21 times
- Joined: May 30, 2012 11:58 am
- Full Name: Matt Peek
- Contact:
Re: iSCSI SAN mode using Synology
UPDATE: After manually selecting the Datastores in the Proxy config it is now backing up in [san] mode
Matt Peek
VMCE 2021
VMCE 2021
-
- Veeam Software
- Posts: 2367
- Liked: 560 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: iSCSI SAN mode using Synology
Hi @peeky1323,
Thank you for your update and glad to hear you were able to get it working. Manual selection should not be required for this, so please continue to work with your Support Engineer and note this update for them in the case; the workaround is safe and will not have any issues, but the automatic selection should work with DirectSAN.
I have seen something like this before and if I remember right it was about permissions for the service account used with the proxy; I will notate the case with my ideas and the Support Engineer will help further isolate this behavior, but feel free to continue using the manual selection for now until Support is able to help explain the behavior we're seeing.
Thank you for your update and glad to hear you were able to get it working. Manual selection should not be required for this, so please continue to work with your Support Engineer and note this update for them in the case; the workaround is safe and will not have any issues, but the automatic selection should work with DirectSAN.
I have seen something like this before and if I remember right it was about permissions for the service account used with the proxy; I will notate the case with my ideas and the Support Engineer will help further isolate this behavior, but feel free to continue using the manual selection for now until Support is able to help explain the behavior we're seeing.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 77 guests