MicroFocus Data Proetctor (HPDP) DP 10 Upgrade - Upgrade prerequisites

MicroFocus Data Proetctor (HPDP) DP 10 Upgrade - Upgrade prerequisites 

Before upgrading an existing product version, consider the following:

• Ensure that the following ports are open for Inet:

  • Fresh Data Protector installation - 5565

  • Upgraded Data Protector installation - 5555

• Disable encrypted control communication (ECC) on all clients and the Cell Manager if you are upgrading from Data Protector 9.x and earlier.

• For information about supported and discontinued platforms and versions, see the latest Support Matrix.

  On platforms on which the Cell Manager is no longer supported, first migrate the Cell Manager to a supported platform and then upgrade to Data Protector 2018.11.

  As an unsupported functional area, the Data Protector Java graphical user interface is not supplied in Data Protector 2018.11. If there are UNIX systems in your Data Protector cell that have the Data Protector Java graphical user interface installed, during the cell upgrade process, you need to choose other systems that will take the role of Data Protector graphical user interface clients. These clients should run on operating systems supported by the original (native) Data Protector graphical user interface.

• License passwords issued for releases prior to Data Protector 10.00 will no longer work with this version.

  You must have a valid active support agreement in place in order to be eligible for new license passwords according to the type and quantity of licenses listed in your support agreement.

  Before you start the upgrade, check the quantity and type of license keys installed in your Data Protector environment and compare it to the quantity and type of licenses listed in your support agreement.

  If you have fewer or different licenses listed in your support agreement than actually installed in your environment, you should not start the upgrade. Otherwise you risk that your Data Protector environment is no longer operational due to missing license keys. Instead, contact your sales representative or partner first to determine what steps are needed to close the gap in the licensed functionality covered by the support contract and the actual licenses currently in use with Data Protector versions older than Data Protector 10.00.

• After the upgrade, the Cell Manager, and Installation Server must have the same Data Protector version installed. Although older Data Protector Disk Agent and Media Agent versions are supported in the same cell, it is highly recommended that the clients also have the same version of Data Protector components installed.

• After the upgrade of a multiple-cell (MoM) environment, all Cell Managers must have the same Data Protector version installed.

• With Data Protector 10.00, JBoss 7.1 is replaced with WildFly 10. During the Data Protector upgrade, the following JBoss configurations are automatically migrated to WildFly:

  • Logger levels and formats
  • LDAP configuration
  • PostgreSQL credentials

  Important Any changes made in JBoss 7.1 standalone.xml file, apart from the configurations listed above, must be manually added in the WildFly configuration file after upgrade.

  Note that during upgrade, Data Protector creates a backup for the old JBoss configuration files in the Data_Protector_program_data folder. By default, the files are available at the following location:

  • Linux: /etc/opt/omni/server/AppServer_<versionNo>
  • Windows: C:\ProgramData\OmniBack\Config\Server\AppServer_<versionNo>

• Run database consistency checks on the existing IDB to validate data consistency prior to the upgrade.

• Perform a backup of the existing Cell Manager system and the Internal Database (IDB).

• Before upgrading, ensure that all GRE Power On open requests are closed. Additionally, make sure that the Live Migrate sessions that are in progress, are completed or aborted.

Limitations

The following limitations apply:

• Changing the Cell Manager platform during the upgrade is not supported. Upgrades are only supported on the same Cell Manager platform (HP-UX to HP-UX, Linux to Linux, and Windows to Windows).

  If your platform is discontinued, migrate the Cell Manager to a supported platform first and then upgrade to the new version.

• In a UNIX environment: The only Data Protector processes that can be running before performing an upgrade are from Data Protector services. To do this, stop the Data Protector services, terminate any running process and restart the services.

• The Internal Database restore is supported only from the same minor-minor Data Protector version, in which the Internal Database was backed up. This is because of the Internal Database schema changes that are present in new releases.
• If you want to restore the Internal Database that was backed up in an earlier Data Protector version, reinstall the particular version, import the Internal Database backup medium, and then perform the restore.
• If the stores created using an older Data Protector version are not visible after upgrading, then you should restart the client (where stores reside).

Share this

ChinniLax