SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: c04350769
Version: 1
CUSTOMER ADVISORY: Data Protector 8.10 Installation and
Upgrade Whitepaper
NOTICE: The information in this document, including
products and software versions, is current as of the
Release Date. This document is subject to change without
notice.
Release Date: 2014-07-17
Last Updated: 2015-09-04

DESCRIPTION
This document describes tools and procedures for users who are planning to
upgrade from the 6.x/7.x Data Protector release to 8.1x. This document does
not apply to users who are planning to upgrade to 9.x.
During the upgrade process, you may encounter few issues. Use this
document to determine whether the Internal Database contains data that may
cause the upgrade failure.
SCOPE
This document includes detailed steps on the following:
1.

Pre-upgrade checks

2.

Install/Upgrade step

3.

Post-upgrade checks

4.

Rollback to previous version
Pre-upgrade steps
Before upgrading to Data Protector 8.1, ensure that you run the pre-upgrade
sanity checks. If any inconsistencies are detected, you must first fix those
problems and then perform the upgrade.
Checks that need to be performed are as follows:

which provides detailed instructions on handling this issue. you must read the Customer Advisory . which includes the step on renaming the directory (to registry. For .QCIM2A50886 . NOTE: Installation instructions for the test environment are notapplicable if you have CMMDB MoM environments. it is highly recommended that you prepare a test environment and test the upgrade in that setup.  Check for any manually created directories in the Data Protector path:  Windows: …\ProgramData\OmniBack\Config\Server\datalists  HP-UX/Linux: /etc/opt/omni/server/datalists If found. see the Rollback chapter. If you already attempted the upgrade and if it failed.  omnidbcheck ­dc This command checks the DataCatalog consistency. NOTE: If you use the Windows platform and the DataProtector (C:###BOT_TEXT###quot;Program Files"\Omniback) directory path includes spaces (which happens if you migrate your Cell Manager environment from Windows 2003 to Windows 2008).old):  Windows: C:\ProgramData\OmniBackConfig\client\components\registr y  HP-UX/Linux: /etc/opt/omni/client/components/registry To ensure a smooth upgrade.OK” for all fields. place them somewhere else during the installation process After both these checks return “Status . omnidbcheck This command ensures that the data consistency is fine. you must perform a full Internal Database backup.

Install/Upgrade Steps After successfully resolving customer issues. If it fails. . If installation completes successfully. Copy the cdb and mmdb folders from the production server to the test server. 3. which are described in the next section. Run omnidbutil ­readdb ­cdb <cdbFolderPath> ­mmdb  <mmdbFolderPath> on your test environment. you do not need to follow the manual installation instructions. Run the default Data Protector 8. HP released few Site Specific Patches (SSPs) and advisory documents on the upgrade process of Data Protector 8. Run omnidbutil ­change_cell_name  <production_server_name>. Installation instructions for the test environment: 1. you should always perform the manual installation. 6. Install the same version of Data Protector as that on your production server. see the Rollback and installation/upgrade steps in this document.1.  Default upgrade. It is described later in this document. If you do not have the test environment. Create VM with the same OS as your production environment.1 installation. Run omnidbutil ­writedb ­cdb <cdbFolderPath> ­mmdb  <mmdbFolderpath> on the production server. you can use one of the following options:  Manual upgrade. 8. 5. 4. 2. Create two temp folders: cdb and mmdb.such environments. 7.

In addition.  Customer Advisory .x install\upgrade process not detecting a space character in the DataProtector data path. SSPUX810_003. Download the appropriate SSP: SSPNT810_003 (Windows). or SSPUX810_003 (HP-UX). These SSPs contain fixes for the omnimigrate. these SSPs contain fixes for the F_dpidb_801_fix_corruption.  Customer Advisory .exe" C:\temp\omnimigrate.QCIM2A50886. If the file is missing. thereby causing the processes to fail. Alternatively.pl  ­export ­shared_dir C:\temp or /opt/omni/bin/perl /temp/omnimigrate. and SSPLNX810_003 were released to fix problems with the upgrade process. Unzip the contents to an appropriate location: C:\temp (Windows) or /temp (Linux/UX). 3. you can use the following steps: 1.pl ­export  ­shared_dir /temp . 4.pl script. SSPLNX810_003 (Linux). which handles the post-upgrade corruptions and adjusts the data fields in the new database. which handles the process of migration and preparation of data from the old database (Velocis) to new (Postgre). Customer Advisory documents were released prior to common problems detected during the install process of Data Protector.docx : Released due to Data Protector 8.QCIM2A51402. Run the following command: %DP_HOME_DIR%/bin/perl. All of these problems can be fixed using the pre-upgrade steps. 2.dll file. For Windows: ensure that you have the msvcp71.1 upgrade process erasing the database in the MoM environment with CMMDB implemented.docx : Released due to Data Protector 8.sql script. download it from the official Microsoft download site.SSPNT810_003. which is located at C:\Windows\SysWoW64.

Run omnidbutil ­writedb ­cdb <pathTo_cdb> ­mmdb  <pathTo_mmdb> NOTE: writedb can be canceled (using CTRL + C) as soon as the dump for the file names of hosts starts with the following message: <DATE> <TIME>Exporting file names for  some. c. create two additional directories: cdb and mmdb. Failure at this step may occur because services are being stopped after printing out the file names of the hosts. It should contain only two lines: (exact folder) OLDCM_SHORTNAME=OldCmName OLDCM_ENDIANNESS=Endianness where.pl ­exportNonASCII  ­shared_dir /temp d. Create the old_cm file. kill the process. delete their content. In the temp directory (C:\temp or /temp).An inter-process communication error may appear at this step.yu. b. Run the export command with the following changes: %DP_HOME_DIR%/bin/perl. . and the server fails to restart them in time. To continue with the install process.pl  ­exportNonASCII ­shared_dir C:\temp or /opt/omni/bin/perl /temp/omnimigrate.. you should replace the Step 4 with the following steps: a.  OldCmName is replaced with the short CM name. This is expected as we kill the process before exporting file names.. If the script hangs after this error.exe" C:\temp\omnimigrate. If these two directories already exist.host­name.

If it is not the case. Run omnistat. Rename the db40 folder to db40. Do not delete any database or configuration folders. 8. =. 5.old.old to db40. 10. 6.old (HP-UX or Linux). installation server) copy and overwrite the %DP_DATA_DIR %\Config\Server\cell\cell_info and installation_server files. Start fresh installation of Data Protector 8. Copy the old configuration files. a. Copy content of db40. Endianness is LITTLE_ENDIAN (Windows or Linux) or BIG_ENDIAN (HP-UX) You should verify this. Note that there is no space between the variable. Make sure no sessions are currently running.1 NOTE: For Windows.old (Windows) or /etc/opt/omni/client/components/registry to registry. Rename db40. Rename %DP_DATA_DIR %\Config\client\components\registry to registry. 7. If you want to keep old cell configuration (clients.old from the previous path to the new path (except DCBF folders). but keep the old files. These steps are applicable only if you do not want to use the old location. the following additional steps are required. Do not copy the files from %DP_DATA_DIR %\Config\Server\install. . 11. and the value. Stop Data Protector services. 9. Uninstall the current version of Data Protector usingomnisetup. it is advisable to use the same location as used earlier. as it can vary. b.sh ­Uninstall (for non-Windows setup).

and rename db40.12.exe"  C:\temp\omnimigrate. Run the following command: "%programfiles%/omniback/bin/perl.pl ­import ­shared_dir C:\temp or .pl ­import  ­shared_dir /temp 13. 3. Therefore.sql ­detail or omnidbutil ­run_script   /temp/F_dpidb_801_fix_corruption. Stop services. renaming is required. which was provided in SSP.old to db40. Run the corruption fix script.pl ­import ­shared_dir C:\temp or /opt/omni/bin/perl /temp/omnimigrate. you can reset the import operation using the following steps: 1. omnidbutil ­run_script   C:\temp\F_dpidb_801_fix_corruption. Restart services and re-run the following command: "%programfiles%/omniback/bin/perl. This will erase all the information collected in the database as well as all catalogs located in the db40 folder. Restart services and run the omnidbinit command.sql ­detail If for any reason your import fails [accidental canceling of the import process (step 12) or any other unknown reason]. 4.exe"  C:\temp\omnimigrate. 2.old. and rename your db40 folder to db40. Perform import of the old data. Stop services.

IDB backups with the old backup spec fail with the following message: “Cannot connect to inet for starting of OB2BAR application postgres_bar.  IDB backup fails with the following error message: “Putting the Internal Databse into the backup mode failed”.pl ­import  ­shared_dir /temp If the problem still persists. contact the HP Support with the omnimigrate logs generated in the /log directory.  After the installation of Data Protector 8.exe on host somehostname”. Workaround: Remove the existing Notifications file (<omnidata\config\server>). Workaround: In . Post-upgrade checks After successfully installing/upgrading. you must recheck the database consistency using the following commands:  omnidbcheck and  omnidbcheck ­dc You may still encounter few issues after installing/upgrading to Data Protector 8.12. This is expected as new licenses must be generated for 8. Workaround: Create a new idb backup specification.1:  If the cell server hostname has changed.  After upgrading.  In the Data Protector GUI. a PB warning “obsolete licenses detected” may appear. you must use omnidbutil -change_cell_name <old_cell_name>./opt/omni/bin/perl /temp/omnimigrate.12. the Reporting context displays an error message when you click Notifications.

Replace$g_default_expireDays = (365 * 24). Change omnigencert. Post-upgrade . set it to on.11 or 8. it must be enabled on the Cell Manager too. 4. Change the default expiration time in the omnigencert. 2. Click the certificate symbol just before or after the address bar. and restart the services. This enables you to verify whether the certificate has expired. If the certificate has expires. Get the keystore password from /etc/opt/omni/client/components/webservice. If not.<omnidata>/server/db80/pg/postgreslq. #  10yrs.conf. Regenerate the certificate using one of the following commands: a.12 patch. Workaround: Visit the following URL: https://<cm-hostname>:7116 . b. Workaround: If clients have ECC enabled. It prompts whether it is allowed to continue. # 24yrs with  the following:  $g_default_expireDays = (365 * 10). For CM with one IP address: perl omnigencert.pl script (line 440): You can change it using one of the following ways: Install 8.properties. check whether archive_mode is set to on.pl. which shows the certificate. 3.  Expanding the backup specification tree results in an error.GUI client unable to connect to HP-UX Cell Server Certificates on HP-UX cell managers installed after 17. a. use the following steps: 1.01 are expired.pl ­server_id <FQDN of Cell Manager>  ­user_id hpdp ­store_password <keystore password from  step 1> . Navigate to /opt/omni/sbin/.

dns:<lucy.com  ­server_san dns:<woodstock.Example:perl omnigencert.12.hp.1 ­user_id hpdp ­store_password  123456 e.pl ­server_id <FQDN of Cell Manager>  ­server_san ip:<IP_1> ­user_id hpdp ­store_password  <keystore password from step 1> Example:perl omnigencert.pl ­server_id <FQDN of virtual node that runs the Cell Manager> ­server_san dns:<FQDN of physical  node 1>.pl ­server_id snoopy. If the CM is a 2-node cluster: perl omnigencert.hp. If the CM has one IP address and is accessed by an IP address instead of the hostname: perl omnigencert.dns:<FQDN of  second IP> ­user_id hpdp ­store_password <keystore  password from step 1> Example:perl omnigencert.hp.com>  ­user_id hpdp ­store_password 123456 c.pl ­server_id snoopy.com>.pl ­server_id snoopy.com  ­server_san dns:<snoopy.ip:<IP_2> ­user_id hpdp  ­store_password<keystore password from step 1> .hp. If the CM has two IP addresses: perl omnigencert.dns:<lucy.com  ­server_san ip:10.11.hp.com  ­user_id hpdp ­store_password 123456 b. If the CM has two IP addresses and is accessed by an IP address instead of the hostname: perl omnigencert.pl ­server_id snoopy.com>.hp.pl ­server_id  <FQDN of Cell Manager>  ­server_san ip:<IP_1>.pl ­server_id <FQDN of Cell Manager>  ­server_san dns:<FQDN of Cell Manager>.hp.com>  ­user_id hpdp ­store_password 123456 d.dns:<FQDN of physical node 2> ­user_id hpdp  ­store_password <keystore password from step 1> Example:perl omnigencert.hp.

6. b.1) from the system. Rollback You may experience failed upgrade/installation of Data Protector 8.Example: perl omnigencert. Restart the services.hp. contact HP Support to get correct binaries with fixes.com -server_san ip:10. It is highly recommended that you always install the latest patch on top of a fresh Data Protector installation to get most of the fixes. 1. 2.12.pl -server_id snoopy. In the case of upgrade. Retain the Data Protector IDB and configuration. b. Uninstall the current Data Protector version (8. For Windows: C:\ProgramData\OmniBack\Config\Server\AppServer C:\ProgramData\OmniBack\Config\Server\idb C:\ProgramData\OmniBack\server\AppServer C:\ProgramData\OmniBack\server\db80 C:\test\test . For any other problems. Add the IP and FQDN of CM (FQDN as resolved by CM).2 -user_id hpdp -store_password 123456 NOTE: Modify the above commands appropriately if clusters with three nodes or systems with more than two IP addresses are used.ip:10.11. 5. Delete the certificate on the GUI client (C:"\Users###BOT_TEXT###lt;USERNAME>\AppData\Local\Hewlett-Packard\Data Protector\ca"). Modify the C:\Windows\System32\drivers\etc\hosts file on the GUI client. Remove all new files created during the installation of 8. If the GUI client and Cell Manager are in different DNS domains: a.1.1.12. correct steps are needed to successfully revert to the prior product release.1.11.

if you install Data Protector at C:\test\test path\omniback. Install the old Data Protector version at the same location.P. The information in this document is subject to change without notice. it will create the file at C:\test\test. neither HPE nor its affiliates. special or consequential damages including downtime cost. Choose the old database and continue with the setup. lost profits. damages relating to the procurement of substitute products or services. Hewlett Packard Enterprise Company and the names of Hewlett Packard Enterprise products referenced herein are trademarks of Hewlett Packard .1 at the location that has a space character in its ProgramData path. subcontractors or suppliers will be liable for incidental. It should detect the old database and prompt you to use that one or create a new one. L. That “File” will be located on the last part of path where the space character is.NOTE: The last file is created during the installation process of Data Protector 8. or damages for loss of data. Hewlett Packard Enterprise Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. or software restoration. For Linux/HP-UX: rm -rf /etc/opt/omni/server/AppServer rm -rf /etc/opt/omni/server/idb rm -rf /var/opt/omni/server/db80 rm -rf /sbin/init. RESOLUTION Not Applicable Hardware Platforms Affected: HP Data Protector Software Components Affected: Not Applicable Operating Systems Affected: Not Applicable Software Affected: Not Applicable Third Party Products Affected: Not Applicable Support Communication Cross Reference ID: IA04350769 ©Copyright 2016 Hewlett Packard Enterprise Company.d/hpdp-* (HP-UX) rm –rf /etc/init. For example.d/hpdp-* (Linux) 3. To the extent permitted by law.

Enterprise Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners. .