How to download a ready-made virtual machine from Windows and open it in VirtualBox and VMware Workstation. Converting TIB file to VHD Is it possible to install a copy on vmware tib

By converting a file to another file extension, you can use other programs to service it. But we should not forget that the TIB file, after conversion to VHD, may differ slightly from the original, for example in the placement of data. The most vital information should be saved, but if you are interested in the file being identical after converting from TIB to VHD, you should act judiciously and select the appropriate application from the list below. This doesn't guarantee that the conversion will be 100% as expected, but it can still help a lot. If, nevertheless, the effect of converting the TIB file to VHD did not meet your expectations, you can try to find on the Internet another version of your file in the TIB format, previously correctly converted by someone else into a VHD file. If this does not work for you, use the information presented in the next section.

Programs for converting TIB to VHD:

Other possible TIB file conversions

If after conversion TIB file You did not get the corresponding result, you can try changing the TIB file format to something other than VHD. On our website you will also find information about the following conversion options:

Converting a file with the TIB extension to another format

What other possibilities are there?

Unfortunately, if after performing the two previously described steps (trying to find your TIB files converted by someone else, and trying to convert it to VHD format yourself), there is still a problem with the file, then there are few solutions left. You can try again to find and install an application that can open the TIB file in its original format (without converting to a VHD file. This solution will be difficult to implement, but will undoubtedly give the best result.

From the above example it is clear that HDD/dev/sdb is connected but not mounted. Let's mount it hard section drive /dev/sdb1 to drive /dev/sda. Let's choose a mount point, for example - /home/user/Video. You can take any mount point.

# sudo mount /dev/sdb1 /home/ user/Video

Everything is very simple, first you write the mount command, then you write what needs to be attached (the number shows the partition number, we only have one), and then where to attach it. This is almost always enough. The disk is mounted using the mount command in the specified folder. In some cases, when there are logical errors on the sections of the connected hard drive, you must additionally specify the file system type. In this case we have ext3.

# sudo mount -t ext3 /dev/sdb1 /home/ user/Video

This parameter can also take the following values:

• -t ntfsor -t ntfs-3g
• -t vfat
• -t iso9660

Respectively for NTFS, FAT and CD drives file systems. The latter is only needed to connect CD/DVD-ROM devices and the .iso disk image.

To manually set access parameters to a mounted partition, specify the following parameter:

• -o rw
• -o ro

# sudo mount -t ext3 -o rw /dev/sdb1 /home/user/Video

# sudo mount -t ext3 -o rw,iocharset=utf8,codepage=866 /dev/sdb1 /home/user/Video

The first one explicitly sets the system locale encoding, in our case it is utf8 (it is different for different distributions, but more often utf8), and the other adds support for the Russian language.

If, however, the hard drive refuses to be mounted in the operating room Linux system, then you can mount it manually. Parameter -o force allows you to force mount hard drive partitions in Linux. Well, for example, like this:

# sudo mount -t ext3 -o force /dev/sdb1 /home/user/Video

For example, my hard drive partition did not want to be mounted after connecting to a Windows machine that was infected with viruses. It so happened that the virus threw autorun.exe at the root of my partition and because of this Linux did not want to mount this partition. The above mount command parameter helped mount the infected partition. After which the virus was successfully removed manually.

Acronis True Image 2010 backup (TIB) files can be converted to Windows backup VHD files. There are several reasons why Acronis recommends doing this:

• You can boot your machine from the converted VHD file to test if it is not corrupt and works fine;
• You can boot from the converted VHD for testing purposes. For example, to install a new application and see if it runs fine;
• You can keep the converted VHD file for emergency situations. For example, if your machine crashes and you need to get it up and running in no time, you can just boot from the VHD file.
• In Windows 7, the VHD file can be mounted as an additional drive.

(!) If you are going to boot from the converted VHD file, it must contain either Windows 7 Ultimate or Windows 7 Enterprise Edition.

(!) If you are going to mount the VHD file in Windows 7, there can be non-system Windows partitions.

(!) Any changes you make to the booted or mounted VHD file are saved to it. If you boot from the VHD file and make changes to the data that was not backed up (e.g. delete a file from drive that was not backed up), these changes will affect your live system.

(!) File backup (as opposed to disk/partition backup) cannot be converted to VHD.

(!) You can only boot the same machine the backup of which was converted to VHD. Booting other machines from the same VHD files will fail.

(!) You cannot run the converted VHD file as a virtual machine.

Have you ever encountered the desire to use a system that you made a copy of using Acronis in a virtual machine? There are times when you completely destroy current system, does not always seem convenient. But the file with the system image stubbornly refuses to be mounted in any virtual machine.
There is a way out; to mount the Acronis image into a virtual machine you will need:

• Acronis True Image;
• StarWind V2V Image Converter;
• VMware Workstation.

You already have an image or several parts of it in the format .tib, which contains the system snapshot you need. Install Acronis True Image, the version for working on the system, not the boot version! Let me make a reservation right away: it’s paid, you can try it trial version, you can buy it or just pirate it - it’s up to you.
Open True Image and go to the section Tools and Utilities- Convert Acronis backup

I used Acronis True Image 2013 with a localizer installed on top; in other versions the location may be different, but in general this function is present.
Here you select your copy of the system, indicate the path where the converted system should go. If your cast consists of several parts, do not despair, specify the last part and the program will pick up all the parts that were there before.
You received the image in the format .vhd. But it also cannot be used in your virtual machine. Now you will need the StarWind V2V Image Converter utility, it is free and can be downloaded from.
Select the storage location for your vhd image and convert it to VMWare growable image(I recommend). The process will be long, and the speed of transcoding will depend on the file size and the power of your computer.
And finally you got the coveted image .vmdk, now it is one, regardless of how many parts there were initially. It is this image that will be subsequently mounted into the virtual machine.
Create new virtual machine in VMware Workstation, select custom installation, indicate the version of the OS, RAM and kernels you will allocate for it, do not forget to indicate in the system installation selection menu that you install the system later and what you want choose existing hard disk. (see screenshots below) When specifying an existing image, you may be asked to plunder the image into a more new format, I recommend not to do this, since the system does not always remain operational after this. I used VMware Workstation 9.0 with localization.

For companies implementing virtualization, the issue of transferring their servers to a virtual environment is relevant. The official method is to use VMware converter (link). But in my practice, migrating at least one (or more) OS through a converter always ends in failure. Moreover, a system that does not migrate is officially supported by VMware and is mentioned in the documentation.

VMware vCenter Converter Standalone functionality:

• Conversion operating system installed on a physical server in a virtual machine for ESXi
• Converting a virtual machine from ESXi to a virtual machine for ESXi latest version
• Converting a Data Protection backup file into a virtual machine for ESXi
• Converting virtual machines from Hyper-V to a virtual machine for ESXi
• Conversion backup Acronis (.tib) into a virtual machine for ESXi
• Converting from a Sumantec backup (.sv2i) to a virtual machine for ESXi
• and other formats into a virtual machine for ESXi

Conversion using the usual method

1

We install VMware converter on the network, most reliably on the machine that needs to be converted.

2

We agree with licensing policy.

3

VMware converter installation folder

4

Two types of program operation. Local installation into the operating system that needs to be converted, or a client-server option, when the VMware converter agent is remotely installed on the OS, and the server part is located, for example, on the administrator’s computer.

5

6

You must indicate the source (what needs to be converted).

7

The program determines the local machine itself and quite accurately.

8

Now we choose where to create a new virtual machine.

9

Specify the ESXi or vCenter server address.

10

The converter is connected to VMware ESXi.

11

Specify the name of the virtual machine that will be created on VMware ESXi

12

We indicate on which LUN the virtual machine files will be placed. And hardware version (version 8 for ESXi 5+)

13

On this step wizard, you can specify the conversion settings more precisely. For example, select the disks that need to be transferred, the virtual network, and more.

14

Since the conversion takes place from a running operating system and the data may change during the transfer, you can set up post-sync, which will occur after the main conversion.

15

FAILED. Therefore more reliable way- this is to first make a backup via boot disk Acronis, and then convert it into a virtual machine. The Acronis Boot CD image can be downloaded.

The transfer procedure is as follows:

• Stop the server that needs to be transferred.
• Boot this server from Acronis Boot CD
• Make a current backup copy, get a .tib file
• Launch VMware Converter and feed it the .tib file
• Otherwise, everything is the same as the transfer using the usual method.

You can do without a converter at all, and create it in manual mode new virtual machine, boot from Acronis Boot CD and restore information from the backup, but you risk seeing a BSOD, because VMware Converter can palm off necessary drivers to a virtual machine, but Acronis does not.