I think the only place you can find the actual filenames restored is on the
client.
The restore session will print a list of filenames to stdout (like what's in
the dsmsched.log file on the client),
and if you can capture that, you're home.
Only thing is, it's up to the user doing the restore to put stdout
somewhere....
For SCHEDULED sessions, what you want is in dsmsched.log, but for MANUAL
sessions, I don't
kow how to forcibly capture that. Maybe wrap the dsmc command up in a
script.
----- Original Message -----
From: "Daniel Swan/TM" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 29, 2000 4:09 PM
Subject: Re: Tracking restores?
> Regarding restores, I'd like to thank everyone for their input. I have no
> found out how to determine
> when a client asked for a restore, and how much data was transferred, but
I
> am unable
> to tell WHAT was transfefred, and hold old the data restored was.
>
> Is there any way to glean this data from a centralized location?
>
> Or, to rephrase my question: Does anyone have any statistics on how old
> data to be restored usually is? I'm looking only for guidelines, as I
> understand this can be highly variable. We are looking at making some
> changes to retention policies here, and trying to get a handle on just
what
> is being restored.
>
> Any help appreciated,
> Dan.
>
