Video Screencast Help

Backup Exec 2010 R3 SP2 Exchange Dag Group Recovery

Created: 31 Oct 2012 • Updated: 06 Nov 2012 | 10 comments
This issue has been solved. See solution.

Hi, need a solution.

I have an Exchange 2010 Dag Group (dag.domain.lo 192.168.55.26) with 4 virtual servers:

mx1 (mx1.domain.lo 192.168.55.21), mx2 (mx2.domain.lo192.168.55.22) - Database storages with RAWS installed on it.;

cas1 (cas1.domain.lo 192.168.55.10), cas2 (cas2..domain.lo 192.168.55.11) - CAS Array with RAWS installed on it.

The backup job works fine, but I can't do a recovery. All recovery jobs are fail with error "The Media Server was unable to connect to remote machine cas.domain.lo on network interface Local Area Connection"

cas.domain.lo is a CNAME of cas1.domain.lo.

I think this happens because cas.domain.lo isn't published. I can't see cas.domain.lo in Remote Agent Utility on any server. How can I publish it?

sry for my eng.

 

Comments 10 CommentsJump to latest comment

VJware's picture

See if this applies - http://www.symantec.com/business/support/index?pag...

Try adding the load balancer name to the hosts file on the media server & see if this name resolves to the CAS's ip address...

And in the restore job, under network & security, do verify if appropriate options are used or not...

Do3e's picture

How can I check current RpcClientAccessServer value?

Hosts file contains all names. cas.domain.lo resolves as 192.168.55.10 (cas1)

There is no network & security option in restore job.

BTW, I have a separate Exchange 2010 server and I can do Exchange Redirection restore to the exchange's administrator account only. If I try to restore to users account, it says "Final error: 0xe0000383 - Failed to log on to Microsoft Windows." Looks like usual user dont have some permissions.

Jaydeep S's picture

Check if the account you are using to restore is a member of the Exchange Organization Management group on this Exchange Server that you are restoring to.

Jaydeep S's picture

Is there any nlb involved? Try removing the nlb for testing the restore.

Do3e's picture

 

It will work, I'm sure. I tested it on separate exchange server.

The problem is with CAS Array.

Jaydeep S's picture

So what is the configuration of the where the restore is failing. CAS Array and NLB? If Yes, try to add the host file entries of both in the hosts file of the Media Sever, restart Backup Exec Services and then attempt to restore.

Also, if there is a nlb involved, is it software or hardware?

Do3e's picture

We don't have hardware NLB. Just a DAG group with CAS Array. Hosts file contains all names, but it didnt work.

Backup_Exec's picture

Hi

 

Please check link below which is known issue in BE 2010 the permanat fix is in BE 2012 if you are using BE 2010 then you have to remove CAS from the NLB before doing restore and add it back to NLB once restore is done but in BE 2012 you can do restore directly

 

http://www.symantec.com/docs/TECH156173

Hope that helps

Thanks

 

 

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

SOLUTION