The behavior with listing under both Local & Network can be explaned
easily. Let's say we have a directory "C:\User homes" shared as
"\\ServerA\home". At TSM client GUI it would be seen both within the
"Local" \\ServerA\c$ tree and under "Network" \\ServerA\home. The latter
is something like mounting a network resource exported by yourself. Why at
all those shares are visible I cannot answer (maybe Pete or Andy can
schedsome light).
I never had time to play with "Network" resources backup but always
avoided it simply because (IMO) it would be a duplicate copy (and TSM
storage waste).

>From Geoff's response it is evident the disk in question is local and thus
journaling should work. Still no clear answer in which category it is
falling - #3, #4 or even #5 but anyway jbb should work.

Geoff, why not to try with all those categories explained to IBM support
and indication you are not falling in #6 scenario. Afterwards it would be
interesting to get the answer why journaling service is not supported in
whatever of other five categories.

Zlatko Krastev
IT Consultant






DFrance <DFrance-TSM AT ATT DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09.11.2002 21:45
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Journaling


Nice response, Zlatko --- I was about to say some of the same!

I agree, and would like for Geoff to reply about what he sees, relative to
the GUI window (one clear indicator).  Do his SAN drives appear under the
"Local" branch or "Network"?  (I noticed at my old 4.2 level, my
locally-defined shares were listed under "Network" --- \\server\uploads
was
there, it even had the local path in parenthesis, on the c$ drive.)

For myself, I am most interested in learning if one of the SANergy
solutions
will be supported by JBB -- the config. where the MDC is on Win2K, owns
the
network shares, etc.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT ayett DOT net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Zlatko Krastev/ACIT
Sent: Saturday, November 09, 2002 8:13 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Journaling


So if we divide the drives in separate categories:
1. Locally attached IDE/SCSI disks - direct-attached-storage (DAS)
2. Direct FC-attached to single system (I am avoiding to use non-shared
term here) - again DAS but using FC
3. SAN-attached disks/subsystems used by single server -
SAN-attached-storage (SAS)
4. SAN-attached disks/subsystems used by several servers but no concurrent
acces to same LUN (again I will not call them SAN-shared to avoid
confusion) - SAS
5. SAN-attached disks/subsystems used by several servers with concurrent
acces to same LUN (in our case MSCS) - SAS
6. LANMAN shares mounted on the TSM client - network-attached-storage
(NAS)