Storage of P2V of NFS mounted in a virtual machine

Similar Questions

• Virtual machines deployed on VSAN without selected with THICK disk storage policy

  Hello

  We had an admin build 50 VMs on our data VSAN store but did not choose the VSAN storage policy while he got the default which allows you to have the THICKNESS of the disks provisioned

  I have chnaged any of the virtual machines to use the VSAN storage policy (which uses a thin) but the virtual machine is still using all the space

  Is there a way to make virtual machines recover white space, now they have a VSAN storage strategy?

  Yes - I have to agree with Duncan. I don't think that there is a way to return/reduce the size.

  An idea is, if you have additional storage, Storage vMotion VM to NFS or VMFS, converting to thin and then back to VSANS with a policy that doesn't have a "thickness".

  Try it with a VM - see if it works.

  A bit of a drag, I know, but I can't think of any other casual way.

  HTH

  Cormac

• Mount a file ISO in multiple virtual machines simultaneously.

  Hello

  I found I can mount the same ISO file to virtual CD 8 VM simultaneously, but failed with the ninth VM. Is there a limitation on this subject?

  Thank you.

  The ISO is mounted in a virtual machine running on an ESX ESXi host, a file lock is held on the ISO file. Each host for the file connection consumes a lock. There is a maximum of eight locks possible for a file residing on a VMFS 3 datastore. This limits the amount of hosts of virtual computers that can access a disk for a cluster of eight ESX/ESXi hosts. This restriction applies to the files of virtual disk (VMDK), ISO CD/DVD images, floppy disks or any other file.

• Random virtual machines after vMotion and Storage vMotion network loss

  Hi all -

  I have a couple of tickets open with VMware and our supplier of SAN, EqualLogic, on this issue.  Since the configuration of our production and DMZ clusters we noticed that the virtual machines will sometimes drop network connectivity after a successful vMotion and Storage vMotion.  Sometimes, although much less frequently, virtual machines also spontaneously lose network overnight.  What happened only a few times.  The strange thing is that the other guests on the VM host are fine - they lose any network.  Actually, I can do no more than 3 computers virtual host to another, and 2 of 3 can switch correctly, so that we lose the network.  The work around?  Simply 'disconnect' from the virtual NETWORK card 'reconnect' and the virtual machine will start the return packets.  I can also switch the VM troubled return to the host State and it will find the network.  I can it reboot and re - win network.  I can re - install the virtual card completely, and she re - win network.

  VMware has seen a lot of mistakes of SAN in our log files in order to update us our SAN firmware to the latest version.  That seems to have fixed that but we still have the issue.  Here are some of the specifications - all environments are virtually identical except for memory:

  Of PowerEdge R810

  NICs Broadcom 5709

  EqualLogic SAN running 5.0.5 F/W

  We use frames.  ESXi is fully patched.  I haven't seen a boss or not, it is only some guest operating system that loses the network, but we are a Windows environment.

  When a virtual machine loses the network, we can not:

  • Ping to it
    
  • Ping it
    
  • Ping him at the virtual machines on the same host or vSwitch
    
  • Ping outside our network
    
  • resolve DNS, etc..
    

  I followed some KBs VMware without success, including:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003839
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & externalId = 1002811 (port security is not enabled)

  -All the VMware tools have been updated to the latest version correct and corresponds to the ESXi host
  -Connected to the service ESXi console, I cannot ping the VM problem by name of host or IP address, but I can ping do not affected by the issue of the OTHER virtual machines.  I can also pings the service console.
  -Connected to the troubled virtual machine itself, I cannot ping other virtual machines, I can't resolve host names, I cannot ping by IP.  The machine virtual CAN ping itself by IP, but not hostname.  I cannot ping other virtual computers on the same virtual switch or network by either IP or host name.  I can't ping the vSwitch network management.
  -All vSwitches are configured in the same way and the same.
  -Notify the switches is set to yes
  -There are a lot of available virtual ports
  -We tried the E1000 and VMXNET virtual cards with no difference.
  -All cards are configured to negotiate, but we tried to force individuals speeds as well as with no difference

  I appreciate your help.  I have problems getting anywhere on this issue with the sellers.

  wkucardinal wrote:

  Still having the issue...

  Sometimes, it might be useful to really check that all uplinks VMNIC for all VLAN does work them. Try this is to create a new portgroup on the vSwitch used by your virtual machines on the host of the first, put a test VM on the portgroup, then go into the NIC teaming policy from the new portgroup and select "Override switch command failover."

  Then down vmnic all except one in unused, then only a single VMNIC is active. Then set the portgroup VLAN to a production of VLAN and try to see if we could ping some expected from the different addresses. If it works, then move VMNIC work until unused and move up to another asset. Try again, and this for all the vmnic. If it works, then you have verified that the configuration of VLANS and other settings are correct on the physical switch in the face of this host ports.

  If several VLANs, repeat the process for all other productions VLAN. Then repeat on the other hosts.

  While that may take some time, occurs if everything is properly configured on the physical switches. When occurs a vMotion virtual machine gets a new "Port code" and is assigned to a new outgoing VMNIC. If there is an error of configuration on one or more physical ports that might seem random, but may still happen on VLAN x on y VMNIC. Given that Port ID policy you use indeed spread randomly VMs on the vmnic these problems may be difficult to diagnose. (Make a disconnection of the VM vNIC gives the virtual machine a new port-ID, which it will move to a new outgoing VMNIC, which might seem to solve the problem.)

• When you use MS 2003 storage server, backups ESXi virtual machine

  Hello

  I have a test lab that I need to put into production, but I need to get to a backup strategy before I can do that.

  I have a server ESXi (3.5 U3) frontal 5 virtual machines that all is in an ISCSI data store that is hosted using the Microsoft 2003 Storage Server platform.

  One of the virtual machines is a file and print box that has a 500GB partition in the virtual machine, but the virtual machine is located on the ISCSI LUN. What is the best way to save these data, that I can't back up just the LUN because I believe that some of the VM configuration files to sit on the front-end server ESXi?

  The nightly backup is always back up all of the LUN (2 TB) because the virtual machine file will always be 500 GB, as it is in full expansion in the file of the virtual machine, so that the incremental backups wanted to work (or will?).

  If I am running a backup script against the host of the virtual machine that comes will produce a 500 GB backup file as it comes to the size of the virtual machine?

  Any help, suggestions or comments are welcome.

  Thank you

  If the data store for ESXi is located on the iSCSI LUN, backup of the iSCSI LUN is all you need to do.  The configuration of the Virtual Machine is stored there, and VMDK files that make up the disks.  If the 500 GB of space on the file and print box is on a LUN that is separated from the iSCSI data store, then you will need to back up both the data store LUNS and the LUNS of 500 GB.  If the 500 GB is just a VMDK file on the data store, the backup data store should get everything.

• T2p scripts fail on NFS mounts

  Hello IDM gurus!

  I'm trying to implement a multi data center (MDC) implementation of OAM 11gR2Ps3. 1 data center is in place and functioning as expected. We try to use T2P scripts described in the documentation of the OAM following MDC to clone the binary (copyBinary.sh) but you see the error message

  Error message: 1

  November 17, 2015 18:46:48 - ERROR - CLONE-20435 some Oracle homes are excluded during the copy operation.

  November 17, 2015 18:46:48 - CAUSE - CLONE-20435 following Oracle homes have been excluded during the copy operation.

  [/ data/Oracle/OAM/.snapshot/daily.2015-11-13_0010/oracle_common, data/Oracle/OAM/.snapshot/daily.2015-11-13_0010/oracle_bip, data/Oracle/OAM/.snapshot/daily.2015-11-13_0010/Oracle_IDM1, data/Oracle/OAM/.snapshot/daily.2015-11-14_0010/oracle_common, data/Oracle/OAM/.snapshot/daily.2015-11-14_0010/oracle_bip, data/Oracle/OAM/.snapshot/daily.2015-11-14_0010/Oracle_IDM1, data/Oracle/OAM/.snapshot/daily.2015-11-15_0010/oracle_common, /data/Oracle/OAM/.snapshot/daily.2015-11-15_0010/oracle_bip] data/Oracle/OAM/.snapshot/daily.2015-11-15_0010/Oracle_IDM1, data/Oracle/OAM/.snapshot/daily.2015-11-16_0010/oracle_common, data/Oracle/OAM/.snapshot/daily.2015-11-16_0010/oracle_bip, data/Oracle/OAM/.snapshot/daily.2015-11-16_0010/Oracle_IDM1, data/Oracle/OAM/.snapshot/daily.2015-11-17_0010/oracle_common, data/Oracle/OAM/.snapshot/daily.2015-11-17_0010/oracle_bip, data/Oracle/OAM/.snapshot/daily.2015-11-17_0010/Oracle_IDM1, /data/Oracle/OAM/.snapshot/daily.2015-11-11_0010/oracle_common /data/Oracle/OAM/.snapshot/daily.2015-11-11_0010/oracle_bip [, data/Oracle/OAM/.snapshot/daily.2015-11-11_0010/Oracle_IDM1, data/Oracle/OAM/.snapshot/daily.2015-11-12_0010/oracle_common, data/Oracle/OAM/.snapshot/daily.2015-11-12_0010/oracle_bip, data/Oracle/OAM/.snapshot/daily.2015-11-12_0010/Oracle_IDM1], and the possible causes are:

  1. all Oracle homes were not registered with an OraInventory.

  2 if all the Oracle homes have been saved with a unique custom OraInventory, pointer file corresponding inventory received no T2P operation.

  3 canonical path to the Oracle Home recorded with OraInventory was not child Middleware House.

  November 17, 2015 18:46:48 - ACTION - CLONE - 20435. be sure that all causes possible, listed in the CAUSE section are supported.

  
  

  .Snapshot in the error message file is a NFS function because it mounts are actually NFS volumes.

  
  

  Are the T2P scripts supported on NFS mounts? If so, how to solve this problem? Would appreciate your comments on how we can solve this problem

  
  

  Concerning

  
  

  Shiva
  

  The issue was due to wrong settings for the frames. This has been fixed by the storage team. T2P scripts were always initially and after that correction of the Storage mounts, they ran successfully. A restoration was necessary, and RCU patterns had to be recreated on the clone

• NFS mounts persist?

  Hi all

  I've updated to Win 7 Enterprise for NFS support.

  I was able to map two NFS shares successfully.

  However, upon restart, the actions are lost. Is it possible (I don't see one in the snap-snap-in mmc NFS) to indicate that they be reconnected at logon. I could use a login script in local GPO to do this, but I was wondering if there was a "better way" (tm).

  A tip for those who struggle with the NFS client: use showmount to see if Windows can even see the actions. I had to set the firewall issues, then showmount showed stocks and I was able to login and navigate through the:

  Server EI C:\Users\owner>showmount
  Export the server list:
  /nfs4exports 192.168.x.0/24
  RAID 192.168.x.0/24/nfs4exports.
  mythstorage 192.168.x.0/24/nfs4exports.

  C:\Users\owner>mount server: / nfs4exports/z: raid
  z: is now connected to the server: / nfs4exports/raid

  The command completed successfully.

  C:\Users\owner >

  Found the answer on the technet site (it's sort of, a persistent systemic mount is not possible, but using a user login script is possible.)

  Basically NFS connections are stored on a basis by user.

  "NFS mounted drive letters are specific session so running this in a script to start most likely will not work." The service would probably need to mount its own drive letters from a script that runs in the context of service. We have specific guidelines, that it is not recommended to http://support.microsoft.com/kb/180362. "

• ESXi 4.1 - blades HP and NFS mounts

  Hello

  I'm having a strange problem with NFS access

  We currently use HP Blades BL680c G5 servers, in C7000 enclosures. Configuration of the switch, Cisco (3120 x) are the same for all ports / ESXs.

  I use VMNIC0 and VMNIC1 in etherchannel / Hash IP access to the warehouses of data NFS on NetApp filers.

  I have now two servers beside I want to reverse for test reasons. These two servers are moving instead of the other.

  Once restarted, these two hosts ar sees no no more data warehouses. They appear as inactive. I can't reconnect them (VI client or esxcfg-nas - r)

  vmkping for Netapp file servers works more also.

  As soon as I put these 2 servers to their original square, everything is back to normal.

  On the side of the cisco switch ports are still configured the same. None of them are closed.

  There I'm missing something, but don't know where to look.

  Thanks in advance

  Hi Hernandez,

  If you're repatching hosts or they always use the same network cables as before (perhaps a change of IP address, or a rule on the host of the NFS export)

  don't forget, you'll have policies created on the NFS mounts 'export' these fixtures for the names of specific hosts or IPs - if you're repatching and change IP etc you can cause this export invalidation,

• Questions of NFS mount points

  I have two questions about how the NFS mount points is in fact from the point of view NFS servers.

  If the mount point of the 'outside' is considered as for example / ISO, would this mean

  1. that the directory is named "iso" or could it be a real name on the local file system on the NAS Server? (As in the names of SMB share, could be different from the name of folder.)

  2. that the folder is actually located directly on the root of the local file system, which is/ISO on the server, or would it be for example/dir1/dir2/iso and always to the outside as appearance / ISO? (As in the SMB, where 'share' creates a new root somewhere on the filesystem that is exposed to the outside.)

  ricnob wrote:

  Thank you! It would be a typical NFS-Unix/Linux server?

  Yes.

  So perhaps it is not defined in the standard how this should be done, but can vary between implementations? (* nix of course most common.)

  Possible, but does MS ever meet standards? Even their own?

  RFC1094/NFS:

  "Different operating systems may have restrictions on the depth of the tree or used names, but also using a syntax different tor represent the"path", which is the concatenation of all the"components"(file and directory names) in the name...". Some operating systems provide a 'mount' operation to make all file systems appear as a single tree, while others maintain a 'forest' of file systems... NFS looking for a component of a path at the same time.  It may not be obvious why he did not only take the name of way together, stroll in the directories and return a file handle when it is carried out.  There are many good reasons not to do so.  First, paths need separators between items in the directory, and different operating systems use different separators.  We could define a representation of network Standard access path, but then each path must be analyzed and converted at each end. "

  AWo

  VCP 3 & 4

  \[:o]===\[o:]

  = You want to have this ad as a ringtone on your mobile phone? =

  = Send 'Assignment' to 911 for only $999999,99! =

• maximum size of the NFS mounts

  Hello

  I would like to know what is the maximum size for mounting NFS into ESX (i) 4? If I need more than 2 TB, I need to use extensions iSCSI volumes. Is it the same thing with NFS or I can come up and use for example a 4 TB NFS share?

  Thank you

  Marcus

  NFS mounts have No. limit.  It is also great that you need to make.  ESX can mount NFS, that's all.  The ONLY limitation for ESX is VMFS, because ESX creates / manages VMFS volumes.  NFS mounts are managed by OTHER systems, they have their own limits.

  NFS is just a huge disk hard as far as ESX is concerned.

• How to start vmware after NFS mounts

  OK, so now I have solved the mystery of editing.  I'm looking for the gurus of linux on how to change the sequence of boot for mounts NFS are made prior to the VMware service.

  I use Centos 5.3 on the host.

  Phil

  Hello

  You must configure vmware to start after nfs and network.

  A simple example makes it easier to understand:

  LS /etc/rc3.d/S*network

  /etc/rc3.d/S10network

  LS /etc/rc3.d/S*nfs

  /etc/rc3.d/S11nfs

  LS /etc/rc3.d/S*vmware

  /etc/rc3.d/S05vmware

  In this case, it may be like this:

  RM /etc/rc3.d/S05vmware

  ln-s /etc/init.d/vmware /etc/rc3.d/S20vmware

  Today, vmware always will begin after the nfs mounts.

  A saludo/best regards,.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. MUCHAS gracias!

• NFS mount options

  I just bought a Qnap NAS box that I want to share with 2 VM hosts.   I did a little research on NFS vs iSCSI and it seems that NFS has some pretty good advantage over iSCSI.  Especially when she is on a network to shared resources.

  The hosts are the two Centos 5.3.

  I wonder what would be the optimum settings (options) for the NFS mount?  I found a couple of some old site, but I wonder what people here use?  Here's a setting string that I found:

  nfsvers = 3, tcp, timeo = 600, TRANS = 2, rsize = 32768, wsize = 32768, hard, intr, noatime

  I'm heading to the coast to look at the man page for NFS now to see what these all mean...

  Thank you

  Phil

  Here's a good explanation of this thing:

  The nolock option prevents the sharing of file locking

  information between the NFS server and the NFS client. The server is

  unaware of the file locks on this client and vice versa.

  Using

  the nolock option is required if the NFS server has its NFS file lock

  the feature in a State broken or remained dead letter, but she works between

  all versions of NFS.

  If another host is accessing the same files that

  your app on this host, there may be problems if file locking

  information sharing is disabled.

  Failure to maintain good

  blocking a write operation to the same host with a read operation on

  another may cause the reader to have incomplete or inconsistent data

  (reads a structure of data/record/line that is written only in part).

  A

  locking failure between two writers is likely to have data

  loss/corruption, such as the later writing replaces the previous one. The

  changes made by the previous write operation may be lost.

  -

• Cannot add NFS mounting

  Try adding that another NFS mount to a 3.5 server.  I have an existing one on a Windows 2003 server that fits very well.  The error I get when creating is:

  & gt; Configuring the host error: cannot open the volume: / vmfs/volumes/f33bc09a-59b57f41 & lt;

  Any ideas?  It is also a 2003 server, but different from the box.

  Hello

  Looks like the esx host IP or subnet does not have access to the NFS share.

  Check the properties of the NFS server.

  http://blog.laspina.ca/

  vExpert 2009

• Windows Server 2008 R2 NFS mounted data store is read only

  I've done this dozens of times in the past, but not with this exact combination successfully:

  ESX4 U1

  Windows 2008 R2 Server Datacenter edition

  NFS Server installed. TCP Version 3.

  The normal configuration that worked in the past:

  NTFS security - total control on ANONYMOUS logon, everyone control total

  The local policies, network access: Let Everyone permissions apply to anonymous users (applied automatically by Windows)

  NFS Sharing - ANSI encoding, allow anonymous access - UID = - 2, GID = - 2

  NFS share permissions - allow all THE MACHINES read-write, ROOT access

  The data store adds OK and appears in the list of data on vClient stores and can be viewed or directly via a Console logon.

  The problem is that the data store is read only! Nothing from ESX can write, delete, or update a folder or a file on the data store. Access Windows NTFS is very well.

  This means also you cannot boot from say a CD ISO on the data store, or create a VMDK guest virtual computer on the data store.

  Given that I had zero problems with this in the past, when with the help of ESX3 or ESX4 connect to Windows Server 2003R2 or several NAS with NFS devices supported I think Windows 2008R2?

  Has anyone seen anything like this before?

  I use it currently; It works fine, but it's the way that you configure the windows nfs export without having to use a mapping service (see images)

  Also, be aware that Windows System Cache is a bit less efficient than linux (but that's ok) you just need to add additional RAM at least 16 GB for the data store busy.

  I also recommend refining delays in setting up nfs for each virtual machine host:

  NFS. HeartbeatFrequency = 10

  NFS. HeartbeatFailures = 5

  And on windows change the properties of the NFS server in the locking tab

  customer collection lock wait 5

• Method to move the virtual machines in the data store temporary so I can rebuild pool recommended NFS

  Our current data store is a mounting NFS on Nexenta (zfs), which has a pool, I need to rebuild (migration of raidz2 to mirror striped for performance). Initially, I was relying on the judgment of all virtual machines, create a new pool, copy (cp - r) of the Nexenta console all virtual machines to the new pool, recreating the pool mirror and then copy (cp - r) all the data back.

  I have seen several discussions on this topic and seems like the simplest method would be to use the feature to "Migrate" so that the virtual machines are not fragmented. However in some of my pre-test when I copy a virtual machine between the basins of the Nexenta console it appears (from the data store Explorer) to initially create the vmdk provisioned and then once completed it copy looks too thin.

  I hope that I can simply copy the Nexenta console, using the option "Migrate" in vCenter on each of my 40 MV looks like it would be * quite * tedious compared to the simple issuance of an order of 'cp - r' and leave all the copies of VMs (1.5 to) during the night and then adding them to each host.

  Does anyone have experience with this? Or maybe a way to generate scripts easily (?) the option "migrate" in vCenter?

  Thank you all!

  You can select multiple VMs in vCenter regularly using CTRL + click or shift + click and both migrate them as long as they have the same storage destination.  You can also schedule it as a task.    Add manually each computer virtual back in hand is not less painful than migrating individually, anyway.