Hi Jeff,
	We've built in backwards compatibility, so that
	the jbmgr_config file can use "mco" or "spt0"
	even tough sysconfig -m only reports mc0.
	Hope this helps.
	Tim, I'd like to understand your issues with
	5.3.5P2. Can you send me the case # logged with
	either NetApp or Legato support (or both)?
	Otherwise, please send me the symptoms.
Cheers,
	Grant
-----Original Message-----
From: Jeff Krueger [mailto:jkrueger@qualcomm.com]
Sent: Friday, March 31, 2000 3:10 PM
To: Tim McDonough
Cc: Toaster
Subject: Re: Budtool v4.6.1 NDMP breaks with DOT 5.3.5P2 
Tim:
We're in the exact same situation.  The first problem is that our tape
library device name is now called "mc0" instead of "spt0".  This is
configured in the jbmgr_config file.
Let us know if you figure this one out.  We'll do the same if we figure
something out!  =)
-- Jeff
>From Tim McDonough on Fri, 31 Mar 2000 13:00:54 PST: 
>
>Howdy All:
>
>    We were placed on the upgrade treadmill last week and
>upgraded
>    our F740 cluster from v5.3.2D1 ( NDMP worked )  -- v5.3.4R3
>    -- v5.3.5P2 ( NDMP no worky )
>
>    Subsequently, our direct attached Budtool NDMP backups
>stopped
>    working and timed out with each request.
>
>    Anyone else seen this, solved this?
>
>    Legato and NetApp are scratching their heads when they're not
>
>    pointing their fingers at one another.
>
>        Tim
>
>
>