Search Engine: Elastic

Article ID: 118360, created on Nov 1, 2013, last review on Jul 14, 2018

  • Applies to:
  • Business Automation


The article describes prerequisites for the PBA for Linux migration from RHEL 4/CentOS 4 to RHEL 6/CentOS 6.

Refer to the main Knowledgebase article #116940 PBA for Linux Migration to RHEL6/CentOS6: Procedure, Known Issues, and Limitations.

General requirements

  1. Make sure that enough free diskspace is available on the source PBA servers (Application, Database, Online Store), available diskspace should be equal or more than 2x size of PBA Application, Database and Online Store data.

    • PBA Application server - 2x size of the /usr/local/bm folder without logs:

      • Calculate size of the /usr/local/bm folder on the source PBA Application server and subtract size of the /usr/local/bm/log folder, e.g. use the 'du' utility to calculate current disk usage:

        # du -hs /usr/local/bm/
        13G /usr/local/bm/
        # du -hs /usr/local/bm/log/ 
        10G /usr/local/bm/log/
      • In the example above size of the PBA Application data without logs is about 3G.
    • PBA Database server - 2x size of the PostgreSQL database data in the /var/lib/pgsql/data folder:

      # du -hs /var/lib/pgsql/data/
      3.7G    /var/lib/pgsql/data/
    • Online Store server - 2x size of the /usr/local/bm/templatestore folder:

      # du -hs /usr/local/bm/templatestore/
      133M    /usr/local/bm/templatestore/
  2. The migration is performed via Backnet using SSH as transport, so make sure that all source and destination PBA servers have BackNet IP addresses configured and that port 22 is not blocked in firewall for connections between all involved servers.

    Refer to the Parallels Knowledgebase article Network configuration for PBA for Linux migration to RHEL/CentOS 6 for more details.

  3. The PBA Migration tool should be installed in the separate RHEL6/CentOS6 Update 1 or later server.

  4. Verify that PBA database verification procedure will not fail after migration. To do so, perform the following steps:

    1) Connect to pba_verify reference database:

            psql -Upba -h{PBA_DB_IP} pba_verify

    2) Delete current tag from the reference database:

            pba_verify=> delete from "BMVersion";

    3) Run database verification:

            /usr/local/bm/tools/ verify_db 

Requirements for PVC-based installation

  • Source PBA Application and Online Store must be deployed as different servers

  • Source PBA containers must operate in the host-routed mode.

  • The required OS and application templates should be installed on the target PVC server:

    • redhat-el6-x86_64 or centos-6-x86_64
    • mod_ssl (for the RHEL6 or CentOS 6 OS template)
  • The following IPtables kernel modules should be installed and loaded on the target PVC server:

    • iptable_mangle
    • iptable_filter
    • ip_conntrack
    • ipt_multiport
    • ipt_state

Requirements for non-PVC installation

  • Source PBA Application and Online Store must be deployed as different servers

  • 3 separate target servers with RHEL6/CentOS 6 Update 1 or later must be prepared

  • The following packages have to be installed on target servers:

    • mod_ssl on the PBA Application and Online Store servers
    • php and php-pdo on the Online Store server
  • PBA Application, Database and Online Store have to be installed and configured on target servers:

    • Use IP addresses different from ones of the source servers
    • Use the same database name and password as in source PBA database server

    Follow instructions in the PBA for Linux Deployment Guide to install and configure all PBA parts.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF