![]() ![]() ![]() Sadly, not all storage arrays have the possibility to configure read-only access, and some of them only offer write access, or no access at all. Since VDDK libraries cannot write back data to lun during restore, is considered a safe configuration. ![]() Usually the best way to present LUNs to Veeam proxy is to place the read-only flag to the LUN itself. Is this the proper way to accomplish this? Am I supposed to do something on the Windows server to prevent it from initializing the LUN and prevent it from assigning a letter to it? After doing this Veeam was able to find the LUN and use direct SAN access to backup. I then assigned the same LUN to a storage group I created for the Veeam backup/proxy server. On my test, the LUN is assigned to a storage group where only the ESX cluster connects. I am trying to get people's recommendation on how they present a LUN to multiple hosts without causing data corruption. I mentioned this to EMC and they said that I am right about that, but if something happens and they get initialized then both hosts could write to the LUN possibly causing data corruption.Īm I presenting the LUNs correctly? What are you doing to prevent multiple hosts from writing to a LUN other than being careful when accessing the disk manager? I know that if the LUNs are not initialized and if they don't have a letter assigned to them on Windows, the OS will not be able to write to them. However, on my test adding the LUN to the backup server storage group without initializing it and assigning letter to it, Veeam was able to see the LUN and back it up via Direct SAN Access mode.ĮMC want me to engage professional service to assist me with this. I already have the LUNs assigned to an ESX Hosts SG.ĮMC told me that I should not present the LUN to two different hosts unless they are on a cluster. This was the message: “Adding a LUN to multiple storage groups is not a recommended configuration because this will allow multiple hosts to have simultaneous access to the LUN.” The one thing that got me a bit concern and the reason to open this ticket, it’s the warning I received from the VNX when I try to add the LUN to the Storage Group where the backup server resides. The LUN is one of the data stores containing 3 VMs. I did a test and presented a LUN to the backup server. I am trying to figure out how to correctly present the LUNs to the backup server. Our Veeam backup/proxy server connects to our VNX5300 via fiber. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |