All points are good ones. The design of TDP for SQL 2.2.1 was done in such a way to help performance and take advantage of the ability of SQL Server backups to stripe backups (up to 64 stripes on SQL 2000 backups) As a result, TDP for SQL does not create a single filespace for every single unique database. As you could see, with the ability of striping, this could create so many filespaces that it would be unmanageable.
So, how do you monitor backups? Lindsay Morris discusses a way. Also, keep in mind that TDP for SQL does TSM Server logging for each and every database that was backed up (or failed to backup.) TDP for SQL also creates a single message at the end of each backup instance giving complete summary statistics for all databases. And so, you could examine the TSM Server activity log to find out the status that you are looking for. That is how it works... and you are right, you can't just do a "QUERY FILESPACE" to find out if all of your database where backed up... you need to issue other queries (QUERY ACTLOG) to get the information you are looking for. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement.