XXXForwarded message:
> From mmk Thu Oct 19 12:28:23 1995
> Date: Thu, 19 Oct 1995 12:28:22 -0400
> From: MAILER-DAEMON (Mail Delivery Subsystem)
> Subject: Returned mail: User unknown
> Posted-Date: Thu, 19 Oct 1995 12:28:22 -0400
> Received-Date: Thu, 19 Oct 1995 12:28:21 -0400
> Message-Id: <9510191628.AA51305 AT mercury.umis.upenn DOT edu>
> To: mmk
>
> --- The transcript of the session follows ---
> 550 set... User unknown: A file or directory in the path name does not exist.
> 550 adsm-l... User unknown: A file or directory in the path name does not
> exist.
> 550 repro... User unknown: A file or directory in the path name does not
> exist.
>
> --- The unsent message follows ---
> From: mmk (Mark M. Klivansky)
> Posted-Date: Thu, 19 Oct 1995 12:28:20 -0400 (EDT)
> Received-Date: Thu, 19 Oct 1995 12:28:21 -0400
> Message-Id: <9510191628.AA15207 AT mercury.umis.upenn DOT edu>
> Subject: ADSM bugs and support. (fwd)
> To: set, adsm-l, repro
> Date: Thu, 19 Oct 1995 12:28:20 -0400 (EDT)
> Reply-To: mmk AT isc.upenn DOT edu
> X-Mailer: ELM [version 2.4 PL23-upenn2.9]
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Length: 2449
>
> Forwarded message:
> >From mmk Thu Oct 19 10:50:16 1995
> Subject: ADSM bugs and support.
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: Thu, 19 Oct 1995 10:50:16 -0400 (EDT)
> Reply-To: mmk AT isc.upenn DOT edu
> X-Mailer: ELM [version 2.4 PL23-upenn2.9]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Length: 2099
>
> Hello,
>
>
> I would like to ask ADSM users if many are happy with a product or support.
>
> A few month ago we installed ADSM on our SP2 machine, but we can't call
> it backup solution yet.
>
> Very often we have tape drive problems, sometimes these errors not in errpt
> but on activity log as OP=WRITE or READ with sense=00.00.00.00.
> These errors terminate process, after 20 GB of data already processed.
>
> Many features which in ADSM books or README files don't work, and I am
> getting fallacious answer, for example, DSMSCHED.LOG pruning will happen
> only after scheduler will be restarted, even IBM suggested to include SCHLOGR
> (days),[s n] in DSM.SYS. So why bother with this parameters, if our goal
> to do backup with centralize scheduler and automate backup as much as
> possible.
>
> Sometimes ADSM create duplicate names in filespaces and refusing to
> backup filesystem from clients nodes because of it.
>
> When we made marketing research of backup product, many IBM representatives
> claimed that in 4q 1994 we will be able to backup ORACLE online, now nobody
> even mentioning if they continue working on this interface, just referring
> to third companies.
>
> I have eggs on my face for recommending implementing ADSM.
>
> My questions are how to correct these problems, to whom to call to get
> quick response and resolutions, often we are waiting week to talk with
> level 2 and other week to get results.
> How people backing up 150 GB of ORACLE data base, knowing it have reliable
> backup in case of restore.
>
> IBM people, welcome to reply.
>
> Thanks.
> Mark
>
>
>
>
> --------------------------
> | Mark M. Klivansky |
> |University of Pennsylvania|
> ------------| E-MAIL : |------------
> \ voice: | mmk AT isc.upenn DOT edu | FAX: /
> \ (215) | | (215) /
> /898-1466 -------------------------- 898-0386 \
> / | | \
> ------------------ ------------------
>
>
>
>
>
>
>
--------------------------
| Mark M. Klivansky |
|University of Pennsylvania|
------------| E-MAIL : |------------
\ voice: | mmk AT isc.upenn DOT edu | FAX: /
\ (215) | | (215) /
/898-1466 -------------------------- 898-0386 \
/ | | \
------------------ ------------------
|
