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
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
On Fri, 31 Mar 2000, Tim McDonough wrote:
Howdy All:
We were placed on the upgrade treadmill last week andupgraded our F740 cluster from v5.3.2D1 ( NDMP worked ) -- v5.3.4R3 -- v5.3.5P2 ( NDMP no worky )
Subsequently, our direct attached Budtool NDMP backupsstopped 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.
for what it's worth, 5.3.4R2 has always worked for us on many flavors of nacs (but we run no 740s), and so far both 5.3.5 and 5.3.5P2 have been stable.
good luck.
pablo
email paul.mikulencak@amd.com ext. 602-2448 "the word pessimism bothers me pager 624-0929 because it is often used instead cube 3.277.042 of the word lucidity."
robert bresson
-
Jeff Krueger -
Paul Mikulencak -
Tim McDonough