DRS storage recommendations

Similar Questions

• Change the PowerCLI Script to use the DRS and DRS storage

  Hello

  I have a PowerCLI script that specifies a host and a data store to create a new virtual machine, which has served us well. Now we have activated the DRS and DRS storage and I wonder what to change in order to take advantage of these features. Are there commands to specify a cluster and the cluster data store and let the DRS to decide the initial investment for a new virtual machine? At the moment we put all hosts and the warehouses of data as variables and use them in the line below.

  Thank you.

  $newVM = New-VM-name $NewVMname - VM $TemplateName Datastore - $datastore - VMHost $vHost - confirm: $false - location $myName

  You set a Datastorecluster?

  If Yes, then you can replace the value of parameter data with the datastorecluster object store.

  Replacing a VMHost with a cluster is not taken in charge I'm afraid.

  But you can use something like this

  New-VM-name TestVM Datastore - DSC - ResourcePool (Get-Cluster-name mycluster |) Get - Resourcepool - name of resources)

  This will automatically select the VMHost.

  The virtual machine appears in the root of the cluster.

  DSC is the name of a datastorecluster in the cluster mycluster

• Use the case of the Cluster data without DRS storage store?

  Can someone tell me please the use case of the Cluster data without DRS storage store?

  Virtually no,.

  The only one that is useful is the aggregation of resources of data warehouses in a cluster data store. But it is aggregation of resources in its crudest form. When you create a virtual machine and the use of a cluster as the destination data store, you must always select the data store that will store the virtual machine.

  Storage DRS off =

  No calculation of initial investment

  No space load balancing

  No I/O load balancing

  No rule affinity VMDK

  No maintenance mode

  For this purpose a group of data without active DRS storage store is a kind of a data store folder.

• DRS storage - storage pools

  I was wondering about a question; If I don't have storage DRS (Enterprise license, no company +) then he even would have no value to set up storage pools (Cluster data store)?  Most of the literature on Clusters of data store is all about storage DRS, but if I don't have that, so what's the advantage?

  Environment of small size; 8 guests, 70 guests.

  True, Ent + is necessary for automatic migration drives VMDK, but you can still use the maintenance mode on a data store and the kickoff of the migration of storage. In addition, there is still the feature of initial implementation of a group of data store that still work without SDR, which is quite handy.

  But, you are right that most of the magic of a data cluster store is coupled to also have storage DRS, I hope that answers your question.

• DRS storage and the ASB

  Interesting question delegate froom:

  When setting a storage DRS cluster, is possible to add a specific attribute data stores in a cluster?

  Yes. I did a lot of time. VSA data warehouses are simply NFS volumes at the end of the day, & DTS fully supports both NFS & VMFS data stores.

  However the licensing question. You need to make sure that you have a license that supports DTS functionality.

  Since we are aiming the ASB in small and medium-sized businesses, many of these customers can buy a company more license for DTS.

  http://www.VMware.com/products/vSphere/buy/editions_comparison.html

  HTH

  Cormac

• Storage recommendations

  We are a small shop 2 running ESX 4.0 currently hosts with only local storage. We will host SQL on 2 of the virtual machine.

  I'm looking for advice on storage shared with decent performance, fault tolerance and scalable. Budget is $ 10,000.

  The EVA4400 I watched is twofold.

  The MSA1000 is terrible gear - I have my own horror stories about it and so do many others.

  The MSA2000 is a very different material.

  -Matt

  VCP, vExpert, Unix Geek

• ESX host with local storage recommended for the host partition table?

  Hi all

  I know that the best practical partition table should look like this:

  Mount Point	Partition	Size	Description
  		/ dev/sda (primary)
  / Boot	ext3	250 MB	Change of extra space for upgrades
  N/A	SWAP	1 600 MB	Change the maximum size of Exchange service console
  /	ext3	5120 MB	Change of extra space in the root
  		/ dev/sda (Extended)
  / var	ext3	4096 MB	Create partition to avoid an overflow of root with log files
  / tmp	ext3	1024 MB	Create partition to avoid an overflow of root with temporary files
  / opt	ext3	2048 MB	Create partition to avoid overfilling root with the log files of VMware HA
  / Home	ext3	1024 MB	Create partition to avoid an overflow of root with agent / user files
  	vmkcore	100 MB	Pre-configured

  However with a system with local storage would you set it up the same way, and whatever it is must be amended to change to get ESX to write log files to the different partitions?  I would like to configure it for future expansion for when the enterprise package is configured.

  Yes, I would set up the same way with an ESX with local storage server and nothing needs to be changed for the vmekernel right at the partition/var - unless of course you want to write to a log server that you need to change a configuration file to point to the server logs.  If you talk to the ESX Enterprise license you willnot have to change partiition table-

  Also on something else if you don't have a SAN/NAS storage you will also need to create a VMFS partition on the local data store to host your virtual machines

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

• Threshold of the DRS Migration recommended

  Using a threshold of the middle of the road product migration a situation where some hosts are overuse RAM and others are underutilizing.  What are the possible caviats / setting of traps to pass a threshold of 4 or 5 migration aggressive?

  What types of problems / benefits were seen with this people?

  Thank you

  VMotion operations take a long time.

  But also consume resources: for example, the memory of the VM (for a while) is used on the source and the destination. Also, TSP is lost (and must be re - build if necessary) when a virtual machine is migrated.

  So, I agree with previous post to stay on a level balanced or conservative.

  André

• Please explain SVmotion (Storage Vmotion) and DRS for storage in simple words

  Friends,

  I little confusing... could you please contact Storage vmotion and DRS for storage in simple words and the important points to remember in this regard...

  Kind regards

  Sirot

  9884106697

  Storage DRS is a feature that you allow warehouses of data aggregated on a single object (cluster) and recommend the implementation of disks in virtual machine based on the performance of the store of data and the available space on the data store.

  The DRS storage uses Storage vMotion to migrate virtual (online) computers from a data store to another to balance data store performance and space.

  You can use Storage vMotion without storage DRS too, moving virtual machine between clusters of DRS storage and warehouses of data even from the local level to the data store shared.

• Storage of hybrid matrices 3 with Betclic

  I have 2 6500ES and 1 6100XS used by 8 ESX hosts approximately 130 virtual machines running.  Performance is important, but I migrated just my MD3000i data on the 6500's, so I already see an improvement... the SSD is impressive.  :)

  I have 3 questions

  1.) can I do 1 pool or 2?  I currently have them in 2 pools, however, I wonder if just do 1 pool and let the faders EQL to load all the work assumes that do it for me... I don't want to have to check the use of the e/s between the basins as I went and manually or using DRS storage so I don't have to. E/s of store DRS requires turning on storage i/o control, which is not recommended according to practice Documentation best EqualLogic VMWare - I'm guessing that because it could hinder the decisions of swing for the loading of the SAN.

  I think I read that best practices says 2 pools, but I don't know if it takes 3 hybrids account.

  With the exception of the virtual machine our data are pretty ephemeral. Receive us a small amount of data, create a large amount of data, duplicate, save it, deliver, then he sits for a period of time before being archived and purged.

  (2.) I think higher than the latency of reading expected when Ops ARE on the 6500 / s fall below 500 Kbps.  It of not crazy high, but revolves around the range 8ms.  I disabled delayed ACK, who brought 12-15 latency time, and want to disable TCP offloading the next maintenance window.  But, is this normal?  My 6100 remains generally less than 2ms read and write

  Updates to the firmware 3) -is it safe to do in activity? Or I really need to stop all my ESX hosts before you do?  The documentation says to do when there is low usage... Does this mean that status at the HQ of SAN said low? or what is considered to be low? Is the same applies to the hard drive firmware updates?

  Thanks in advance!
  David

  Re: 1. I suggest that keep you in the two pools.  Only because of the difference in size between the 6500's and 6100 s.   You could go to 3 swimming pools, but they run you the risk of having to move virtual machines to balance IO.

  Re: 2. I'll try also turn off RSO, great Recieve Offload.

  Re: 3 upgrades.  E/s low means when the table is not widely used.  So yes, a low e/s of SANHQ reading would show that.  If your company is not active 24 x 7, so it's normal after hours time span weekend.   Most important is giving the login_timeout 60 ESXi servers and by setting the disktimeout value to 60 in virtual machines.  With the recent firmware the time required to failover and early response is usually less than 30 seconds.  But not always, one may be closer to 60 seconds under load.  It is also essential to ensure that the switch ports happen immediately on the transition.  (AKA portfast)   This way when the CM goes down, the ports are online immediately.    In addition, to be able to handle a FW update also means you can manage a CM failover on a HW problem.

  Disc FW updates.   Yes.  The updates take place one disc at a time.   Then, the player is power rolled, to update the FW.   That time is very fast, and single e/s to this player is paused, then resumed once the player comes back online.   But again, the best time is low i/o.

  In a perfect scenario, yes make upgrades in a window of Maint would be ideal.  At least stop the virtual machines.   In this something unexpected occurred offshore lucky.

  Since it is ESXi you run at least 6.0.7 firmware?

  Kind regards

• Questions about the implementation of clusters of storage and DTS on active cluster

  I have a few questions about the implementation of clusters of data store and SRS storage in VSphere 5.1.

  We have a data center with about 15 HP blades and a few servers non-lame.  The hosts are all either VSphere 5.0 or 5.1.  Our back-end storage is an EMC VNX 5700 with about 20 stores of data.  All the VMWare is managed by VCenter 5.1 running on a dedicated physical machine.

  Currently, each data store is used individually; No piles of data store are put in place.  When a new virtual machine is created, the administrator usually chooses the data with the most space store.  Periodically, we will go back and manually storage vMotion machines to balance the load.

  Recently, we have expanded the VNX storage, so we now have LUNS in different pools, with different levels of performance.

  What I would do is set up for the data store clusters, so that us when a virtual machine is created, the administrator must not know what data store is in which pool.  Also take advantage of the DRS storage so that the burden of storage will be "refine" himself a little.

  I know the setting up of a cluster of storage in a 'clean' environment is quite simple, but my concern is creation/conversion data warehouses existing in active production in the cluster, while they are used.

  If I access the screen "data warehouses and store data from clusters ', right-click on the data center and create a cluster, and then move the various data stores in the new cluster, will there be an interruption in the production running systems?

  I also wonder about activation of storage i/o control.  It is not currently enabled on data warehouses.  I know it's useful for the StorageDRS, but will be allowing any negative impact on the system?  If I turn on the warehouses of data, is there anything else I should do or set in addition to all that allows him?

  Finally, we are in the process of Site Recovery Manager configuration.  SRS has an impact on the configuration of the data clusters and DTS store?

  Thanks in advance for your comments.

  Mike O.

  Gregg Robertson wrote:

  Hello

  Clusters of data and using DTS store doesn't impact RS even if you create a cluster of data store for storage of replicated data and another for everyone else, this way you machines virtual you want to replicate are not moved on warehouses of data that are not replicated , but will still have the ability to move if there is a conflict.

  Gregg

  With all due respect but SRM and DTS don't go together. SRM does not at all support the use of DTS. So if you are configuring SRM forget DTS for now.

  Reason for this is that SRM knows no DTS and VMs can be in flight when a failover should occur, and bad things can happen. Also, the protection breaks when a virtual computer is moved between data warehouses in a cluster data store.

  In short: don't go there.

• I need a storage policy

  I would like to take advantage of this group of ideas.

  -2 machines, single processor Quad Core Xeon 5430 - 2.66 GHz (Harpertown), SCSI RAID 1, 4 GB, 146 GB 10 000 rpm.

  -VMware ESXi on both.

  -Operating system is FreeBSD 7.1 64 on virtual machines.

  -For all 5 computers virtual and load balancing for a manual failover.  For example assignments change IP in the Panel when there is a problem.  DNS round robin load balancing.

  This is not a typical VMware environment.  My interest is not consolidate servers but rather portability, performance and failover reserve.  Balanced load site is a web server that serves the time between 12,000 and 45 000 unique visitors.  The disk controller is not a cheapie so it is quite it bit faster than a single SCSI on readings and has no visible punishment on writing, not that it matters because I am not related to records in the native environment.  In the native environment, I use most of the 4 GB of ram, that's why we are moving to 64-bit.  We are are proven, we can run this on a single dual AMD server, but it is typed too.  As we move this site anyway, I decided to use it as a test for ESXi.  If she can stand in virtue of the present, I have no need to worry about its use anywhere.  After all, server consolidation is to make a server even when busy, no?  This will make busy.

  In addition to being open to criticism of the plan above, I don't think I have a good conservation strategy. I need your ideas on a strategy for the SCSI, store backups VM and VM and user data operating systems models.

  Thanks for your comments!

  Hello

  One of the things I've heard in the in the webinar was NOT at volumes local VMFS of installation, not even for the swap.  I do not have available CF, but I do iSCSI and NAS.  I have a kvm, the box is on the list of compat, but I can't seem to install a USB stick to boot from, so I guess I'll need a little mirror to launch the ESXi so that I can connect to the virtual machines on the iSCSI.  Since we are talking about the software initiators, we talk about moving the SCSI, treatment of the HBA to the CPU, making it the largest RAM and CPU.  What you say about it?

  Yes, this is exactly the case.

  I read at: http://blogs.vmware.com/storage/2008/07/vmwares-proprie.html on the VMFS.

  "Clustering - the device second and vital of VMFS is supported for sharing or grouping. VMFS is responsible for the coordination of several independent ESX safely servers, read and write in the same block device. «It's VMFS that manages the basis for safe transfer of the ownership of the data from one server to the other during the VI high level such as vmotion, DRS, storage vmotion, HA, etc.» * Comment to the Webinar: * "RDM is required for clustering when you twoVMs on two different ESXi servers."

  The last statement is for Clusters of shared within the VM disk. Don't not to store the virtual machines. You cannot use local VMFS. Even though I always like to have one for reasons of redundancy. What happens if the storage matrix dies for some reason any? I have enough local disk to run virtual machines from there if necessary.

  I would like to clearly understand the meaing of these statements.  For example we say in a situation of balance of load that you have several servers to access the same data VM on the same logical unit number?  If so, how that is arbitrage?  DBMS would certainly be a special case.

  The VMFS is up-to-date, you will need to store your virtual machines on a Cluster to the current file system, which might be NFS, or VMFS on iSCSI.

  What NFS/iSCSI servers you plan to use?

  Best regards

  Edward L. Haletky

  VMware communities user moderator

  ====

  Author of the book "VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.»

  Blue gears and SearchVMware Pro Articles: http://www.astroarch.com/wiki/index.php/Blog_Roll

  Security Virtualization top of page links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

• DTS related question

  Let me make the following more detailed information:

  http://pubs.VMware.com/Release_Notes/en/VRA/vrealize-automation-701-release-notes.html

  • Spend an a vSphere storage DRS data store to another causes the system to delete instead of create a VM *.

  If you move a data store a vSphere DRS storage cluster to another group of DRS vSphere storage and level of automation of the target cluster is not automatic, replenishment created machine causes the system remove the machine with the following error: StoragePlacement: data store not specified by drive in VM DTS-people with reduced mobility. This problem will not occur if the virtual machine is cloned.

  Solution: Check that the automation of the target cluster level is set to automatic before moving a cluster DRS storage data store one vSphere to another.

  Known issues that the above is related to the vRA? This seems to be related to only vSphere environment without vRA.

  It is of vRA, but under a set of very specific circumstances: by selecting the action day 2 "reconfiguring" after the store of the migration data to a cluster of data store that does not DTS set to automatic.

  Grant

• SVMotion individual disks

  I can svmotion one a vdisk virtual machine at the same time? or do I have to move all the virtual drives in a virtual machine to a new data store at the same time?

  Yes, you can simply select the advanced option on the data store selection screen, select the specific virtual disk that you want to migrate, and then select the destination data store.

  Store the configuration of virtual machines and disks files in different places.

  one Click Advanced. b For the virtual machine for each virtual disk configuration file, select Browse and select a data store or cluster storage DRS. c (Optional) If you selected a cluster DRS for storage and do not use Storage DRS to this virtual machine, select Disable DRS storage for this virtual machine and select a store of data within the storage DRS cluster. d Click Next.

  Migrate a virtual machine with Storage vMotion in vSphere Web Client

• Displacement of the VM attached to several data stores

  ESX 5.1.  I'm moving from one SAN to another.  I have a Windows VM file server that is attached to the "OS" data store which is 100 GB (for the OS, program installation, etc.) and the data store 'Data' that is 500 GB (where the file real stock data is stored).  On the new San, I created new warehouses of data, "New_OS" and "See you."

  What is the best way to move my data to the new data warehouses?  I know that I can use storage VMotion to move the virtual computer, but who will attempt to move the 'BONES' and 'Data' to 'New_OS' correct?  (Which of course will not work, since there is not enough space.)  I think that I have to remove 'Data' of the existing virtual computer, move it to 'See you' via a browser data store, move the computer virtual using VMotion, then add "you see?"  This sounds more complicated than it should be.  Am I missing something here?

  Thank you.

  Am I missing something here?

  Yes, it lacks the 'Advanced' option in Storage vMotion which will allow that move you each hard to a data store different... to do this, just follow the screens of Storage vMotion and select the data store, click on advanced and for each virtual hard disk and virtual machine configuration file, select the data store you want.

  Take a look at the documentation: http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-A15EE2F6-AAF5-40DC-98B7-0DF72E166888.html

  Store the configuration of virtual machines and disks files in different places.

  one Click Advanced. b For the virtual machine for each virtual disk configuration file, select Browse and select a data store or cluster storage DRS. c (Optional) If you selected a cluster DRS for storage and do not use Storage DRS to this virtual machine, select Disable DRS storage for this virtual machine and select a store of data within the storage DRS cluster. d Click Next.