comments or mounted VMFS iSCSI?

I'm stuck. I'm about to do some conversions from P - to-V, but before I do I want to make sure I have properly configure my storage. Any help would be GREATLY appreciated.

Setup

Reference Dell R710 running ESXi 4

Dell EqualLogic PS6000 iSCSI SAN

Currently, I have a few very large volumes on the SAN (2.0 1.5 TB) to be my warehouses up to some comments from Suse Linux ES. I have volumes/data warehouses for the operating system itself that I ride the big volumes/data warehouses in the sharing of files/Home areas, etc.. Although the 2.0 TB 1.5 we should last awhile, I fear I might have to increase the storage space in the next 2 years. What I read, I can not simply to increase the size of the volume on the SAN and then increase the VMFS datastore. If this is true, who can put me in a difficult position later.

So my question is - I'd be better off using an initiator iSCSI in the prompt to mount these volumes directly from the SAN? I would gain the ability to resize these volumes in the future?

I'm losing sleep over this...

Thank you

Jason

I think that the answer will almost always come down 'it depends' rather than a "this is how you should do it."  You will need to run instant EqualLogic or replication on this large LUN?  If so, it might make more sense to have it as an iSCSI attached inside the guest volume and not a VMDK file on a VMFS storage.  You will always be able to expand the LUNS on the fly if you need to.  That way the snapshot might be conscious application, but I don't know if the EqualLogic Host Integration Toolkit supports Linux (maybe, not sure).

If you attach it inside the comments rather than VMFS volumes then you will need to do multiple paths inside the host, rather than the ESX level.  Not better/worse, just different.

Make sure you understand all your needs before making any design decisions that will be difficult to change in the future.

Tags: VMware

Similar Questions

  • Size max for NFS and VMFS (iscsi, FCP) datastore on vSphere 4.1 and 5.0

    Hello

    What is the maximum size for NFS and VMFS (iscsi and FCP) data created on vSphere 4.1, 5.0, and 4.0 stores?

    Thank you

    Tony

    Hi Tony,.

    You should find the answers in the various maxima of Configuration documents:

    Good luck.

    Concerning

    Franck

  • Use consolidate hacer backup form of UN VMFS iSCSI por

    Hola,

    He estado use mirando consolidate backup para hacer form of VM, el esta in una EMC AX4 - 5i iSCSI storage.

    There are backup consolidate in una VM (the that alverga VC), he disabled diskpart. There me da error only tells me that no you can access al volumen VMFS. Esta maquina esta in ese volumen VMFS. me han said that the worm directly el storage ha Máquina.

    También he wont backup consolidate in una Máquina fisica conectado por iSCSI he has the SAN y he disabled diskpart. Aun no he submitted any disco al servidor desde the cabina. The pregunta es:

    I need presentale the donde tengo el volumen al servidor fisico VMFS LUNs?

    As tengo seguridad of Al leer o el servidor directly write (SIN the ability del ESX) Quebec not to corrompera the LUN?

    Any recommendation?

    Gracias y Saludos.

    Saludos

    Hola

    If Jose, one extended ahora muy practica.

    Cafeterias that cerebro ultima version of VCB (1.5 creo recordar) there are the version that supports iSCSI instalar

    Saludos,

    Jose Maria Gonzalez,

    -

  • Increase the size of your VMFS ISCSI

    Hello!

    I've got ESX 3.5 connected to a LEFT HAND ISCSI SAN.  the VMFS is on the SAN.

    I want to increase the size of the VMFS, so that I can add virtual machines more him.

    Increase in size on the SAN is no problem, but how to get the ESX servers (I use virtual Center)

    to 'see' the increase in the size of the volume?

    I assuming I just "update" under "storage" configuration, but just want to make sure.

    Is there a risk of disruption of service? -> is - it possible in the middle of the day?

    Thank you!

    Increase in size on the SAN is no problem, but how to get the ESX servers (I use virtual Center) to 'see' the increase in the size of the volume?

    You do not have.  You can't resize VMFS volumes.  You must move your VM, remove the logic unit number, recreate the LUN of good size, move the rear of your virtual machine.

    Supposedly wll ESX 4.0 (vSphere) allows to resize, but for now no way to do it.

    There are extensions, but this is not recommended.  This space just ADDS and tacks on the original system, but it exposes you to more risk, better to recreate the lun.

    ! http://communities.vmware.com/servlet/JiveServlet/downloadImage/5441/VMW_vExpert_Q109_200px.jpg | height = 50 | width = 100 | src = http://communities.vmware.com/servlet/JiveServlet/downloadImage/5441/VMW_vExpert_Q109_200px.jpg !

  • What comments has mounted iso?

    I have an old logic unit number that I used as an ISO repository... I have since moved to a differnet LUN and remove than an old man. Problem is there is an ISO which is still used on one of my guests. Without going through a lot of many machines, is there an easier way to see who is using the ISO?

    Thank you

    Hello.

    Try RVTools .

    Good luck!

  • How can a datastore iscsi never mounted/dismantled on a host?

    Hello

    I wonder how do I know if a store of data never mounted/dismounted iscsi on a host?

    Here are the steps and I got in trouble.

    1. Add iscsi target static to the host.

    2 rescan HBAs

    3. If the data store is connected recently vSphere will rise this data store. If not and the data store was dismantled to the host of the last connection and then I manually mount (mountVmfsVolume) this data store.

    If I manually mount a data store that involves automatic Assembly of vSphere so it will be occurs "InvalidState Exception" on statement "mountVmfsVolume" from the CROWD. The exception message is "the operation is not allowed in the current state.

    How can I know if the data store will be auto-monté and avoid this exception of CROWD? Is any information that I can use before getting this data store manually?

    Wood

    Hi, wood,

    read the following article.

    Disassembly of a LUN or detachment of a unit of data/warehouse of several 5.x/6.0 for VMware ESXi hosts (2004605)

    When the device is detached, it remains in a State not fitted even if the unit is represented (in other words, the detached state is persistent).

    To set the device online, the device must be fixed.

    If you want unit decommission definitely an ESXi host, manually remove the NAA to configuration of the host entries:

    So you can use command base for esxcli detached storage unit list to check if the host has upped this device earlier or not.

    When the device is presented at the start (or manually permanently removed from service before), it will not appear in the list.

    When the device with a VMFS was removed earlier and not permanently taken out of service, the naa.ID appears in the list.

    Kind regards

    Ralf

  • Comments iSCSI - is a second vNIC a good idea?

    If the implementation of the guest with iSCSI operating systems internal initators, how do you deal with access to the iSCSI network?

    As in, it seems advisable to have a separate iSCSI storage network that guests normally cannot reach. But if some of the guests must run internal to access certain LUN on the same SAN as VMFS data warehouses are on iSCSI, how should it be set up?

    I think about adding a second virtual NETWORK adapter to the guests and put this vNIC on the portgroup of storage network with VLAN correct, as it would be to the less restricted to a small number of comments to achieve net iSCSI. What is a possible solution?

    How would you protect the accessed directly VMFS iSCSI LUN and, eventually, destroyed by the guests? CHAP or a SAN security feature?

    I think about adding a second virtual NETWORK adapter to the guests and put this vNIC on the portgroup of storage network with VLAN correct, as it would be to the less restricted to a small number of comments to achieve net iSCSI. What is a possible solution?

    Yes, another vNIC is actually the only way to connect to the storage.

    How would you protect the accessed directly VMFS iSCSI LUN and, eventually, destroyed by the guests? CHAP or a SAN security feature?

    Follow these steps on the side storage. According to storage, create hosts or host groups and present different LUNS only to guests who should see.

    André

  • Remove an iSCSI Datastore VMFS

    We are currently migrating to NFS over iSCSI and while doing some tests, I deleted a vmfs ISCSI using the VIC data store. When I went to add to the data store to the esx server, he said the volume was empty. If you do this with NFS, you can mount the volume again as it does not destroy the volume.

    My question is what happens if you want to remove the data store because you no longer want on ESX01, but you always want on ESX02. The volume will be destroyed and therfore ESX02 will not see this volume?

    Another question I have is what happens if I have an ESX machine that created the data store, then on another computer ESX try adding the same data store. The data store appears as empty when you try to create the volume on the second machine?

    Thank you

    Rombus wrote:

    So would do you by deleting the IP address of the esx of its list on the target server and then re-scan?

    Yes, but réanalysant does that with iscsi HBAs (even here the deletion of the target may be necessary); with software disable it, kill, and activation of the initiator iscsi is required (commands on the console) - or you restart your Esx host.

  • If I put in place an openfiler VM as a data store iSCSI & vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

    If I put in place an openfiler VM as a data store iSCSI & vmfs on two ESXi hosts, both ESXi hosts can access two data warehouses?

    The reason why I ask, is that I have two hosts ESXi ESXi 4 running.  I do my backups with ghettoVCB, which I modified to create thin backups on one of the drives the.  I then wput them to the server, which causes them to become thick.  Directly targets the backup in a vmfs iSCSI on the server in the face shop.  It would save a step and the vmdk backup should remain thin.

    Thank you!

    The short answer is Yes. If you allow the ESX servers to see the LUN. This setting is configured to the Openfiler.

  • RS 5 - NFS/VMFS and RDM

    3 x vSphere 5 update 1 guests

    RS 5

    NetApp PROD = mass of FAS3240s (8.02) DR = unique FAS2040

    Our virtual cluster uses NFS data warehouses. We hired an engineer to come in and deploy SnapManager for SQL and SharePoint. During this deployment they install our servers (SQL and SharePoint farm) with ROW 4. During the installation we spun a datastore to VMFS (iSCSI) to store the mapping of RDM files on. Everything was fine.

    Recently, we have begun a deployment of RS 5 I was told that the RDM are managed natively by MRS during the recovery process. Discover, it is and it isn't. Using guests on NFS data warehouses and RDM mappings on a separate data store, we were not able to add a guest in a protection group without seeing errors due to the RDM come back with "not replicated" status, even if we can see the relationship of snapmirror for data store AND mapping ROW in the table view manager. What I've read, so that the SRM properly manage a guest with RDM, the RDM must be on the SAME data store that is located in the comments, as well as the mapping of RDM files. Since SnapDrive one will not allow you to store these mapping on a NFS datastore files, we could not accomplish a fully automated "SRM"recovery without the use of scripts customized via the SnapDrive one and SQL CLI commands."

    So here's my question. What are the pro and the con us a mixed environment on the warehouses of data running? Through testing, I set up a datastore VMFS (iSCSI) with a test prompt. I then fixed 2 RDM local in this data store and then stored the mapping of RDM files it as well. Created a group of protection without problem. Recovery went through without a problem.

    Our current facility is:

    SQLSERVER1:

    Comments = NFS Datastore 1

    RDM1 = NetApp Volume 1

    RDM2 = NetApp Volume 2

    RDM3 = NetApp Volume 3

    RDM4 = NetApp Volume 4

    Mapping of RDM files = Volume VMFS NetApp 1

    Proposed configuration:

    SQLSERVER1

    Reviews - VMFS Datastore 1

    RDM1 - VMFS Datastore Qt1/1/Lun1

    RDM2 - VMFS Datastore 1/Qt2/Lun1

    RDM3 - VMFS Datastore 1/Qt3/Lun1

    RDM4 - VMFS Datastore 1/Qt4/Lun1

    * qt = qtree

    In the present example, snapmirror would be at a volume of verses level qtree it's done now.

    All advice is appreciated.

    You can create a FLIGHT/LUN (VMFS) for your comments. Storage vMotion the prompt for the new VMFS datastore. If you wish, you can remap the ROW pointers to live under this same VMFS datastore. This is the approach I took for this scenario.

    You do snapsjmirrors of Volume or Qtree level based? Best practices say allows you to create a single FLIGHT per LUN.

    Proposed configuration:

    SQLSERVER1

    Reviews - VMFS Datastore 1 (Storage vMotion)

    RDM1 - 1 Datastore VMFS to file pointer, RDM location = / VOL1/Lun1

    RDM2 - 1 Datastore VMFS to file pointer, RDM location = / VOL2/Lun1

    RDM3 - 1 Datastore VMFS to file pointer, RDM location = / VOL3/Lun1

    RDM4 - 1 Datastore VMFS to file pointer, RDM location = / VOL4/Lun1

  • 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

  • vmfs volume online

    Thank you for all your help.

    I have a volume VMFS with 200G and 1 virtual machine running on it, I want to develop by:

    -increase the size of the lun to storage san to 500G

    -extend this VMFS to 300G of vcentre.

    Is it safe to do online extend VMFS when the virtual machine is running?

    The comments on this VMFS VM config:

    -Windows 2008

    - c:\ 30 GB

    - d:\ 160 GB

    After developing the VMFS, I will be the drive D:\ this 160 GB to 300 GB virtual machine, which means that the vmdk file will be 300G.

    My question is that vmdk will growth to 300 GB across the old size vmfs and the new vmfs size 300 GB, questions about this scenario?

    That is, can the vmdk expand the size and use on a VMFS keys expanded?

    Thank you

    Patrick

    Hi Patrick,

    Is it safe to do online extend VMFS when the virtual machine is running?

    No Yes No worries on that.

    After developing the VMFS, I will be the drive D:\ this 160 GB to 300 GB virtual machine, which means that the vmdk file will be 300G.

    My question is that vmdk will growth to 300 GB across the old size vmfs and the new vmfs size 300 GB, questions about this scenario?

    That is, can the vmdk expand the size and use on a VMFS keys expanded?

    After you develop the VMFS, your host will see a single 500 GB data store. If you can develop your vmdk to 300 GB without problem.

    To expand your vmdk, just right click on your vm--> 'Change the setting'--> select your hard drive--> and type the new size. Then, in your guest OS expand your partition.

    Kind regards

    Julien.

  • the iSCSI LUN mapping

    How ESXi is mapped LUN vmfs iSCSI extends? The reason why I ask, is that in my opinion, he should do a mapping to make it persistent after a reboot?

    fajarpri wrote:

    @Rikard, similar like that. How ESX knows that Lun0 will extent1 and Lun1 goes to extend2 in this store a data?

    Wouldn't there is possibility that ESX detects Lun1 first than Lun0 and thus risk recognizing as extent1?

    I guess it's a bit 'Internal ESXi', but it should be the NAA or T10 number reported by the SAN and no id LUN itself using ESXi to recognize discs. Given that these numbers never change, there is risk of errors between reboots. I have a vague memory of which is a kind of question on the 3.x versions, but do not these days.

  • question of iSCSI san

    Hello everyone,

    I just created my first with software e open iscsi san solution.

    My situation: on the local disk, I put my VM

    I created 4 iscsi data warehouses

    1 will be used to back up my VM and can be reached for Vsphere

    The other 3 serve as a backup for my 3 VMS solution. I am connected to them through the Iscsi initiator in the virtual machine, format them, and now they appear as an additional drive in the virtual machine. I can see them in Vsphere but is no longer in data warehouses, but in devices (because they are formatted as NTFS)

    Now the question:

    Is it possible to see what data is on data warehouses that are formatted to ntfs When you are not connected to the virtual computer?

    When a virtual machine should crash, backupped data should always be saved to disk iscsi, but where can I get it?

    Thanks in advance, onkt

    NTFS is only accessible via windows server only. You can mount the iSCSI drive backup on another virtual computer.

  • ESX 3.5, iSCSI and Cisco 3750

    I have a pretty basic or newly created three ESX environment 3.5 servers, switches from NetApp for storage and a battery (two) of Cisco 3750.

    IM using for my data vmfs iSCSI store and will only run about 15-20 VM at best. This isn't a great environment but I want to plan for future growth and I won't get a second chance to get the stack of 3750 correct configuration.

    I have 2 GB ethernet by the host to the storage and 4 GB of my NAS ethernet ports all converge on the stack of Cisco.

    Can someone point me to a cisco config guide or the white paper which can guide me for the installation to take advantage of the cross battery etherchannel and balancing of load on the side of esx?

    Suggestions?

    Experiences?

    Advice?

    Much appreciated in advance.

    Hello.

    While it's not hardware Cisco, Scott Lowe has some excellent articles on this subject.

    http://blog.scottlowe.org/2007/06/13/Cisco-link-aggregation-and-NetApp-vifs/

    http://blog.scottlowe.org/2008/10/08/more-on-VMware-ESX-NIC-utilization/

    Good luck!

Maybe you are looking for