John,

Sounds like you might not have defined a tape coordinator/portoffset
pair for this port number. Check the output of the AFS command
'backup listhosts'. This should show you something like:

        Tape hosts:
            Host foo, port offset NN
            Host bar, port offset NN

To define additional pairs, use:

backup addhost -tapehost <tape machine name> [-portoffset<TC port offset>]

You have to define unique port offsets for each instance of buta
you plan to use, otherwise, only the first occurrence defined to
the AFS backup database will be used. This procedure is discussed in the
'AFS/DFS Backup Clients' ADSM manual, as well as in the 'AFS System
Administrator's Guide'.

--Ruth
On Nov 3,  3:21pm, "J. O'Neall" wrote:
On Nov 3,  3:21pm, "J. O'Neall" wrote:
}
} I must have misunderstood something.
}
} I'm starting to test the use of buta in our ADSM/AFS environment.  I started
} up one copy of buta (port 0) and then a dump to it.  So far so good.
}
} Then I start another copy of buta, with the same options except port 2.  The
} ADSM server sees both sessions.  But  when I do a dump specifying port 2
}
}    backup dump volset dumplevel -porto 2
}
} it prepares the dump, lists the volumes ... and bombs out with a message
}
} backup: no such host/port entry ; Can't connect to tape coordinator at port
} 2
}
} Can someone explain what I'm doing wrong.  It seems that you need as many
} buta instances as you want to run simultaneous dumps, right?
}
} Thanks in advance.  John
}
} John O'Neall
} Centre de Calcul de l'IN2P3
}