We want to capture a backup of the current, production configuration, in a format that will serve as a backup in the conventional sense, but also can be used to construct virtual machine clones that take off from the current state of our production machine, and are safely hackable in a virtual-hosted development environment.ĪV301 is the target physical machine in this example. The CentOS 7 version of the NMR Console software configuration is currently installed in “production” mode on host named. Note that you need to specify a right UUID in /etc/fstab which you can obtain from blkid command.Backing up a CentOS Physical Machine and Cloning it as a Virtual Machine Now you have additional 226GB in a new partition ( /mariadb-data). Realtime =none extsz=4096 blocks=0, ~]# mkdir ~]# mount -t xfs -o defaults /dev/sda2 ~]# df -Hįilesystem Size Used Avail Use% Mounted on Log =internal log bsize=4096 blocks=26880, version=2 Naming =version 2 bsize=4096 ascii-ci=0 ftype=1 $ vagrant ~]$ sudo su ~]# mkfs -t xfs -f /dev/sda2 Restart VM and format and mount the new partition The next reboot or after you run partprobe(8) or kpartx(8) WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
Partition 2 of type Linux and of size 210 GiB is set dev/sda1 * 2048 83886079 41942016 83 ~]# fdisk /dev/sdaĬhanges will remain in memory only, until you decide to write them.īe careful before using the write command. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes
Restart the VM and run the following commands. You can search forĬ = '250GB' # <- Add this line to increase from 40GB to 250GB, for instance Install the vagrant-disksize plugin $ vagrant plugin install vagrant-disksizeĪdd the following line to Vagrantfile # Every Vagrant development environment requires a box. Which seems to be the case for the official CentOS box. The following steps are based on a Vagrant VM box which does NOT use LVM for a root partition, How to increase a VM's disk space Environments
0 kommentar(er)
