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

    What is ABS?

    The Epicor Automated Backup Solution (ABS) uses CrashPlan PRO to product Eclipse customers with data backup both on-site and at a secure off-site location. The ABS Failover offering utilizes this off-site backup to offer hosting for customers a disaster situation.

    The product is currently available for Eclipse Customers running Linux and Windows servers. The ABS software is installed and configured by Epicor.

    There are three levels of backup for the ABS product:

    • Tier 1 – CrashPlan PRO software alone offers the ability for local backup copies within the customer network
    • Tier 2 – ABS Off-Site Backup: adds the protection of a secure, off-site backup
    • Tier 3 – ABS Failover: adds the ability to failover to Epicor’s hosting environment

    The CrashPlan PRO software used by ABS offers:

    • Local or off-site data backup storage in a secure location
    • Byte differential backups, using compression and de-duplication for efficient transportation and archiving
    • Incremental, backup versions
    • Email backup alerts and reports
    • Data is encrypted during transport and backend storage
    • Failover for Epicor Eclipse systems (Eclipse Database, Forms, Imaging and Internet Gateway servers)

    Contact your inside sales representative for more information and pricing.

    How do I configure sendmail to relay outbound email under Linux?

    • Install prerequisite packages:
    yum -y install sendmail-cf
    • Open the configuration file /etc/mail/sendmail.mc for editing
    • Locate the section below and uncomment the SMART_HOST line:
    dnl # Uncomment and edit the following line if your outgoing mail needs to
    dnl # be sent out through an external mail server:
    dnl #
    dnl define(`SMART_HOST', `smtp.your.provider')dnl
    • Configure appropriately, like below:
    define(`SMART_HOST', `mail.corporatedomain.net')dnl
    • Apply the changes and refresh sendmail:
    make -C /etc/mail/
    service sendmail reload