Retrieve iscsi LUNs

Similar Questions

• Attach an iSCSI lun to 5.1 and 5.5 to move virtual machines

  I have 1 Server esxi 5.1 I've built a bunch of VM now connected to a 4 TB iSCSI LUN.

  I gave recently 2 new 5.5 servers.

  Ideally, I would like to connect these 2 servers to the same lun iSCSI is used by the Server 5.1. Then, stop/forget each VM on 5.1, browse the data store on 5.5, add to the inventory and it start up. After all the machines are moved, I can do some changes on the material on the Server 5.1, it blow and install 5.5.

  I plead for the trouble, or is a reasonable way to do?

  Welcome to the community - Yes that works-

• How to clean and do a fresh install with attached iscsi LUN?

  I intend to migrate both esx 4.1 with esxi5.1 hosts before you wipe and do a clean install.  Each host is connected to two iscis without, with 4 LUNS of each SAN attached to each host.  Each lun
  spread over 3 degrees is. I plan on vmotion (not storage vmotion) guests from one host to another to make the upgrade.  I'm stuck on the determination of what will happen to the iSCSI LUNS after I
  upgrade to esxi5.1 guests.  It seems that I should just be able to reattach, but I'm not sure.  Can I just attach the LUNS to the new installation 5.1 hosts and see all the
  VMDK intact, or is there something that I am on?

  And should the migrated to another host virtual machine continues to run on the iscsi san, while I upgrade of the host, they were released since then?  It seems that storage must be removed from the process as the LUNS
  should not remain attached to the host after it is cleared and the iqn name no longer exists.

  
  Am that I on the right track here?  What Miss me?

  jackjack2, understand you this? I went ahead and moved to esxi 5.0 U2 of ESX 3.5 u5. Had to perform clean install and I have an iSCSI SAN. That's what I did:

  1 a taken a screenshot from all my ESX host configurations. Go to configuration-> software adapter-> click on the iSCSI--> properties--> iqn copy map and alias-> click the dynamic discovery tab and note any IP address. You may need these IPs with the discovery of data warehouses later.

  2. after having documented the configs, put the host in maintenance mode.

  3. after maintenance, remove the host from the vcenter server. Connect directly to the host and close.

  4. remove all the network cables. Cable marking help before you detach the cables.

  5. clean install esxi 5.0.

  6. after installation, before rebooting, set the network cables.

  7. configure and test the management network. If your network management test fails, see if you have anything that is entered in the id vlan. Chances are that your port is not shared resources in the physical switch. In this case, remove the id vlan (during the configuration management network) work.

  8 bring the vcenter server host.

  9 configure the network, dns, time, etc.

  10 Add a software iSCSI adapter. This card will have a new iqn. Either you provide this iqn to your SAN administrator so that it can update side SAN, or you can use the old iqn name.

  11. in my case, I made a copy of the new iqn and then deleted. Entered the old iqn name obtained in step 1. Additionally, entered the alias (since one was present before). After that, a new analysis and update still does not fill in data warehouses. So, I went to the properties of the iSCSI adapter and then discovered added tab dynamic addresses IP that did not exist before (otherwise, you will need to enter the virtual IP address of the cluster that you data store (s) belong to). Once the IP addresses have been added to the dynamic discovery tab, he asked if I wanted to rescan the HBAs. I said yes and viola! my data stores have been populated.

  12 Add the host to the cluster.

  Note that you can add iSCSI adapter when you affiliate you the host to the cluster. However, in this case HA will not be happy because no heartbeat of data storages will be detected. In addition, when data warehouses are discovered it may appear initially as not mounted. Don't panic. After a minute or two it will be mounted.

  I hope this helps!

• ISCSi LUN Vmware question

  I have two luins iscsi for vmware build hook etc. up to an emc celerra server.

  question-

  If I extend the iscsi on celerra lun in vmware puts it auto-mattically updated space iscsi LUN or is there more steps involved.

  Hello.

  There are more steps involved, after performing the operations on the Celerra.

  Use http://kb.vmware.com/kb/1752 as your starting point.

  Good luck!

• Stream access to the ISCSI LUNs on esxi v4

  Greetings,

  Wonder just anyone could throw me some lights on it?

  Esxi v4 does support stream access to a single lun? The reason behind this is I want to consolidate LUN based on roles (exch, file, etc.), that is to say, a lun (datastore) will host all the servers exch only running on different hosts.

  Thanks in advane.

  Felix

  Hello

  Yes No... multi host access to iscsi LUNs is possible... that's what san / storage isa he's shared on the subject. Just make sure that Suur iscsi luun u plan on using is in the list compatibilityy supported so that u get the support of vmware in the future if you need. ESX / ESXi have a clustered file system.

  TM

• iSCSI LUN maximum

  So I'm looking at the documentation for maximum rates of configuration and it is said that the maximum LUN of Fiber Channel is 2 TB. This also applies to the iSCSI LUNS?  For example, I have an iSCSI LUN 5 TB ESX 'sees', but when I try to establish VMFS on it and add it to the usable storage, it allows me to choose the whole 5 TB, but only write 930GB and says "complete".

  I have to chunck this 5 to in max 2 TB LUNs, and then write my 5 to VMFS on multiple LUNS instead of one?

  Thank you!

  Yes, the limitation applies to iSCSI too. As you said already correctly, you must present the LUNS with Max 2 TB less than 512 bytes.

  The reason for this limitation, see http://kb.vmware.com/kb/3371739

  André

• How to use a larger than 2 TB iSCSI LUN?

  I have a server ESXi (4.1 U1) connected to an iSCSI NAS network, where 4 LUNS have been defined and presented to this host. all LUNS are 3 TB in size. ESXi correctly sees the LUNS and recognizes their size 3 to.

  I know that the maximum size for a VMFS data store is 2 TB, so creating a single data store for each logic unit number would be a waste of space. I know also that the creation of multiple data on a single LUN warehouses is not recommended, and it does not seem work either: If there is already a data store on a LUN, the just vSphere Client won't let me create something else here, it is not even list it in the list of available devices for the creation of data warehouses.

  I know that I can use extensions to create a store of data from more than 2 TB, but it seems to work across multiple LUNS: when I try to increase the size of a data store using the same logic unit number where he resides, ESXi is trying to increase it in fact, it won't go above 2 TB in size.

  My question is: is it possible to combine two extensions in the same logical unit number, so actually creating a composed of 2 extensions 1.5 TB 3 TB data store?

  If this is not possible, is it possible to create two data warehouses in the same iSCSI LUN? I know that this is not recommended, but it should at least be possilbe... but looks like it's not.

  If this is not possible, then... How to make use of these 3 to LUN?

  You can carve up the LUN and then it recombine.

  How to use these LUNS 3 TB is to get rid of them and the re - present as< 2tb="">

• ISCSI LUN appears not

  I'm having some trouble to make the new iSCSI LUN to appear, I created. I've included some screenshots of my set up.

  Thanks in advance!

  Paul

  OK, but vol1Share is limited a.58. Did you mean a shorter mask as 255.255.255.0? the 255.255.255.255 signifie.58 et.58 only. Your ESXi is sur.60. Another poster has noticed the spec VLAN that has to go. You did not show pages discovered properties of the iSCSI initiator, but maybe you got that too. I have all this software run here and screenshot can't do anything that you can't go, but for now, you have not shown all the pieces and parts that show you matched lot of information.

• VMotion using on OpenFiler iSCSI LUNS

  Does anyone know if it is possible to 'share' a logic unit number on an OpenFiler iSCSI target so I can use VMotion? So far, I can't my second ESX server to connect to the LUN.

  Should not be a problem,

  Follow this: http://www.petri.co.il/connect-vmware-esx-server-iscsi-san-openfiler.htm

  of http://superuser.com/questions/101662/vmotion-using-iscsi-lun-on-openfiler

  StarWind software developer

  www.starwindsoftware.com

• Error in adding an iSCSI LUN - use software iSCSI initiator...

  Hi guys,.

  I can't add an iSCSI LUN to my host ESX4.0. It is the iSCSI Software initiator that is activated and I can see the LUN after I launch a new analysis.

  While adding the LUN as a data store, it throws me an error, please find the attached for the snapshot file.

  The real question is if I add a lun iSCSI and then remove it and again try to re add it whether or nor the old signature are found that do not readd it.

  Is there a command that I can use to remove all the LUNS already assigned and delete it existing signatures.

  Let me know guys if the above is not clear.

  Kind regards

  Use fdisk to create a partition and vmkfstools - C command to format the partition as VMFS. You use a supported storage array?

• ESXi 4.0 - attached an iSCSI Lun and you want to import a VM to...

  OK, I have attached an iSCSI LUN that has a couple of VM on it from a previous generation test. Now, I want to import those virtual machines to my ESXi 4.0 host. Can someone give me step by step on this operation method?

  You'll just want to browse the data store, right-click on the VMX files and select Add to the inventory.   After you have added, you will want to check the network label to ensure that it exists on the new server.  If one of the virtual machines have been using VMdirectpath, generic SCSI devices, etc. you'll want to update those as well.

  Dave

  VMware communities user moderator

  New book in town - Start Guide quick vSphere -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

  You have a system or a PCI with VMDirectPath?  Submit your specifications to the unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.

• ISCSI LUN can support backup VMWare Consolidation?

  Dear all,

  ISCSI LUN can support backup VMWare Consolidation?

  Could help you find some documents for this?

  Thank you

  Dennis Dai

  see page 22 of http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_vm_backup.pdf

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• ESX 3.5 and iSCSI LUNS

  Good so I'm setting up my servers ESX using iSCSI LUNS.  I do not have the LUN in a VM, I want the servers to use.  Is it possible to do?  And how can I do for that implemented?

  Scott

  You must enable initiator initiator or software hardware

  If you go to the inititiator of the software, you must enable on each ESX host, by going to the configuration of the VI Client storage adapter tab. (you will see something like vmhba32, activate it)

  Once it is enabled, you must add your target (as we are talking about software initiator, it supports only dinamic discovery).  Recommendation, isolate the network cards that will connect to the iSCSI network.

  concerning

  Jose

• Extend an iscsi LUN without losing VM

  I created originally for my data store a 500 GB iSCSI VMFS LUNs. I noticed that I had more available SAN storage, so I increased the size of 500 GB to 1.3 TB LUN LUN for our VMWare data store. I currently have a VM DC on this LUN I want to thank. When I go to the store and add the extension, it is said that the drive will be formatted and all data will be erased. There is a host of ESXi v3.5. What is the best way to extend this LUN without losing my VM domain controller?

  Should I try to move the virtual machine to the internal storage using the browser to store data? What do I have to use VMWare Converter to move the virtual machine off the iscsi lun until the LUN is extended, or is there another way? With your recommendations can also provide you with exact to directions?  It is a production environment, and I don't have a lot of experience, make this type of move.  Your comments are greatly appreciated.

  Hey Monty,

  One thing to remember, whenever you play no matter what sizing such thing w.r.t. the LUN always take relevant backup and can do what you want to play. The error you get is the error for the new extend this when adding, all the data on the new measure will be lost, so certainly, you can spend without any hestations.

  Concerning

  Anil

  Save the planet, go for green

  If you have found my reply to be useful, feel free to mark it as useful or Correct.

• ESXi5: File server: 8TB iSCSI LUN

  I'll put up an ESXi5 and plan to host my server files on it. The file server uses storing a Raid6 NAS available on iSCSI (with MPIO).

  The server storage is about 8 TB, which will be shared via a Windows 2008R2 Guest VM.

  Now I need to find the best options to expose the storage for Windows.

  Looks like my options are:

  -Use VMFS on iSCSI and vmdk files ordinary LUN.

  -Use RDM (do not know if it works with iSCSI) and provide a RAW disk to the vm file server.

  -Use of iSCSI directly from the Windows VM (can cause a high CPU utilization), prove less effective.

  The most common and options of would apply we would be the first option, however I would be worried to have my WHOLE being in a single VMDK file file server (or several)? If it gets corrupted, I would I lose its content business? Is this something that happens? Especially since this is managed ethernet (iSCSI)?

  Really this all come down to: vmdk is safe, and is there a way to get it back where the vmdk file is corrupt (in the same case).

  Additional info:

  I didn't need the partition of data to be snapshoted if I snapshot files server.

  Thank you!

  I mounted the iscsi Target inside the bone of the VM. Works very well. I also have a secondary backup iscsi NAS for increased security outside (even RAID 6 is not flawless) and I do weekly backups of my virtual machines to a different data store. Storage of the user in a vmdk files is a bad choice. If all this is corrupt (or just the OS) you will have a hard time to retrieve data from a VMFS partition. There are very few options to read under Windows or Linux. Better safe than sorry

  Concerning

  Tony