VMware Cloud Community
pearlyshells
Contributor
Contributor

HIde DataStore from VirtualCenter View

Our SAN Administrator just installed New DAE's for our Virtual SAN Infrastructure. However, one of the LUNs belongs to vRangerPro backups and is part of the SAN group that is visible in our VirtualCenter DataSTores. I have been advised by our SAN Administrator to not touch this LUN. To ensure this does not happen I would like to make this DataStore LUN invisible. How can I do that?

0 Kudos
9 Replies
java_cat33
Virtuoso
Virtuoso

Hi - I'm assuming you are using an iSCSI SAN since you are presenting your vRanger backup lun to the ESX hosts?

0 Kudos
pearlyshells
Contributor
Contributor

We are using Fibre channel SAN. I have no idea what or why the SAN admin set it up this way. However, since he has I need to ensure protection for the datastore so that no one inadvertently does anything to it

0 Kudos
java_cat33
Virtuoso
Virtuoso

Are you going to be doing vRanger backups integrated with VCB?

0 Kudos
pearlyshells
Contributor
Contributor

yes we are

0 Kudos
java_cat33
Virtuoso
Virtuoso

Last time I checked (just before ESX 3.5 Update 2 and VCB 1.5 was released) VCB was not supported to run on a VM when using a FC SAN. If this is still the case you will need to change your setup (do not present the vRanger backup vol to the ESX hosts).

For example - in the setups that I configure - a LUN is created on a FC SAN and presented to the physical VCB/vRanger box ONLY (not the ESX boxes). This lun is used for storing the VM backups. You then present the VMFS volumes to the physical VCB/vRanger box (after you have disabled automouting of volumes etc as per VCB setup guide).

I hope this helps....

0 Kudos
pearlyshells
Contributor
Contributor

interesting......sounds as if that may be the intention of our SAN administrator. Since he presented the LUN to VC, what should I do?I suppose I need to wait for the SAN Admin to return and have it reconfigured. I see in an email he sent me that he "had to put this LUN in the same storage group as the ESX hosts and the vRanger Proxy". I'm not certain why he "had to put the LUN in the same storage group". My guess is that he didn't know of another way to do it. It sounds to me that you are indicating that he should have made it a RAW LUN (?....I'm not a SAN Admin) so that it is available to vRanger but not to VirtualCenter? But, how do you present VMFS to vRanger? I hope that doesn't sound dumb....we're new to all of this.

0 Kudos
java_cat33
Virtuoso
Virtuoso

Your vRanger/VCB is phyiscal correct? What you need to do is remove the vRanger lun from the list of datastores in VC if you formatted it as VMFS already, unpresent it from the ESX hosts and present it to a physcial vRanger/VCB server.

In regards to presenting VMFS luns to the VCB box....... it's just like how you present an existing lun to a new ESX server. You make sure the lun ID's are the same etc.

LUNA is LUND ID 1 on ESX1, ESX 2 and VCB

LUNB is LUN ID 2 on ESX1, ESX2 and VCB

Have a read of this guide for detailed info - it's important you follow every step exactly!

pearlyshells
Contributor
Contributor

many thanks. I'll read the weblink and discuss with our SAN Administrator upon his return

Grateful for your help

0 Kudos
java_cat33
Virtuoso
Virtuoso

Not a problem - the most important step is making sure auto-mounting of volumes is disabled on your VCB box before presenting the VMFS volumes.

0 Kudos