Versions Compared

Version Old Version 6 New Version 7
Changes made by

Amit Munwes

Amit Munwes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Execute the following commands:
    Note: Starting from DPOD 1.0.22.0, it is possible to use a user with sudo permissions instead of running the upgrade by the root user itself.

    Code Block
    mkdir -p /installs/backups
cd <CEF_DIRECTORY>
chmod 755 <CEF_FILE>
sudo ./<CEF_FILE>

  • By default, the installation will extract temporary files to /app/tmp directory. To change the destination directory, use the option --staging-path <directory>.

  • Do not interrupt the software update process after it has started.
    If SSH connection is lost during upgrade, the upgrade will still continue. Reconnect to the server and check the log files for the process status and outcome.

  • Note: Once the upgrade to 1.0.22.0 is completed, DPOD no longer requires the root user for performing administrative tasks via the server CLI (e.g.: using SSH).
    Most of the administration of DPOD should be performed with the non-administrative user that is also running the DPOD services (usually dpodsvc or storeadm), such as starting/stopping services, configuring LDAP, export/import, etc. These tasks can also be accomplished from the Admin Console.
    However, since DPOD also configures the operating system (the httpd service, OS limits, firewall rules, services in /etc/init.d, etc.), some actions require sudo, such as the installation, upgrading DPOD, backup, restore and generating a mustgather file.

  • Note: Once the upgrade to 1.0.22.0 is completed, CLI commands need to be executed with their full path.
    e.g.: Use /app/scripts/app-utils.sh instead of app-util.sh.

...