Re: Syntax for query volume where deviceclass=file
HI Andrew et al; Thank you for helping with that. I had not made the mental adjustment that something in a TSM query could be case-sensitive. I have now. Best wishes, Keith
Re: Syntax for query volume where deviceclass=file
Keith, This is one case where the quest is case-sensitive. Try: q vol /adsm/vg014/0026.BFS Good lock, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Keith Arbogast Sent: Tuesday, August 23, 2011 1:11 PM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Syntax for query volume where deviceclass=file I'm in syntax purgatory trying to get output from "query volume" on a devclass=file storage pool. If I add the reported volume name as an argument, 'No match' is returned to the query. If I omit the Volume name, and append 'deviceclass=file' or 'stg=', with format=detailed, normal output is returned but for all volumes in the storage pool. No library or paths or storage agents are defined on this TSM server. Would someone please clear the smoke for me? Here is what I'm doing and the output. tsm: TSMVEI01>q vol stg=vmsnap Volume NameStorageDevice Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - /adsm/vg014/0026.BFS VMSNAP FILE 16.4 G 0.0 Filling /adsm/vg014/002A.BFS VMSNAP FILE 16.4 G 11.4 Filling /adsm/vg015/0021.BFS VMSNAP FILE 16.4 G 0.0 Full /adsm/vg015/0027.BFS VMSNAP FILE 16.3 G 100.0 Full /adsm/vg100/0028.BFS VMSNAP FILE 16.4 G 46.4 Filling /adsm/vg101/0029.BFS VMSNAP FILE 16.4 G 45.1 Filling /adsm/vg103/0019.BFS VMSNAP FILE 16.4 G 0.0 Full tsm: TSMVEI01>q vol /adsm/vg014/0026.bfs ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. Thank you, Keith
Re: Syntax for query volume where deviceclass=file
Hi Keith, The volume name is case sensitive, so try: q vol /adsm/vg014/0026.BFS Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-08-23 14:11:22: > From: Keith Arbogast > To: ADSM-L@vm.marist.edu > Date: 2011-08-23 14:13 > Subject: Syntax for query volume where deviceclass=file > Sent by: "ADSM: Dist Stor Manager" > > I'm in syntax purgatory trying to get output from "query volume" on > a devclass=file storage pool. If I add the reported volume name as > an argument, 'No match' is returned to the query. If I omit the > Volume name, and append 'deviceclass=file' or 'stg=', > with format=detailed, normal output is returned but for all volumes > in the storage pool. No library or paths or storage agents are > defined on this TSM server. Would someone please clear the smoke for me? > > Here is what I'm doing and the output. > > tsm: TSMVEI01>q vol stg=vmsnap > > Volume NameStorageDevice > Estimated Pct Volume > Pool Name > Class Name Capacity Util Status > --- > -- - - > /adsm/vg014/0026.BFS VMSNAP FILE 16.4 > G0.0 Filling > /adsm/vg014/002A.BFS VMSNAP FILE 16.4 > G 11.4 Filling > /adsm/vg015/0021.BFS VMSNAP FILE 16.4 > G0.0 Full > /adsm/vg015/0027.BFS VMSNAP FILE 16.3 > G100.0 Full > /adsm/vg100/0028.BFS VMSNAP FILE 16.4 > G 46.4 Filling > /adsm/vg101/0029.BFS VMSNAP FILE 16.4 > G 45.1 Filling > /adsm/vg103/0019.BFS VMSNAP FILE 16.4 > G 0.0 Full > > tsm: TSMVEI01>q vol /adsm/vg014/0026.bfs > ANR2034E QUERY VOLUME: No match found using this criteria. > ANS8001I Return code 11. > > > Thank you, > Keith
Syntax for query volume where deviceclass=file
I'm in syntax purgatory trying to get output from "query volume" on a devclass=file storage pool. If I add the reported volume name as an argument, 'No match' is returned to the query. If I omit the Volume name, and append 'deviceclass=file' or 'stg=', with format=detailed, normal output is returned but for all volumes in the storage pool. No library or paths or storage agents are defined on this TSM server. Would someone please clear the smoke for me? Here is what I'm doing and the output. tsm: TSMVEI01>q vol stg=vmsnap Volume NameStorageDevice Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - /adsm/vg014/0026.BFS VMSNAP FILE 16.4 G 0.0 Filling /adsm/vg014/002A.BFS VMSNAP FILE 16.4 G 11.4 Filling /adsm/vg015/0021.BFS VMSNAP FILE 16.4 G 0.0 Full /adsm/vg015/0027.BFS VMSNAP FILE 16.3 G 100.0 Full /adsm/vg100/0028.BFS VMSNAP FILE 16.4 G 46.4 Filling /adsm/vg101/0029.BFS VMSNAP FILE 16.4 G 45.1 Filling /adsm/vg103/0019.BFS VMSNAP FILE 16.4 G 0.0 Full tsm: TSMVEI01>q vol /adsm/vg014/0026.bfs ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. Thank you, Keith
Re: Ang: [ADSM-L] Backupset restore question - different server OS's
On 08/23/2011 11:16 AM, Strand, Neil B. wrote: Yes, things tend to move quickly around here and I might be attempting to use TSM in an unconventional manner. I have to move about 90 TB of data from data center A to Data center B. The data centers have dissimilar SAN storage and very limited WAN connectivity between each other. Each server at the new data center will be a new system and needs to be seeded with data from the currently running system. Some servers will only require a few GB of seed data while others will require several hundred GB and a few have several TB of seed data. I have to have a data migration solution ready next week and should begin migration shortly after Labor Day. My Plan in a nutshell: 1. Generate a backupset on a TSM V5.5 AIX server on encrypted 3592 media at data center A 2. Ship the encrypted media to data center B 3. Define a backupset and generate a backupsetTOC(optional) from the encrypted 3592 media on the TSM v6.2 Linux server at Data center B. Data center B has the appropriate encryption keys to decrypt the media. 4. Restore backupset data to the appropriate client from the TSM V6.2 Linux server at Data center B - No TSM DB Upgrades required or planed. The TSM V6.2 Linux server is a fresh install. This turns on whether the backupset format is as architecture-agnostic as the export format. I would expect the export/import to work across architectures; for the backupset, I wouldn't know where to put my money. I would say that it will either work reliably , or fail immediately. You might attempt it with something sized less than a tape volume, (or even just a few GB, and send it over the WAN) and find out. The encryption et. al. are red herrings in the test process, I'd skip it. (and then test with non-sensitive data, natch) - Allen S. Rout
Re: How to completely get rid of TSM6.2/DB2 on AIX
If, you encounter any install issues and need to uninstall TSM 6 and that uninstall isn't successfully you can remove Deployment Engine and it's references from /etc/inittab and /etc/services. I strongly recommend contacting support before doing this though. After having performed a complete uninstall, attempt again to install the 6.2.3 as the recommended level. Mikael
Re: Ang: [ADSM-L] Backupset restore question - different server OS's
Yes, things tend to move quickly around here and I might be attempting to use TSM in an unconventional manner. I have to move about 90 TB of data from data center A to Data center B. The data centers have dissimilar SAN storage and very limited WAN connectivity between each other. Each server at the new data center will be a new system and needs to be seeded with data from the currently running system. Some servers will only require a few GB of seed data while others will require several hundred GB and a few have several TB of seed data. I have to have a data migration solution ready next week and should begin migration shortly after Labor Day. My Plan in a nutshell: 1. Generate a backupset on a TSM V5.5 AIX server on encrypted 3592 media at data center A 2. Ship the encrypted media to data center B 3. Define a backupset and generate a backupsetTOC(optional) from the encrypted 3592 media on the TSM v6.2 Linux server at Data center B. Data center B has the appropriate encryption keys to decrypt the media. 4. Restore backupset data to the appropriate client from the TSM V6.2 Linux server at Data center B - No TSM DB Upgrades required or planed. The TSM V6.2 Linux server is a fresh install. There are two methods of performing a backupset restore - 1. Attach client to media containing the backupset data OR 2. From a TSM server containing backupset data. (Ref: TSM for AIX V5.5 Admin Guide - pg 454). I plan to perform the second. I plan to move the backupset data from server to serverB as described in TSM for AIX V6.2 Admin Guide pg. 520 as such there should be no issues with DB differences between TSM V5 & V6 unless the data written to the backupset media is significantly different. I also ran across "IC62418: Backup set and Table of Contents support in Tivoli Storage Manager Version 6.1" which discusses backupset compatibility between V5 TSM servers and V6.1.2 or higher TSM servers in the "Problem Conclusion" section. Since I have not built the Linux TSM server yet, I cannot test the compatibility of the 3592 media written by AIX and then read (hopefully) by Linux and this has me concerned. It looks like a backupsetTOC is not required but would be nice to have. Your comments are welcome. Thank you, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Monday, August 22, 2011 3:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: [ADSM-L] Backupset restore question - different server OS's I've read through your question 3 times now and I'm still trying to figure out what you're doing :) You're mentioning creating backupsets. For me, a backupset is a way of restoring a client without having to transfer the data across the LAN. But you're also mentioning TSM servers placed on AIX and Linux respectively. Are you trying to move a TSM server from AIX to Linux? I've never heard of anyone transfering client data betweeen TSM servers using backupsets, I didnt even know it was possible. Did you mix it up and mean export tapes? Cant answer for AIX > Linux, but for example AIX > Windows wont work since the way the OS writes/reads labels of the tape isnt the same (tried it, didnt work for me, perhaps someone else was more lucky). Is there a reason you dont want to do a server-to-server export? Generally (and I'm only talking from my own experience) tapes, databases and normal volumes arent compatible between OS's. The way they handle tapes are just too different. If you try to explain what you're trying to accomplish, perhaps it's easier to help. Or it's just getting late and I'm too tired :) Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Strand, Neil B." Sänt av: "ADSM: Dist Stor Manager" Datum: 08/22/2011 20:25 Ärende: [ADSM-L] Backupset restore question - different server OS's I am currently running TSM V5.5 on AIX. I am setting up a TSM V6.2 server on Linux at a new data center. I would like to use backup sets to transfer client data from the old to the new data centers. This backupset data will be used to populate the newly built clients - not as a backup data store. Both the old and new data centers have IBM TS1120 drives in their TS3500 libraries. I don't plan to attach each client to tape drives and would perform the backupset restore via TSM server. Does anyone know or have experienced creating a backup set on a TSM V5 server on AIX and then recovering that backup to a TSM V6 server on Linux? The Linux server would need to generate a TOC from the tape created
Re: Ang: [ADSM-L] How to completely get rid of TSM6.2/DB2 on AIX
Thanks for the tip. It seems that the uninstaller failed to remove the contents of /etc/tivoli/tsm/instance.info thus making the installer fail on the next try. I remember the old days when a TSM install was done in a minute. Best regards Hans Chr. On Mon, Aug 22, 2011 at 9:44 PM, Daniel Sparrman wrote: > > The autonomous installler places files under /var/ibm that needs to be > removed incase the installation fails. I'm not infront of a machine atm so I > cant give you the exact path, but previously when installations failed, I > made sure to remove the entire directory containing configuration files > (telling the installer what is installed) and the log files. I believe there > is also files under /etc that needs to be removed, but like I said, I'm at > home and have no access to any production machines so I cant give you the > exact path. > > Best Regards > > Daniel Sparrman > > > > Daniel Sparrman > Exist i Stockholm AB > Växel: 08-754 98 00 > Fax: 08-754 97 30 > daniel.sparr...@exist.se > http://www.existgruppen.se > Posthusgatan 1 761 30 NORRTÄLJE > > > > -"ADSM: Dist Stor Manager" skrev: - > > > Till: ADSM-L@VM.MARIST.EDU > Från: Hans Christian Riksheim > Sänt av: "ADSM: Dist Stor Manager" > Datum: 08/22/2011 20:41 > Ärende: [ADSM-L] How to completely get rid of TSM6.2/DB2 on AIX > > Hi, > > I've got a problem. An installation failed when creating an instance and I > decided to uninstall and start over. I removed the installation using the > uninstall script provided. But when I ran install.bin the next time it asked > for the password of the instance owner and then failed. > > So it seems something is left behind after uninstall confusing the > installer. > > Any idea what it might be? Expect reinstalling AIX of course. > > AIX61 TL03 > > Hans Chr.
