Lu Ann,
Backtrack uses the ADSM API and therefore using the BA GUI will yield
nothing. You can compile and use the sample API program included with the
client and use that as a text interface to view objects, or, you can use
the show versions command from the server admin interface.
30,000 objects seems quite a bit. I'm sure it depends on your retention
and # data files. Check the # generations that your DBAs have set to make
sure everything is okay. Also make sure the management class you have them
bound to has:
vere=1 verd=0 rete=0 reto=0
This allows the backtrack software to correctly control versioning.
Otherwise, you'll have objects that take much longer to expire than what
you might have envisioned.
David Hendrix
Lu Ann Mezera <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 09/18/2000
12:03:13 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: ADSM and SQL-Backtrack
I am looking there when I am in the dsm GUI. The folder is there but when
I
try to expand it, it is empty. Is there another way to look at it in the
dsm GUI or should I use a different ADSM tool? Thanks for your help.
Lu Ann Mezera
Data Center Supervisor
Lab Safety Supply
(608) 757-4909 voice
(608) 757-4652 fax
[EMAIL PROTECTED]
-----Original Message-----
From: Fluker, Tom R [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 18, 2000 12:02 PM
To: [EMAIL PROTECTED]
Subject: Re: ADSM and SQL-Backtrack
look at "/BACKTRACK:oracatalog" your backups are there
Tom Fluker
Viasystems Technologies
> -----Original Message-----
> From: Lu Ann Mezera [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, September 18, 2000 12:18 PM
> To: [EMAIL PROTECTED]
> Subject: ADSM and SQL-Backtrack
>
> We have ADSM 3.2.1 and are in the processing of implementing SQL
> Backtrack
> to backup up our Oracle databases on AIX and SQL Server 7.0 databases on
> NT.
> We know that Backtrack is pushing the backups to ADSM because when our
> Information Architect goes into Backtrack to do a database restore, she
is
> successful. Also, the amount of scratch tapes in our MagStar are rapidly
> depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see
> two
> (2) names for our Database AIX node where the Oracle databases are
> installed
> called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see
> there are 30,000+ files and 240+ gig worth of data.
>
> This is my question. When I go into the ADSM gui, I see the high level
> file
> space structure of those 2 /BACKTRACK filespaces but don't see any
> file/directory detail. Why is this?
