Del, MOUNTWAITFORDATA is set to yes and shows so in the query.
The SQL name is correct. We have the DESTINATION set to tapepool in preparation for SAN backups. I'm running a test to see if going to a diskpool makes a difference, because that's what my test servers do. Ah, now it works. I can see the container files in the RELOCATE screen. This is temporarily not a problem because I'll set up an include to send the metadata to a non-migrating diskpool. Once we go to a SAN backup, is this going to be a problem? According to the Storage Agent documentation, I can't have a disk storage pool as a destination, but the new pool isn't a destination for the data. Naturally, I know you thought of that and it will work, Del. Conclusion - with this version of TDP SQL 2.2 I must have the metadata in a diskpool in order to RELOCATE the data during a restore. The query of the fileinfo will fail with an ACO0151E. The GUI RELOCATE will simply yield a blank window with no container files showing, and therefore, you will be unable to do the relocate. Thanks for the help! Bill Smoldt STORServer, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Del Hoobler Sent: Wednesday, January 09, 2002 4:14 AM To: [EMAIL PROTECTED] Subject: Re: Can't access TDP SQL /fileinfo metadata > I have several TDP SQL agents backing up Microsoft SQL 2000. Two of them > can't retrieve the fileinfo data with the command: > > tdpsqlc query tsm Northwind full /fileinfo > > They return the error ACO0151E. > . > . > . > Any ideas how I can fix this? Bill, I have one idea. If you enter the command: tdpsqlc query tdp Do you have: MOUNTWaitfordata .......................... Yes This must be "Yes" in order for meta data that has migrated to tape to be accessed. If that's not it... read on... Try Joel's suggestion... If Joel's ideas do not resolve the situation, please place a call with IBM/Tivoli support. A trace will help explain what is going wrong. Service will have you add the following options to the tdpsqlc command: -tracefile=tdpsqlc.trc -traceflag=all,api That will produce data that will help diagnose what is going wrong with the TSM query. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] "Celebrate we will. Life is short but sweet for certain..." -- Dave
