Removal of VMs - best practices?

Similar Questions

• What best practices to remove a host server data store without emptying the contents of the data store

  Hi all

  This question was probably asked a million times. the best practice to remove a host server data store without emptying the contents of the data store?

  I have two clusters and I moved host group A to group B. host A is now to see data from Cluster Both A store and Group B datastore. We want that host A to store data in Cluster B. The Cluster a data store is not and can not be empty coz VM A Cluster using data warehouses. So I just unpreset the data LUN to host A store and Reanalyze the data store? Or there is a better way to do it?

  Thank you all

  Yes that's what I meant - should have specified where virtual machines are running.

• Removes the source of capture-best practices

  What are the best practices for capturing removes the source (10g)? I need to put the data in the data warehouse. Asynchronous CDC can do the job, but should I be aware of? If someone can talk about best practices of implementation of this? Other options?
  Thanks in advance.
  
  Published by: Rinne Sep 23, 2010 11:05

  do a delete trigger or enable auditing
  concerning

• Design by using NetApp's best practices

  I am preparing for my VCP5 and I read the new book by Scott Lowe. the book describes how the traffic should be isolated. your vMotion, vmkernal, etc., but in many organizations, I see the NetApp with some of data warehouses and a few LUNS to CIFS share LUNS. I guess you can have your vmMotion on a VLAN separated, but would not safer just configure a windows VM file server to host your files? In freenas and openfiler forums, they stress is not to run their software in virtual machines in a production environment.   Physical separation would be better then just a VLAN? I was inking and correct me if I'm wrong. I think the CIFS shares in a virtual hosting machine would SAN, vMotion, vmkernal, most reliable if you have redundant switches on both sides VMware hosts. So if your kernel switches drop your vmware environment will not drop.

  > traffic must be isolated.

  Yes, the network traffic must be split on networks separated for various reasons, including performance and safety.

  > NetApps with MON a few for data warehouses and a few LUNS to CIFS share.

  Yes, if you have a NetApp file server you can block-level storage server as FCP or iSCSI, CIFS or NFS file-level storage.

  > I guess you can have your vmMotion on a VLAN separated, but would not safer just configure a windows VM file server to host your files?

  OK, you lost me.  Yes, you must separate the vMotion traffic to enhance the performance and because the vMotion traffic is not encrypted.

  I don't see where you're going for vMotion to a Windows file server?

  However, if you are referring to, why don't you your NetApp instead of Windows CIFS Server:

  You don't need to patch and reboot the NetApp at least once a month.

  Performance is better

  You don't need to buy a Windows license and then maintain Windows

  Snapshots.  NetApp has the best shots in the business.  When your Windows I/O high, or just typing box because it of Tuesday and removes all of your VSS snapshots you really wish you had a NetApp.

  > In the forums of freenas and openfiler, they stress is not to run their software in virtual machines in a production environment.

  Note that there are a ton of storage there equipment running as VMs and server NFS for shared storage, including left and they have been stable for years.

  > Physical separation would be better then just a VLAN?

  Yes, if you have the infrastructure.  When it comes to the first time I've seen reference you VLAN?  Are you talking about now the NetApp as the series 2020 with two network cards where you need to carry all traffic (managent, CIFS and iSCSI) through them via VLAN?

  Like this: http://sostechblog.com/2012/01/08/netapp-fas2xxx-fas3xxx-2-nic-ethernet-scheme/

  > I was inking and correct me if I'm wrong. I think the CIFS shares in a virtual hosting machine would SAN, vMotion, vmkernal, most reliable

  CIFS is nothting to do with SAN, vMotion or VMkernel.  CIFS (SMB) is the protocol used mainly by Windows file sharing

  > If you have redundant switches on both sides of the VMware hosts. So if your kernel switches drop your vmware environment will not drop.

  You always want to redundant switches.  No single point of failure is the best practice.

• Roles, permissions - DataCenter, file, Cluster, host Layout - best Practices\How-to

  Have a little problem with permissions and roles. I'm sure it will be an easy one for those of you with more experience of working with roles. I hope that my layout organization made with quote boxes is readable.

  The Organization has just spun a new host ESXi 4 for developers and added in vCenter. Developers want to use the vSphere Client\VIC to manage the ESX Server. They need rights to create virtual machines, remove VMs, clone VMs, VMs potential power. However, we don't want them to be able to reach production.

  According to the diagram below, the new host of development, labeled as "HostC (autonomous DEVELOPMENT host)", is located under "Data Center-City-2", who also owns the production ESX clusters. " And obviously I don't want developers having rights on production groups.

  Lets say I have create a role called 'HostC Dev Sandbox Rights', add users and assign directly to "HostC" below. This role contains the VM 'create' right, however when I run the wizard Creation of VM of HostC as a member of the role the vSphere Client tells me this task requires rights create VM on the level of data center! But given these developers to create VMS access on the data center would give them rights to create virtual machines in the poles of Production! Which is obviously a problem.

  I can't believe that our need to give these rights to ONLY one host in a DataCenter is rare. I don't know that there is a misunderstanding on my part of how to configure VMware roles for best practices.

  Anyone with more expirence on VMware roles ready to help me on this one? Thanks in advance!

  Organization representative Schema using quote boxes:

  vSphere (vCenter Server)

  City of DataCenter-1

  Many cases, clusters, hosts

  City of DataCenter-2

  FolderA (Division A)

  ClusterA (A Cluster of Production)

  HostA1 (Production host in Group A)

  HostA2 (Production host in Group A)

  %Windir%$NTUninstallKB941568_DX8$\Spuninstb (division B)

  Focus (Production Cluster B)

  HostB1 (Production host in Group B)

  HostB2 (Production host in Group B)

  HostC (autonomous DEVELOPMENT host) - under %windir%$NTUninstallKB941568_DX8$\Spuninstb but not in the cluster

  City Center-3

  Many cases, clusters, hosts

  You can apply permissions directly to the data store.  I didn't need to go further than the clusters in our environment, but what really works for you is to place data warehouses in folders for storage.  Have the records be the names of your groups hosts and clusters.  Then place the warehouses of data for each cluster in the corresponding folder.  Then, just apply permissions for the data on the record instead of warehouses in each individual data store.  Off topic a little, but a records of something in the store of data discovered lack is the function of "views of storage" and I put a future application.

  Yes, if you set permissision to the view of the data store the user can turn opinion and see.  Extensive your permissions framework tests is guaranteed before pushing users.  Looks like you are already doing.

• What is the best practice to move an image from one library to another library

  What is the best practice to move an image from a photo library to another library of Photos ?

  Right now, I just export an image on the desktop, then remove the image from Photos. Then, I open the other library and import these images from the office in Photos.

  Is there a better way?

  Yes -PowerPhotos is a better way to move images

  LN

• Code/sequence TestStand sharing best practices?

  I am the architect for a project that uses TestStand, Switch Executive and LabVIEW code modules to control automated on a certain number of USE that we do.

  It's my first time using TestStand and I want to adopt the best practices of software allowing sharing between my other software engineers who each will be responsible to create scripts of TestStand for one of the DUT single a lot of code.  I've identified some 'functions' which will be common across all UUT like connecting two points on our switching matrix and then take a measure of tension with our EMS to check if it meets the limits.

  The gist of my question is which is the version of TestStand to a LabVIEW library for sequence calls?

  Right now what I did is to create these sequences Commons/generic settings and placed in their own sequence called "Functions.seq" common file as a pseduo library.   This "Common Functions.seq" file is never intended to be run as a script itself, rather the sequences inside are put in by another top-level sequence that is unique to one of our DUT.

  Is this a good practice or is there a better way to compartmentalize the calls of common sequence?

  It seems that you are doing it correctly.  I always remove MainSequence out there too, it will trigger an error if they try to run it with a model.  You can also access the properties of file sequence and disassociate from any model.

  I always equate a sequence on a vi and a sequence for a lvlib file.  In this case, a step is a node in the diagram and local variables are son.

  They just need to include this library of sequence files in their construction (and all of its dependencies).

  Hope this helps,

• 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 design of a printing environment?

  Greetings,

  If there is a better place for this, please let me know.

  Objective:

  Redesign and redeploy my printing environment with best practices in mind.

  
  

  Overview: VMWare environment running 2008 R2, with about 200 printers. I have a majority of printers HP ranging from 10 years old again. LaserJet MFP, OfficeJets, etc... etc... In addition to the copiers Konica, Xerox and Savin. Many of our models of printer are not taken in charge in 2008, and still less x 64.

  Our future goals include services eprint, as well as the desire to manage the print quality, and levels of consumition by something like Web Jetadmin.

  Currently we have a 2003 Server x 86 server running our printers very old and 6 months ago the rest on a single x 64 server 2008r2. We ended up not giving it the attention to detail, it is necessary and pilots have become very congested, this led to a PCL6 only, UPD update that ended up corrupting several drivers through the UPD PCL 5 and 6 of the spectrum. At this time, we brought a second server 2008r2 and began to emigrate to those affected. In some cases, we were forced to remove manually the drivers off the customer system32-> coil-> driver and reinstall.

  I've not had much luck finding good best practice information and thought I'd ask. Some documents I came across suggested that I should isolate a universal driver to a single server, such as 3 servers for PCL5, PCL6, and Psalm then, there is the need to deal with my various copiers.

  I appreciate your advice, thank you!

  This forum focuses on the level of consumer products.  For your question you can have the best results in the forum HP Enterprise here.

• Physically, move a server blade in a different location - best practices?

  Hello

  Is there a best practice to move a physical blade to another location?  I can't find a document about it.

  We want to move a slide to another location due to keep grouped similar environments but do not want to disassociate the profile.

  Can we just unassign, and then take it out and put in another location and let it automatically reactivate.  The profile will remain with the server?

  You say - associate profile and then re - associate profile again?

  Thank you

  A

  Hi Adrien,.

  Thank you for poining, I guess I wrote too soon.

  Yes it takes the decomission.

  Here are the steps to update:

  (1) shut down the operating system on the blade,

  (2) Disassocite the service profile, wait dissociate it in full (check the status on the WSF of the blade tab)

  (3) Decomission the blade of the UCSM (check the status on the tab of the WSF for the process)

  (4) to remove the blade from the current location,

  (5) move the blade into the slot again.

  (6) wait for blade to discover fully (even once, check the condition of the WSF of the blade tab), you may be required to validate / recognize the slot to accept the blade and trigger the discovery.

  7) once discovered associated with the profile back

  (8) start the dos operating system.

  I would check the documents and let you know.

  . / Afonso

• Best practices to move a volume

  Hello

  What is the best practice to move a volume to a PS4100 to another PS6100

  PS two are not in the same group.

  Today, we have a PS5000 which reproduce on the PS4100. The administrator create 2 volumes on the PS4100 (because there is not enough space on the PS5000).

  We will replace the PS5000 with a new PS6100XV, and we want to move the volume of the PS4100 to the new PS6100.

  What is easiest way to do this with minimal downtime on this volume?

  I think that it is best to create a replica of volume 2 of the PS4100 to the new PS6100, disconnect the volume of the PS4100 and put the volume on the PS6100 online. fix?

  Thank you

  You can replicate as you have described.  Depending on the host operating system it may be easier to do at the level of the host.   With VMware ESX, you can move live VMS using vMotion Storage.

• denying denying interceptor inline best practices

  We recently deployed an inline IPS solution using software 5.1 7 E1. We wish to refuse-attacker-victim-pair-Inline for a few signatures on a particular subnet on the network but to destroy the rest.

  To implement this correctly, I think that we must use Action SigEvent filters on the sensor and use the commands > for all subnets agree that we want to allow deny actions for.

  I have seen that in the configuration of the sensor, you can implement in the section > a > statement. My understanding is that does more for fleeing rather than deny solutions online.

  Am I right about that?

  Please could someone on the list post that it is the best practical solution to deny deny attackers inline.

  create 2 event action filters.

  The first action event filter will match signatures and subnets you want to deny on and do not subtract all actions. Make sure that you set to "stop the match".

  The following will match the same signature but the address 0.0.0.0 - 255.255.255.255. remove the appropriate actions.

  The net result is that the filter action first event will apply when it matches and the second when it doesn't.

• Best practices: linking opportunity data step contact SFDC

  Hi - I was hoping someone could give me a best practice to manage and automate the following use cases.

  I have tried a number of different things in Eloqua but met a roadblock.

  CASE OF USE/PROBLEM:

  I need to remove contacts from a campaign of education that are associated with a designated SFDC opportunity as won.
  I realized my first step, which is to remove a contact from a campaign by referencing a custom object.

  However, I need updated chance data mapped to a contact to handle all upward.

  Thus so, my real problem is updated (every 30 minutes or more) data in the custom about opportunities object table.

  What I've tried map data updated to a contact opportunity:

  (1) auto Synch the opportunity table an object custom

  I was able to bring opportunities but the email address/contact data is stored on the Contact role table so no e-mail address were brought in Eloqua.

  (2) automatic synchronization on the Contact role opportunity table an object custom

  This works if I do an automatic synchronization and automatic synchronization does not work with the updated filter, and the last successful Upload Date.

  Is it possible to change the filter to make the data when the opportunity is changed and not the role of Contact?
  And if so, can someone give me direction on how to implement that in Eloqua?

  If you know of something else to do to manage this entire upward please let me know. I appreciate any assistance.

  Blake Holden

  Hi Kathleen,.

  I understand. Below shows you an automatic synch successfully pull data in the role of opportunity Contact SFDC Eloqua. Once a week, I still don't have a full automatic synchronization to ensure that all data from, but most of the time, it is entirely automated.

  Blake

  

• 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 :)