Author: paul.deluca

How do I shut down Eclipse on my AIX server?

  • Stop VSIFAX:
vfxsched stop
  • Stop samba:
vi /etc/inetd.conf
  • Comment out netbios lines
refresh -s inetd
  • Kill existing sessions:
ps -ef|grep mbd|awk '{print $2}'|xargs -i kill {}
  • Stop APC PowerChute:
ps -ef|grep ups|awk '{print $2}'|xargs -i kill {}
  • Stop PostgreSQL:
su - postgres -c "/u2/pgsql/bin/pg_ctl stop -l logfile -D /u2/pgsql/data"
  • Stop SYSTEM.ADMIN, phantoms, JBoss:
/u2/eclipse/modules/bin/services.sh -k -d all
  • Stop UV processes:
cd /u2/uv
bin/uv
#ESC
MASTER OFF ALL
Q
  • Stop remaining phantoms, UV processes:
ps -ef|grep phantom|awk '{print $2}'|xargs -i kill -4 {}
who -u |grep -v root|awk '{print $7}'|xargs -i kill -4 {}
  • Stop UV:
uv.rc stop
  • If UV complains that there are open processes, check:
lsof /u2
ipcs -mop|grep 0xaceb
  • Kill each remaining process, as shown in the example below, and try to stop UniVerse again:
kill -4 12345

Which directories should I backup on my Eclipse servers?

The following directories contain the most critical files necessary to recover your Eclipse systems:

  • Database server (AIX, RHEL):
    • /u2 (contains your Eclipse database, UniVerse, JBoss and VSIFAX)
    • /snap/u2 (if using snapshots, this contains the same data as above, but frozen in time)
    • /etc (contains your operating system configuration files)
    • /home (contains your users’ home directories)
    • /usr/spool/uv (contains your legacy UniVerse printer configuration files)
  • Forms server (Windows):
    • C:\Program Files\EclipseForms (contains your Eclipse Forms software)
    • C:\Users\All Users\Application Data\EclipseForms (contains your Eclipse Forms configuration files)
  • Internet Gateway (IGATE) server (Windows):
    • All shared directories containing Eclipse web sites (ex IIS shared directories, etc.)
  • Imaging server (Windows):
    • All shared directories containing Eclipse file shares (ex image attachments, signature scans, etc.)

The UniVerse database must be stopped or suspended during backup to ensure data consistency. The standard Eclipse backup scripts have been modified to use snapshots to allow backups to take place on active systems.

While backing up the directories below should be minimally sufficient to recreate your system in the event of a disaster, backing up the entire system is always recommended when possible. By backing up the entire system, you protect against the loss of miscellaneous files or those inadvertently placed outside of their standard locations.

How often should I update my AIX server?

In general:

  • The firmware should be updated twice yearly
  • The AIX level should be updated twice yearly
  • IBM ESA should be installed and configured to “phone home” hardware errors

Performing updates:

  • Complete a full system and data backup
  • Run the current levels through IBM FLRT to check against known issues
  • Install updates in the recommended order: HMC, firmware, AIX level

Strongly Suggested:

  • The system administrator should subscribe to firmware notifications from IBM’s website
  • Firmware should be updated at least:
    • At least twice yearly for regular Release Level scheduled releases
    • Whenever subscription notice advises HIPER fix
    • Whenever new hardware is added
    • Whenever an outage is scheduled, review firmware level and apply updates if convenient

Additional resources:

How do I update the firmware on my AIX server?

We recommend using the IBM Fix Level Recommendation Tool to determine which level(s) of firmware needs to be installed, and in which order the updates are applied.

Please refer to the documentation included with each firmware release for important notes and installation instructions.

If you have any questions regarding which updates are recommended, the order by which to install the updates, or how to install the updates, please call IBM directly at 800-IBM-SERV.

For your convenience, here are general installation instructions:

  • Downloaded the latest firmware for your system from IBM Fix Central (.rpm file) to the /tmp/fwupdate directory
  • Review the README for prerequisites and warnings
  • Extract the firmware package:
rpm -Uvh --ignoreos /tmp/fwupdate/*.rpm
  • Update the firmware:
/usr/lpp/diagnostics/bin/update_flash -f fwlevel
  • During the server firmware installation process, reference codes CA2799FD and CA2799FF are alternately displayed on the control panel. After the installation is complete, the system is automatically powered off and powered on.
  • Once the firmware update is complete and verified working and before proceeding with any further firmware updates, use the AIX diagnostics tools to commit the firmware. At an AIX command prompt, type the following:
/usr/lpp/diagnostics/bin/update_flash -c
  • The update_flash -c command might run for 10 or more minutes.