Tag: aix

How do I schedule a nightly tape backup on AIX?

Traditional tape backups are kicked off by the Eclipse phantom scheduler. The SYS.BACKUP.DVR phantom itself simply executes the /bin/save script, which in turn performs the backup routine and returns a status to Eclipse.

To view/change the nightly backup phantom that runs from within Eclipse:

  • <F2> for System
  • <ALT><A> for Phantom Status
  • <ALT><E> for Schedule
  • Press <Enter> to view all phantoms for all user IDs
  • Select the “System Backup” phantom and press <ALT><E> to Edit
  • When you’ve made the appropriate modifications, press <ESC> to save and exit
For Linux systems, we recommend that you schedule the tape backup and snapshot script simultaneously via crontab, as detailed in this KB article.

How do I restart JBoss on AIX?

Basic Restart Procedure

Log into the server as root and run the following command

/u2/eclipse/modules/bin/services.sh -d jboss

The application server will immediately begin the restart procedure, and it should be back up and running within 2-3 minutes on most servers.

Extended Restart Procedure

If the application server crashes, and attempts to restart it using the basic restart procedure above, or at the direction of Eclipse support, please follow this procedure as root to perform an extended, clean restart of JBoss:

  • Stop the JBoss service:
/u2/eclipse/modules/bin/services.sh -d jboss
  • Kill any errant JBoss processes:
ps -ef|grep jboss|awk '{print $2}'|xargs -i kill -9 {}
  • Kill any errant J2EE (connection pool) phantoms on the database server:
ps -ef|grep SOLAR.J2EE.CONNECTION|awk '{print $2}'|xargs -i kill -4 {}
  • (Optional) Backup logs for diagnosis (releases 8.7.2 and below):
cd /u2/eclipse/modules/jboss/server/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • (Optional) Backup logs for diagnosis (releases 8.7.3 and above):
cd /u2/eclipse/modules/jboss/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • Remove JBoss temporary directories (releases 8.7.2 and below):
rm -rf /u2/eclipse/modules/jboss/server/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/server/eclipse/log
rm -rf /u2/eclipse/modules/jboss/server/eclipse/data
rm -rf /u2/eclipse/modules/jboss/server/eclipse/work
  • Remove JBoss temporary directories (release 8.7.3 and above):
rm -rf /u2/eclipse/modules/jboss/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/eclipse/log
rm -rf /u2/eclipse/modules/jboss/eclipse/data
rm -rf /u2/eclipse/modules/jboss/eclipse/work
  • Remove the CONNECTED.APP.SERVERS control record:
cd /u2/eclipse
/u2/uv/bin/uv
ed control connected.app.servers
fd
y
q
  • Start the JBoss service:
/u2/eclipse/modules/bin/services.sh -e jboss

How do I access the serial console on my IBM pSeries blade?

First, verify that serial over LAN (SOL) is enabled:

  • Login to your BladeCenter’s AMM web interface
  • Select Blade Tasks -> Serial Over LAN -> Serial Over LAN Status -> Enable Serial Over LAN
  • Select Enable Serial Over LAN via the drop-down menu under Serial Over LAN Configuration -> Save
  • Enable SSH by selecting MM Control -> Security -> Enable SSH Server -> Save
  • Enable telnet by selecting MM Control -> Network Protocols -> Telnet Protocol -> Enable Telnet -> Save

Once SOL has been enabled, connect to the blade’s console:

  • Open an SSH or telnet session to the BladeCenter
  • Run the following command to set the environment the appropriate blade. For example, to set the environment to blade 1 and open a console session:
system> env -T system:blade[1]
system:blade[1]> console
Console login:
  • To exit the console, use CTRL-[ followed by SHIFT-(

What is the procedure to restore an Eclipse database server?

If the need arises to restore the Eclipse database, we recommend following the general procedure below:

  • Whenever possible, backup the existing system
  • Whenever possible, move the existing /u2 filesystems to a new location and create new /u2 filesystems
  • Restore the database filesystems
  • Start the UniVerse database, SYSTEM.ADMIN and JBoss application server

If the need arises to restore an Eclipse database server from bare metal, we recommend following the general procedure below:

  • Install the OS (Red Hat Enterprise Linux or AIX) using the DVD media
  • Configure the OS for use with Eclipse
  • Restore the OS configuration files (i.e. users, printers, email relay configuration, etc.)
  • Install and configure the UniVerse database and VSIFAX
  • Restore the Eclipse filesystems (/u2/eclipse, /u2/pdw, etc.)

What is the typical directory structure of an Eclipse database server?

A typical Eclipse database server running AIX or Linux contains the following important directories:

  • /u2: base directory for Eclipse installation
    • /u2/eclipse: Eclipse database
      • /u2/eclipse/modules: contains the JBoss application server and SYSTEM.ADMIN utility
      • /u2/eclipse/ereports: default location of Eclipse Reports temp space and archives
    • /u2/pdw: PDW database files
    • /u2/vsifax: VSIFAX installation
      • /u2/vsifax/lib: VSIFAX configuration files
      • /u2/vsifax/spool/logs: VSIFAX log files for troubleshooting purposes
    • /u2/uv: UniVerse database
    • /u2/unishared: UniVerse database shared files
    • /u2/uvinstall: UniVerse database installation files
    • /u2/uvtmp: UniVerse database temp space
    • /u2/UTILS: miscellaneous Eclipse utilities external to the core application
  • /usr/spool/uv: UniVerse spooler temp space, configuration and driver files