Tag Archive: Workaround

Mar 30

Resolving FilterListenerService installation issue

You may run into this non-critical issue during upgrade to Data Protector A.09.09 on Windows Cell Managers in case to the installation was done to a non-default path, e.g O:\Omniback and the VEPA integration is also installed. Error: could not locate INF file ‘C:\Program Files\Omniback\bin\HPEDpHsm.inf’ is displayed during the patch bundle setup High CPU load caused …

Continue reading »

Feb 28

Resolve Cell Manager installation failures on RHEL7

Starting with Data Protector A.09.05 Red Hat Enterprise Linux 7.0 and 7.1 is now a supported Cell Manager platform. But running the regular installation procedure on a fresh RHEL 7.1 system does not work, even with all requirements met. [root@linux ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.1 (Maipo) [root@linux ~]# uname -a Linux jetlnx01.godyo.int …

Continue reading »

May 10

Clean up after Data Protector IDB restore

IDB restore with Data Protector 8 and later is really straight forward. It allows a much more granular recovery than in previous versions, since it’s done using a fully featured module instead of a file system hot-backup. You’re able to restore the IDB (PostgreSQL database) including log file recovery, DCBF files and configuration files individually or all together …

Continue reading »

May 09

Re-initialize Data Protector IDB (PostgreSQL)

This post will show you how to re-initialize the Internal Database of Data Protector 8 or later to start from scratch without the need for re-installation. This was quite simple on previous versions and needs to be adjusted for the new PostgreSQL database and JBoss application server. These instructions will work on Linux and HP-UX. If I find a proper …

Continue reading »

May 07

Failed to open Data Protector GUI: Internal Error

I just came across a strange Data Protector User Interface error. After a fresh installation the DP GUI reported the following error during first start. Internal Error Non-recoverable error: (0) Failed to initialize the working environment. System error: Unknown The debug.log created in the home directory of the user had the following error in it …

Continue reading »

Apr 25

Delete db40\dcbf folder after migration to DP 8.x

If you migrate from a previous version to Data Protector A.08.00 or later on Windows, you might come across an issue where you’re unable to remove the old db40\dcbf directories using GUI or omnidbutil -remove_dcdir. This is most likely caused by the used path separator inside the Internal Database. Since version 8 the path separator …

Continue reading »

Aug 14

Data Protector Push installation for Debian clients

Integrating Debian or Debian-based Linux clients (e.g. Ubuntu) into a Data Protector cell could be a pain, if you have more than a bunch of them. Patch rollout and release upgrades will even take more time if you poke around with alien to convert the Data Protector rpm into deb format. There are some simple requirements …

Continue reading »

Aug 03

Restore from NDMP device mirror

I just came across an issue at customer site where Data Protector Device Mirror was used to duplicate NDMP backups. In general this is a great way to reduce the amount of time it takes to create separate sets of media at backup time. The worse thing is, this feature is not supported in Data …

Continue reading »

Jul 22

Patch Data Protector standalone client

There are cases in with you need to apply GA patches to a UNIX client and you don’t have an Data Protector UNIX IS (Installation Server) available. This is worse, because the patches are designed to update an installation server only. The following procedure will help you out. Instead of applying the patches to an …

Continue reading »

Dec 30

Quiesced Snapshots for Exchange 2010 on vSphere 5.0

Due to an upgrade from vSphere 4.0 to 5.0 some of our virtual machines stopped working in VEPA/vStorage backup sessions. I’ve noticed that a quiesced snapshot using vCenter was not possible. I was able to fix the most of them by reinstalling VMware Tools to fix some VSS inconsistencies, but an Exchange 2010 VM caused …

Continue reading »

Older posts «