ADSM-L

Re: ADSM client under DEC/OSF1 ??

1994-10-31 21:26:13
Subject: Re: ADSM client under DEC/OSF1 ??
From: "Keith A. Crabb" <KEITH AT UHUPVM1.UH DOT EDU>
Date: Mon, 31 Oct 1994 20:26:13 CST
On Fri, 28 Oct 1994 09:56:31 PDT MJ Lopatin said:
>The DEC/OSF1 client is on our list of potential future clients,
>because we have heard of the need for it, especially in Europe.
>However, there is no timetable for when we could deliver a
>DEC/OSF1 client at this time.
>You may want to investigate the DEC Migrate package, sold by DEC.
>It converts a DEC Ultrix image file to an OSF image file.  We don't
>have DEC Migrate here yet, and can make no claims about it.  However,
>an ADSM customer told us he converted our DEC Ultrix client using
>DEC Migrate, and the client worked fine for him on OSF1,
>with only one problem: the native OSF file system showed up as
>UNKNOWN in the GUI menu, but it still was backed up and restored
>properly by ADSM. Again, we can't verify what this customer
>says yet, but it might be worth a try if you are really desperate.
>If you do end up trying DEC Migrate, could you please post the
>results here? Thanks.
>MJ Lopatin
>ADSM Client Development

I'm working with the Ultrix V1R2M3-IP20200 client.

Well, I'm glad someone has it working, it isn't being that nice to me.
I'm at OSF/1 2.0, DEC Migrate 1.2-3 on a 3000-600 and having a consistent
set of problems.  My filesystems are UFS and show up as such in the GUI,
perhaps he's running with AdvFS? (DEC's Advanced File System).  /proc
shows up as being UNKNOWN but isn't highlighted for backup so that's
good.  We have a DEC 2100 AXP with AdvFS but, being unsuccessful with
my workstation I haven't tried anything with it.  DEC Migrate seems to
do a good conversion of the files, no errors are generated when the
conversion runs.  This is pretty standard for Migrate, I used it for
several things for the first couple of weeks after I received my Alpha
until I had enough time to port all the applications I use from Ultrix
to OSF.  The migrated ADSM Ultrix client seems to work fine at first.
I backed up a small partition, tried restores, archive, retrieve, the
utilities, etc. and all seemed to be fine.

The problem occured when I went to backup the entire system.
With all 3 partitions (/, /usr, /macross) selected, I ran an incremental
backup.  The backup died after ~11,800 files, a box popped up stating
process killed and that's all that shows in the dsmerror.log file
as well.  Choosing the smaller partitions (/, /macross) seems to work
fine and they back up without complaints (~3100 and ~3600 files
respectively).  Choosing just /usr and doing an incremental and it
makes it to ~14,500 files and dies with the same error, process killed.
The backups die at the same place +/-~2 files each time.  I've tried
various options with Migrate and had no success.  One of the two dsm
processes just ups and dies.  The one option that comes to mind is
to split up /usr into a variety of VIRTUALMOUNTPOINTs or just exclude
a bunch of /usr since most of it's system files anyway.  But geez that's
kludgy, I might do it for my workstation or others here in my department
but, that's not an agreeable answer for other OSF/1 systems around
campus.

I'd be very interested in the configuration of the other OSF/1 persons
machine or any better ideas on a workaround solution for the problem.
Of course an actual OSF/1 client would be real nice too :).

---
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
<Prev in Thread] Current Thread [Next in Thread>