Buddy,

NetBackup does not use Netbios. It uses tcp/ip. You can add the entries that
you need into the /etc/hosts table of the b system and should resolve fine.
If the information is already in DNS then you should be ok as well. You can
do an Alternate Client restore of an exchange database without having to go
in and change DNS info. I am not sure which version you are running but the
VERITAS NetBackup Admin Guide for MS Exchange should have details on how to
do an Alternate Client restore that would fit your requirements.

Skip

-----Original Message-----
From: Buddy Lumpkin [mailto:BLumpkin AT echarge DOT com]
Sent: Friday, September 29, 2000 1:08 PM
To: 'Veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Exchange Restore


Hello All,

I would like to backup our exchange server (A) and restore to another NT
server (B) that is freshly built to test the backup and restore process. Is
it sufficient enough to rename B to A and change DNS and hosts file entries
on the backup server so that A resolves to the system that is being restored
(B)? Does Netbackup try to resolve names with Netbios? Do we need to put
server B on an isolated network with the backup server to restore?

I thought was that Netbackup would only use standard name resolution and
that it would be fine to restore on the same network as the production
Exchange server ( turning off the netbackup service on the production
Exchange Server just in case..). But we have some people here that feel the
Netbios traffic ( Browse Masters, etc..) will screw things up. Server B has
no WINS entry.

Thoughts?

Thanks in Advance.

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