UNSOLVED
Ms Exchange Cluster Priveleges Error
This is my first post so please bare me with on this thread.
Networker host is v7.3.2 | Ms Exchange 2007 Active-Passive Cluster has both NW User client + NW User for Exchange Server client installed.
------------------------------------------------------------------
Problem is: I cannot achieve successful backup of Exchange Mailboxes. Problem Client is set with following save-set info: MSEXCH:MB, with appropriate privileges/credentials, I think?
However, I get the following error on Networker host in daemon.log:
"..........Impersonation was requested by: "user/server@domain", but the user does not have enough privileges to impersonate......"
If I run a manual job from Exchange Virtual Cluster I get the following error in networkr.raw:
".....nsrxchmbsv:mapi(1295): Insufficient permissions to access mailbox. See documentation for required permission settings...."
I have read the relevant chapters and implemented procedures as per manual EMC Networker Module for MS Exchange Server rel 5.1 (admin guide).
I have retraced steps as much as possible, but I cannot get anywhere with this problem.
Any help would be greatly appreciated!!
Thanks
Jim
Networker host is v7.3.2 | Ms Exchange 2007 Active-Passive Cluster has both NW User client + NW User for Exchange Server client installed.
------------------------------------------------------------------
Problem is: I cannot achieve successful backup of Exchange Mailboxes. Problem Client is set with following save-set info: MSEXCH:MB, with appropriate privileges/credentials, I think?
However, I get the following error on Networker host in daemon.log:
"..........Impersonation was requested by: "user/server@domain", but the user does not have enough privileges to impersonate......"
If I run a manual job from Exchange Virtual Cluster I get the following error in networkr.raw:
".....nsrxchmbsv:mapi(1295): Insufficient permissions to access mailbox. See documentation for required permission settings...."
I have read the relevant chapters and implemented procedures as per manual EMC Networker Module for MS Exchange Server rel 5.1 (admin guide).
I have retraced steps as much as possible, but I cannot get anywhere with this problem.
Any help would be greatly appreciated!!
Thanks
Jim
csanchezgonzale
11 Posts
156
0
Posted November 14th, 2007 02:00
Hi.
I have the same message:
Impersonation was requested by: "user/host@domain", but the user does not have enough privileges to impersonate.
But the Exchange backup works correctly; we have the backup configured at Storage Group level.
My question is, why this message appears? and how can i make it dessapear?
Thaks a lot.- Hi - Yes I also have a client job running and set for MSEXCH: and this will backup all storage groups as expected and works fine without errors. My only problem is that when running the MSEXCH:MB for mailbox brick-level backup I get errors as stated before.
I Have a sun case logged for this and they are now in touch with backline support (EMC) also, but so far any suggested fixes have failed, so if anyone as any suggestions please let me know.
The other annoying problem that I have with the exchange jobs is that after any successfully completed backup the savegroup job still appears to be running and will not stop? - Impersonation I believe can be addressed through some admin lists in NSRLA, but I never really tested it. Number of those seen on server side are also caused by NMC server where sometimes (!?) they would get addressed by putting SYSTEM/administrator/root user on admin list. I so far ignored that message as I could not see any harm - I'm really interested in what EMC is going to suggest.
As fo savegrp and Exchange, you probably have module 5.1 which against server earlier than 7.4 causes issues. There is a patch for 7.3SP3. At least it sounds like that problem.
ble1
6 Operator
•
14354 Posts
•
56186 Points
156
0
Posted November 11th, 2007 04:00
Mailbox access is problem. I would advise you speak to Exchange admin and make sure user you are zsing to MB backup has rights as outlined in docs. I believe there is a KB article dealing with this as they are several threads in this forum too.