Fawzi,

we have a very similar environment, an SP2 with 76 nodes and users which
are doing archive from all nodes. I have introduced on common ADSM node
for user data of all SP2 nodes. This is the default node. So a user
doing a regular archive sends his data to this node. I should mention
we  have a common Filesystem for all nodes (PIOFS) and the homedirectory
of the users reside in AFS which is also common to all nodes.

Werner


Fawzi J. Al-Matar wrote:
>
> We have about 37 SP2 nodes with 800G of data.  ADSM is backing up all
> this data in a daily basis. However, a lot of users use the archive
> function to archive projects.  Since these users have a lot of data to
> archive from different SP2 nodes, the retreive is difficult for them
> since they have to know the node they archived their data from.
>
> To resolve this problem, I came up with an idea to have a log for all
> archived data sorted by logon ID and listing the path, des, and node
> name.  This list will be updated in a daily basis after the command (Q
> arch F=d) is performed. Users can go to this log and find out from which
> node they performed their archive from.
>
> So far so good.    When I wanted to implement this, I found out that the
> command line does not give you the archived logon ID, where this log
> will be a failure.  However, the GUI will give you all the information
> including the logon ID.
>
> Note: I issue the   Q ARCH F=d   as root.
>
> My question: Did any one face this kind of request and what are the
> options to resolve this request.
>
> Fawzi Al-Matar
>
> Saudi Arabia

--
=======================================================================
=======================================================================
Werner Baur
Leibniz-Rechenzentrum   X.400: S=Baur;OU=lrz;P=lrz-muenchen;A=d400;C=de
Barer Str. 21          RFC822: Werner.Baur AT lrz DOT de
D-80333 Muenchen         Tel.: ++49-89-28928781
Germany                   Fax: ++49-89-2809460
=======================================================================