Best practices VM Machine

Hello

I have a general question. Is it better to create a volume and store all virtual machines on it, or is it a better idea to create a volume for each individual virtual machine? Please list some advantages and disadvantages.

Thank you

With Equallogic, you can use Manager of AutoSnapshot for VMware, which could be very powerful.

But in this case is better to have 1:1 for the virtual machine and the Volume.

André

Tags: VMware

Similar Questions

  • Single user, working on both machines, best practical question

    I use Dreamweaver at home and at work.  I'm working on my sites only.  I have just started working with DW and don't know the best practice to achieve.  The way I do now is through a folder synchronized on both machines that hosts the site.  The establishment is a local folder on the two machines that automatically syncs on the WWW.  I created a site on my machine at home with a folder root for the site and the images and then created another site on my work machine and was pointing at the root sync folders.  Is the best practice for this set to the top.

    I guese that im afraid of is the feature of auto update of links and such to within DW.

    Thank you!

    I have the same configuration and DW Check In / Check Out feature works for me.

    This requires a local copy of the site on home and work machines more copy remotely on the web.

    I have check no matter what files I need to work, modify and then download and archive when I'm done.

    DW manages everything.

  • Machines and ESXi ESXi virtual memory best practical considerations

    We have a new Infrastructure built current and capacity planning that happens. It would help if someone can provide me with best practices on the hardware requirements while building ESXI hosts.

    See the technical white paper for a bit more on this topic below.

    https://www.VMware.com/PDF/Perf_Best_Practices_vSphere5.5.PDF

  • Best practices Oracle 11 G database machine

    We currently have a production on 10g database which us will be upgrading to 11g 2 on the database device. On this database, we have a staging area, a data warehouse and an Operational Data Store. (all to separate the schema). My question is what is the best practices in the implementation of our new Oracle database environment?
    Should separate us the area of transit, Data Warehouse and the Operational Data Store in their own individual database? What are the advantages and disadvantages of doing this?
    I'm looking for expertise on what to do?

    Thank you
    PAM

    Reference to Oracle data warehouse architecture is below...
    http://www.Oracle.com/us/solutions/Datawarehousing/058925.PDF

    See you soon
    David

  • Best practices on how to code to the document?

    Hello

    I tried to search the web tutorials or examples, but could not get to anything. Can anyone summarize some of their best practices in order to document the LabVIEW code? I want to talk about a quite elaborate program, built with a state machine approach. It has many of the Subvi. Because it is important, that other people can understand my code, I guess that the documentation is quite large, but NEITHER has yet a tutorial for it. Maybe a suggestion ?

    Thank you for your time! This forum has been a valuable Companion already!

    Giovanni

    PS: I'm using LabVIEW 8.5 btw

    Giovanni,

    Always:

    Fill in the "Documentation" in the properties of 'VI '.

    Add description to the controls of its properties

    Long lines label

    Label algorithm, giving descriptions

    Any code that can cause later confusion of the label.

    Use the name bundle when clusters

    Add a description tag in loops and cases. Describing the intention of the loop/case

    Follow the good style guide as will make reading easy and intuitive vi.

    I'm sure there are many others I can't think...

    I suggest you to buy "LabVIEW style book", if you follow what this book teaches you will produce good code that is easy to maintain.

    Kind regards

    Lucither

  • Just improved m tips on best practices for sharing files on a Server 2008 std.

    The field contains about 15 machines with two domain controllers, one's data is the app files / print etc...  I just upgraded from 2003 to 2008 and want to get advice on best practices for the establishment of a group of file sharing. Basically I want each user to have their their own records, but also a staff; folder. Since I am usually accustomed to using windows Explorer, I would like to know if these actions can be done in the best conditions. Also I noticed on 2008 there is a feature of contacts. How can it be used? I would like to message or send an email to users their file locations. Also, I want to implement an admin at a lower level to handle the actions without making them far in on the server, not sure.

    I read a certain bbut I don't like test direct more because it can cause problems. So basically a way short and neat to manage shares using the MMC, as well as the way that I approach their mail from the server of their actions. Maybe what kind of access cintrol or permissions are suitable also for documents. Also how can I have them use office templates without changing the format of the model.

    THX

    g

    Hello 996vtwin,

    Thank you for visiting the Microsoft Answers site. The question you have posted is related to Windows Server and would be better suited to the Windows Server TechNet community. Please visit the link below to find a community that will support what ask you:

    http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

    Hope this helps J

    Adam
    Microsoft Answers Support Engineer
    Visit our Microsoft answers feedback Forum and let us know what you think

  • Dell MD3620i connect to vmware - best practices

    Hello community,

    I bought a Dell MD3620i with 2 x ports Ethernet 10Gbase-T on each controller (2 x controllers).
    My vmware environment consists of 2 x ESXi hosts (each with 2ports x 1Gbase-T) and a HP Lefthand (also 1Gbase-T) storage. The switches I have are the Cisco3750 who have only 1Gbase-T Ethernet.
    I'll replace this HP storage with DELL storage.
    As I have never worked with stores of DELL, I need your help in answering my questions:

    1. What is the best practices to connect to vmware at the Dell MD3620i hosts?
    2. What is the process to create a LUN?
    3. can I create more LUNS on a single disk group? or is the best practice to create a LUN on a group?
    4. how to configure iSCSI 10GBase-T working on the 1 Gbit/s switch ports?
    5 is the best practice to connect the Dell MD3620i directly to vmware without switch hosts?
    6. the old iscsi on HP storage is in another network, I can do vmotion to move all the VMS in an iSCSI network to another, and then change the IP addresses iSCSI on vmware virtual machines uninterrupted hosts?
    7. can I combine the two iSCSI ports to an interface of 2 Gbps to conenct to the switch? I use two switches, so I want to connect each controller to each switch limit their interfaces to 2 Gbps. My Question is, would be controller switched to another controller if the Ethernet link is located on the switch? (in which case a single reboot switch)

    Tahnks in advanse!

    Basics of TCP/IP: a computer cannot connect to 2 different networks (isolated) (e.g. 2 directly attached the cables between the server and an iSCSI port SAN) who share the same subnet.

    The corruption of data is very likely if you share the same vlan for iSCSI, however, performance and overall reliability would be affected.

    With a MD3620i, here are some configuration scenarios using the factory default subnets (and for DAS configurations I have added 4 additional subnets):

    Single switch (not recommended because the switch becomes your single point of failure):

    Controller 0:

    iSCSI port 0: 192.168.130.101

    iSCSI port 1: 192.168.131.101

    iSCSI port 2: 192.168.132.101

    iSCSI port 4: 192.168.133.101

    Controller 1:

    iSCSI port 0: 192.168.130.102

    iSCSI port 1: 192.168.131.102

    iSCSI port 2: 192.168.132.102

    iSCSI port 4: 192.168.133.102

    Server 1:

    iSCSI NIC 0: 192.168.130.110

    iSCSI NIC 1: 192.168.131.110

    iSCSI NIC 2: 192.168.132.110

    iSCSI NIC 3: 192.168.133.110

    Server 2:

    All ports plug 1 switch (obviously).

    If you only want to use the 2 NICs for iSCSI, have new server 1 Server subnet 130 and 131 and the use of the server 2 132 and 133, 3 then uses 130 and 131. This distributes the load of the e/s between the ports of iSCSI on the SAN.

    Two switches (a VLAN for all iSCSI ports on this switch if):

    NOTE: Do NOT link switches together. This avoids problems that occur on a switch does not affect the other switch.

    Controller 0:

    iSCSI port 0: 192.168.130.101-> for switch 1

    iSCSI port 1: 192.168.131.101-> to switch 2

    iSCSI port 2: 192.168.132.101-> for switch 1

    iSCSI port 4: 192.168.133.101-> to switch 2

    Controller 1:

    iSCSI port 0: 192.168.130.102-> for switch 1

    iSCSI port 1: 192.168.131.102-> to switch 2

    iSCSI port 2: 192.168.132.102-> for switch 1

    iSCSI port 4: 192.168.133.102-> to switch 2

    Server 1:

    iSCSI NIC 0: 192.168.130.110-> for switch 1

    iSCSI NIC 1: 192.168.131.110-> to switch 2

    iSCSI NIC 2: 192.168.132.110-> for switch 1

    iSCSI NIC 3: 192.168.133.110-> to switch 2

    Server 2:

    Same note on the use of only 2 cards per server for iSCSI. In this configuration each server will always use two switches so that a failure of the switch should not take down your server iSCSI connectivity.

    Quad switches (or 2 VLAN on each of the 2 switches above):

    iSCSI port 0: 192.168.130.101-> for switch 1

    iSCSI port 1: 192.168.131.101-> to switch 2

    iSCSI port 2: 192.168.132.101-> switch 3

    iSCSI port 4: 192.168.133.101-> at 4 switch

    Controller 1:

    iSCSI port 0: 192.168.130.102-> for switch 1

    iSCSI port 1: 192.168.131.102-> to switch 2

    iSCSI port 2: 192.168.132.102-> switch 3

    iSCSI port 4: 192.168.133.102-> at 4 switch

    Server 1:

    iSCSI NIC 0: 192.168.130.110-> for switch 1

    iSCSI NIC 1: 192.168.131.110-> to switch 2

    iSCSI NIC 2: 192.168.132.110-> switch 3

    iSCSI NIC 3: 192.168.133.110-> at 4 switch

    Server 2:

    In this case using 2 NICs per server is the first server uses the first 2 switches and the second server uses the second series of switches.

    Join directly:

    iSCSI port 0: 192.168.130.101-> server iSCSI NIC 1 (on an example of 192.168.130.110 IP)

    iSCSI port 1: 192.168.131.101-> server iSCSI NIC 2 (on an example of 192.168.131.110 IP)

    iSCSI port 2: 192.168.132.101-> server iSCSI NIC 3 (on an example of 192.168.132.110 IP)

    iSCSI port 4: 192.168.133.101-> server iSCSI NIC 4 (on an example of 192.168.133.110 IP)

    Controller 1:

    iSCSI port 0: 192.168.134.102-> server iSCSI NIC 5 (on an example of 192.168.134.110 IP)

    iSCSI port 1: 192.168.135.102-> server iSCSI NIC 6 (on an example of 192.168.135.110 IP)

    iSCSI port 2: 192.168.136.102-> server iSCSI NIC 7 (on an example of 192.168.136.110 IP)

    iSCSI port 4: 192.168.137.102-> server iSCSI NIC 8 (on an example of 192.168.137.110 IP)

    I left just 4 subnets controller 1 on the '102' IPs for more easy changing future.

  • Best practices for the configuration of virtual drive on NGC

    Hello

    I have two C210 M2 Server with 6G of LSI MegaRAID 9261-8i card with 10 each 135 GB HDDs. When I tried the automatic selection of the RAID configuration, the system has created a virtual disk with RAID 6. My concern is that the best practice is to configure the virtual drive? Is - RAID 1 and RAID5 or all in a single drive with RAID6? Any help will be appreciated.

    Thank you.

    Since you've decided to have the CPU on the server apps, voice applications have specified their recommendations here.

    http://docwiki.Cisco.com/wiki/Tested_Reference_Configurations_%28TRC%29

    I think that your server C210 specifications might be corresponding TRC #1, where you need to have

    RAID 1 - first two drives for VMware

    RAID 5 - 8 hard drives within the data store for virtual machines (CUCM and CUC)

    HTH

    Padma

  • The ESXi 4.1.0 to 6.0 upgrade. -upgarde and best practices

    Hi guys,.

    We are a small business with a single physical server, ESXi 4.1.0 installed with approx. 8 VMs. We plan on buying Essential Kit 6.0 ESXi because that's all we need right now. However, as VMWare says that 4.1.0 to 6.0 upgrade is NOT supported (matrices of the interoperability of products VMware), how we improve our host and VMS?

    I guess the correct way will be upgraded from 4.0. 5.5 U3 first, then to 6.0. However, if we buy the 6.0 license essential Kit, that we will be able to always download and install and upgrade of the host and all VMs to U3 5.5, and 6.0. Essentials?

    In addition, what are the best practices to upgrade a single host with multiple virtual machines? What I did research, we should back up important files from virtual machine, all critical data, etc. All recommendations are welcome. My understanding is that the upgrade also virtual machines will be upgraded automatically, that's correct - methods of upgrade to ESXi 5.5 (2058352) | VMware KB

    Best regards

    D. Stanchev

    Hello

    As you said, you cannot upgrade host ESXi 4.x to 6.x, you must first upgrade 4.x to 5.x and then switch to 6.x

    Before moving to 5 or 6, make sure you ESXi host is compatible with ESXi 6.

    Check cheque and VMware hardware compatibility list if your server is listed.

    Although you'll have a 6 ESXi license kit, you can download ESXi 5.x and use it to upgrade process.

    Only if you need to use 5.x permanently, then you need to get your license keys downgraded to 5.x, otherwise once you upgrade host to 5.x, go ahead and level to ESXi 6.x

    Backup-

    Before you begin the upgrade, make sure that you have backup of all VMs critics.

    Either you can download/export all VMs as OVF, or you can use Veeam's free edition to make the backup of virtual machines

    -Update

    You can join the server ESXi ISO Installer and boot server form ISO and update.

    During the Installation process make sure to select ' PRESERVER VMFS and upgrade ESXi host '

    If you do not keep vmfs, all virtual machines will get deleted during the installation/upgrade process.

    Once you get ESXi Host upgrade to Upgrade VMFS 5.x version so that it can support 6.

    Then finally the ESXi host to 6.x upgrade, yet once make sure PRESERVE you VMFS during installation.

    If you have vCenter Update manager, use update reach the average upgrade easy it is to upgrade.

    Thank you

    Hentzien

  • vCenter Best Practices Database

    I'm looking for the VMware documentation that tells me that if it is advisable to keep the vCenter and vCenter database on a different machine in the production environment.

    My about 500 VMs infrastructure and I currently have the DB and vCenter on the same machine.

    I keep DB on a separate machine is better than having the single point of failure and I think that's what vmware recommends.

    However I'm looking for the Vmware documentation that points.

    I went through the best practices database link in the doc that you shared.

    strange, that VMware has not mentioned clearly anywhere if it's good to keep the DB and vCenter application on separate computers.

    Documentation need concrete who can back up.

    Thanks for your update :)

  • VRA7 deployment best practices

    Hello

    I'm looking at in the deployment of VRA7 with the NSX.

    is it always best practices to get your vm management running on a cluster that is different to your virtual machines in the workload, the reason why I ask is NSX, with this integrated is better she is hung up on a vcentre or two.  I found the documentation below but I al looking for a little more in detail in the physical setup and roll cventres how much a typical would need.

    vRealize Automation 7.0

    see you soon

    Hi Skoch, thanks for the reply.

    I imagined he would have a lot of bugs but our outgoing env is UAT, so we have an opportunity to upgrade and just continue to work with 7 and keep up to date... I think that 7 gives us some great improvements so hopefully worth long term.

    We are trying to do the update in April / may so fingers crossed a new update is released.

    see you soon

  • I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

    I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

    Hello

    Please check the content below, you may find useful.

    Please refer to the URL: Documentation VMware Site Recovery Manager for more detailed instructions.

    Important

    Check that there is no cleanup operation pending on recovery plans and there is no problem of configuration for the virtual machines that protects the Site Recovery Manager.

    1 all the recovery plans are in ready state.

    2 the protection status of all protection groups is OK.

    3 the status of the protection of all the individual virtual machines in the protection groups is OK.

    4 the recovery of all groups of protection status is ready.

    5. If you have configured the advanced settings in the existing installation, note settings you configured before the upgrade.

    6 the vCenter local and remote server instances must be running when you upgrade the Site Recovery Manager.

    7 upgrade all components Server vCenter Site Recovery Manager on a site until you upgrade vCenter Server and Site Recovery Manager on the other site.

    8 download the setup of Site Recovery Manager file in a folder on the machines to be upgraded the Site Recovery Manager.

    9 make sure no other facilities-\no updates windows restarts done shoud

    Procedure:

    1. connect to the machine on the protected site on which you have installed the Site Recovery Manager.

    2. backup the database of Site Recovery Manager by using the tools that offers the database software.

    3. (optional) If you upgrade of Site Recovery Manager 5.0.x, create a 64-bit DSN.

    4 upgrade the instance of vCenter Site Recovery Manager server that connects to vCenter Server 5.5.

    If you upgrade a vCenter Server and Site Recovery Manager 4.1.x, you upgrade the instances of vCenter Server and Site Recovery Manager server in the correct sequence until you can upgrade to Site Recovery Manager 5.5.

    a upgrade vCenter Server 4.1.x to 5.0.x server.

    b Update Site Recovery Manager of 4.1.x to 5.0.x.

    c upgrade server vCenter Server 5.0.x to 5.5.

    Please let me know if it helped you or not.

    Thank you.

  • Best-practice for hardware virtualization?

    Hardware virtualization is disabled by default when I create new virtual machines in my VMware clusters. But what are the best practices for this what settings are recommended? Are there reasons NOT to activate the hardware virtualization?

    IMO there is no advantage in allowing virtualization of hardware if you have no need for the virtual machine (for example, a virtual host of the ESXi).

    André

  • Best practices for backup of a VM Web server?

    This question comes from another thread, that I created, but I figure I might as well start a thread fresh since it is his own question.

    Basically, I have an environment that I inherited when I started my new job within this environment, there is a lonely VM that runs from our Web server and was created using VMware player (will go to the workstation for the snapshot feature).

    I am extremely concerned by the fact that there is no backup strategy for it, so I'm interested in finding the best way to save this virtual machine.

    Being that it's a machine virtual I instantly thought, but of course I'm open to dictate what best practices.

    A lot of what I've read so far indicates to stop or suspend the virtual machine, then copy files, however is there a way to do that without temporarily take down my Web server?  It's just that we have customers in the world that has access to the server to different time zones and I want her to be in place 24/7.

    You'll have to stop the Virtual Machine and close VMware Player and uninstall VMware Player to install VMware Workstation and it is the time where you should make a backup copy of the master of the Virtual Machine.  Once installed VMware Workstation and the Virtual Machine is back and then runs to reduce the minimum time for subsequent backups you necessarily do not do such proposed by Richardson Porto although I don't disagree with what he says.

    In theory anyway, and in practice, when you want to backup you would take a cliché Hot and then copy the Parent disk such that it is now read-only and the Virtual Machine is still running while you make a copy of the Parent disk.  Once you have copied the Parent disk, you can then remove the snapshot thus merging Delta and drive Parent and now ready for the next time you want to back up the drive.  The duration of that Virtual Machine is interrupted during the snapshot warm and hot snapshot delete should be considerably less and then stop and restart the virtual machine.  The reason why I said "in theory" because while it is supposed to work in practice, nevertheless if you correctly shutdown the guest operating system before capture instant, so you do not rely on VMware Workstation to make sure that everything works all in being hot.  Not that you should have problems, it's hot, however you remove a layer of the process that has the potential of being wrong compared to when is cold, even if it is cold takes a little longer.

    In both cases, I would avoid cloning because it changes the UUID and MAC address of the clone of the parent company and by creating a second occurrence technically need a second license for the Windows operating system that is installed on the cloned virtual machine.  In other words an archived copy complete or exact unedited from the original is a legitimate backup a clone of IMO is a second occurrence but it has a different UUID and MAC address.  It would be like taking a copy of the operating system with a single license and install on two different physical computers.  Also by doing as I have suggested and make a backup copy of Master of the Virtual Machine and then just save the Parent read-only disks disk hard virtual are themselves not a computer virtual and just that copy a backup, however can be used to restore the same Virtual Machine driven and not having not any changes in the UUID MAC addresses etc.

    Finally, you should look into what you are running in the guest operating system and how to properly save Web Site and database, or user data etc in the guest operating system.  In other words, you should always have a copy backup of the virtual machine and everything that is necessary in the guest operating system to be able to restore it without necessarily restore all of the Virtual Machine.  IMO it's better to have several and backup types to have more options in a recovery scenario!

  • Best practices for network configuration of vSphere with two subnets?

    Well, then I'll set up 3 ESXi hosts connected to storage shared with two different subnets. I configured the iSCSI initiator and the iSCSI with his own default gateway - 192.168.1.1 - targets through a Cisco router and did the same with the hosts configured with its own default gateway - 192.168.2.2. I don't know if I should have a router in the middle to route traffic between two subnets since I use iSCSI ports linking and grouping of NETWORK cards. If I shouldn't use a physical router, how do I route the traffic between different subnets and use iSCSI ports binding at the same time. What are the best practices for the implementation of a network with two subnets vSphere (ESX host network: iSCSI network)? Thank you in advance.

    Install the most common iSCSI would be traffic between hosts and

    the storage is not being routed, because a router it could reduce performance.

    If you have VLAN 10(192.168.1.0/24) iSCSI, VLAN 20 (192.168.2.0/24) ESX

    MGMT and VLAN 30 (192.168.3.0/24) comments VMs and VLAN 40 (192.168.4.0/24)

    vMotion a deployment scenario might be something like:

    NIC1 - vSwitch 0 - active VMK (192.168.1.10) MGMT, vMotion VMK (192.168.4.10)

    standby

    NIC2 - vSwitch 1 - current (VLAN30) guest virtual machine port group

    NIC3 - vSwitch 2 - active VMK1 (192.168.1.10) iSCSI

    NIC4 - vSwitch 2 - active VMK2 (192.168.1.11) iSCSI

    NIC5 - vSwitch 1 - current (VLAN30) guest virtual machine port group

    NIC6 - vSwitch 0 - MGMT VMK (192.168.2.10) standby, vMotion

    VMK (192.168.4.10) active

    You would place you on VLAN 10 storage with an IP address of something like target

    192.168.1.8 and iSCSI traffic would remain on this VLAN. The default value

    gateway configured in ESXi would be the router the VLAN 20 with an ip address of

    something like 192.168.2.1. I hope that scenario help set some options.

    Tuesday, June 24, 2014 19:16, vctl [email protected]>

Maybe you are looking for