Last Friday, Matthias wrote...
> We are waiting for an ADSM client for VMS and DEC OSF/1.
> In the meantime we are helping ourselves.
> We took an ULTRIX client, converted with DECmigrate to OSF/1 AXP and run.
> There is one major problem with it:
> After some 15700 files dsm hangs or stops, regardless of number or type
> of files.
Matthias,
We have both the DEC OSF/1 and VMS clients on our list of
known requirements from customers. We are actively looking into
both clients now. Customer input and our own business needs will
determine if we can provide either one as a new ADSM client,
so thanks for letting us know of your interest.
Here's something that may help you on DEC OSF/1:
Keith Crabb of Houston tried DECmigrate with our ADSM DEC Ultrix
client, and had your same problem, until he upgraded to OSF/1 3.0,
Patchlevel 1, with AdvFS. The problem went away, and his OSF/1 client
now seems to work with ADSM. I've reposted his note below.
We can't make any guarantees about DECmigrate and our Ultrix client,
but if you need to get something working now on OSF/1, you may want
to give it a try on an OSF/1 3.0 machine.
- MJ Lopatin
ADSM Client Development
========================================================================
Received: from VM.MARIST.EDU by vnet.IBM.COM (IBM VM SMTP V2R2) with TCP;
Thu, 08 Dec 94 03:02:01 EST
Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R2)
with BSMTP id 3489; Thu, 08 Dec 94 02:18:40 EST
Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
(LMail V1.2a/1.8a) with BSMTP id 3410; Thu, 8 Dec 1994 02:18:39 -0500
Date: Thu, 08 Dec 94 00:47:57 CST
From: "Keith A. Crabb" <KEITH AT UHUPVM1.UH DOT EDU>
Subject: DEC OSF/1 and Ultrix client.
To: ADSM-L List <ADSM-L AT VM.MARIST DOT EDU>
I reported that I had a problem with a migrated Ultrix ADSM v1r2l0.3
client on my OSF/1 2.0 system with UFS, or more specifically that it
died after about 14K files with a memory fault. I've been running
the same migrated client successfully on an OSF/1 3.0 patchlevel 1
with AdvFS filesystems for _all_ partitions using a DEC 2100-A500MP.
The filesystems all show up as UNKNOWN, of course, but it doesn't
seem to have any effect on the clients ability to backup or restore
files. I haven't really tested archive/retrieve well as we don't
really use it here yet. The executing images tend to get a bit larger
than they do under Ultrix while running and I'm pretty sure there is a
memory leak at work somewhere but, it's not significant enough that I
won't use it. (This may also account for the failure I see under
OSF/1 2.0 with the memory fault but, OSF/1 3.0 is a bit more robust
and is probably just not dying under the same problem)
The machine being tested only has about 40K files on it right now
as we haven't released it to users yet. It's been running nightly
incrementals for the last couple of weeks without problems. The only
actual bug I've come across is that when doing a line-mode restore
of a file you must use actual quotation (") marks to delimit the
file as though you were using wildcards, even when restoring a
specific file. I haven't had the time to do the v1r2l0.4 client
and doubt I will in the near future since I want to upgrade my
own workstation to OSF/1 3.0 sometime.....Personally I'm not allowing
anyone outside me to run the migrated code, we may/may not run it
once the machine is brought into production. We have some reservations
about running migrated code period, just especially where user data is
concerned though. Hopefully the information may help someone else
in a tight spot who is willing to be a bit more daring though.
---
Keith A. Crabb Keith AT UH DOT EDU
Keith A. Crabb Keith AT UH DOT EDU
University of Houston Operating Systems Specialist +1-713-743-1530
|
