TSM Restore file problem
 

Hi,

I am trying to restore a file from our tsm server but i get an error saying "ANS1302E No objects on server match query"; howvere i do see the file listed in backup listing from server. Belwo are the findings

So can anyone please suggest what i am missing here ?

You should have a support contract for TSM. I would contact your vendor to determine why TSM would be giving you the error.

You've posted a few TSM related questions, and never seem to acknowledge it when people tell you "TSM is an expensive piece of software, and to run it, you have to have IBM support. CALL THEM." TSM is NOT a standard Linux program, and there probably aren't a whole lot of folks that have a ton of experience with it.

Did you read the error notes from IBM??? Did you try to look this up?
http://publib.boulder.ibm.com/infoce...Fmsgs5581.html

The error message tells you the cause, and gives you a solution...again.
http://www.linuxquestions.org/questi...ed-4175441403/
http://www.linuxquestions.org/questi...ic-4175445992/

Well i agree with you here in some way but also differ in other. While calling the vendor for support whether its IBM or Symantech or any other is always an option but to be used at last. I am not a TSM server admin, i look for the client side issues that's why i post when i am not able to find the solution after all the lookup on internet. And just to mention i always look for the error and solution as you were suggesting but if it doesn't work only then i come here on LQ. Anyways thanks for your replies.

Why?? You're PAYING for use of the support line/resources. It should be used FIRST.
If you don't have TSM administrator rights, you can't change anything, much like not having SUDO/root rights on a Linux system. If you can't change it, you can't fix it, so turn it over to the administrator, since that's their job.
Sorry, but ALL TSM messages are available on IBM's website with a very simple search. The errors have SOLUTIONS posted with them. And again, any solution that requires the TSM administrator, needs the TSM administrator to fix.
Doesn't appear to be the case, since each TSM message you've posted was easily found on the net, along with a solution. But since you say you're NOT the TSM administrator, that person needs to be the one you contact about error messages. Talk to your co-workers.

So basically, if you cut away all the shouting, raised blood pressure and aggravation, the OP simply should be heading for http://www.ibm.com/support/entry/por...torage_Manager, right?..

Well, there wasn't any of that, but yes.

Without TSM admin rights, there's nothing you can do. The only thing (from a client side) that a local administrator (a 'node' from TSM's point of view) can do is perform a basic client install, and do backups/restores. But backup sets generated from the TSM server can't be controlled by the node admin...which is why the TSM administrator needs to be involved.

Ah, OK, never mind then. I thought I saw a blood vessel pulsing ;-p

Quick question if you don't mind: does the dsmc allow "select * from backup where node_name='TTLPP0005' and ll_name like '%.deletekeys.PAID.dat%'"?
Or would you really need to access the dsmadmc for that?

The short answer is: it might. :)

The longer answer is, what you get back will depend on what you have on the TSM server, and the rights the node user of dsmc has to the DB on the TSM server. For example, if I set up a node in TSM, and give that node access to ONLY it's own resources, you won't be able to query a different node name. However, you can give rights to a domain group, so any node in that backup domain would be able to read any OTHER node, via that SQL command. It would also work if you specify an admin-level user name when you call dsmc. I've spent years developing a pretty comprehensive TSM monitoring system, and all of these things have bit me before. :)

I thought of that before posting so it's not really a surprise, plus compartmentalizing does make sense.

Yes, compartmentalization does make sense, but unless you've been hip-deep into TSM before, it's a fair question. The web-based tool I wrote to do this handles all that behind the scenes, but it was a nightmare to code. On a plus note, I don't have a line of node-administrators at my desk going "Hey dude...did my server back up last night?". :)

Well at least you know how to code it.


...which I guess is what the OP is doing right now :-]

...because I dug through manuals for hours, finding answers, and calling TSM support.
Nope...he's not a TSM administrator; they're bothering someone else. :)