Author: "Hart, Charles" <charles.hart AT MEDTRONIC DOT COM>
Date: Wed, 18 May 2005 10:02:20 -0500
We ran a immediate action sched to archive files form a Windows server. The archive was complete, but when you go in to the TSM BA Client GUI the archive does not show up in the retrieve options. The
Verify that the node name you used for the archive is the same as the name that is used for launching the GUI. --Original Message-- From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
Author: "Hart, Charles" <charles.hart AT MEDTRONIC DOT COM>
Date: Wed, 18 May 2005 10:22:59 -0500
I checked all possible node names (ie it's a cluster) none reflect the Archive. Argggg --Original Message-- From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Ochs, Duane
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 18 May 2005 08:36:25 -0700
Well, it's *got* to be out there somewhere. Check the beginning (where the scheduled action starts) of the dsmsched.log file to confirm the node name and server name (in case you have multiple TSM se
Being security-conscious, TSM will not allow one person to see what files have been backed up or archived by another person. Be sure to perform the query as either the original archiver or as superus
The only problems we have had with a very similar environment was the combination of cluster name, nodename, options files and TSM servers being incorrect. You may want to go through the steps taken
Did you use the command line to run a "q archive"? There is a known problem where the data is archived and can be seen by the command line but not but the GUI. We just had this problem. We were given