name resolution requirements of netbackup - Veritas Net Backup

This is a discussion on name resolution requirements of netbackup - Veritas Net Backup ; Can anybody confirm the name resolution methods (DNS, WINS) supported by
NetBackup datacenter with respect to remote backup / restore processes.
This question arises in the design of build of Windows 2000 forest root
domain controllers that need to be ...

name resolution requirements of netbackup

This question arises in the design of build of Windows 2000 forest root
domain controllers that need to be backed up remotely.

It is preferable that these hosts are resolvable only by DNS and not WINS
(given the legacy nature of the protocol).

This of course is only a valid design if the NetBackup software is able to
resolve remote host names by DNS.

Thanks.

Graham Turner

Re: name resolution requirements of netbackup

NBU uses DNS

"Graham Turner" wrote:
>Can anybody confirm the name resolution methods (DNS, WINS) supported by
>NetBackup datacenter with respect to remote backup / restore processes.
>
>This question arises in the design of build of Windows 2000 forest root
>domain controllers that need to be backed up remotely.
>
>It is preferable that these hosts are resolvable only by DNS and not WINS
>(given the legacy nature of the protocol).
>
>This of course is only a valid design if the NetBackup software is able
to
>resolve remote host names by DNS.
>
>Thanks.
>
>Graham Turner
>
>
>

"Graham Turner" escreveu na mensagem
news:3e2e90da@hronntp01....
> Can anybody confirm the name resolution methods (DNS, WINS) supported by
> NetBackup datacenter with respect to remote backup / restore processes.
>
> This question arises in the design of build of Windows 2000 forest root
> domain controllers that need to be backed up remotely.
>
> It is preferable that these hosts are resolvable only by DNS and not WINS
> (given the legacy nature of the protocol).
>
> This of course is only a valid design if the NetBackup software is able to
> resolve remote host names by DNS.
>
> Thanks.
>
> Graham Turner
>
>
>