Page Comparison

...

If you choose NOT to migrate transaction data (only configuration data) skip to "Create Staging Directory"

Exporting The Data LVM Configuration (Volume Group) On The Source Installation

The /data mount point is mapped to the LVM volume group vg_data .

• Stop the application services using the Main Admin Menu CLI (option 2 → "stop all" )

• un-mount the /data mount point
  
  

  Code Block
  language bash theme RDark
  umount /data

  
  

• Mark the volume group as non active
  
  

  Code Block
  language bash theme RDark
  vgchange -an vg_data output : 0 logical volume(s) in volume group "vg_data" now active

  
  

• Export the volume group
  
  

  Code Block
  language bash theme RDark
  vgexport vg_data output : Volume group "vg_data" successfully exported

  
  

• Comment /data mount point in OS FS table
  
  Comment the following line in /etc/fstab

  Code Block
  language bash theme Confluence linenumbers true
  #/dev/mapper/vg_data-lv_data /data ext4 defaults 1 2

• TODO - not needed if reinstalling the same server

• 
  

Disconnect the Data Disk and Connect to New System

Stop The System

shutdown the server (virtual / physical ) using the command

shutdown -h 0

Virtual Environment

Copy the Virtual Data Disk From Current VM

• Edit the current virtual machine settings
• Locate the data disk (hard drive number 3 )
• It is recommended to copy the data disk vmdk file the new system directory (we recommend NOT to move the vmdk file but copy it, in order to keep fallback option if an issue will be raised during migration).
  
  

Edit the New System OS FS table

Change the /data mount point in OS FS table

From : /dev/mapper/vg_data-lv_data /data                   xfs     defaults        0 0
To   : /dev/mapper/vg_data_old-lv_data /data                   xfs     defaults        0 0

Rename /data LVM volume Group

Rename the data volume group vg_data in the new system to avoid volume group collision when connecting the data disk from the old system

vgrename vg_data vg_data_old

output : Volume group "vg_data" successfully renamed to "vg_data_old"

Connect the Virtual Disk to New VM

• Shut down the new system
  
  

shutdown -h 0

...

• Configure the virtual disk to the new system by adding new hard drive and choosing existing

• Start the new VM

Configure New Disk

• Make sure the new exported volume group (LVM vg) and physical volume (LVM pv) are recognized by the OS
  
  

...

• Verify the data volume group status
  
  

  Code Block
  language bash theme RDark
  vgdisplay vg_data output : --- Volume group --- VG Name vg_data System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 101.97 GiB PE Size 32.00 MiB Total PE 3263 Alloc PE / Size 3263 / 101.97 GiB Free PE / Size 0 / 0 VG UUID 4vIe7h-qqLR-6qEa-aRID-dU8w-U5E2-gV7FoJ

  
  

Add the new mount point to OS FS table

• Configure the /data mount point to OS FS table by adding the following line
  
  

...

• Comment the following line
  
  

  Code Block
  language bash theme Confluence linenumbers true
  #/dev/mapper/vg_data_old-lv_data /data xfs defaults 0 0

  
  

• Restart the system
  
  

  Code Block
  language bash theme RDark
  reboot

  
  

• Make sure the /data mount point is mounted using vg_data volume group
  
  

  Code Block
  language bash theme RDark
  df -h output : Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_root-lv_root 4.0G 1.6G 2.5G 39% / devtmpfs 7.9G 0 7.9G 0% /dev tmpfs 7.9G 56K 7.9G 1% /dev/shm tmpfs 7.9G 9.1M 7.9G 1% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/sda1 2.0G 101M 1.8G 6% /boot /dev/mapper/vg_data-lv_data 101G 81M 96G 1% /data /dev/mapper/vg_root-lv_var 4.0G 109M 3.9G 3% /var /dev/mapper/vg_logs-lv_logs 11G 44M 11G 1% /logs /dev/mapper/vg_shared-lv_shared 509M 26M 483M 6% /shared /dev/mapper/vg_root-lv_tmp 2.0G 726M 1.3G 36% /tmp /dev/mapper/vg_inst-lv_inst 7.0G 2.8G 4.3G 40% /installs /dev/mapper/vg_app-lv_app 7.0G 1.4G 5.7G 20% /app /dev/mapper/vg_apptmp-lv_apptmp 4.0G 33M 4.0G 1% /app/tmp tmpfs 1.6G 0 1.6G 0% /run/user/0

  
  

• Start the application services using the Main Admin Menu CLI (option 1 → "start all" )

Verify The Application Is Working Properly

TODOLogin to DPOD WebUI and use the "Internal Health" screens to verify all components are up and running.

Remove the Old data volume group

• Mark the volume group as non active
  
  

  Code Block
  language bash theme RDark
  vgchange -an vg_data_old output : 0 logical volume(s) in volume group "vg_data_old" now active

  
  

• Export the volume group
  
  

  Code Block
  language bash theme RDark
  vgexport vg_data_old output : Volume group "vg_data_old" successfully exported

  
  

• Shut down the new system
  
  

• 
  

  Code Block
  language bash theme RDark
  shutdown -h 0

  
  

• Remove the unused virtual disk from VM (should be the 3rd virtual hard drive )
  
  

• Start the VM

Verify The Application Is Working Properly

TODO

Anchor
Creating Staging Directory Creating Staging Directory

Create Staging Directory

...