Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 2857

Exchange 2010 DAG Backup Issue

$
0
0
Oui, j'ai besoin d'une solution

Hi Firends,

 

I have some issue with Exchange 2010 DAG database backup, not sure what could be the reason. to brief about my setup, below are the details

 

exch1.abc.net (DAG node1) 

exch2.abc.net (DAG node2)

exch3.abc.net (HUB/CAS node1)

exch4.abc.net (HUB/CAS node2)

exch-DAG (dag virtual name)

exchange-mail (exchange front-end virtual name)

 

I have NBU 7.5.0.6 client installed on all physical servers and services are running on domain admin account (service account) with required all previleges. 

In NBU Admin Console -> host properties -> Clients  I have modfied hte account to use (service account) and other paramters in checkbox and the exchange-mail in proxy host settings

In NBU Admin Console -> Host Porperties -> Distributed Application Restore Mapping the below are the entries added

Application Host       Component Host 

exch-DAG                  exch1.abc.net

exch-DAG                  exch2.abc.net

exchange-mail            exch3.abc.net

exchange-mail            exch4.abc.net

 

We have the GRT enabled backup for Exchange 2010 DAG databases. 

ISSUE : We have the successful backup once we restart the services. when we try to restart the backup the Exchange GRT backup wil fail with the STATUS CODE (2)  with following message "none of the requested files were backed up(2)"

After the job fail, I have tried to browse the database from selection list within backup job polices and found that I could not able to browse. Again once I restart the netbackup services on database server and HUB/CAS server, then once backup will go fine and agian have the same issue of failure of jobs with the status code 2. Appreciate your help on this.

 

Thanks 

 

Rane 

 

 

 

 

 

 

 


Viewing all articles
Browse latest Browse all 2857

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>