Skip to main content

We've Moved!

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

How to install/upgrade Protector on Windows and Linux

Before you begin

CautionThin Image snapshot operations default to Provisioned using floating device. In versions prior to 6.5, this setting would automatically fallback to Fully provisioned if the hardware storage device did not support floating devices. With the introduction of Cascade mode snapshots in version 6.5 (now the default mode), this automatic fallback has been removed. Consequently:
  • Data flows created in versions prior to 6.5 that contain Thin Image snapshot operations, with cascade mode is enabled, will now fail if the underlying hardware does not support floating device. These data flows must be manually reconfigured to use the correct provisioning type. Please note that if these data flows also contain replication operations, then these will be re-evaluated when the modified data flows are re-activated.
  • Data flows created in versions prior to 6.5 that contain Thin Image snapshot operations, with cascade mode enabled, will now fail if the P-VOLs have any pre-existing non-cascade mode snapshots. If cascade mode is to remain enabled then any non-cascade mode snapshots must be deleted.
  • For data flows created in version 6.5 or later, if the hardware storage device on which Thin Image snapshot operations are performed does not support Floating device and Cascade mode, then Thin Image operations will fail, unless the appropriate settings are selected in the respective data flows.

Caution
Note

When upgrading, it is highly recommended (and often necessary) to upgrade all nodes to the same version. The recommended order in which to upgraded is:

  1. Internet Connected Nodes. If ICNs are not upgraded first, they may not be able to be 'push upgraded' through the UI. ICNs may appear to go offline until the master is upgraded.
  2. Master Node(s).
  3. Clients acting as ISMs, controlling Hitachi Block and File storage devices.
  4. Clients acting as Data Destinations, such as Repositories.
  5. Clients acting as Data Sources, such as application servers.
Note
  • For a new installation, the Master node must be installed before any Client nodes.
  • When installing a new Master, you must select the account to use for initial Protector log-on. These credentials will be input to the Protector UI to enable the initial Access Control Tasks to be performed.
  • Read the release notes shipped with the installer to ensure that the currently installed version can be upgraded to the new version. It may be necessary to upgrade to an intermediate version first and perform additional actions prior to and after upgrading.
  • You may need to create an exception in your anti-virus software when installing.
  • DO NOT upgrade while replications are in the process of pairing. Any active replications must be in the paired state before upgrade is carried out.
  • It is recommend that you perform an upgrade only after currently active backups have been completed.
  • Before upgrading, unmount any mounted snapshots and replications.
  • If a node's OS is upgraded, it may be necessary to reinstall Protector, as different Protector components are installed for different OS variants.
  • If you uninstall a Client node, you will need to delete it from the Nodes Inventory before subsequently reinstalling it. This ensures that the Master node regenerates new identifiers for that node. If you do not do this then the reinstalled Client will not be recognized.
  • Operating System Specific Behaviour:
OS Note
Linux We recommend that Linux source nodes have a Logical Volume Manager (LVM) on each volume group.
Linux

Ensure you have execute permissions using the command chmod 755, before running the installer.

A minimum of 10 GB of free space is required in the 'unused' portion of the volume that is to be backed up. This is in addition to the space required for the allocated storage area. For example, if 100 GB of usable storage is required, then the total disk size will be 110 GB (100 GB of usable storage and 10 GB of unused storage for snapshot administration).

All nodes that will participate in a backup data flow need to have Ops Center Protector installed. A node used only to access the web based user interface does not need to have any components installed on it.

Procedure

  1. Locate and run the installer appropriate for the target OS and hardware architecture.

    TipProtector can be installed directly from the command line if required. Refer to Installing and upgrading Protector from the command line for details of the installer's command line options.
    The installer filename has the following format:

    Protector-Rm.n-m.n.n.nnnnn-ostype-proctype

    where:

    • m.n-m.n.n.nnnnn - is the version and build number
    • ostype - is the target operating system type:
      • Win
      • Linux
    • proctype - is the target processor type:
      • x64
    The Setup wizard will be launched if a GUI shell is available. If not then the same information will be presented using the text mode shell.
  2. If a previous installation of Ops Center Protector is found, the installer will prompt you to upgrade or abort the installation.

    • Click Yes to upgrade the existing Protector installation on this node.
      TipWhen upgrading along a supported version upgrade path, any existing data flows, policies, schedules etc. will be preserved. If any further actions are required post upgrade, then these will be described in the Release Notes shipped with the new version.
    • Click No to exit the installer wizard, in which case no changes will be made to the current installation.
  3. When the Setup wizard appears, a welcome message is displayed. Click Next to begin the installation.

  4. When prompted, read the License Agreement.

    • Select I accept the agreement if happy to proceed and click Next.
    • Select I do not accept the agreement if not happy to proceed and click Next. The installation will be aborted and no changes will be made to the machine.
    License keys are entered once the installation is complete via the Licenses Inventory in the UI (See How to Add a License).
  5. To install in a non-default location, enter the path in the Installation Directory field or use the folder browser. Click Next.

  6. Select the type of installation then click Next.

    • Master Select this option to install the Master node in your network. If this is a new installation then the Master node must be installed before any Client nodes. The Master node is the central controller for all other nodes and serves as the connection point for the Web UI and REST API.
      NoteThe Master node automatically has all the capabilities of a Client node. It is however recommended that the Master node functions only as a Master. Multiple Master nodes can coexist on the same network, however Client nodes can only be authorized and controlled by one Master node.
    • Client - Select this option to install all other node types. The specific roles assumed by Client nodes are defined via the Nodes Inventory Nodes Inventory once installation is completed (See How to add a node). These roles include:
      • Data Sources (basic hosts, VMs, application servers, etc.)
      • ISMs (for controlling Hitachi Block and File storage hardware, etc.)
        CautionISM nodes and their associated CMDs used to control storage devices must not be shared with applications other than those forming part of the Ops Center suite.
      • Repositories (acting as host based backup storage destinations)
  7. Specify a node name to be used within Ops Center Protector then click Next.

    NoteNode names are limited to a maximum of 64 characters. By default, the name is set to the machine’s host name. This name is only used by Protector, and will not change the name set by the operating system.
  8. If the Master is being installed:

    1. Select a local User Account for logging on to the Protector web user interface immediately after installation is complete. You must know the password associated with the selected account. The account used can be changed after installation of the Master. Click Next.

    2. Accept or edit the Protector User Interface Port used to connect to the web based UI. By default it is set to 443, but can be changed if you already have another web server running on that port.

  9. If a Client is being installed:

    1. Enter the Master Hostname or IP address or a DNS resolvable name of the Master node. If it is known that this node will be operating over a non-secure network, then we recommend enabling the Internet connected node option. This will encrypt transmitted data as an extra security precaution. Over-the-wire encryption requires a license and may not be available in some territories.

  10. When the wizard indicates that it is ready to begin the installation, click Next.

    Ops Center Protector files are copied to the designated directories and the necessary components installed.
  11. When the wizard indicates that the installation is complete, you will have the option to Start Hitachi Ops Center Protector User Interface Now in a web browser. Click Finish.

    NoteYou do not need to restart the machine. The installer starts all the necessary Ops Center Protector components on the system.

    If a third party firewall is installed on the network, Protector will generate firewall warnings when it starts running. See How to configure a third party firewall for Protector.

  12. If this is a new installation of a Master node, then use a web browser to log on to the user interface at: https://<Master>/#/Login, where <Master> is the IP address or DNS name of the Master node. Refer to How to configure a server side SSL certificate using a UI to prevent security warnings being displayed by the web browser.

    NoteInitial logon must be done with the username specified for the User Account during the Master installation. The username must be qualified with the local domain name master as follows:

    <username>@master

    or

    master/<username>

    or

    master\<username>

  13. Set the locale and time zone appropriate the location of the nodes you are working with.

    See How to change the UI settings
  14. If you are upgrading, the rules should now be reactivated and all destination nodes should be manually resynchronized with their sources. The upgrade process is then complete.

  15. Finally, refer to one of the following topics to setup accounts for those users that required access to the Protector user interface.

 

  • Was this article helpful?