ADSM-L

Accessing another node from java web-client very slow

2004-11-09 12:53:55
Subject: Accessing another node from java web-client very slow
From: Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 9 Nov 2004 11:52:54 -0600
When I want to restore NodeA data to NodeB, I typcally go to the
web-client for NodeB and select the menu item "Access Another Node".
Once I tell it the node I want to access, I go to the Restore button.
Here's where the trouble starts.  When I drill down through the
directory structure to find what I want restored, it takes an obscene
amount of time.  For instance, on a netware client I click the "+" sign
next to VOL1: to epand it's contents......then wait 20minutes until it
actually appears.   Click "+" on the next level down in the directory
structure......and wait 20minutes until that appears.  You see where I'm
going with this.  So is this just the way things are, or should it not
be this bad?   I know it shouldn't be this bad, but the question, I
guess, is whether it's this bad for other people also.  Anyone have tips
on improving the response time?  Yes, I could just use the command-line,
but I look at that as a last resort.  I don't want to have to train
multiple people on using syntax for the b/a client commandline.


Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

<Prev in Thread] Current Thread [Next in Thread>