The bitfile is only needed to find out what tape an object is on.

This is a nasty issue.  I am guessing what you really want is to know if a
specific machine registry gets broken and is not getting backed up so you
can address whatever happened.  I think a select of the inactives not in the
actives would answer the question, but not the problem.  If you delete
anything or change the objects will still show up, but the object may be
broken in a way that it is unusable.

The following SQL statement may help you.  There is a way to concatenate the
node name to the hl_name and do it for your entire environment, but the SQL
solution set could get so big the TSM server will never give the answer
back.  So, I recommend you get a list of the nodes, make this a macro and
run it for each node.

select hl_name from backups where node_name='[node_name]' and filespace_name
= '\\[node_name]\c$' and hl_name like '\ADSM.SYS\%\MACHINE\%' and
state=inactive_version and hl_name not in (select hl_name from backups where
node_name='ABACODEV' and filespace_name = '\\[node_name]\c$' and hl_name
like  '\ADSM.SYS\%\MACHINE\%' and state=active_version)

The other option is, there are only 4 objects in an NT world based on what I
can see, SAM, SECURITY, SOFTWARE, SYSTEM.

select node_name, count(hl_name) from backups where node_name='[node_name]'
and filespace_name = '\\[node_name]\c$' and hl_name like
'\ADSM.SYS\%\MACHINE\%' and state=active_version and ll_name in ('SAM',
'SECURITY', 'SOFTWARE', 'SYSTEM') group by node_name

Ultimately, registry integrity is a windows issue and you should be running
registry integrity checking software if that is your problem.  Remember,
recovering a Windows server is not necessarily an "always can event" because
often the problem is the registry that is broken and the backups are damaged
as well.  So, very often you are rebuilding the system and restoring the
application data after a server crash.  I can tell you there is better news.
Under Windows 2000 a real API was created to save the "SYSTEMOBJECT".  That
is a good or a bad thing depending on your point of view.  The way the
system object is saved does some integrity checking and saves the dlls and
other software that are part of the software image.  Now the bad side is TSM
has had a slew of problems getting the system object expiration to work
correctly.

By Windows V10, Paul's code name "RIN TIN TIN", we may have a Windows system
that can do a recovery like a mainframe and save the world.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Lisa Cabanas [mailto:CABANL AT MODOT DOT NET]
Sent: Tuesday, January 21, 2003 11:31 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: oh great SQL gurus..... statement for validating that all of the NT
servers all have valid registry backups


Hello again,

I was hoping one of you nice SQL gods/goddesses (Paul???) would help me
construct a SQL select statement that won't halt my server, won't take days
to run, and will help me validate that all of our NT servers all have active
and inactive copies of c:\adsm.sys\...\MACHINE\*

Now that I get to looking.... I don't easily see how to get what I am
looking for with a select-- is this actually going to be a show bitfile
kind-of-thing? (yuk)

TIA

lisa