-
- Enthusiast
- Posts: 56
- Liked: never
- Joined: May 12, 2014 2:05 pm
- Contact:
Direct SAN access
Hi!
I'm doing some tests in VBR 9 and trying to get direct san access to work.
but i'm wondering if i can connect the SAN to a physical server and add it to the virtual veeam as a proxy and runt it like that.
Or this is no supported?
Do i have to run VBR on the same machine that has the SAN connection?
I'm doing some tests in VBR 9 and trying to get direct san access to work.
but i'm wondering if i can connect the SAN to a physical server and add it to the virtual veeam as a proxy and runt it like that.
Or this is no supported?
Do i have to run VBR on the same machine that has the SAN connection?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Direct SAN access
You can add any physical server that has access to the datastores as a proxy server in Veeam B&R. Veeam B&R itself can be installed anywhere.
-
- Enthusiast
- Posts: 56
- Liked: never
- Joined: May 12, 2014 2:05 pm
- Contact:
Re: Direct SAN access
So my setup is correct.
The problem i have right now is this:
Error: Failed to open VDDK disk [[Datastore] Test/Test.vmdk] ( is read-only mode - [true] ) Failed to open virtual disk [Datastore] Test/Test.vmdk (flags: 4) Logon attempt with parameters [VC/ESX: [VCenter];Port: 443;Login: [domain\user];VMX Spec: [moref=vm-2840];Snapshot mor: [snapshot-2932];Transports: [san];Read Only: [true]] failed because of the following errors: Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.
The SAN is connected via FC to the physical server and i can see the volume as online (without letter as it should be)
The proxy is running Windows 2012 R2 same as the VBR server.
And i have done the following:
SAN POLICY=OfflineShared
automount disable
Any suggestions?
The problem i have right now is this:
Error: Failed to open VDDK disk [[Datastore] Test/Test.vmdk] ( is read-only mode - [true] ) Failed to open virtual disk [Datastore] Test/Test.vmdk (flags: 4) Logon attempt with parameters [VC/ESX: [VCenter];Port: 443;Login: [domain\user];VMX Spec: [moref=vm-2840];Snapshot mor: [snapshot-2932];Transports: [san];Read Only: [true]] failed because of the following errors: Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.
The SAN is connected via FC to the physical server and i can see the volume as online (without letter as it should be)
The proxy is running Windows 2012 R2 same as the VBR server.
And i have done the following:
SAN POLICY=OfflineShared
automount disable
Any suggestions?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Direct SAN access
Please contact support for a closer look at your setup.
-
- Influencer
- Posts: 16
- Liked: 2 times
- Joined: Feb 17, 2015 2:05 pm
- Full Name: Shawn McClanahan
- Contact:
Re: Direct SAN access
Bump. Checking to see if this specific issue was resolved.
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Direct SAN access
Hi,
Unfortunately OP hasn't shared his case ID. So you need to open your own case if you experience the same symptoms. If your issue is not identical then please describe it.
Thanks
Unfortunately OP hasn't shared his case ID. So you need to open your own case if you experience the same symptoms. If your issue is not identical then please describe it.
Thanks
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Direct SAN access
Saw this error when we had not enough rights on the vCenter.
Sometimes it happens that customer mounts the datastores to the proxy after Veeam installation. Then Veeam is not aware of these volumes. Wait 24 hours or start a manual rescan (Backup Infrastructure - Managed Server - Servername (the proxy) - right-click rescan.
For backup the disk can be zoned or mapped read only. The volumes in Windows can be offline.
Sometimes it happens that customer mounts the datastores to the proxy after Veeam installation. Then Veeam is not aware of these volumes. Wait 24 hours or start a manual rescan (Backup Infrastructure - Managed Server - Servername (the proxy) - right-click rescan.
For backup the disk can be zoned or mapped read only. The volumes in Windows can be offline.
Who is online
Users browsing this forum: Bing [Bot] and 34 guests