CLOUDBERRY BACKUP BARE METAL INSTALL
CLOUDBERRY BACKUP BARE METAL SOFTWARE

It is perfectly valid to create, loop-mount and edit partitions in a sparse file that is (even substantially) larger than the host file system - as long as you do not do anything actually writing data to the skipped areas in the file. I accidentally avoided this recently:īut the problem is that the target KVM host has less space than the The problem you describe does not necessarily occur in practice. (This answer discusses the block-device-level alternative, it is most appropriate if you want to keep partitioning & boot-manager configuration intact while migrating to virtual) The final step was to check if the old physical machine's hostname or IP address is put in some configuration files: find.

CLOUDBERRY BACKUP BARE METAL SOFTWARE

/var (not everythink, depends on the software you use)./usr (not everythink, depends on the software you use)./etc (I excluded files like hostname, fstab, /default/grub, /network/interfaces and a buch of other directories related to kernel/initram/lvm).Vimdiff <(dpkg -list) physical_mchine_packages.txt Then I turned off all services, except the existential ones like SSHd.Īfter I did that I decided to use apt-clone and not to copy the packages and binaries from one machine to another: # on the physical machine:Īpt-clone clone What I did actually is, I first checked the Inode and Block sizes on both filesystems in order to make sure they're identical to each other (using tune2fs).

Of course I could also do this via rsync, but the principle is more or less the same.Īs anx asked me to do it, I'll answer my own question :) My solution was not so sophisticated ans anx's, but I'd like to share it with you anyway.

CLOUDBERRY BACKUP BARE METAL INSTALL

The second option would be to install the same packages on the KVM with exactly the same version numbers (according to dpkg -list), disable all services on the bare metal server (to keep the data consistent) and put /etc, /var/, /usr and everything else that is important from the bare metal server into a tarball and simply unpack it on the KVM.

I thought about switching off all Perl and Apache services and transferring the hard disk via dd over the network - but the problem is that the target KVM host has less space than the sda from the bare metal server is big (in the end it uses less space than is available, sda is just oversized). But now we have to move and for this reason we need some kind of smart workaround. Why do I not install the application directly in the VM? The installation of this application (Perl stuff with Apache web server, running on the same server for about 10 years) is so complex that you would rather break something. Now I want to transfer all data and applications that are on this server to a VM and run it on a KVM host. I have the following problem: We have a dedicated (bare metal) hardware server (Debian 10) on which we have no direct physical access.

Cloudberry backup bare metal