Pretty confused by all the "in comments" in the emails, so I will say remove
UNIX and bring on Windows :-)

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver at Astrium-eads.net



-----Original Message-----
From: David Rock [mailto:dave-bu at graniteweb.com] 
Sent: 17 July 2006 16:02
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Unix Master, Windows Media server possible?


* Ed Wilts <ewilts at ewilts.org> [2006-07-17 06:40]:
> On Mon, Jul 17, 2006 at 12:53:51PM +0200, Drunen van, Marcel wrote:
> > The whole concept of NetBackup ensures multiplatform operations, 
> > which is one of the main reasons why I suggest it to my major 
> > customers. In general my advise is to have the master server on a 
> > Windows system, as the GUI is much easier to use (and often faster).
> 
> I disagree.  Put the master server on a Unix system, and then use the 
> Windows GUI on a Windows media server or other server.  You'll get the 
> best of both worlds.

Or use the CLI ;-)

> > The majority of problems I encounter with multi-OS systems is the 
> > slightly different way UNIX and Windows work with name resolution 
> > when multiple LAN segments are involved. Make sure your Windows 
> > system only has one network name, don't try to bind a different name 
> > to each NIC, as you can easily do on UNIX systems.
> 
> Again, I disagree.  Whenever possible, you should use a dedicated 
> backup interface and you can refer to it by its own name - i.e. 
> server.prod.foo.com for the front side and server.back.foo.com for the 
> backup network.  Just make sure that NetBackup is configured properly 
> and you won't have any problems.  We've been doing this for years.
> 
> The only place we've been hurt by this is if you have a master/media 
> server and try to use 2 names for the system at the same time (one for 
> the master functionality and one for the media functionality).  This 
> worked fine in the 3.x, 4.x, and 5.x days, but broke with 6.0.

As long as your server support team knows what they are doing, dual-homing
the systems will work.  In our environment, the backup team has little
control over the client systems and must rely on the server admins to
properly handle name resolution and routing.  Screw that up, and it gets
ugly to troubleshoot in a hurry.  

A lot of the ideas suggested here do assume a certain amount of technical
expertise.  Don't ever forget about the "Net" part of NetBackup. :-)

-- 
David Rock
david at graniteweb.com _______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or 
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS 
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or 
obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England