Restaurar es normal, si queremos podemos redirigir la restauración a una ubicación disinta copiarlo a la máquina con VMWARE, etc...
El problema es cuando creamos una máquina virtual y utilizamos el disco que hemos restaurado.
Al iniciar la máquina nos da un error como este:
Failed to open disk scsi0:0: Unsupported or invalid disk type 7. Ensure that the disk has been imported
Lo que hay que hacer:
# cd /vmfs/volumes/4ea1d6da-96726826-9557-002219d568cb/vm-win7test
# vmkfstools -i vm-win7test.vmdk -d zeroedthick vm-win7test1.vmdk
Utilizar la función zeroedthick para importar correctamente el disco, ocupara todo el espacio, pero al menos tenemos levantada la máquina.
Extraido de:
http://skabelka.com/node/136
VMware: Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7" error when trying to power on a VM on ESXi 5
Submitted by Vitalii on Sat, 02/04/2012 - 04:47
I got this error when I tried to
power on VM just imported from another VMware ESXi Server into my
virtual environment based on VMware ESXi 5.
I got a message such as
"Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0,
'/vmfs/volumes/4ea1d6da-96726826-9557-002219d568cb/vm-win7test/vm-win7test.vmdk'
Failed to open disk scsi0:0: Unsupported or invalid disk type 7.
Ensure that the disk has been imported."
To fix this problem, I had to reimport the VM using the "zeroedthick" argument for the "vmkfstools" command:
# cd /vmfs/volumes/4ea1d6da-96726826-9557-002219d568cb/vm-win7test
# vmkfstools -i vm-win7test.vmdk -d zeroedthick vm-win7test1.vmdk
Destination disk format: VMFS zeroedthick Cloning disk 'vm-win7test.vmdk'... Clone: 100% done.
With the "zeroedthink" option, a flat file is created with complete
disk size allocated to the file. For example, my Windows 7 was created
to use 60GB file, so a ".vmdk" file of 60GB is created.
Other supported disk formats are explained below.
When you create or clone a virtual disk, you can use the -d
–diskformat suboption to specify the format for the disk. Choose from
the following formats:
. zeroedthick (default) – Space required for the virtual disk is
allocated during creation. Any data remaining on the physical device is
not erased during creation, but is zeroed out on demand at a later time
on first write from the virtual machine. The virtual machine does not
read stale data from disk.
. eagerzeroedthick – Space required for the virtual disk is allocated
at creation time. In contrast to zeroedthick format, the data remaining
on the physical device is zeroed out during creation. It might take
much longer to create disks in this format than to create other types of
disks.
. thick – Space required for the virtual disk is allocated during
creation. This type of formatting doesn’t zero out any old data that
might be present on this allocated space. A non-root user is not allowed
to create this format.
. thin – Thin-provisioned virtual disk. Unlike with the thick format,
space required for the virtual disk is not allocated during creation,
but is supplied, zeroed out, on demand at a later time.
. rdm - Virtual compatibility mode raw disk mapping.
. rdmp – Physical compatibility mode (pass-through) raw disk mapping.
. raw - Raw device.
. 2gbsparse - A sparse disk with 2GB maximum extent size. You can use
disks in this format with other VMware products, however, you cannot
power on sparse disk on an ESX Server host unless you first reimport the
disk with vmkfstools in a compatible format, such as thick or thin.
. monosparse – A monolithic sparse disk. You can use disks in this format with other VMware products.
. monoflat - A monolithic flat disk. You can use disks in this format with other VMware products.
