olas Cassimatis
Sent: Friday, May 09, 2008 1:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Fw: TSM not updating itself
Is the N: Drive on CUBS2 local, or a mapped/clustered drive? If it's
mapped, you'll have to add it to the domain statement, as it would not
be
part of "all-lo
ocedure.
Nick Cassimatis
- Forwarded by Nicholas Cassimatis/Raleigh/IBM on 05/09/2008 01:59 PM
-
"ADSM: Dist Stor Manager" wrote on 05/09/2008
12:59:19 PM:
> [image removed]
>
> TSM not updating itself
>
> Fred Johanson
>
> to:
>
> ADSM-L
>
> 05/09/2008 01:
On May 9, 2008, at 1:37 PM, Fred Johanson wrote:
But it is an incremental,just not on a TSM schedule.
It needs to be an unqualified Incremental, which runs to completion,
for the Last Backup timestamps to be updated. I would check the
actual client backup log, partly to verify that the action
!st that some serious data size being backed up.
Can you verify that q actlog log really shows n drive being backed up?
Could it be some other drives? Also is it just being backed up a
particular directory path or going to thru all of N via dsmc i with
excludes statement?
I suspect that it is
Subject: Re: [ADSM-L] TSM not updating itself
That's what you'd expect if you were NOT doing an INCREMENTAL. The Q
FILES statistics only get updated when an incremental backup covering
the filespace is started/completed.
David Ehresman
University of Louisville
>>> Fred Johanso
That's what you'd expect if you were NOT doing an INCREMENTAL. The Q FILES
statistics only get updated when an incremental backup covering the filespace
is started/completed.
David Ehresman
University of Louisville
>>> Fred Johanson <[EMAIL PROTECTED]> 5/9/2008 12:59 PM >>>
Anyone seen anythin
Anyone seen anything like this? Q FI returns this:
Node Name: CUBS2
Filespace Name: \\cubs2\n$
Hexadecimal Filespace Name: 5c5c63756273325c6e24
FSID: 1
