Backup a 2nd Exchange Srvr in the same site?

[Dan]

I'm running Exch and Windows 2003. Last week I installed a new Exch server into the same site. I've installed the remote agent on it. However I am unable to see mailboxes on that server. I have moved my mailbox to it.

Firstly, where should I see the mailbox? Should it be under the new server? All I have under the new server in the selection tree is the normal C:, D: etc. nothing else.

I've heard about having one BackupExec Mailbox per server, but I can't find any more info about it.

Kind regards,
Dan

[SANDEEP_PILLAY]

Hi,

A uniquely named mailbox for the Backup Exec service account must exist on the Exchange server. A unique name is a name that is not already in use by the organization, that also is not contained as a portion of another mailbox name (i.e. "mailbox" would not suffice as a unique name if there were also names like "mailbox01," "mailbox02," etc. on the same system.) The mailbox must not be hidden.


In order to isolate the issue, please refer to the following technotes:

- Preliminary Troubleshooting List for Exchange and mailbox backups

http://seer.support.veritas.com/docs/242606.htm

- How to protect Exchange 2000 and 2003 servers using the Backup Exec for Windows Servers Exchange Agent

http://seer.support.veritas.com/docs/266074.htm

- How to configure the Backup Exec service account to have sufficient rights to connect to an Exchange 2000 server

http://seer.support.veritas.com/docs/234575.htm

We hope this will help.

[Dan]

I've been through those articles but am still no better off.

Basically I can see one exchange server (It's also the Backup exec server) And the mailbox for BackupExec is unique.

If I expand the remote server I do not see anything to do with Exchange. But I do see the C: D: etc.

All the BE services are running under an acct that has the correct permissions on the Exchange Org.

Any more suggestions?

[Vidyaj__Patneka]

Hi,


Kindly follow the steps given below,

1. Create a new user account (for eg vrtsbkup) and its mailbox.


2. Assign Admin and Domain Admin rights(Backup Operator rights not required)


3. Assign the exchange full Admin rights from Exchange System Manager


4. Assign it local Admin rights on Exchange Server


5. Send email to this account and check if the email is received


6. Go to network>logon accounts, create a logon account for the new account (vrtsbkup )


7. Right click on mailboxes and select connect as and type in the user name vrtsbkup and its password


8. Also ensure that the BackupExec Services account has the following rights.
i) Act as part of the Operating System

ii) Backup Files and Directories

iii)Create a Token Object

iv) Manage Auditing and Security Log

v) Restore Files and Directories


=====================================
Backup Exec will treat a mailboxname not as unique if it is a character-subset of another mailboxname, so for example "Admin" will not be a unique mailboxname for BE if a mailbox named "Administrator" exists.

Please refer to the following technote for additional information on this:





http://seer.support.veritas.com/docs/262707.htm


Hope this helps.

[Dan]

Hi,

Steps 1-6 I have done. But step 7? What "Mailboxes" do i click on, as the only mailboxes I see are the ones on the local exchange server and not the ones on the remote exchange server?

I can backup the local exchange server fine, but I don't see any Information Store icon, mailboxes icon etc for the remote Exchange server.

Dan

[Dan]

Still no better, tried changing the RestrictAnonymous key too as per another article. Anyone have more suggestions?

[Dave_Bunye]

Have you confirmed that the Exchange services on the second server are running? Sounds like they are not running, which would explain not being able to see any information store items.

If the services are running, also make sure all the stores are mounted.

[Ken_Putnam]

if you have Exchange Admin installed on the Media server, if you login as the BEWS Service Account, can you see and access the second server throught it?

[Ameet_Thakkar]

Kindly refer the steps mentioned in the following technote inoder to solve the problem.


Title:- Cannot see Information Store in Exchange 5.5 or Exchange 2000 even though Enable Exchange Support is enabled in VERITAS Backup Exec (tm)

http://seer.support.veritas.com/docs/248233.htm

Also,

Issues of this kind could can occur because of proper rights and permissions to Exchange or it could be related to License.



Please refer to the following technote inorder to troubleshoot the problem with IS not being visible on the Backup Selection list.


1) Title:- The Microsoft Exchange Directory and Information Store are not visible in the Backup Selection tab. Or, if the selections are visible and selectable, the backup of the Exchange Directory and Information Store fails and returns an Unable to attach error.


http://seer.support.veritas.com/docs/237347.htm

2) Title:- The Information Store is not visible in the backup selection list.

http://seer.support.veritas.com/docs/270151.htm


We hope this helps. Let us know if the problem still exists and revert back with the error message.

[Dan]

Well eventually I've got it sorted. Thanks to everyone for the help and I've learnt a lot. At the end of the day I removed the remote agents, reinstalled it after a reboot and it all pops up fine.

[Dave_Garber]

Did you do anything beyond reinstalling the agent? I uninstalled the remote agent, reinstalled and still can't see anything Exchange related. I even uninstalled the licence and reinstalled it, but no good.

It works fine for the Exchange 2000 server I have here, but not the Exchange 2003 server running on Windows 20003 server.

[Dave_Bunye]

Look under Shadow Copy Components.

[Dan]

Hi,

Is it on a Cluster by any chance?

[Dave_Garber]

Yes, this is a cluster.

[Dan]

Remember to select the Exchange Virtual server and not the Cluster network name. You won't see any Exchange stuff under the Cluster Network name or any of the nodes.

[Dave_Garber]

Thanks Dan. I believe this is related to my problem. I verified your comments on my first Exchange cluster - the only name that shows information store selections is the Exchange Virtual. Problem is, when I built the new cluster, I used the cluster name as the Exchange virtual name. I'm going to attempt to create another virtual name and IP, bring the cluster down and associate the Exchange services with the new name (essentially renaming the cluster to the new name). Hopefully, that'll do the trick?

[Dan]

To be honest, I didn't know your exchange virtual server could have the same name as the cluster network name. Mind you, I've never tried it. I hope that's the problem though, good luck, let me know how you get on.

Dan