Hi everyone,
your are completely right: It takes a couple of days
to restore a big file server with ADSM V2 client.
IBM suggests to set skiplanserveracp to yes in dsm.opt,
if you have to use V3 client.
But in this case you will loose all your ACL user data in
case of a restore
Of course you can use BACKACC/RESTACC commands
to backup/restore ACLs to/from a file.
But this commands have no performance on big file
servers.
The fixtest for HPFS386 seems to work, but I dont place
it into production until it is officially fixed.
please direct your questions to the developer that is
responsible for the HPFS386 Apar IC20624
and to his chief:
Dale Mark Mock
ADSM Client Development
5600 Cottle Road
DQT/051-2, office 2B62
San Jose, Ca. 95193
Internet -- DMOCK @ US.IBM.COM , Phone -- outside 408-256-8908 , tie
line 8-276-8908
His chief is
Kevin Brooks
kevinbr AT us.ibm DOT com
Regards
___________________________________________________
Michael Hartmann
IT Development
Bankhaus Trinkaus & Burkhardt
Koenigsallee 21/23 40212 Duesseldorf Germany
Phone: ++49+211 910 2364
E-Mail: michael_hartmann AT trinkaus DOT de
___________________________________________________
Hi everyone,
I want to react to this mail because of the following :
We have OS/2 servers with ADSM client V2 and ADSM server V2.
When we have a crash of a server, we have serious problems and need several
days to restore the machine.
ADSM is an IBM product, OS/2 is also an IBM product.
But there is no effort to update the ADSM software for OS/2 and there is
even
no info about the future of
ADSM on OS/2.
People from IBM also read this subscriberlist ( maybe off the record).
My question : when will we have some info about the future and expectations
of
ADSM on OS/2 ???????
Herwig Evenepoel
KBC Belgium
Michael_Hartmann AT TRINKAUS DOT DE on 08/09/98 12:19:00
To: ADSM-L AT VM.MARIST DOT EDU@Internet
cc: (bcc: Herwig Evenepoel/U29346/KB/KredAlm)
Subject: Re: Problems with OS/2 Warp
Shane,
like you we are still running V2 OS/2 clients on our LanServers,
but this is *very* dangerous. The backup performance is OK,
but please examine the restore performance of a whole
filespace containing 150.000 -200.000 files. Our V3.1.0,3 MVS-Server
(running at performance group 1 at this time !) needed 7(!) hours
just to transfer a file list of 120.000 files to the client.
Remember: just for a file list, no restore operation of
even a single file!.
A version 3 client does not transfer a file list to the client before
beginning with the real restore of the files. This feature of V3 is
called "no query restore". V3 clients will begin to restore the files
immediatly. The server orders the file list for the client!
So if your machine is a file server with so many files, believe
me, V2 is *no* recommendation at all. In case of a disaster
you will get in serious trouble!
In my opinion it is better to convert your servers to NT than
waiting for the official HPFS386 fix (I think not available in this
millenium)
___________________________________________________
Michael Hartmann
IT Development
Bankhaus Trinkaus & Burkhardt
Koenigsallee 21/23 40212 Duesseldorf Germany
Phone: ++49+211 910 2364
E-Mail: michael_hartmann AT trinkaus DOT de
___________________________________________________
Hi,
Thanks to all of you who supplied info on how to get the V3 ADSM client to
operate successfully on my OS/2 Warp V3 client PC. Yes, the client PC is
running HPFS386 and is a server.
I tried the patch, but I got the same error. I tried the dsm.opt also, but
to no avail - still the same.
So, I went back to good old V2.1 on the client (V3 on the ADSM server), and
it goes like a rocket.
We have another Warp machine and it also had the same error. We tried the
same patches etc but it did not work. I put it back to V2.1 and it's fine
now.
As such, I have recommended to our technical staff to use V2.1 on all OS/2
clients, and V3.x on NT. This will get us out of trouble until we convert
the last of our OS/2 machines to NT.
Regards
Shane
______________________________________________________________________
Der Austausch von Nachrichten mit Trinkaus & Burkhardt via E-Mail dient
ausschliesslich Informationszwecken. Rechtsgeschaeftliche Erklaerungen
duerfen ueber dieses Medium nicht ausgetauscht werden.
Correspondence with Trinkaus & Burkhardt via e-mail is only for information
purposes. This medium is not to be used for the exchange of legally-binding
communications.
|
