We asked Legato for a combination patch, and they did it, but took about 4
weeks to do it.  We had a problem with Exchange restores, and also the
problem with licenses not being read properly.  At first, they said that we
could have either one, but would have to live without the other one until
the next release.  When I pushed them, they said that they would ask if a
combination patch could be done.  As I said, it took a couple of weeks, but
it did finally arrive.  However, you must realize that you become your own
alpha tester, as you are the first one to get it! 

David M. Browning Jr.
LSUHSC Enterprise Network Operations/Help Desk
(504) 568-4364 - Direct
(504) 914-7550 - Cell

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
On
Behalf Of Tim Mooney
Sent: Thursday, June 23, 2005 11:53 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Conflicting patches (LGTpa69733 and LGTpa75831),
what to do?

In regard to: [Networker] Conflicting patches (LGTpa69733 and
LGTpa75831),...:

> However, this presents a few problems. I suppose that LGTpa75831 doesn't 
> include the fixes in LGTpa69773, and I have also seen nsrmmd crashes
myself 
> with that nsrmmd version, but on the other hand, netware restores don't
work 
> with the nsrmmd included in LGTpa69773. It doesn't feel good to replace
the 
> nsrmmd everytime I need to get a netware restore done, so is anyone aware
of a 
> better solution? A patch that fixes both issues perhaps?

My experience with patches of this type in the past indicates that
Legato's hot-fix patches tend to fix just the issue the customer is
having, and Legato rarely releases a patch that includes fixes for
multiple different issues.

It's possible that if you call support and indicate you need an nsrmmd
that fixes *both* issues, they'll eventually produce one.  When there are
multiple serious problems with a particular binary, it would make sense
that they would automatically roll the fixes into one patch, but for
whatever reason (SQA, I would imagine) that seems not to be their practice.

Unless you call and ask for an accumulated patch, my guess is that you
won't see a binary that fixes both issues until they release their next
maintenance update (7.1.4 or 7.2.1 or both).

Tim
-- 
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=