I get this question a lot:”Does the VMware Consolidated Backup proxy host need to have the same LUNs with the same ID’s presented?”.
VMware Consolidated Backup needed to have identical LUN ID’s to be able to match LUN’s but that has changed. It doesn’t matter anymore which LUN ID your host and proxy server see cause VCB just compares VMFS signatures. So I can hear you guys thinks, what about my RDM’s? (Raw Device Mappings) Well obvious VCB can’t compare the VMFS signatures, but it can compare the NAA ID’s and that’s what it does as of VCB 1.1. So in other words, as long as you just publish all LUNs you want VCB to backup it doesn’t matter which LUN ID they have.
And if for some reason your SAN doesn’t support NAA ID’s, well then you will be stuck with the “matching LUN ID’s” method you have been using for a while.
By the way NAA stands for “Network Address Authority” and is a unique identifier for you LUNs.
When I read a really great blog post I usually do three things:1.Share it with all the close friends.2.keep it in all my common social bookmarking sites.3.Be sure to come back to the blog where I first read the post.After reading this article I am really concidering going ahead and doing all three…
Because of the LUN ID Mismatch, I’m facing issue with RDM LUNs presented on one ESX Server shows different LUN ID, and when I present the same LUNs they show different LUN IDs. So, vMotion is not possible and an error shows up Direct-Access map LUN is not accessible.