Article ID: 118361, created on Nov 1, 2013, last review on Aug 15, 2014

  • Applies to:
  • Business Automation


The article describes preparation steps 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.

Preparing to PBA for Linux Migration

  1. Check customer specific containers: make sure you have custom RPM package available as it will be asked by the migration script.

  2. To speed up migration process it is better to install and cache OS templates on the target PVC server before migration.

  3. Make sure that PBA encryption key(s) and passphrases are available at hands. It will be required to upload them after migration.

  4. Custom domain/payment plug-ins should be re-compiled for RHEL6/CentOS 6 before migration.

  5. Backup custom locale(s) in the /usr/local/bm/conf/locale folder.

  6. Backup all XML customization in the /usr/local/bm/conf/wnd/BM/customization/customization folder.

  7. Get the list of PBA RPM packages installed on source PBA servers (compare it with the list of packages after migration to make sure that all required packages are installed), use the command like this to get it:

    # rpm -qa | grep '^bm'
  8. Save 'iptables' rules on source PBA servers (restore custom iptables rules after migration):

    # iptables-save >
  9. Save custom cron jobs configured in the /etc/crontab, /etc/cron.*, /var/spool/cron on source PBA servers (to be able to restore them after migration).

  10. If custom HTML to PDF conversion tool is used in PBA then make sure that you will be able to install it on the PBA Application server after migration - RHEL6/CentOS 6 x64.

  11. Create fresh backup of all source PBA servers

    • PVC-based installation - use the native PVC tools 'vzbackup/vzabackup'

    • Non-PVC installation - use 3rd Party backup software

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF