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:

omnidbcheck
This command ensures that the data consistency is fine.

omnidbcheckdc
This command checks the DataCatalog consistency.

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, place them somewhere else during the installation process

After both these checks return Status - OK for all fields, you must perform a
full Internal Database backup.
NOTE: If you use the Windows platform and the
DataProtector (C:\"Program Files"\Omniback) directory
path includes spaces (which happens if you migrate your
Cell Manager environment from Windows 2003 to Windows
2008), you must read the Customer Advisory - QCIM2A50886 ,
which provides detailed instructions on handling this
issue.
If you already attempted the upgrade and if it failed,
see the Rollback chapter, which includes the step on
renaming the directory (to registry.old):

Windows:
C:\ProgramData\OmniBackConfig\client\components\registr
y

HP-UX/Linux: /etc/opt/omni/client/components/registry

To ensure a smooth upgrade, it is highly recommended that you prepare a test

environment and test the upgrade in that setup.
NOTE: Installation instructions for the test environment
are notapplicable if you have CMMDB MoM environments. For

such environments, you should always perform the manual

installation.
Installation instructions for the test environment:
1.

Create VM with the same OS as your production

environment.

2.

Install the same version of Data Protector as that on

your production server.

3.

Create two temp folders: cdb and mmdb.

4.

Run omnidbutilwritedbcdb<cdbFolderPath>mmdb
<mmdbFolderpath> on the production server.

5.

Copy the cdb and mmdb folders from the production

server to the test server.

6.

Run omnidbutilreaddbcdb<cdbFolderPath>mmdb
<mmdbFolderPath> on your test environment.

7.

Run omnidbutilchange_cell_name
<production_server_name>.

8.

Run the default Data Protector 8.1 installation.

If installation completes successfully, you do not need to follow the manual
installation instructions, which are described in the next section.
If you do not have the test environment, you can use one of the following
options:

Manual upgrade. It is described later in this

document.

Default upgrade. If it fails, see the Rollback and

installation/upgrade steps in this document.

Install/Upgrade Steps
After successfully resolving customer issues, HP released few Site Specific
Patches (SSPs) and advisory documents on the upgrade process of Data
Protector 8.1.

SSPNT810_003, SSPUX810_003, and SSPLNX810_003 were released to fix

problems with the upgrade process. These SSPs contain fixes for the
omnimigrate.pl script, which handles the process of migration and preparation
of data from the old database (Velocis) to new (Postgre). In addition, these
SSPs contain fixes for the F_dpidb_801_fix_corruption.sql script, which
handles the post-upgrade corruptions and adjusts the data fields in the new
database.
Customer Advisory documents were released prior to common problems
detected during the install process of Data Protector.

Customer Advisory - QCIM2A50886.docx : Released due to

Data Protector 8.x install\upgrade process not
detecting a space character in the DataProtector data
path, thereby causing the processes to fail.

Customer Advisory - QCIM2A51402.docx : Released due to

Data Protector 8.1 upgrade process erasing the database
in the MoM environment with CMMDB implemented.

All of these problems can be fixed using the pre-upgrade steps. Alternatively,
you can use the following steps:
1.

Download the appropriate SSP: SSPNT810_003 (Windows),

SSPLNX810_003 (Linux), or SSPUX810_003 (HP-UX).

2.

Unzip the contents to an appropriate location:

C:\temp (Windows) or /temp (Linux/UX).

3.

For Windows: ensure that you have the msvcp71.dll

file, which is located at C:\Windows\SysWoW64. If the
file is missing, download it from the official Microsoft
download site.

4.

Run the following command:

%DP_HOME_DIR%/bin/perl.exe"C:\temp\omnimigrate.pl
exportshared_dirC:\temp
or
/opt/omni/bin/perl/temp/omnimigrate.plexport
shared_dir/temp

An inter-process communication error may appear at this

step. This is expected as we kill the process before
exporting file names. If the script hangs after this
error, kill the process. Failure at this step may occur
because services are being stopped after printing out the
file names of the hosts, and the server fails to restart
them in time. To continue with the install process, you
should replace the Step 4 with the following steps:
a.

In the temp directory (C:\temp or /temp), create

two additional directories: cdb and mmdb. If these two
directories already exist, delete their content.

b.

Run omnidbutilwritedbcdb<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>Exportingfilenamesfor
some.hostname.yu...

c.

Run the export command with the following

changes:
%DP_HOME_DIR%/bin/perl.exe"C:\temp\omnimigrate.pl
exportNonASCIIshared_dirC:\temp
or
/opt/omni/bin/perl/temp/omnimigrate.plexportNonASCII
shared_dir/temp

d.

Create the old_cm file. It should contain only

two lines: (exact folder)
OLDCM_SHORTNAME=OldCmName
OLDCM_ENDIANNESS=Endianness
where,

OldCmName is replaced with the short CM

name.

Endianness is LITTLE_ENDIAN (Windows or

Linux) or BIG_ENDIAN (HP-UX)

You should verify this, as it can vary. Note that there

is no space between the variable, =, and the value.
5.

Make sure no sessions are currently running.

Run omnistat.

6.

Stop Data Protector services.

7.

Rename the db40 folder to db40.old. Do not delete any

database or configuration folders.

8.

Uninstall the current version of Data Protector

usingomnisetup.shUninstall (for non-Windows setup).

9.

Rename %DP_DATA_DIR
%\Config\client\components\registry to registry.old
(Windows) or /etc/opt/omni/client/components/registry to
registry.old (HP-UX or Linux).

10.

Start fresh installation of Data Protector 8.1

NOTE: For Windows, it is advisable to use the same

location as used earlier. If it is not the case, the
following additional steps are required. These steps are
applicable only if you do not want to use the old
location.
a.

Copy content of db40.old from the previous path

to the new path (except DCBF folders).

b.

Copy the old configuration files, but keep the

old files. Do not copy the files from %DP_DATA_DIR
%\Config\Server\install.
If you want to keep old cell configuration (clients,
installation server) copy and overwrite the %DP_DATA_DIR
%\Config\Server\cell\cell_info and installation_server
files,

11.

Rename db40.old to db40.

12.
Perform import of the old data. Run the following
command:
"%programfiles%/omniback/bin/perl.exe"
C:\temp\omnimigrate.plimportshared_dirC:\temp
or
/opt/omni/bin/perl/temp/omnimigrate.plimport
shared_dir/temp
13.
Run the corruption fix script, which was provided in
SSP.
omnidbutilrun_script
C:\temp\F_dpidb_801_fix_corruption.sqldetail
or
omnidbutilrun_script
/temp/F_dpidb_801_fix_corruption.sqldetail
If for any reason your import fails [accidental canceling of the import process
(step 12) or any other unknown reason], you can reset the import operation
using the following steps:
1.

Stop services, and rename your db40 folder to

db40.old.

2.

Restart services and run the omnidbinit command. This

will erase all the information collected in the database
as well as all catalogs located in the db40 folder.
Therefore, renaming is required.

3.

Stop services, and rename db40.old to db40.

4.

Restart services and re-run the following command:

"%programfiles%/omniback/bin/perl.exe"
C:\temp\omnimigrate.plimportshared_dirC:\temp
or

/opt/omni/bin/perl/temp/omnimigrate.plimport
shared_dir/temp
If the problem still persists, contact the HP Support with the omnimigrate logs
generated in the /log directory.
Post-upgrade checks
After successfully installing/upgrading, you must recheck the database
consistency using the following commands:

omnidbcheck
and

omnidbcheckdc

You may still encounter few issues after installing/upgrading to Data Protector
8.1:

If the cell server hostname has changed, you must use

omnidbutil -change_cell_name <old_cell_name>.

After the installation of Data Protector 8.12, a PB

warning obsolete licenses detected may appear. This
is expected as new licenses must be generated for 8.12.

In the Data Protector GUI, the Reporting context

displays an error message when you click Notifications.
Workaround: Remove the existing Notifications file
(<omnidata\config\server>).

After upgrading, IDB backups with the old backup spec

fail with the following message: Cannot connect to
inet for starting of OB2BAR application
postgres_bar.exe on host somehostname. Workaround:
Create a new idb backup specification.

IDB backup fails with the following error message:

Putting the Internal Databse into the backup mode
failed. Workaround: In

<omnidata>/server/db80/pg/postgreslq.conf, check
whether archive_mode is set to on. If not, set it to
on, and restart the services.

Expanding the backup specification tree results in an

error. Workaround: If clients have ECC enabled, it must
be enabled on the Cell Manager too.

Post-upgrade - GUI client unable to connect to HP-UX Cell Server

Certificates on HP-UX cell managers installed after 17.01 are expired.
Workaround: Visit the following URL: https://<cm-hostname>:7116 . It prompts
whether it is allowed to continue. Click the certificate symbol just before or
after the address bar, which shows the certificate. This enables you to verify
whether the certificate has expired. If the certificate has expires, use the
following steps:
1.
2.
3.

a.

Get the keystore password from

/etc/opt/omni/client/components/webservice.properties.
Navigate to /opt/omni/sbin/.
Change the default expiration time in the
omnigencert.pl script (line 440): You can change it using
one of the following ways:
Install 8.11 or 8.12 patch.

b.

Change omnigencert.pl.
Replace$g_default_expireDays=(365*24);#24yrswith
thefollowing:$g_default_expireDays=(365*10);#
10yrs.

4.

Regenerate the certificate using one of the following

commands:

a.

For CM with one IP address:

perlomnigencert.plserver_id<FQDNofCellManager>
user_idhpdpstore_password<keystorepasswordfrom
step1>

Example:perlomnigencert.plserver_idsnoopy.hp.com
user_idhpdpstore_password123456
b.

If the CM is a 2-node cluster:

perlomnigencert.plserver_id<FQDNofvirtualnodethat
runstheCellManager>server_sandns:<FQDNofphysical
node1>,dns:<FQDNofphysicalnode2>user_idhpdp
store_password<keystorepasswordfromstep1>
Example:perlomnigencert.plserver_idsnoopy.hp.com
server_sandns:<woodstock.hp.com>,dns:<lucy.hp.com>
user_idhpdpstore_password123456

c.

If the CM has two IP addresses:

perlomnigencert.plserver_id<FQDNofCellManager>
server_sandns:<FQDNofCellManager>,dns:<FQDNof
secondIP>user_idhpdpstore_password<keystore
passwordfromstep1>
Example:perlomnigencert.plserver_idsnoopy.hp.com
server_sandns:<snoopy.hp.com>,dns:<lucy.hp.com>
user_idhpdpstore_password123456

d.

If the CM has one IP address and is accessed by

an IP address instead of the hostname:
perlomnigencert.plserver_id<FQDNofCellManager>
server_sanip:<IP_1>user_idhpdpstore_password
<keystorepasswordfromstep1>
Example:perlomnigencert.plserver_idsnoopy.hp.com
server_sanip:10.11.12.1user_idhpdpstore_password
123456

e.

If the CM has two IP addresses and is accessed

by an IP address instead of the hostname:
perlomnigencert.plserver_id<FQDNofCellManager>
server_sanip:<IP_1>,ip:<IP_2>user_idhpdp
store_password<keystorepasswordfromstep1>

Example: perl omnigencert.pl -server_id snoopy.hp.com

-server_san ip:10.11.12.1,ip:10.11.12.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.
5.

If the GUI client and Cell Manager are in different

DNS domains:

a.

Modify the C:\Windows\System32\drivers\etc\hosts

file on the GUI client. Add the IP and FQDN of CM (FQDN
as resolved by CM).

b.

b. Delete the certificate on the GUI client

(C:"\Users\<USERNAME>\AppData\Local\Hewlett-Packard\Data
Protector\ca").

6.

Restart the services.

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. For any other
problems, contact HP Support to get correct binaries with fixes.
Rollback
You may experience failed upgrade/installation of Data Protector 8.1. In the
case of upgrade, correct steps are needed to successfully revert to the prior
product release.

1.

Uninstall the current Data Protector version (8.1)

from the system. Retain the Data Protector IDB and
configuration.

2.

Remove all new files created during the installation

of 8.1.
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

NOTE: The last file is created during the installation

process of Data Protector 8.1 at the location that has a
space character in its ProgramData path. That File will
be located on the last part of path where the space
character is. For example, if you install Data Protector
at C:\test\test path\omniback, it will create the file at
C:\test\test.
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.d/hpdp-* (HP-UX)
rm rf /etc/init.d/hpdp-* (Linux)
3.

Install the old Data Protector version at the same

location. It should detect the old database and prompt
you to use that one or create a new one. Choose the old
database and continue with the setup.
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, L.P.
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. To the
extent permitted by law, neither HPE nor its affiliates,
subcontractors or suppliers will be liable for incidental, special or
consequential damages including downtime cost; lost profits; damages
relating to the procurement of substitute products or services; or
damages for loss of data, or software restoration. The information in
this document is subject to change without notice. Hewlett Packard
Enterprise Company and the names of Hewlett Packard Enterprise
products referenced herein are trademarks of Hewlett Packard

Enterprise Company in the United States and other countries. Other

product and company names mentioned herein may be trademarks of their
respective owners.