Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
coiter Absent Member.
Absent Member.
3925 views

DP8.1 Remote IDB Backup failure.

for some unknown reason all my site backups of IDB is now failing backup every day.

 

the debug.log file shows nothing of interest, then failed to send smnp trap..

 

sessin log says the following:

[Normal] From: OB2BAR_POSTGRES_BAR@xxxx "DPIDB" Time: 6/20/2014 8:13:58 AM
Check of the Internal Database consistency succeeded

[Normal] From: OB2BAR_POSTGRES_BAR@xxxxx "DPIDB" Time: 20.06.2014 08:13:58
Putting the Internal database into the backup mode finished

[Critical] From: OB2BAR_POSTGRES_BAR@xxxx "DPIDB" Time: 6/20/2014 8:13:58 AM
Putting the Internal Database into the backup mode failed

 

archive_mode= on is enabled.

 

this error was not present on DP7, but its now on DP8

 

it is only the remote site offices that has this error, IDB backup at main server is working normally.

 

all omnidb checks are just fine, no errors reported.

 

what is it that i am missing.?

 

0 Likes
4 Replies
Highlighted
Bob_Clark Absent Member.
Absent Member.

Re: DP8.1 Remote IDB Backup failure.

DP 8 uses an entirely different IDB than DP 7 did

 

What is the OS-type of the cell maanger?

 

Some of the things that can cause this

 

UNIX Cell Manager:

UNIX domain sockets connection to postgres database could not be done because

unix_socket_directory postgres's config parameter is changed from default /tmp to /var/opt/omni/tmp
This looks like it was fixed on the DP site
 
----------------
 
Windows Cell Manager:
 
psql: FATAL:  SSPI authentication failed for user "hpdp"

Changing the user and configuring it in the following way:


1.) This services must be run with the new user:
[HP Data Protector] - Internal Database service
[HP Data Protector] - Internal Database connection pool
[HP Data Protector] - Application Server


2.) Modify Permissions for the new user should be added to folder:
\ProgramData\server\db80


3.) New must be added with:
omniinetpasswd -add { User@Domain
Domain\User }... [Password]


4.) Mapping should be corrected in:
- Config\Server\idb\idb.config (PGOSUSER='Domain\newuser';)
- server\db80\pg\pg_ident.conf
MAPNAME SYSTEM-USERNAME PG-USERNAME
hpdpidb newuser hpdp
 
You will probably need toget a case opened, and have this debugged to see if one of these are the problem, or, if it is something else
coiter Absent Member.
Absent Member.

Re: DP8.1 Remote IDB Backup failure.

i will have to check, but it worked just fine when it was DP 8.0 backup, so all the IDB is version 8 already.

 

It is when going up to version 8.1 the fault started to come.

 

the normal backp of the fileserver is working just fine, its just the IDB backup that is faulty.

 

All cell managers re Windows 2008 R2 Servers.

0 Likes
DeDa
Visitor.

Re: DP8.1 Remote IDB Backup failure.

Hi,

 

DId you by any chance look inside the logs to see if you can find any additional infromation why did putting of the IDB into backup mode failed?

 

 

0 Likes
Absent Member.. Dadwelch Absent Member..
Absent Member..

Re: DP8.1 Remote IDB Backup failure.

Thanks Bob_Clark, 

"New must be added with:
omniinetpasswd -add { User@Domain
Domain\User }... [Password]"

This sorted the same issue for me.

We changed the password that the IDB services run a while ago, but since the service account logins were updated at the time all looked good. I didn't realise that HPDP kept a copy of the credentials within the IDB for the backup process to use!

Cheers

Chris

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.