Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to restore Exchange Client Access Server using Netbackup 7.1.0.4

Created: 28 Sep 2012 | 17 comments

hi can you please guide me on how to successfully restore our Exchange Client Access Server into a different server. step please.

Discussion Filed Under:

Comments 17 CommentsJump to latest comment

captain jack sparrow's picture

Though it's not NBU questions..

Still Below would help you alot in rebuilding CAS (Presuming Disaster on Primary CAS Server and you are trying to build it on another server)

http://technet.microsoft.com/en-us/library/dd87688...

http://technet.microsoft.com/en-us/library/ff62937...

http://technet.microsoft.com/en-us/library/bb12435...

http://exchangeserverpro.com/exchange-server-2010-...

http://www.msexchange.org/tutorials/Recovering-Exc...

 

it isn’t necessary to back up your client access server (CAS). This makes sense because all of a client access server’s configuration information is stored in Active Directory. That said, you should still know how to rebuild a failed server.

If your CAS fails due to an irreparable hardware problem; follow these steps to repair it:

  1. Reset the client access server’s computer account within the Active Directory Users and Computers console. Do not delete the account.
  2. Install Windows on the new server and then install the same OS version as the failed server.
  3. Rename the server to match the name the CAS used and join the server to your domain.
  4. Depending on the version of Exchange Server and service pack you were running, insert the corresponding installation media into the server and run the following command:

    Setup.com /M:RecoverServer

  5. After the command runs, Setup will install the Exchange binaries and use the information stored in Active Directory to rebuild your CAS.

Note: This technique can also be used to rebuild any other Exchange Server roles, except for the edge transport server.

These steps work well to rebuild a failed client access server; however, there is a major caveat. This method only works if the server is running a standard configuration, which is unlikely since many organizations personalize their Outlook Web Access interface.

Using these steps will rebuild the CAS to a functional state, but any OWA customizations will be lost. This happens because Setup copies the Exchange binaries from the installation media, not your customized files.

Rebuilding a CAS and recovering OWA customizations
You have two options for recovering OWA customizations after rebuilding your client access server:

  1. Perform a full server backup, then restore the entire server.
  2. Make a backup of your customizations, then rebuild your CAS using the five step outline above. After that, you can restore your OWA customizations from backup.

In my environment, I only back up OWA customizations. In the event of a failure, my infrastructure is configured such that Exchange Setup rebuilds the CAS and then I manually restore customizations.

Although configuration information stored in Active Directory may change slightly, binaries on the server itself probably won’t change unless you install a patch or perform additional customizations.

Considering the static nature of a CAS, it’s tempting to make a full server backup and then store your backup in a fireproof vault. The only problem is that a full backup will quickly become outdated.

Windows periodically resets the password associated with Active Directory accounts, which gives your backup a limited shelf life. Depending on the version of Windows your CAS is running, the backup may only be relevant for 60 days. This happens because the password breaks synchronization with the password stored in the backup.

You can also reset the computer account password to use your backup, but it’s easier to back up only customizations. That way, you don’t have to worry about your backup becoming outdated -- as long as you make a new backup with each additional customization.

Coutesy : SearchExchange

Hope this helps

 Cheers !!!

CJS

 

Peterpan's picture

Hi theres no way for NBU to backup and restore the CAS server the best suite for this is to follow the procedure above?

:-)

Peterpan's picture

i've tried to backup our exchange CAS Server with the condition below.

NBU

   1. Shadow Copy

   2. System State.

   3. All Local Drive.

then we restore it as my expectation the application will be running fined unfortunately the Exchange Application is not running and all services of Exchange application is not presented. how can i restore it gracefully.

 

 

:-)

captain jack sparrow's picture

Backup and Recovery of CAS is outlined below

http://exchangeserverpro.com/exchange-server-2010-client-access-server-backup-and-recovery

It also includes backup selection.. Give a best try in UAT ;-)

 

Hope this helps

 Cheers !!!

CJS

 

Peterpan's picture

@Captain Jack

would like to confirmed if the system State backup functionality of NBU are different to system backup of Windows Native Backup?

 

:-)

Peterpan's picture

@Captain Jack

to give you an overview on what i need to satisfy on the NBU?

there is one instance that we have to restore a windows native backup when one of our server have failed please see below steps.

Note: given there is an available OS

1.  restore the system state from the Windows Native backup then reboot.

2. restore all local drive then reboot.

as expectedly we have successfully restored the backup then after that all the application are running properly same as the point in time backup.

 

how can i do this system state restore using the NBU note that i am restoring system state on the VHD (Hyper-V)

 

hope anyone could help...

:-)

captain jack sparrow's picture

Firstly .

Do not perform Alternate client method for system state

Restoration on same client would be same as traditional NBU restore method using BAR gui

Simply deploy NBU client reboot in  directory restore mode

start BAR GUI and use  the same method to perform restore

 

Windows native backup is nothing but another sort of backup solution (BE,NBU,CommVAULT, NT etc.)

If you did backup using Native backup , then don't expect it  to be restorable by NBU (writing/reading format  method are differents)

Hope this helps

 

 Cheers !!!

CJS

 

Peterpan's picture

@captain jack

 

Im not restoring the native backup using NBU i only want to know how NBU do the system state backup/restore with NT Backup.

:-)

Peterpan's picture

@captain jack

 

Im not restoring the native backup using NBU i only want to know how NBU do the system state backup/restore the same with NT Backup.

:-)

captain jack sparrow's picture

Very simple method

just create MS-windows policy, add clients and under backup selection client on hand (directives)

select system state or shadow copy components

It would take care of it

 

 

 Cheers !!!

CJS

 

Peterpan's picture

Yes I did that already but unfortunately after restoring the services is not visible and the application is not running properly

:-)

captain jack sparrow's picture

which services are missing ?can post snaps along with tar logs of restore performed and also job details if possible

 

Your queries are still unclear to me. Are these just queries or you are actually facing this issues

 Cheers !!!

CJS

 

Peterpan's picture

all of the microsoft exchange services are not showed up after system state restore.

 

Yes I am currently facing this issue.

 

currently our backup method is using the system state backup of Windows 2008 and we are on the stage of implementing of NBU on our environment we tried to backup our exchange CAS Server using NBU then when we are tried to restore the system state backup ofcourse using NBU and it was successfully then i check all the services of exchange it didnt showed up. 

:-)

Peterpan's picture

To give you a clear view on my objective i want to restore my exchange CAS server using NBU as expected after restoring the application the application is up and running from the point in time backup like we did on the restoring windows systems state using native backup from windows 2008. 

:-)