James,

I had the same setup and the same problem in NB5.x and Exchange 2000.  I 
suspect the agent was looking at the mail database and seeing the 
hostname of the server only.  The quick solution was putting the primary 
interface of the system on gigabit and living with the performance hit 
during the backup window, which was late at night.
I never found a method to implement backups of exchange, like you 
describe, by looking through this list or the Veritas site.  Possibly 
due to the method by which the exchange system was built, the policy I 
used to backup the filesystems used the FQDN, but the policy for the 
mailboxes and mail store used the short name. 

I think we left the backup network on the box for filesystems, because 
it wasn't a big deal to have a couple of extra gig ports consumed, and a 
few years later we were forced onto Notes.  Problem solved.

-Jon

> Hi All
>
> I'm backing up a customer's machine over a dedicated backup network with 
> our own naming convention, which doesn't always relate to the actual 
> name of the machine. This has been working OK for Filesystem and SQL 
> backups, but I am unable to get an exchange backup working in this way.
>
> Example
>   
> 10:26:43.171: [5140.964] <4> backup_create: INF - NetBackup Temp 
> Directory: 'D:\Program Files\Veritas\\NetBackup\Temp'
> 10:26:43.171: [5140.964] <2> tar_base::V_vTarMsgW: ERR - object not 
> found for file system backup: Microsoft Information Store:
>
> So it looks like I'm missing a bit of configuration on the Exchange 
> agent to tell it to use a certain name when talking to Exchange...
>
> Can anyone help?
>
> Thanks!
>
> James

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu