Tips

Before setting up ActiveImage Protector, please make sure the required packages and drivers are installed.

Installation of the required packages and drivers for setting up ActiveImage Protector

Installing the required packages and drivers using the script included in the product media

Before setting up ActiveImage Protector, you need to install the required packages.
The use of this script facilitates installation of the required packages and drivers.

If the system has internet connection, the required packages are installed.

  • Package installation over internet is not supported on Red Hat Enterprise Linux and clone OS of the equivalent OS 7.0 - 7.5.

When the system does not have internet connection, you need to have Setup DVD for the respective distribution OS.
The yum repositories are added from set-up DVD of the respective distribution OS.
The package is installed from the repository of setup DVD of the respective distribution OS.
*When the kernel version is updated from the release version, you cannot install the packages from the OS setup DVD and internet access is required.

Note
When the product is installed on CentOS 7.x, since the required packages are included in Everything ISO, please prepare for Everything ISO.

  1. Please log in as “root” user.

  2. Run the script “AIP-packages-tool.sh” on terminal.

    # ./AIP-packages-tool.sh

Installation Menu includes the following items:
**The item [8] is displayed on Red Hat Enterprise Linux 8 or later and clone OS of the equivalent OS only.

  • [1] Agent Installation of required modules for using agents
  • [2] GUI Installation of required modules for using GUI
  • [3] [1]-[2]All Installation of agents and GUI module
  • [4] Kernel-devel Installation of Kernel-devel
  • [5] Install datto driver Installation of datto drivers
  • [6] Install AIPLinux Installation of AIPLinux
  • [7] Uninstall datto driver Uninstallation of datto drivers
  • [8] AAS Installation/uninstallation of Actiphy Authentication Service
  • [9] help Help
  • [10] exit Exit

Settings to configure before backing up MySQL / MariaDB

Please configure the following before backing up MySQL / MariaDB.

  1. Please install one of the following packages: mysql-devel mariadb-devel mariadb-connector-c-devel

  2. Upon completion of the package installation, please run the following command and see if the following command is executable.

    # mysql_config

  3. Launch ActiveImage console, go to [Preference] - [MySQL Setting] and enter the credentials for administrator account.

    link

  4. When the credential information is authenticated, please run the backup task. When starting the backup process (when taking a snapshot), MySQL database will be temporarily locked to create the backup image file.

Restore LVM system with VG configuration change

Usually in order to perform a bare metal recovery of a LVM system, the same number of HDD with the same capacity or larger than the backup source is required. When restoring to a location where there is no guarantee of the same number of HDD, take the following procedures to change the VG configuration and restore the LVM system.

  1. Boot up Boot Environment.

  2. Launch the restore wizard and select the image file created for backup type [LVM]. Click on [Next] button, and the message "Do you want to restore the LVM configuration information?" will be displayed. Select [Yes] on the dialog. Boot up boot environment by using BE media.

  3. Restore only disks that have boot volumes (usually "/dev/sda") to a newly configured HDD.

    When the process is started, two restore tasks will be performed. The restoration of the VG is attempted with the second task but will ends with an error because the VG is not correctly configured at this point.

  4. Select [Utilities] to open the terminal and run the following.

     # vgdisplay
 -> Displays the backup information of VG provided by metadata restored in "/dev/sda".
 # vgremove -f <Restored VG name>
 -> Forcefully delete the restored VG.
 # fdisk /dev/sda
 -> Create a partition for PV of Linux LVM (8e) type in "/dev/sda2".
 * Please make sure you have available space size larger than the VG to restore.
 # pvcreate /dev/sda2
 -> Specify "/dev/sda2"as PV.
 # vgcreate <Source VG name> /dev/sda2 (Specify PV to be included in VG.)
 -> Create VG for restore destination.

  5. From the [View] menu, click on [Refresh] to refresh the disk information. The newly created VG will be displayed in the disk information.

  6. Click on [Restore Image] to start the restore wizard and select the same image again. Click on [Next] and the message "Do you want to restore the LVM configuration information?" is displayed. Select [No] on the dialog.

  7. Restore the backup image of VG to the newly created VG. Upon completion of restore processing, select [Operations] - [Reboot System] to exit Boot Environment. Boot from the LVM system which VG configuration is changed for.

Backup KVM host - VM (RHEL series)

  1. Install AIP Linux on KVM host.

  2. Configure the preliminary settings on VM.

    # yum install qemu-guest-agent

  3. Copy each script on the Linux VM which the database is implemented.

    Overwrite copy fsfreeze-hook to the following.
    /etc/qemu-ga/

    Copy the required files for MySQL, Oracle and PostgreSQL to the following.
    /etc/qemu-ga/fsfreeze-hook.d/

    ERespectively grant root privileges and execution permissions.

  4. The following settings are required to configured for MySQL and MariaDB only.

    # echo pwd=xxxxx > /etc/qemu-ga/qemu-ga.conf

    *Enter the password in xxxx for root user.

  5. Please set the qemu-agent policy to permissive on the VM.

    # semanage permissive -a virt_qemu_ga_t

  6. In order to log the process that the fsfreeze script is rejected on VM, clear the audit logs.

    # truncate -s 0 /var/log/audit/audit.log

  7. Run vm_freeze on KVM host.

    # /opt/Actiphy/scripts/vm_freeze.sh

    *If the process stops in the midst, press Ctrl+C to terminate it.

  8. Run vm_thaw.sh on KVM host.

    # /opt/Actiphy/scripts/vm_thaw.sh

    *If the process stops in the midst, press Ctrl+C to terminate it.

  9. Confirm the required permissions on the VM.

    # ausearch -m AVC | audit2allow -a

  10. If the required permissions are insufficient on the VM, create the necessary permissions as non-mandatory rules.

    # ausearch -m AVC | audit2allow -a -M ga_rule

  11. Enable the policies created on VM.

    # semodule -i ga_rule.pp

  12. Reboot qemu agent on VM.

    # systemctl restart qemu-guest-agent.service

  13. Run vm_freeze.sh on KVM host.

  14. Run vm_thaw.sh on KVM host.

  15. Check the following log records on VM and ensure that they are normally running.
    /var/log/qemu-ga/qga-fsfreeze-hook.log

  16. Run a backup task on KVM host using AIP.
    Configure the following option settings in Advanced Settings in AIP on KVM host.
    Script to execute before the snapshot is taken vm_freeze.sh Time out 3 minutes
    Script to execute after the snapshot is taken vm_thaw.sh Time out 3 minutes

Backup KVM host - VM (ubuntu series)

  1. Install AIP Linux on KVM host.

  2. Configure the preliminary settings on VM.

    # /opt/Actiphy/scripts/Pre_conf_ubuntu.sh

  3. Copy the respective scripsts on Linux VM on which DB is implemented.

    Overwrite-copy fsfreeze-hook to the following.
    /etc/qemu/

    Copy the required files for MySQL, Oracle and PostgreSQL to the following.
    /etc/qemu/fsfreeze-hook.d/

    Respectively grant root privileges and execution access permissions.

    The following settins are required to configure for MySQL, MariaDB only.

    # echo pwd=xxxxx » /etc/qemu/qemu.conf

  4. Enter the password for root user in xxxx.

  5. Run vm_freeze.sh on KVM host.

  6. Run vm_thaw.sh on KVM host.

  7. Please check the following log records on VM.

    /var/log/qemu/qga-fsfreeze-hook.log

  8. Run a backup task on KVM host using AIP.
    Configure the following option settings in Advanced Settings in AIP on KVM host.
    Script to execute before the snapshot is taken vm_freeze.sh Time out 3 minutes
    Script to execute after the snapshot is taken vm_thaw.sh Time out 3 minutes

HyperBack VM (Linux) on KVM, Proxmox - RHEL series

  1. Configure the preliminary settings on VM.

    # yum install qemu-guest-agent

  2. Copy each script on the Linux VM which the database is implemented.

    Overwrite copy fsfreeze-hook to the following.
    /etc/qemu-ga/

    Copy the required files for MySQL, Oracle and PostgreSQL to the following.
    /etc/qemu-ga/fsfreeze-hook.d/

    Respectively grant root privileges and execution permissions.

  3. Set the qemu-agent policy to permissive on the VM.

    # semanage permissive -a virt_qemu_ga_t

  4. In order to log the process that the fsfreeze script is rejected on VM, clear the audit logs.

    # truncate -s 0 /var/log/audit/audit.log

  5. Configure HyperBack schedule settings on HyperAgent machine for the VM.

  6. Confirm the required permissions on the VM.

    # ausearch -m AVC | audit2allow -a

  7. If the required permissions are insufficient on the VM, create the necessary permissions as non-mandatory rules.

    # ausearch -m AVC | audit2allow -a -M ga_rule

  8. Enable the policies created on VM.

    # semodule -i ga_rule.pp

  9. Reboot qemu agent on VM.

    # systemctl restart qemu-guest-agent.service

  10. Run HyperBack task again.

  11. Check the following log records on VM and ensure that they are normally running.
    /var/log/qemu-ga/qga-fsfreeze-hook.log

HyperBack VM (Linux) on KVM, Proxmox - ubuntu series

  1. Configure the preliminary settings on VM.

    # yum install qemu-guest-agent
    # mkdir /etc/qemu
    # qemu-ga -D > /etc/qemu/qemu-ga.conf

    Open qemu-ga.conf by using Editor and delete the following two lines.
    block-rpcs=
    allow-rpcs=

    Append the following to the last line.
    fsfreeze-hook=/etc/qemu/fsfreeze-hook

    Open the following file by using Editor and edit ExecStart.
    /usr/lib/systemd/system/qemu-guest-agent.service

    ExecStart=-/usr/sbin/qemu-ga
    → ExecStart=-/usr/sbin/qemu-ga -F /etc/qemu/fsfreeze-hook

    # systemctl daemon reload
    # systemctl restart qemu-guest-agent.service

  2. Copy each script to the Linux VM where the database is implemented.

    Overwrite copy fsfreeze-hook to the following.
    /etc/qemu/

    Copy the required files for MySQL, Oracle and PostgreSQL to the following.
    /etc/qemu/fsfreeze-hook.d/

    Respectively grant root privileges and execution access permissions.

  3. Configure HyperBack schedule settings on HyperAgent machine for the VM.

  4. Run HyperBack task again.

  5. Check the following log records on VM and ensure that they are normally running.
    /var/log/qemu-ga/qga-fsfreeze-hook.log