Forum Discussion

Mat_OPC's avatar
Mat_OPC
Level 3
14 years ago

Ajout d'un agent pour Exchange 2010

J'ai procédé à l'ajout d'un agent Backup Exec 2012 sur un serveur Exchange 2010. L'agent ne me propose pas l'Information Store d'exchange ainsi que les boîtes courriels. Il se contente de m'afficher les répertoires de fichiers comme si c'était un serveur sans composante exchange.

Peut-être ai-je fait une erreur et si oui quelle est la marche à suivre pour l'ajout d'un agent sur serveur Exchange afin de profiter des paramètres propres à un agent Exchange server 2010?

Merci à l'avance. :o)

9 Replies

  • Is the Exchange license entered in the media server ?

    Ensure the correct remote agent ( correct by version & bit )is installed on the exchange server & the service is running under local system account...

    And, confirm if you meet the requirements per http://www.symantec.com/docs/HOWTO73784

  • On the backup Exec server I can see under "License informations"  Agent for Microsoft Exchange Server and yes for "Under license" and "Installed".

    Backup Exec remote Agent version on Exchange 2010 svr is 14.0.1798 is running under local system account.

    Media Server has access to Exchange Svr, uses a domain & local administrator account (the same for every job).

    I'll read the requirements and post later this week.

     

     

     

  • Do check if the Organization Management role is granted to the BE service account or not

  • As i saw in the requirement, I installed Exchange Management Tools on BE server. Now I can connect and manage Exchange Sp1 by it. I checked that BE service account is named under the Organization Management role. I uninstalled the windows agent et pushed it again.

    I didn't mention some details in earlier posts:

    We have a clustered Exchange Server environnement (2 exchanges svr).

  • Is the remote agent installed on both nodes ? If yes, are the services running under the local system account...

    Check if there is any grp policy applied on either node with a deny access/logon...

    And try enabling anonymous support on each node and the BE server - http://www.symantec.com/docs/TECH15416

  • Ensure AOFO is not checked in the backup job properties...

    from the command prompt, type: vssadmin list writers

    check if the VSS writers are stable or not..

    And in many cases, if the Exchange license is not present, this occurs as well.

  • I've unchecked any checkbox in the AOFO on the DAG job.

    The BE service account doesn't have right to run vssadmin on exchange svr but admin account does. We saw that "Microsoft Exchange Writer" state is '[1]stable' with no error.

    Sounds like a license issue ? I have a license for 1 exchange agent.

  • The BE service account should have enough rights to run this command...and this command should list all the writers not just the exchange one...check the status of all writers

    EDIT...also, do try removing the Exchange license key from the BE server...add it again & do complete the license install wizard till the end...create a new backup & test