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
Grant:
Clever backwards compatibility. =) I also like the sysconfig -m command. I found that last night and got the "mc0" from it.
In case you are interested, Ephraim is checking out our case #106622. I imagine it is the same problem as Tim is having.
When talking to all three filers direct attached to the jukebox, Budtool's rpc.jbmgr says:
Fri Mar 31 15:31:04 2000> ****************************************************************** Fri Mar 31 15:31:04 2000> ------ E R R O R ------- Fri Mar 31 15:31:04 2000> Connection to NDMP server timed out. Fri Mar 31 15:31:04 2000> ****************************************************************** Fri Mar 31 15:31:04 2000> ****************************************************************** Fri Mar 31 15:31:04 2000> ------ E R R O R ------- Fri Mar 31 15:31:04 2000> Failed to create a connection to server host griddle Fri Mar 31 15:31:04 2000> griddle: RPC: Program not registered Fri Mar 31 15:31:04 2000> ******************************************************************
The machine controlling the jukebox seems to be talking better and at least able to do a jbupdate and read barcodes into BudTool, but we can't run backups.
Also, looking on the media changer filer, Budtool appears to be making several (like 50 or 60) unsuccessful attempts to connect before actualling getting an NDMP session open.
Thanks for jumping in on this one Grant!
-- Jeff
From "Melvin, Grant" on Fri, 31 Mar 2000 15:28:28 PST:
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
-
Jeff Krueger -
Melvin, Grant