Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Updating the system

You can update system software by uploading new update packages.

ImportantHitachi Vantara does not provide updates or security fixes for the host operating systems running on system instances.
Before updating

In order for a system to be updated:

  • All instances and services must be healthy.
  • Each service must be running on its best-practice number of instances.
  • Each instance must have enough disk space for the update.
  • All required network ports must be available on each instance.
  • There can be no in-progress package uploads or installations.
During an update
  • All running jobs are paused.
  • System availability considerations:
    • Instances shut down and restart one at a time during the upgrade. Other instances remain online and able to service requests.
    • The Admin App remains available but is in a read-only state. You can monitor the progress of the update, but you cannot make any other changes to the system.
    NoteSystems with two instances are more susceptible to availability outages during an update than systems with three or more instances.
Verifying update status

As an update runs, you can view its progress on the Configuration > Update page. Also on this page, you can view all system events related to system updates.

Results of an update

After an update, the system runs a new version of the software. Additionally:

  • If any of the built-in plugins were updated, your system automatically uses the latest versions of those plugins.
  • If an existing service is replaced with a new service, the system automatically runs that new, replacement service.
  • If any new services were added, you might need to manually configure those services to run on the system instances.
Update errors

If errors occur during an update, the Update page displays information about each error and also displays a Retry button for starting the update over again. Some errors might not be resolved by restarting the update.

If you encounter errors during an update, contact your authorized service provider.

New services and components added during an update

A system update might add new services or plugins. You need to manually configure your system to start using these new components; your system does not start using them automatically.

Before updating

In order for a system to be updated:

  • All instances and services must be healthy.
  • Each service must be running on its recommended number of instances.
  • Each instance must have enough disk space for the update.
  • All required network ports must be available on each instance.

    Updating to a new version of HCI might add new services to your system and might require access to new ports. For the list of ports required by the version of Hitachi Content Intelligence to which you are updating, see the Installing HCI document included with the update package.

  • There can be no in-progress package uploads or installations.
    ImportantIf you are updating from an HCI version earlier than 1.4.0, make sure Docker is up to date or else the update will fail. The minimum required Docker API version is 1.26. Verify the Docker version by running the docker version command. Do the following if it is not up to date:
    1. Stop the run script from running. You do this using whatever method you're currently using to run the script.
    2. Update Docker to the most up to date version supported by HCI. For information on how to do this, see the Docker website.
    3. Put all instances back up. On each virtual machine that is to be a system instance, start the runapplication script using whatever methods you usually use to run scripts.

During an update

  • All running jobs are paused.
  • System availability considerations:
    • Instances shut down and restart one at a time during the upgrade. Other instances remain online and able to service requests.
    • The Search App remains accessible. Users can continue to search for data, but searches might take longer than usual to return results.
    • The Admin App remains available but is in a read-only state. You can monitor the progress of the update, but you cannot make any other changes to the system.
    NoteSystems with two instances are more susceptible to availability outages during an update than systems with three or more instances.

Verifying update status

As an update runs, you can view its progress on the Configuration > Update page. Also on this page, you can view all system events related to system updates.

Results of an update

After an update, the system runs a new version of the software. Additionally:

  • All running workflow tasks remain paused.
  • If any of the built-in plugins were updated, your system automatically uses the latest versions of those plugins.
  • If an existing service is replaced with a new service, the system automatically runs that new, replacement service.
  • If any new services were added, you might need to manually configure those services to run on the system instances.

Update errors

If errors occur during an update, the Update page displays information about each error and also displays a Retry button for starting the update over again. Some errors might not be resolved by restarting the update.

If you encounter errors during an update, contact your authorized service provider.

New services and components added during an update

A system update might add new services or plugins. You need to manually configure your system to start using these new components; your system does not start using them automatically.

Applying a system update

Admin App instructions

Procedure

  1. Click the Configuration window.

  2. Click Update.

  3. Click the Install tab.

  4. Click and drag the file into the Upload window.

    The update file is uploaded and the system verifies that the file is valid. This might take several minutes.
  5. On the Update page, click View in the Update Status window.

    The Verify & Apply Update page displays information about the contents of the update.
  6. To start the update, click Apply Update.

Results

The system verifies that it is ready to be updated. If it isn't, the update stops. In this case, you need to correct the problems before the update can continue.

Related CLI commands

getUpdateStatus

installUpdate

deleteUpdate

loadUpdate

uploadUpdate

Related REST API methods

GET /update

POST /update/install

DELETE /update/package

POST /update/package

POST /update/package/load — (Retrieves update package from a data connection)

You can get help on specific REST API methods for the Admin App at REST API - Admin.

 

  • Was this article helpful?