Page Comparison

...

Application Files and Internal DB

Invoke the backup command

app_backup.sh
INFO : backup finished successfully. for more information see log file /installs/system-backup/full-backup-2017-09-11_17-17-59/full-backup-2017-09-11_17-17-59.log

The output backup directory will be the location of the backup log as printed in the backup status message (in the example above this is /installs/system-backup/full-backup-2017-09-11_17-17-59 ).

Copy the backup directory to a temporary location outside the current DPOD systemCreate a backup of static configuration and configuration database using the backup utility here.

Services Files

DPOD's service files are located in the /etc/init.d directory

...

• Stop the application services using the Command Line Interface (CLI) (option Option 2 → "stop allStop 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

  
  

...

• Comment out 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

  
  

• Ensure 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 Command Line Interface (CLI) (option Option 1 → "start allStart All" )

Verify The Application Is Working Properly

...

• Start the application services using the Command Line Interface (CLI) (option Option 1 → "start allStart All" )
• In the web console navigate to system → nodes and edit the IP address of the agents in your data node raw.
• Re-configure syslog for the default domain on each monitored device (the Setup Syslog for device  on the Gateways section)
• Restart the keepalive service using the Command Line Interface (CLI)

Update the Store Configuration File

...

Code Block
language bash theme RDark
/app/scripts/update_store_allocation.sh -l 4

Verify The Application Is Working Properly

...