I had the same problem. I wanted to install the client on an additional 4
servers which happened to be database servers so they could not be rebooted.
Veritas said if you weren't planning on installing and using OTM you may not
have to reboot. If you were installing the open file manager, then a reboot
was required. I still have not got the client installed on those servers for
that reason so I would also be interested in a solution if there is one.

Don O'Shea
Sr. Operations Analyst
BCE Emergis
Financial Services Division
Phone: (905) 707-4000 Ext. 3765
Fax: (905) 707-4329
mailto:don.oshea AT emergis DOT com


-----Original Message-----
From: Scott Garrett [mailto:sgarrett AT technomancer DOT com]
Sent: Wednesday, April 05, 2000 12:56 PM
To: Veritas Netbackup Users Group
Subject: [Veritas-bu] NT client vs. system dlls


Has anyone found a way to install the netbackup client (3.2 + current jumbo
patch) without having to reboot?  They are putting mfc42.dll, Msvcp50.dll,
Msvcp60.dll and msvcrt.dll into the system dir, which makes it want to
reboot.  In my environment, every server belongs to a different customer,
which means scheduling downtime for each customer, and coming in at sucky
hours to do this install.  Does anyone know of a way around this so I can
set up NT machines in a sane way?  (I know, it's an oxymoron).  I tried
convincing people to use Solaris or Linux, but for some strange reason,
customers WANT NT as their servers.

-- 
        Scott Garrett     mailto:sgarrett AT technomancer DOT com
                                          http://www.technomancer.com

  *** Unix *is* user friendly.  It's just picky about who its friends are.



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu