We are backing up w2k machines in 2 seperate 3.4 environments (mostly) without 
issues.

On clinet install there is an option to install an OTM manager, which we do, 
which I can only assume fixes the problem you are experiencing.
The only downside is that the status code at completion is 1 rather then 0, 
which initially played hell with some of our reporting scripts.

We have also had 2 out of 4 machines require a registry change to (from memory) 
increase the buffer allowed for otm files. (the backups were erroring, but I 
can't remember the code) I found this fix on this mailinglist months ago, so if 
you want to try that, you would need to search thru the archives.

Hope that helps!

-suz

Once upon a time, Richard Hellier wrote :
> I'm trying to "bolt on" some Windows 2000 servers into an existing
> "all UNIX" NetBackup installation.  On running some test backups,
> I get lots of hangs whenever (I guess) the N/B client encounters
> an open / busy file.
> 
> So ... my question is "How do others in the same boat handle this
> situation?"
> 
> Thanks!
> 
> Richard.
Content-Description: Card for Richard Hellier



-- 
Suzi Archer                       Connect.com.au
Systems Group                     Lvl 9, 114 Albert Rd
sarcher AT connect.com DOT au            South Melbourne
(03) 9674 3815                    VIC,  3205