Brett, Thanks for the answers.
I don't want to downplay the hard work that goes into developing the TSM
products and we could go on discussing this forever trying to please
everyone.
Hopefully I can convince my company to abandoned desktop backup in 2000 and
I won't have these issues any more. It is still the only product I would use
for desktop backup though.
Overall I like ADSM on the NT server, AIX server and Netware server
environment and my list of changes is a real short list, ( like a full
backup option. Not a selective. Too many volumes, not enough time.)
I do think Tivoli should shuffle in a few more and new customers for their
input though.
Take care...
CR
-----Original Message-----
From: Brett Walker [SMTP:walkerbl AT US.IBM DOT COM]
Sent: Tuesday, November 09, 1999 2:43 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM V3.7.1 32bit client Critique..
Let me try and address these issues:
>* The progress clock issue still remains. Once the restore
has been
>committed the clock should remain counting regardless of whether or
not
any
>data is currently being transferred. Give the user some indication
that
the
>session is still running . There should be more progress indicator
messages
>during a restore for example:
>* Requesting Data..
>* Requesting Tape Media..
>* Mounting Tape Media.
>* Searching Tape Media..
>* Transferring Data..
Yes, the clock should keep running. As we become more and more
threaded,
we will be able to fix this problem. In terms of status, we put up
as much
as we can. The server doesn't tell us every little thing its doing,
like
scanning the tape, and I'm not sure how much of the intricacies of
tape
handling should really be exposed to the end user. I agree that the
status
verbage needs to be improved.
>* During the restore there are two status windows now. The
default
>window showing a progress indicator stating "Preparing" and amount
of data
>moved. The second window, and more important window has lost some
important
>information and is not launched by default. This wind will only
appear if
>invoked manually or at the completion of the restore. Ok, a bit
lame. And
>while I'm at it why don't the windows scale to the main window
automatically
>and to the standard default. Hmmmm? A Programming 101 may be in
order.
There are 2 reasons why the windows come up in the order they do.
First
and foremost, it is to be consistent with Backup. Status reporting
and
window handling should be the same between functions when at all
possible.
The paradigm is now if you need the extra details, you can display
them at
any time. Otherwise they stay hidden, don't take up screen real
estate,
and don't require as much processing for updating the display.
>* Some of the displayed information on the initial window for
the
>restore like "Backup sets" and "System object" should be optional
by
having
>an on/off select option in the view pull down where you can check
it on or
>off, off being the default. I have 26,000 users now and I try to
minimize
>their confusion. I would also like to turn off menu items like
Archive and
>Retrieve. We don't use this function of adsm ooops TSM. Also, if
you are
>doing a backup the local drives are called "Local". When doing a
restore
the
>local drives are now called "File Level". Interesting???
This has always been an issue. How much do we allow the
administrator to
taylor which functions, menu items, etc, are displayed to the end
user.
Regarding "Local" and "File Level". In Backup, we know which drives
are
local, remote, removable, etc, so the distinction makes sense. For
Restore, we don't really have this information available. We needed
a new
subheading for non-image filesytems that contained files. This is
what we
came up with, after debating even worse names. I hate it as well -
if you
have a better name, please let me know.
We did in fact ask feedback from some customers. Unfortunately, we
can't
ask everyone. But feedback and suggestions on this list is very
important.
Considering all the functions and support we deliver, we try to fix
and
enhance as much as we can, many from suggestions from you folks. We
aren't
superhuman, though <grin>.
Cheers,
Brett
Brett Walker
ADSM Development, IBM
walkerbl AT us.ibm DOT com
tie 276-0265
----------------------------------------
"According to our log, we're down to our last 3000 vomit
bags - it'll never be enough."
JerryLawson <jlawson AT THEHARTFORD DOT COM> on 11/08/99 07:40:29 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT
EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: TSM V3.7.1 32bit client Critique..
Cris -
I agree with your statements point for point - in fact, I asked for
the
progress indicator messages regarding tape mounts for 3.1, and did
it get
any
better?
I too wonder about all of the requirements that are in the hopper,
and
whether anyone actually reviews them.
Jerry Lawson
jlawson AT thehartford DOT com
______________________________ Reply Separator
_________________________________
Subject: TSM V3.7.1 32bit client Critique..
Author: owner-adsm-l AT VM.MARIST DOT EDU at SMTP
Date: 11/5/99 11:15 AM
I am constantly amazed at how IBM/Tivoli can't see the forest
through the
trees.
Here are some observations since I started looking at the V3.7.1
client
interface:
* The progress clock issue still remains. Once the restore has
been
committed the clock should remain counting regardless of whether or
not any
data is currently being transferred. Give the user some indication
that the
session is still running . There should be more progress indicator
messages
during a restore for example:
* Requesting Data..
* Requesting Tape Media..
* Mounting Tape Media..
* Searching Tape Media..
* Transferring Data..
* During the restore there are two status windows now. The
default
window showing a progress indicator stating "Preparing" and amount
of data
moved. The second window, and more important window has lost some
important
information and is not launched by default. This wind will only
appear if
invoked manually or at the completion of the restore. Ok, a bit
lame. And
while I'm at it why don't the windows scale to the main window
automatically
and to the standard default. Hmmmm? A Programming 101 may be in
order.
* Some of the displayed information on the initial window for
the
restore like "Backup sets" and "System object" should be optional by
having
an on/off select option in the view pull down where you can check it
on or
off, off being the default. I have 26,000 users now and I try to
minimize
their confusion. I would also like to turn off menu items like
Archive and
Retrieve. We don't use this function of adsm ooops TSM. Also, if you
are
doing a backup the local drives are called "Local". When doing a
restore
the
local drives are now called "File Level". Interesting???
Others have brought up these points also and I am constantly amazed
that I
have 26,000 desktop clients, 100+ Novell and NT clients, 100+ Unix
clients
and not once did IBM pick up the phone and say: "Given that you have
a
large
number of clients, and must see where some improvements could be
made,
would
you mind giving us some input to the future design of the product?"
Nope, Nada, zilch, 0
I have tried to go the proper channels to no avail.
Hmmm .... where did I put the phone numbers of those others backup
vendors....
That's my opinion, we welcome yours.
disclaimer: My opinions ARE the opinion of my employer. I put in
nicer
words
though.
Have a nice weekend all... Back to my testing.
CR
__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / TSM (ADSM)
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com
|
