Exchange Agent Configuration

[Ourcup]

Hi, I am currently evaluating BackupExec9.0 with Exchange option.

I have performed a successful FULL backup of exchange but coming from ARCserve I am confused by the overall architecture of BE.

The Exchange Agent has been installed on the 'media server' aka backup server - the remote agent has been installed on the exchange svr. Rather worryingly however the job summary log stated, "agent used - no"

Now, if the agent was not installed correctly I would not expect to be able to select the Information store and drill down to the Heavy/Medium/Light mailboxes etc..and I would not expect to see the log summary detailing a full breakdown of the various exchange components.

That said, the BE Admin Guide is a little ambiguous and it is unclear to me whether the exchange agent should be installed separately on the exchange server or whether the exchange agent is installed automatically as part of the remote agent install.

Quote from the guide, "The VERITAS Backup Exec Agent for Microsoft Exchange Server is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up Exchange Server databases."

I have not seen anyway to install the exchange agent as an individual component (either locally or remotely) and can only conclude that it was indeed installed as part of the remote agent install (thanks to the licence for exchange on the backup server) - Is this correct?

I was also surprised that BackupExec does not appear to display the exchange svr directly below the backup server (only in the browse list)- comments?

Thanks,
Neil

 

[SQLBill]

The Exchange Agent and Remote Agent are two different options and require two different licenses.

That said...if you are using the evaluation version of Backup Exec, you should be able to install all of the options from the disk. (I was able to do this with ver 8.6, that's how I tested to see which options I really needed.)

-SQLBill

 

[bartibog]

I contacted veritas lastnight with the same issue....it's a bug in version 9...should be a fix for it soon!