We use HP-UX master for our 6.5.x install
and backup many Windows machines (along with HP-UX and Linux).
For backup VLAN we just have a separate
NIC in both master and clients. We modify hosts file on the master to add the
NIC of the clients. We typically specify the client names as clientb and use
that clientb name in the policy instead of client. On the clients we specify
the backup NIC of the master as the actual hostname of the master. This
works for most things.
MS-SQL backups require use of the actual
database names so that causes a few wrinkles for those backups but for
everything else it works swimmingly.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of BeDour, Wayne
Sent: Wednesday, June 03, 2009
2:10 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Dedicated
B/U vlan setup questions
Our environment, HP-UX 11-31 with a SureStore 20/700 tape
library, one master / media server running NetBackup 6.5.2 backing up mainly HP
servers with a few Sun and Windows boxes thrown in. One NBU 6.5.2 SSO
media server running on windows.
The majority of our backups are via direct connected bcv
filesystems and very few backups over the network. We are looking at
expanding our NetBackup environment to include more windows servers and need to
look into setting up a dedicated backup vlan. We looked at this back in
the NBU 3.1 days and ran into issues and dropped it. Time to look into it
again, any advice / things to look out for / white papers / pointers / or
anything else that anyone can share or point me to?
Thanks in advance…
Wayne BeDour
Unix System Administrator
PH: 313-593-9876
Internet: wbedour AT lear DOT com