Hello Robert,
This change will require a re-architecture of a large portion of the MB
backup -- that part which identifies and selects mailboxes to be saved (and
the MB recover code will have to understand *both* methods). It is more of
a new feature, or a new design, than a fix. As such, it is not a good
candidate for a QuickFix: we do not want to take steps in a QuickFix that
might have the net effect of destabilizing a backup environment. In fact,
this fix is similarly not suitable for a supplemental or maintenance release
either, for the same reason. Thus we should anticipate this level of change
being present in 4.1 or 5.0 or such, where it has gone through a full test
suite, but not in 4.0.1 or any hotfix to 4.0.x.
On the other hand, a disabled mailbox should not cause the job to be flagged
as a failure.
Thanks,
_Scott
-----Original Message-----
From: Maiello, Robert [mailto:robert.maiello AT THOMSON DOT COM]
Sent: Friday, March 12, 2004 2:24 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Exchange 2003
Yikes, how about a hotfix? It would seem, even if we can live with not
backing up these mailboxes, the backups
will be flagged as failed every night.
Robert Maiello
-----Original Message-----
From: Scott Bingham [mailto:SBingham AT legato DOT com]
Sent: Friday, March 12, 2004 5:13 PM
To: 'Legato NetWorker discussion'; 'Robert Maiello'
Subject: RE: [Networker] Exchange 2003
I believe that we're currently planning to target that for this summer -- no
promises.
_Scott
-----Original Message-----
From: Robert Maiello [ mailto:robert.maiello AT THOMSON DOT COM
<mailto:robert.maiello AT THOMSON DOT COM> ]
Sent: Friday, March 12, 2004 1:49 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Exchange 2003
Thanks for understanding the reasons for a disabled account so well. Do
you have a timeframe for the next release?
Robert Maiello
Thomson Healthcare
On Fri, 12 Mar 2004 12:27:24 -0800, Scott Bingham <SBingham AT LEGATO DOT COM>
wrote:
>Hello Robert and Anuj, et al,
>
>I, for one, do consider this (disabled/disconnected mailbox failure) to be
a
>severe limitation, and currently plan to lift it in the next release of the
>Exchange Module, subject to limitation -- the limitation being that the
>mailbox in question must be a healthy, properly configured Exchange
mailbox.
>
>The typical reason where a mailbox might be disabled, but healthy and in
>production: An Exchange administrator can build an environment where a
>mailbox on the local Exchange Server is associated with a user whose
account
>is in a different Forest, in Active Directory terms. In this scenario, the
>local AD has a specially-configured Disabled User for the account. (This
is
>described in detail in various Microsoft documentation, including KSKB
>articles 278888 and 322890.) Our current product relies upon AD for access
>to the mailbox, and thus cannot access it. This is what we currently plan
>to address.
>
>If, on the other hand, an admin has a normal local mailbox, and perhaps an
>employee leaves the company, and the admin goes to "Users and Computers"
and
>disables the account, then Exchange Server will refuse us access to the
>mailbox. We cannot change that. There will still be a workaround
available
>to Exchange-savvy admins, however, in that one can lie to Exchange, and
>assign the well-known-ID of "SELF" to the "msExchMasterAccountSID" property
>in AD for that user. (Microsoft describes this method in MSKB 278966,
>although they refer to a slightly different symptom.) This simulates the
>remote-forest user scenario, as far as Exchange Server is concerned, and
>will allow a privileged user access to backup the messages. Again,
>unfortunately, that will not help us in the current Exchange Module
>releases. I am working on it.
>
>Please note that all of this applies to Robert's error message, and the 2nd
>and 3rd of the error messages within Anuj's post. The 1st and 4th error
>messages indicate that a particular message has been denied to us by
>Exchange Server, e.g. by an antivirus program.
>
>Hope that this helps,
>_Scott
>
>-----Original Message-----
>From: Robert Maiello [ mailto:robert.maiello AT THOMSON DOT COM
<mailto:robert.maiello AT THOMSON DOT COM> ]
>Sent: Thursday, March 11, 2004 6:22 AM
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: Re: [Networker] Exchange 2003
>
>
>We started testing this module. We needed to get a new copy/fix of the
>4.0 Exchange Module.. build 190. This allows it to work when the client
>name is greater than 15 characters.
>
>We have encountered the "unable to process mailbox, account xxx is
>disabled".
>
>Apparently, according to our support case, the module/product is not
>designed to backup a disabled mailbox. Does anyone else find this to be
>a severe limitation?? If a persons's mailbox is disabled we would still
>like to get a backup of it. Is this something that is physically possible
>or is a mailbox inaccessible to everything once disabled?
>
>
>Robert Maiello
>Thomson Healthcare
>
>On Thu, 11 Mar 2004 12:27:51 +0530, Anuj <anuj AT ACE-DATA DOT NET> wrote:
>
>>Hi,
>>
>>It has finally started backing up a few mailboxes. For others, it is
giving
>>errors like -
>>
>>1. "[448] mb_item.cpp(2121): IMAPIContainer::OpenEntry() = 0x80004005:
The
>>client operation failed. (Microsoft Exchange Server Information Store)".
>>
>>2. "[448] Exchange Mailbox "A K Singh" is not connected to an Active
>>Directory user. It will be skipped."
>>
>>3. "[448] adsutil (3435): Unable to process mailbox, account kumar
>>Subramanian is disabled".
>>
>>4. "[448] mb_item.cpp(2446): The Exchange Server has refused to allow
>>backup of item: Customer Statement for email:kalran AT encorpworld DOT com"
>>
>>Any clues on these would be of great help.
>>
>>Regards,
>>Anuj Mediratta
>>Ace Data Devices Pvt. Ltd.
>>I-132, Kirti Nagar, New Delhi - 110 015.
>>Mobile : 32334262
>>Email : anuj AT ace-data DOT com
>>----- Original Message -----
>>From: "Scott Bingham" <SBingham AT LEGATO DOT COM>
>>To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
>>Sent: Tuesday, March 09, 2004 4:46 AM
>>Subject: Re: [Networker] Exchange 2003
>>
>>
>>> Hello Anuj,
>>>
>>> Shannon's advice is very good; even better, use the GUI, selcting just
>one
>>> or two usernames. Get that working before attempting to schedule
>backups.
>>>
>>> In addition: ensure that the Client on the NetWorker Server is set with
>>the
>>> correct information. In particular, check that the "Backup command"
under
>>> the "Remote" tab is correctly set to invoke nsrxchsv.exe.
>>>
>>> More complete and informative error messages for Exchange Module are
>>always
>>> found in its private logfile, which is found in nsrxchsv.log in the
>>> ...nsr\applogs folder on the Exchange Server.
>>>
>>> Make sure that you are doing database backups first -- they are much
more
>>> important that mailbox backups.
>>>
>>> Thanks,
>>> _Scott
>>>
>>> -----Original Message-----
>>> From: Shannon Ward [ mailto:sward AT rackspace DOT com
<mailto:sward AT rackspace DOT com> ]
>>> Sent: Saturday, March 06, 2004 8:21 AM
>>> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>>> Subject: Re: [Networker] Exchange 2003
>>>
>>>
>>> Haven't worked with the Exchange module yet, but you might try running a
>>> command line manual backup of Exchange from the client (assuming that
>>> there is a command line utility on the client.) That might produce some
>>> additional troubleshooting messages.
>>>
>>> --Shannon Ward
>>>
>>>
>>> On Sat, 6 Mar 2004 09:57:55 -0000 Anuj Mediratta wrote:
>>>
>>> > Hi All,
>>> >
>>> > I am nstalling Exchnage module 4.0, NW 7.1 in a setup using Windows
>2003
>>&
>>> > MS Exchange 2003.
>>> >
>>> > We are able to take the IS group backup but when we try the mailbox
>>backup
>>> > either individual or all mailboxes using the saveste -
>>> > MSEXCH:MB/georger or
>>> > MSEXCH:MB, we get the error -
>>> >
>>> > Feb 28 15:43:19 encorp-bdc: --- Unsuccessful Save Sets ---
>>> > Feb 28 15:43:19 encorp-bdc: *
>>encorpmail.encorpworld.com:MSEXCH:MB/georger
>>> > 1 retry attempted
>>> > Feb 28 15:43:19 encorp-bdc: *
>>encorpmail.encorpworld.com:MSEXCH:MB/georger
>>> > nsrexec: authtype nsrexec
>>> > Feb 28 15:43:19 encorp-bdc: *
>>encorpmail.encorpworld.com:MSEXCH:MB/georger
>>> > savefs: A required privilege is not held by the client.
>>> >
>>> > The networker remote exec services on the exchange server are logged
on
>>> > using the Exchange administrator username & password. The remote user
>>> > field
>>> > in the client specification is also using the same administrator
>>> > username &
>>> > password. Removing username & password from remote user field does
note
>>> > help. The error remains the same in both cases.
>>> >
>>> > We do not have a dedicated Exchange administrator. The domain
>>> > administrator
>>> > for Windows 2003 controls all Exchange server related activities.
Every
>>> > time a new user is created, a new mailbox gets created automatically.
>>> >
>>> > We are unable to locate where to enable any priviledges to this
>>> > administrator & take backups using Legato.
>>> >
>>> > Can some one help me on this?
>>> > regards,
>>> > Anuj
>>> >
>>> > --
>>> > Note: To sign off this list, send a "signoff networker" command via
>>email
>>> > to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>> > http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>>> > also view and post messages to the list.
>>> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>>
>>> --
>>> Note: To sign off this list, send a "signoff networker" command via
email
>>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>> http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>>> also view and post messages to the list.
>>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>>
>>> --
>>> Note: To sign off this list, send a "signoff networker" command via
email
>>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>> http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>>> also view and post messages to the list.
>>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>>
>>
>>--
>>Note: To sign off this list, send a "signoff networker" command via email
>>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>> http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>>also view and post messages to the list.
>>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html
<http://listmail.temple.edu/archives/networker.html> where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service.
________________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
