VSA abandoned? VSAN or SAN?

Similar Questions

• virtual san solutions (VSA): what is the current state of the field?

  As of many SMEs, we feel the pressure from DAS and get on some sort of SAN.  We are planning an implementation of iSCSI SAN, which will probably (at least partially) kind of VSA to take advantage of our DAS ability in the new iSCSI environment.

  What are the main actors in the field of the VSA?  My Google search has turned up:

  the storage facility for vsphere (not crazy about the use of low disk space)

  FalconStor

  StarWind vsa

  Device HP LeftHand VSAN

  In addition, we consider OpenFiler/FreeNas...but it is not clear to me if he can really operate in VSAN mode (e.g. RAID between hosts, etc.)

  Are there others that we should consider?

  Works all stand as a clear leader for a reason any (price/functionality/usability/reliability)?

  Performance there data?

  Thank you.

  I just wanted to add a small clarification around the vSphere Storage Appliance. Yes, it start with a requirement of RAID10 on each host, but this was relaxed in early 2012, while it supports now also two configurations of RAID5 RAID6 & - http://blogs.vmware.com/vsphere/2012/01/raid10-requirement-for-vsphere-storage-appliance-vsa-relaxed.html

  The point here is we do not want a failure of the single PIN to bring down a node in the cluster.

  Just in case this is the reason why you expected the vSphere Storage Appliance.

  HTH

  Cormac

• Format disk VSANS for 3.0 is not / / failure realign suite virtual items SAN / / due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Hi all

  After the upgrade of "6.0 Update 2" and try to update the disc format to version 3.0, I received the error message below.

  Impossible to change the route following the virtual items SAN:

  be4db256-0ab4-9801-c523-0cc47a3a34ca, c2bcb056-5d5f-0f02-f096-0cc47a3a3320, c0bcb056-70a6-180c-c583-0cc47a3a3320, e413b256-90b5-dd1a-cce6-0cc47a3a34ca, c2bcb056-64aa-ee1e-0bb3-0cc47a3a3320, c0bcb056-4b47-5529-b59d-0cc47a3a3320, 6644b256-e0f8-3338-737d-0cc47a3a34ca, d411b256-08ea-f83b-9774-0cc47a3a34ca, c0bcb056-a489-9541-efbe-0cc47a3a3320, 3f6abc56-28fd-4a48-4f8a-0cc47a3a34ce, d411b256-784F-a45a-714d-0cc47a3a34ca, c1bcb056-6671-c45c-2254-0cc47a3a3320, 3f6abc56-1061-ab60-e4c8-0cc47a3a34ce, f17bb356-fcdf-3469-502-a-0cc47a3a3320, cfe8b156-606f-ee6a-4356-0cc47a3a34ce, d411b256-4450-3777-e3bf-0cc47a3a34ca, c1bcb056-b24e-cb7a-7b1a-0cc47a3a3320, f17bb356-f008-9581-2468-0cc47a3a3320, 31bdb056-0a02-4882-9094-0cc47a3a34ca, c1bcb056-2a83-a596-ed2c-0cc47a3a3320, f17bb356-08a1-529f-c375-0cc47a3a3320, c1bcb056-4edc-FFAF-bf04-0cc47a3a3320, c1bcb056-c9e2-fec8-1930-0cc47a3a3320, c1bcb056-4e92-e4e4-9b92-0cc47a3a3320-e413b256-dcd0-f6fd-8ae2-0cc47a3a34ca,

  due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Does anyone has an idea to solve this problem?

  The articles and the script are now available to resolve this problem. A more permanent solution is in preparation.

  Details of the issue, including links to the scripts and KBs are here - http://cormachogan.com/2016/03/31/vsan-6-2-upgrade-failed-realign-objects/

  Thank you for your patience.

• vSAN 6.0 - Virtual by default on SAN storage policy does apply a VM show not

  My VM on my datastore vSAN all show "not applicable".

  The weird part is that caching SSDS still works. How will I know? Because my performance SQLIO tests indicate hundreds MB/s and my braces are only a single SAS6 Drives. No spindle drive a possible way to do this.

  Now the default virtual SAN storage strategy shows also non-compliant, but I can't seem to find the cause.

  Where should I look?

  I'm confused... lol

  Begin by restarting the profile flown by the demon of storage in vcenter.

  When using the appliance, connect with ssh and run "/etc/init.d/vmware-sps restart".

  (Or restart the whole camera)

• VSAN guests can access the FC SAN storage at the same time?

  Soon we will invest in new ESXi hosts and we want to design them for the ability to VSAN. But since VSAN is a fairly new technology, we also want the same hosts to act as our old guests and have warehouses of data in our SAN (FC SAN attached storage) environment.

  Host VSANS have access to VSAN and FC SAN storage at the same time?

  What advantages and disadvantages do you see with this design?

  Yes, there is nothing to stop an ESXi participating both host a cluster VSAN, and also had access other storage taken in charge of protocols such as NFS, FC, FCoE or iSCSI.

  However, you will not be able to use the LUNS or Volumes presented on NFS, FC, FCoE or iSCSI for storage VSAN.

  VSAN requires local disks to build the VSAN data store.

  I guess the only concern would be the additional management that comes with having many types of different storage, but this is true even if VSAN wasn't in the picture.

• SAN oppure VSA?

  Ciao,.

  in azienda stiamo affrontando by the prima volta a progetto di virtualizzazione by server of it consolidamento dei.

  Is di una 15 di server per i più disparati usi, nessun carico heavy, microsoft windows 2003 e diversi 2008 che tutto if sono aggiunti nel tempo of base. We have a server exchange 2003 by 100 caselle di posta elettronica (80 GB totali), a couple di SQL2005 per dialogare con e AS400 have quali appoggarci per tutti i ahime ancora che girano tra gli uffici access programs. To 60 users autenticati in fileserver communica... PrintServer per stampanti di 40ina... etc.etc...

  Questi giorni ho stimato che tutti i server, [total spazio - spazio libero], announcement: sistema e dati to 1, 6 to, includes file inutili, doppioni etc...

  Abbiamo pensato come a DELL partner, e poco più di one anno fa sono stati raccolti I dati IOPS / s con DPACK.

  He risultato e stato (com 95%) di 500IOPs I quali devo add UN 20% di crescita degli ultimi 12mesi.

  Quindi posso stimare by stare tranquillo 600IOPs nella spartizione di 40% 60% e read write.

  Devo add che mi'd proved a fattore di crescita per i as mesi e buon at least I as anni 2...

  Infatti tutti i sistemi microsoft will be date: 2012 server, SQL2012, 2013 e introdurro Sharepoint Exchange con servizi vari.

  Not reach around sara nulla di heavy. E che sfrutteranno users he saranno più una typical al sistema.

  So mi sento di dover Winegardner di concepire system di virtualizzazione per essere in grado di at least to work with it 100% to più degli IOPS / s verificati da DPACK... quindi come punto fermo 1200IOPs, 40 %R, 60 %W.

  Ebbene, e stato end here da subito, updated a questo periodo, una soluzione composed di

  2 * Server r.620 etcetc...

  1 * SAN Equallogic PS4200XV 3.5 "- 12 * 600GB 15K.

  2 * 6224 switch

  1 * SIN Marin di backup con veeam

  Licenza essential Plus vmware.

  Bene...

  End da subito ero entusiasta di questa soluzione anche is vedevo nella SAN UN punto delicato.

  All'epoca non conoscevo nulla di IOPS / s e compagnia bella.

  So e ragionando informandomi knew vari forum ho trovato che probabilmente una soluzione più semplice e più economica managed directly by da vmware could VSA appunto essere.

  Quindi per esempio, nello specifico:

  2 * brain con 12 R720XD 3.5 "- 12 * 600GB 15K Server.

  quindi he consueto RAID10 fisico... e sopra vmware VSA.

  (PS: which point it sparirebbe unique failure introduced dalla SAN di cui sopra)
  

  E who... mi fermo e mi rivolgo a Voi, infinitamente più FSE di me... by the way dei consigli e valutazioni in merito.

  Grazie, ansioso di argomentare he seguito.

  Lo spazio netto total sara di 3.6 TB circa, in NFS Datastore diviso da 2 1.8 TB circa.

  The Nic per server must be at least 4.

  The macchina esterna affiliate by he VSA Service of Cluster (quorum).

  Dal preventivo seems to me di understand che Azro delle licenze OEM from VMware.

  Fatti UN preventivo Reed rates da some partner VMware, what risparmiare qualcosina e avresti it VMware supporto e invece di quello Dell.

  Ciao

• Execution of ESX under ESX with a HP VSA SAN Guest

  Hello

  I run an ESX host as a physical ESX host by these steps.  Both are on ESX4.1.  I imported the HP VSA SAN on ESX virtual host to test some scenarios, but I can't at all stages of start-up it is because it is showing the error below.

  

  Do you know how I can fix this problem?  I looked online and it could be due to the BONE for comments being unable to see a compatible processor to boot the 64 bit OS.  I wanted to disable the paravirtualization, but I can't locate under Options > Advanced Options > settings for the VM VSA paravirtualization.

  Do anyone know how I can fix this problem so I can test in these conditions?  Thanks in advance for any help.

  You can't execute nested 64 bit VMs with ESXi 4.  No amount of change options will change that.

• Remove the virtual SAN HP P4000 VSA

  Hello

  We have 2 Dell poweredge 2950 host running vpshere 4.0 and we have virtualized internal storage of these Dell using P4000 VSA happening as a virtual machine on each host. Our virual servers use this storage.

  Recently, we introduced NetApp FAS2020 on our network and we move all the virtual servers for the netapp.

  My question is "what is the best way to remove theP4000 VSA Vsphere? (I don't want leave no trace). We don't have support with HP and could not find much information on the web.

  I've attached screenshots of the console management VSA and vsphere.

  Concerning

  Azalarab

  Hello.

  These are just virtual machines that use the local VMFS storage on servers, so to get rid of them first to power them off.  Then right-click on them and choose "Delete from Disk.  This will permanently delete.

  Good luck!

• All disks in a single host went from vSAN

  Hello

  I recently had a power cut at home. My 3 node cluster came back OK, but I noticed that the vSAN was missing lots of storage.

  After investigation, it seems that all the disks in a single host have been abandoned (all 4 were operating before the incident).

  I tried to reboot the host, but this has not solved the problems I encounter.

  My file server is unable to turn on because of that, I think it was resynchronize components during the power failure happened.

  Because I have data on these discs (my file server), I hesitate to re - install ESXi on the host or do something with the disks

  I am due to upgrade my version of 3 disc format, but that he was reluctant to do this either at the present time because of my data!

  Environment:

  - vCenter Server Appliance 6.0 U2 (build 3634794)

  -ESXi 6.0 Update 2 (build 3620759) on all hosts

  Please can someone advise on the measures I should then carry out?

  See below for information and some screenshots.

  Thank you

  Metadata health check informs me that the disks have failed, but all 4 disks functioned as expected before the power failure:

  

  Research in the "Virtual SAN health status" column, it shows no health information on disks

  

  Comparison to another host:

  

  The host CAN display the disks on it's HBA, see below:

  

  Update:

  Managed to find the size of the memory heap LSOM and the command 'secret' to increase

  For my own sanity and to keep track of what I did, here's what I did.

  You can see where I had already changed their values before the default.

  

  Edit:

  The command VMWare wanted to keep this secret is in their archives here:

  http://vmware1140.rssing.com/Chan-4263175/all_p2889.html

  I do not understand why VMware wants to keep this command of the community? Currently, I am testing now with the two heapsizes to the maximum configuration. My host is starting

  He typed at the origin:

  Dear Simon,

  I tried:

  vsish EI Setup/config/LSOM/intOpts/heapSize 2047

  to increase the heapsize memory LSOM has allocated,

  then did restart, without success on 192.168.240.55,

  He is still unable to establish the Group of disks with memory error...

  And this has changed to:

  Dear Simon,

  I tried the command you gave me in the SR to increase the

  HEAPSIZE memory LSOM allocated, then did restart.

  without success on 192.168.240.55.

  He is still unable to establish the Group of disks with memory error...

• SAN health service virtual VMWare

  Hello

  Any who stumbled upon this question. We are in the process of updating the vcenter 6.0 to 6.0U1. During the upgrade Setup attempted to stop vsan-health service that didn't exist, and the upgrade has been abandoned. I try to install the plugin from vsan, the installation was successful, but the windows service has not been registered. Here is the log of errors and hope that someone can help me to resume the service.

  '"D:\Program Files\VMware\vCenter Server\vpxd\scripts" ' is not recognized as internal or external, command an executable program or batch file. "= VMWare Virtual SAN Health Service installed = '.

  Thanks in advance

  Found fixed the name of the VMWARE_PYTHON_BIN variable doesn't have the full path to: \Program Files\VMware\vCenter Server\python\python.exe

• Regarding switch SAN

  Recently, we bought 2 Cisco SAN switch. Part configuration remains at the side of the customer. I have not yet used. Need ideas for payment of fees.

  They already have 2 storage SAN, 4 physical servers and they want SAN on HA.

  We have 12 ports on two SAN license and we have 24 SFP connector

  From what I have learned, it is we don't have to stack cable for HA. We can do this by using the LC connector.

  Also read VSANS, Zones and port channel. Why do we need to VSAN, port and canal zone.

  Why do we actually use SFP and LC cables? I am told that the STS can run to 8 Gbps. Prices SFP LC times to a faster speed.

  How can I configure SAN to work properly?

  Older document, but it contains the answers to all your questions:

  http://www.Cisco.com/en/us/docs/storage/san_switches/MDS9000/SW/rel_2_x/...

• Global vs FIC VSAN specific on NGC

  What is the difference and therefore the impact of the creation of a global VSAN (VSAN noticeable to both fabric interconnect) rather than creating a VSAN FIC - A and FIC - B-specific?

  I create Global and then assign one to vHBA - a FIC - A and the other to vHBA-b on FIC - B.

  Also, with the FC Switching (UCS 1.4) this (set) get worse?

  Aida,.

  This comes down to design.  Most people like to keep their completely separate SAN fabrics.  Unlike in the passage where the uplinks are crisscrossed every way imaginable for redundancy, in the CF world, that's all that separates your fabrics.  For this you would normally connect a FI to a single switch SAN (fabric-A) upstream and the other END to their other (fabric (B).  You would create the VSAN on the fabric of interconnection rather than overall as you do not need two available on the two FI VSANS.

  Another approach is to create in the world, but in this design, need you either a link between each FI and SAN EACH switch or use VSAN circuits (assuming the two VSANS exists on both the SAN upstream switches). The complication here is when you set your vHBAs, you must assign them to a VSAN on A or b.  It is a hard hairpin and offers benefits without hot spare. There is no failover with CF as there is for the Ethernet (aka Fabric Failover).  All CF redundancy is managed at the level of the BONE by multipathing drivers.

  The first design keeps your CF much more simple and deterministic access.  You know that all vHBAs connected to the fabric Interconnect-A go to VSAN X, and all the vHBAs related to the fabric Interconnect-B go to VSAN Y.  This is assuming that you're only using two VSANS for your environment.

  The only time wherever you need FC switch mode is if you plan use direct attach FC/FCoE tables with your interconnections.  There is no increase in complexity here regarding the VSAN design, same best practices apply.

  Kind regards

  Robert

• UCS connection to SAN switches

  I set up direct UCS in the SAN before, but not San switches to connect.  My understanding of the main differences between the two is as follows:

  (1) with SAN switches, you configure VSAN.  To do this, go to the SAN-> SAN Cloud tab and configure your vSAN ID here.  Then in your vHBA template, configure it to use the proper vSAN ID you configured under cloud of SAN.  Nothing else to do here?

  (2) whereas with direct-attached storage connect FI - A SPA and SPB and FI - B to SPA and SPB, with san switches will FI - A ' switch-1' and FI - B is going to "switch-2'."  Is this correct?  If so, anyone know why it should be that way?

  No problem, tbone-111

  As much as I know, that two vHBAs are supported at this time.  It is best to use 1 from the face and side b 1.

  The vHBAs that are used depend on which WWPN you zoned on your boot LUN.

  For the following example, assume the following group:

  1.) my vHBAs are named vHBA_A1, vHBA_B1, vHBA_A2, vHBA_B2 (A tissue face a and B for b-side)

  (2.) vHBA_A1 is the first HBA on my side, and vHBA_B1 is the first HBA on b-side

  AND

  3.) WWPN of the HBA is zoned properly my boot ports storage processor (SP) of the LUN on the FC switch

  AND

  4.) WWPN of the HBA is hidden correctly on my table LUN

  Those are logical, ANDS, they must ALL be true to prevent headaches later.

  5.) disk Array A0 and B1 SP ports are connected to my A fabric FC switch.  A1 and B0 are connected to my fabric B.

  6.) this example of strategy will start A fabric be the path of MBR

  Best practices - FYI, having at least 2 SAN political Boot (1-A-side, 1 for side b and distribute among your Service profiles).

  In my startup policy, I check the will to apply vHBA naming option and specify my names of vHBAs (sorry I have no screenshots available.  Everything started with a new company and do not yet have access lab).

  My primary SAN parameter can be: the main target: wwpn of A0 and secondary target: B1 wwpn

  My secondary SAN setting can be: the main target: wwpn of B0 and secondary target: A1 wwpn

  It would be a good idea to speak with the Admins of storage while you set up the first two servers to boot on each fabric for all troubleshooting.

  If the zoning and LUN masking are configured correctly, you should see WWPN listed during the boot sequence of UCS server to the point where the starting CF driver is loaded.

  Of course, download TAC Cisco on the line, if you encounter obstacles that you can not go beyond.

  I hope this helps,

  Trevor

  ======================================================================================

  If my answers were useful somehow, please note accordingly.  Thank you!

  Post edited by: Trevor Roberts Jr

• UCS Fiber Channel FI for San switch wiring & config

  My question is about the correct wiring & vSAN configuration by the UCS FI switch San (Cisco MDS).

  Currently my wiring is as follows:

  Fi1 port 25 - SW1 port 3

  Fi1 port 26 - SW2 port 3

  Fi2 port 25 - SW1 port 4

  Fi2 port 26 - SW2 4 port

  On the side of the switch San, our guys of storage configured vlan10 SW1 and SW2 as vlan20. For this reason, I was not able to have a vSAN by FI, I read is recommended, because the VLAN switch cross FIs. Now, when I created vHBAs I have 4 vHBAs per server, 2 by IFS by vlan if I want redundancy with a switch or a loss of FI.

  Question: Is this the correct configuration on the side of the SAN switch? Do I actually create 4 vHBAs per server? I do not have my incorrect wiring & I should just be linking FI1 to SW1 on two ports & FI2 to SW2?

  Help or advice would be appreciated!

  ~ Tara

  Hi Tara,

  There are two ways of wiring of your SAN infrastructure.  It boils down to a design decision. Traditionally the SAN admins prefer to keep their separate/isolated tissue.  In this design THAT MDS-1 only connect to FI - A and MDS-2 would connect only to the FI - B.

  Another option is to connect each MDS at each END.  This gives each FI SAN fabric access and allows to create double VSANS (that exists on each FI) rather than separate them.

  You don't need four vHBAs by UCS Server - some adapters support no more than two in any case.   What you do is create two vHBA by the Service profile, each host will have access both to VSAN 10 and 20.  What you can do is to shift your tissue of vHBA while 1/2 access your Service VSAN 10 via FI - profiles and the other half access VSAN 10 FI - B.  This will help to distribute the load accordingly.

  E.g.

  First 1/2 of SPs

  vHBA0 - VSAN10 - fabric-A

  vHBA1 - VSAN20 - fabric-B

  1/2 second of SPs

  vHBA0 - VSAN20 - fabric-A

  vHBA1 - VSAN10 - fabric-B

  As you can see a bit of a manual balancing can act.  The best scenario would be to isolate (re-cable) to your network SAN fabrics according to the traditional SAN design above.

  Kind regards

  Robert

• trunk VSAN 6248 uplink interface

  Hi all

  I'm new to the UCS platform,

  I want to master multiple VSANs in FI 6248 on the single interface / portchannel. to 5548 upstream switch. Since the location of different heterogeneous storage 2.

  Ask let me know opportunities, configurations or any recommendations are available for configuring it.

  Hello Christine,.

  You can enable port FC port trunking and create port channels for FI of UCSM CF (SAN tab > SAN clouod).

  On N5K, you must enable fport-channel-trunk feature and create CF port-channel.

  Padma