Del,
The filespace information only shows be the backup start/end for the
INSTANCE. I could go in an backup a single database and the filespace
information will change? It doesn't tell me that there is a database in an
instance that hasn't backed up in xx-days, like I could get that information
from B/A client filespaces. I believe Mr. Lindsay Morris says that
ServerGraph uses the filespace information to list filespaces that haven't
been backed up in x-days, or even last night. He uses this information
instead of the client completion or event records for successfully backups.
Take DB2 for example...there is a filespace for each database backed up.
Now the backup start/end times aren't maintained, but if they were this type
of information would be of more benefit in tracking backups, cleanup,...
Now I love the strides taken in the TDP agent reporting, but there are
still some things I would like to see. Makes central monitoring a bit
easier...
Bill Boyer
DSS, Inc.
"There are 10 kinds of people in the world those who understand binary and
those who don't." - ??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Del Hoobler
Sent: Wednesday, November 13, 2002 9:28 AM
To: [EMAIL PROTECTED]
Subject: Re: SQL 2.2.1
Mehdi,
What "filespace information" are you referring to?
DP for SQL will not update:
Capacity (MB)
Pct Util
because it is ambiguous in the context of DP for SQL.
Remember, those numbers correlate back to a "volume"
capacity and how much of it is utilized.
but DP for SQL will update:
Node Name
Filespace Name
FSID
Platform
Filespace Type
Last Backup Start Date/Time
Last Backup Completion Date/Time
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Never cut what can be untied.
- Commit yourself to constant improvement.
====================================================================
> Can someone email me a good example of DSM.OPT, SQLFULL.CMD for SQL 2.2.1
as
> well as the batch file they use to start SQL Scheduler Service. I do run
my
> SQLFULL.CMD successfully and the log shows me Number of bites sent but
TSM
> Server does not update its FileSpace information.
