Difference between revisions of "Reload Install"

Latest revision as of 16:23, 6 March 2017

Installation performs the following tasks:

• Installs the Reload System software to the path: /opt/beginfinite/reload.
• Creates initialization scripts to start the Reload Daemon on server bootup.
• Creates various Reload initialization scripts such as "reload, reloadd, reloadm, and reloadj" in the /usr/sbin directory, so that they are available to the Linux administrator "root".
• Sets up a default Reload System configuration.
• Starts the Reload Daemon.
• If needed, the installation also installs the GroupWise DBCOPY and GroupWise Agent packages, unless these packages have been installed before, or if the installation determines that other GroupWise agent software is already installed.
• If the Reload server has a connection to the Internet and can browse the web, then the Reload server will attempt to install a piece of software called Xdialog. The Xdialog is used to view Reload log files in a graphical user interface. It cannot be bundled with Reload, because of licensing issues, so Reload downloads it to the Reload server if the server has a connection to the Internet. Xdialog is not required.
• Installs a Reload Administration icon to the root user's Xwindows desktop. If you are in an XWindows type session, you should see an icon on the root user's desktop. This icon is compatible with a basic GNOME or KDE installation. The icon is for convenience, and may not work in all Linux desktop environments.

[edit] Prerequisites

Reload requires:

• SUSE Linux Enterprise Server (SLES) version 11 SP3 or SP4, or version 12
• Sufficient disk space
  • For each GW Post Office, allocate at least 150% of production Post Office disk usage for 14 days of backups
  • For Retain, allocate at least 114% of the production Retain disk usage for 14 days of backups

If Reload runs out of disk space backup jobs will stop.

[edit] Installation

Download [Reload]

Install Reload by running the following command in the same directory the download is in:

rpm -ivh reload5.rpm

[edit] Post-Install Tasks

• License Reload by browsing to the [Licensing Website] and entering your validation keys
• Browse to the Reload Web Administration console

http://<Reload_Server_Address>:5555

• On the Toolbar, select Tools | License
• Submit the license

[edit] Uninstall Reload

To uninstall the Reload Software Package, run:

/opt/beginfinite/reload/uninstall

This only removes the Reload Software Package. The configuration data, profiles and profile backups are left in their storage directories. The data can be removed manually.

[edit] Reinstall Reload

To reinstall Reload Software Package, run:

reloadu

[edit] Reload in a Cluster

Reload can be implemented where GroupWise is in a cluster.

Reload Cluster

[edit] Upgrading Reload

• To upgrade Reload from the Web Console, choose upgrade from the Tools dropdown menu, press Go, and select Upgrade Now.

• To upgrade Reload from the Retain Administration, run:

reload

then choose System | Tools | Upgrade | Upgrade Progress will be shown onscreen.

• To upgrade Reload from the command line, run:

reloadu 
reloadu -r will force a download of the available version even if you previously downloaded it.
reloadu -h shows a help page

If the Reload server does not have access to the internet then the update can be downloaded from http://download.gwava.com/download.php?product=Reload&version=current

Copy the file to the Reload Server and place in

/opt/beginfinite/reload/upgrade

At a command prompt, type:

reloadu

[edit] Automatic Upgrades

• To have Reload automatically upgrade itself, create a cron job:

crontab -e

and enter

00 1 * * 3 root /usr/sbin/reloadu

[edit] Upgrading the Collector

• If you are using the Collector/Server Model, the collector will upgrade itself from the server when the next job begins:

When the Reload server is upgraded it dumps the upgrade rpm in:

/reload/[POprofile]/gre_data/sync/gre_data/proc/upgrade

When a backup job runs the collector uses rsync to check for an rpm upgrade file. If it does it transfers the rpm to:

/opt/beginfinite/reload/upgrade

If successful the collector upgrades itself, then corrupts of the rpm on the Reload server so it can’t upgrade again. The Reload server will check the rpm for corruption and if it is, deletes the corrupt rpm since the upgrade has been completed.

[edit] Reload Logs

Reload logs what it does to make troubleshooting easier.

The log files can be found in:

/opt/beginfinite/reload/logs
/opt/beginfinite/reload/save

For support purposes, Reload will create a single zip file of all the logs which can be downloaded from the Reload Web Administration page:

• Browse to Reload Web Administration
• Select "Tools | Download Logs | GO | "Download The RELOAD SUPPORT.ZIP File"

Alternatively, the support log file may found on the Reload server in:

/opt/beginfinite/reload/support/reload_support.zip

There are a number of logs: [1]

• EVENT.LOG = General logging.
• AGENT.LOG = Detailed log file of all Reload activity.
• ERROR.LOG = Error state reported to the system. The error that occurred and its time stamp
• MONITOR.LOG = Reload version and build, license information, profile names, Groupwise agent version, and other general reload configuration information.
• DAEMON.LOG = Checks for jobs, generating the diagnostic log, and the support (reload_suport.zip) log file.
• DIAGNOSTICS.LOG = Server statistics like kernel version, disk space, processor, memory, NIC, resolv.cfg, hosts, and fstab.
• <profile>.EVENT.LOG = Contains almost all of the data that is in the event.log that is specific to the profile.
• <profile>.AGENT.LOG = Contains almost all of the data that is in the agent.log that is specific to the profile.
• *.TEST.LOG = test connectivity, rights, enables profile, and lists what OS the GroupWise is installed on.
• UPGRADE.LOG = Upgrade process activity.