Quick items :

1)         Absolutely a great idea. =)

2)         Make it non-routable - don't want anyone else's traffic interfering with yours.

3)         Make it mandatory that all new deploys get a drop onto the dedicated backup network (way way easier than doing it later)

4)         Get your network folks to reserve some extras for future growth. Have them actually tell you what they are. =)

5)         Document the required routing for the backup subnets (current and future) and add it to your client installation docs. If you can push #3 past your deploy folks, get the routing statements added at that point so you don't have to worry about it.

6)         For clients with the backup subnet drops, only reference them in NB according to their backup subnet hostname (i.e. myserver-bak). On the client side, only reference the Master/Medias by their backup subnet hostnames. Keeps everything nice and clean and really cuts down on traffic trying to go in one interface and out another. =)

- John Nardello

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

**********************

** LEGAL DISCLAIMER **

**********************

This E-mail message and any attachments may contain 

legally privileged, confidential or proprietary 

information. If you are not the intended recipient(s),

or the employee or agent responsible for delivery of 

this message to the intended recipient(s), you are 

hereby notified that any dissemination, distribution 

or copying of this E-mail message is strictly 

prohibited. If you have received this message in 

error, please immediately notify the sender and 

delete this E-mail message from your computer.