Hi Melite,
Yes it is...
With regards to the agent, I'd start with deploying the agent remotely from your BEWS server. If the correct agent is installed, it will actually state that, and you won't be able to proceed with the installation as it will exit.
On your selection list, find the second server in question, right-click it, and choose
Install Remote Agent/Advanced Open File Option.
In fact, I'd suggest you do this everytime you update your backup server with patches or with service packs. They inevitably have patches for Remote Agents and licensed agents like SQL/Exchange etc.
With Backup Exec, you can do a redirect of your files. On your restore job, you will find a tab called
File Redirection. As long as the server you want to restore too has the RAWS agent (Remote Agent for Windows Server) installed and communicating, you can restore to it. You would be insterested in using the
Restore to path option which will redurect to that server.
For Exchange, I'd suggest rather staging that to disk first. It cuts out a lot of additional work that needs to be done to start a restore again if it fails. I wrote an article about this a couple of months ago, and you can use the first part which details duplication to disk. From there, it's the normal disaster recovery procedures for Exchange as per Microsoft.
| https://www-secure.symantec.com/connect/articles/restoring-exchange-or-individual-mailboxesitems-using-backup-exec-howto |
It's fine that you have the full version of Exchange on your second server, but it's a full license. If you cannot afoord that license for now, I'd go with the RAWS agent installed on that server until you need to load up a working version of BEWS. The RAWS agent is a lot cheaper, and if server 1 dies, you are able to use the licenses you have on server 2 to get it operational.
Hope this helps?
