Backup Exchange from another domain

[Bas_Harnas]

Hi. I'm trying to backup Exchange mailboxes from another domain. Both domains are on the same subnet, so they are reachable. Normal data is backed up fine. However, Exchange mailboxes keeps coming with "Unable to attach" message. Userid's and passwords are the same on both domains. Any suggestions how to solve this?

Any help would be greatly appreciated.

[Kevin_Hendry]

Ok, Does the backup account have access to the Exchange Service Account? It will need to in order to backup individual mailboxes.

Regards,

KEv

[Bas_Harnas]

Hi Kev,
In this case it is the Administrators account with similar passwords on both domains.

Regards,
Hans

[Ameet_Thakkar]

GENERAL CHECK LIST FOR BACKING UP EXCHANGE SERVER:

Please make sure following:

Exchange agent licenses is registered/Installed on the media server and "Remote agent" is installed on the exchange server.

Make sure you have given following rights to the backup exec service account.

1) Domain admin
2) Exchange full admin
3) Local admin of the remote exchange machine.

Most of the time account does not have "DOmain admin" and "Exchange FUll admin" rights.

4) Make sure the Backupexec service account has a unique mailbox (Ex-"admin" and "administrator" is not unique because they contain the same subset of characters).

If not please create it and activate the mailbox by sending atleast one mail.You can even check in the system
manager if the mailbox is listed there or not?

If this does not help,Proceed further.

Is the mailbox hidden in the exchange address list.
If yes, then please Unhide the mailbox from Exchange Address lists. (From the active-directory--right click the user--properties---click exchange advanced---uncheck the box.


Is the mailbox active?
Please make sure you have activated the mailbox by sending atleast one mail.


Related Documents:
Logon Account " " failed to access "\\SERVER\Microsoft Exchange Mailbox". Access Denied
http://support.veritas.com/docs/256313

How to configure a Microsoft Exchange 5.5 & 2000 individual mailbox backup: A comprehensive overview
http://support.veritas.com/docs/249456

When attempting to back up mailboxes, an error was encountered because the mailbox that is used to attach is not unique.
http://support.veritas.com/docs/262707

How to confirm that an Exchange mailbox name is unique within the Exchange organization when configuring VERITAS Backup Exec (tm) to back up Exchange mailboxes
http://support.veritas.com/docs/256537

How to protect Exchange 2000 and 2003 servers using the Backup Exec for Windows Servers Exchange Agent
http://support.veritas.com/docs/266074
----------------------------------------------
We hope this helps.

[Rohit_Sonawale]

Kindly update us on this issue.

[Bas_Harnas]

Still no success. If you select the mailboxes through the "text-interface" it is selected but the message "unable to attach" keeps appearing. When selecting through the grafical interface it keeps coming with the selection of a userid. The strange thing is that normal data from that server is backed up perfect.
Could this have anything to do with Microsoft updates or any other issue?

[Ken_Putnam]

From the Backup Selections screen, right click the Exchange icons and give it the admin id from the remote domain in the form

domain\user-id.

You must be a member of the domain that Exchange is installed into to access that Exchange System

[Dave_Bunye]

As Ken notes, you needto use an account which belongs to the domain the exchange server is in. A backup job can use multiple logon accounts to accomplish this (and I do it every day myself) The logon account you use to connect to each domain needs to have rights to a mailbox on that server. Having a user name which is similar with the same password doesn't work. It needs rights.

[anoop_nair_2]

Hi,

Kindly update us on the issue.

[Bas_Harnas]

I think the problem is solved. In the first domain there was a userid administrator (which was renamed to admin). In the new domains there were two userid's. So by doing the same as in the first domain the problem seems solved. There were indeed as everyone said too few rights for the NOT RENAMED user and they were not sufficient.

Thanks very much!