Highlighted
Absent Member.
Absent Member.
2199 views

omnimm - list pools

Jump to solution
Hello,

I scheduled my backups in a win2l cell srv with all patches installed.
The backups are tested by manual runs, and previews.
However when they are scheduled they w
will not run.
Event tells me :

[138:709] Health check message: "omnimm -list_pools" failed.

Description:

Actions:
Check the following log file for more details:
* /var/opt/omni/log/HealthCheck.log (UNIX)
* \log\HealthCheck.log (Windows)

When i check the log :

Status: All Data Protector relevant processes/services up and running.

Exit code: 0

======> Running: omnimm -list_pools
You have no permission for the requested media management action.

Exit code: 1

======> Running: omnidbutil -show_cell_name
Catalog database owner: "fzsbck01.fz.local"

Exit code: 0

=====================================
Health check ended: 6/9/2004 12:30:06 PM
Health check result: Errors occurred
Health check exit code: 1

When i check the services for CRS it states a local admin is responsible ??
Should this be local system account.
I never configured this, how is this possible.

Any help is appreciated...

rmk
0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.
The CRS service must run under a domain admin account. That is why your schedules aren't executed.

best regards,
Kurt

View solution in original post

8 Replies
Highlighted
Absent Member.
Absent Member.
hi,

not sure if u have done anything to this file:

OMNIHOME\Config\Cell\user_restrictions

which may have cause some permission problem.

u may like to reply on the content of this file.

regards.
what you do not see does not mean you should not believe
0 Likes
Highlighted
Absent Member.
Absent Member.
The CRS service must run under a domain admin account. That is why your schedules aren't executed.

best regards,
Kurt

View solution in original post

Highlighted
Absent Member.
Absent Member.
Name resolution most likely.

You have no permission for the requested media management action.

The CRS account runs as a particular user. Is this user correctly defined in the Data Protector user's list as an admin user?

It's possible the user matches multiple entries in the UserList file, but it matches an entry higher up in the file which id's the user as only a user or an operator or something.

Thanks,
Scott
HP Support
Highlighted
Absent Member.
Absent Member.
Very much the same problem, all user accounts both in AD and DP look fine to me.

[138:709] Health check message: "omnimm -list_pools" failed.

Description:



Actions:
Check the following log file for more details:
* /var/opt/omni/log/HealthCheck.log (UNIX)
* \log\HealthCheck.log (Windows)


Same message os the author in the Healthcheck.log file.

Thoughts?
0 Likes
Highlighted
Absent Member.
Absent Member.
Sorry, also the file

OMNIHOME\Config\Cell\user_restrictions

Does not exist.

Cheers
0 Likes
Highlighted
Absent Member.
Absent Member.
Log onto the cell manager as the account the CRS service runs as. Run OmniBack\bin\omnimm -list_pools. Work?

If not, then stop the DP Inet service. Add the startup parameters -debug 10 inet.txt and then hit start (start first, close second, not the other way around0.

Run omnimm -list_pools again.

Stop inet, clear the startup parameters, start inet.

Get the *inet.txt file from OmniBack\tmp and post that as well as OmniBack\config\users\UserList

Thanks,
Scott
HP Support
0 Likes
Highlighted
Absent Member.
Absent Member.
I think I worked it out.

When you use the DP manager tool to add the users, for some reason it puts the AD servers name in instead of the domain name.

So the account tries to authenicate to the Server as opposed to the domain. Could be wrong.

I haven't actually tried this yet, but I think that changing the servers name to the domain name will correct it.

I'll post later when I try it out.

Thanks for the info.

Shayne
0 Likes
Highlighted
Absent Member.
Absent Member.
The UserList file shows exactly the user parameters configured to allow DP access.

The 10 range of the INET debugs will show exactly the credentials presented by a connecting process.

The CRS debug will show the user account which crs.exe is running as. That might actually be the better process to run with in this case.

omnisv -start -debug 1-100 hp.txt
omnisv -stop

What's in the header of the CRS debug file in OmniBack\tmp?

Thanks,
Scott
HP Support
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.