Re: Deleting data older than a certain range
The client command Delete BAckup is the surgical way to dispose of old backups. Alternately, you may find older backups isolated to tapes which you can Delete Volume at the TSM server, or perhaps use Move commands to isolate the old backups for such treatment. Richard Sims, sitting in the dark at Boston University thanks to our alleged electrical utility company
Help with tsm script
I have a script which under tsm 5.5.4 server gives a report of The storage pool name, count ov reclaimable volumes, and reclaimable space for the specified percentage. You execute as follows: Run reclaim-check 55 Under tsm 6.2.2, I get an arithmetic exception sqlstate 22003. I don't see the problem. Script follows: SELECT distinct stgpool_name as "Pool", - count(volume_name) as "No. Volumes", - cast(sum(cast((est_capacity_mb / 1024 * - (pct_utilized / 100)) - as decimal(9,3))) as decimal(9,3)) - as "GB Reclaimable" - FROM volumes - WHERE pct_reclaim>$1 - GROUP BY stgpool_name Any ideas? The error message gives no help as to what part of the expression gives the exception. Thanks for any help you can give. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Help with tsm script
Do you have the document "Changes to the SELECT command" from http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=/com.ibm.itsm.srv.upgrd.doc/r_srv_upgrd_cmd_select.html? The last section is Data types for arithmetic operations. Compare your "cast(sum(cast((est_capacity_mb / 1024 * (pct_utilized / 100))" string to last example in the article. The example has two "as decimal" strings; you might need an "as decimal" spec on the "pct_utilized /100"? Harold Vandeventer Systems Programmer State of Kansas - DISC harold.vandeven...@da.ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Tuesday, June 07, 2011 9:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help with tsm script I have a script which under tsm 5.5.4 server gives a report of The storage pool name, count ov reclaimable volumes, and reclaimable space for the specified percentage. You execute as follows: Run reclaim-check 55 Under tsm 6.2.2, I get an arithmetic exception sqlstate 22003. I don't see the problem. Script follows: SELECT distinct stgpool_name as "Pool", - count(volume_name) as "No. Volumes", - cast(sum(cast((est_capacity_mb / 1024 * - (pct_utilized / 100)) - as decimal(9,3))) as decimal(9,3)) - as "GB Reclaimable" - FROM volumes - WHERE pct_reclaim>$1 - GROUP BY stgpool_name Any ideas? The error message gives no help as to what part of the expression gives the exception. Thanks for any help you can give. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Help with tsm script
I have a script that lists reclaimable space by volume for a given storage pool. I've added line numbers so I can see how many tapes would be reclaimed at a given percentage. It runs on Unix from a command prompt. === #!/usr/bin/ksh # # This script checks reclaimable space in a tape storage pool # The list is displayed with line numbers and is sorted by # reclaimable space in descending order. # Check that a parameter is passed if [[ $# != 1 ]] then echo Usage: cr \ exit 4 fi dsmadmc -id= -pass= -displ=list "q vol stg=$1 f=d" | grep Reclaimable | sort -n -r -k 4 > $1.usage cat -n $1.usage | more rm $1.usage === Sample output: ch2uptsm1 $ ./cr ch2win_offsite 1 Pct. Reclaimable Space: 99.3 2 Pct. Reclaimable Space: 98.7 3 Pct. Reclaimable Space: 98.1 4 Pct. Reclaimable Space: 97.9 5 Pct. Reclaimable Space: 97.5 6 Pct. Reclaimable Space: 97.4 7 Pct. Reclaimable Space: 96.8 8 Pct. Reclaimable Space: 93.1 9 Pct. Reclaimable Space: 88.9 10 Pct. Reclaimable Space: 87.8 11 Pct. Reclaimable Space: 86.9 12 Pct. Reclaimable Space: 86.3 13 Pct. Reclaimable Space: 86.0 14 Pct. Reclaimable Space: 84.6 15 Pct. Reclaimable Space: 83.9 16 Pct. Reclaimable Space: 80.9 17 Pct. Reclaimable Space: 79.0 18 Pct. Reclaimable Space: 77.9 19 Pct. Reclaimable Space: 77.1 20 Pct. Reclaimable Space: 76.0 Hope this helps, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Tuesday, June 07, 2011 9:24 AM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Help with tsm script I have a script which under tsm 5.5.4 server gives a report of The storage pool name, count ov reclaimable volumes, and reclaimable space for the specified percentage. You execute as follows: Run reclaim-check 55 Under tsm 6.2.2, I get an arithmetic exception sqlstate 22003. I don't see the problem. Script follows: SELECT distinct stgpool_name as "Pool", - count(volume_name) as "No. Volumes", - cast(sum(cast((est_capacity_mb / 1024 * - (pct_utilized / 100)) - as decimal(9,3))) as decimal(9,3)) - as "GB Reclaimable" - FROM volumes - WHERE pct_reclaim>$1 - GROUP BY stgpool_name Any ideas? The error message gives no help as to what part of the expression gives the exception. Thanks for any help you can give. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Help with tsm script
This works: select distinct stgpool_name as "Pool", count(volume_name) as "No. Volumes", cast( sum(est_capacity_mb / 1024 * pct_utilized/100) as decimal(9,3))as "GB Reclaimable" FROM volumes WHERE pct_reclaim > $1 GROUP BY stgpool_name I don't know why. May be a bug: https://www-304.ibm.com/support/docview.wss?uid=swg1IC61919 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Tuesday, June 07, 2011 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help with tsm script I have a script which under tsm 5.5.4 server gives a report of The storage pool name, count ov reclaimable volumes, and reclaimable space for the specified percentage. You execute as follows: Run reclaim-check 55 Under tsm 6.2.2, I get an arithmetic exception sqlstate 22003. I don't see the problem. Script follows: SELECT distinct stgpool_name as "Pool", - count(volume_name) as "No. Volumes", - cast(sum(cast((est_capacity_mb / 1024 * - (pct_utilized / 100)) - as decimal(9,3))) as decimal(9,3)) - as "GB Reclaimable" - FROM volumes - WHERE pct_reclaim>$1 - GROUP BY stgpool_name Any ideas? The error message gives no help as to what part of the expression gives the exception. Thanks for any help you can give. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: TSM & client machine renames
Paul, Regarding the characteristic where the TSM Scheduler remembers the nodename. For Windows: " The service seems to remember the node name in effect when the service was created, even in the absence of a 'nodename' option in dsm.opt. I don't know whether there is a way to change the node name the service uses; we advise client system administrators to remove the service and create a new one when a Windows system is renamed." ** Your way of fixing this is best; uninstalling then reinstalling the scheduler. ** There is a registry entry for the TSM Scheduler service that contains the node name. I used to have a problem with some of the new Windows servers that came into TSM MISSing their backup for authentication reasons. A Windows admin eventually told me why and their way to fix it. In our case, the servers were all built from the same image. They all had the same machine name. When TSM was installed and the Scheduler set up and tested, it was under the standard "build" nodename. Subsequently, before the machine went into production, it was renamed. Sometimes the nodename in the dsm.opt file was changed, but authentication still failed. The Windows folks used to edit the Registry entry for the TSM Scheduler service...but your method is much safer. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: Thursday, June 02, 2011 3:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM & client machine renames -Paul Zarnowski wrote: - IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Help with tsm script
Thanks to all I got the script working. Harrold sennt me the link to the select changes doc, and after casting all the subresults to decimal, things worked out. I don't understand, as all the specified columns are defined as decimal, but it is as it is. Thanks to all, richard, Wanda, etc. for your assistances as well. I filed all away for future reference. Now to fix the rest of the scripts. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: TSM & client machine renames
Thank you for all of your suggestions. To answer some of your questions: - The nodename is usually specified in the dsm.opt, not defaulted from the machine name; - Our nodenames are generally NOT related to the machine name (but this may change as a result of our AD reorg); - We do not have central administration of all of our desktop systems, so we cannot "reach in" to each system from one central location (again, this will likely change AFTER the AD reorg, but that doesn't help me now); - Most of our systems use Scheduler Service, with a smaller percentage using CAD; - We have no standard disk configuration, so cloptsets are probably not a solution. Here is what I think we need to do: For each machine being renamed: 1. On TSM server, rename filespaces at same time period as machine rename (before the next daily backup runs); Preferably have tool that will allow us to trigger this rename remotely, in a secure manner; 2. On client system, edit the dsm.opt file and change any references to machine names to have the new machine name (e.g., in DOMAIN, INCLUDE, or EXCLUDE options); 3. IF the TSM nodename is being renamed, also on client system modify the registry entries to change the old nodename to the new nodename; Uninstalling and re-installing the scheduler will be cumbersome, so we will be looking for a script that can do this quickly; I'm also hoping to avoid a password re-seed. I don't know (yet) if we will be renaming TSM nodes as part of this exercise or not, but suspect we might be. ..Paul At 12:22 PM 6/7/2011, Huebschman, George J. wrote: >Paul, >Regarding the characteristic where the TSM Scheduler remembers the nodename. > >For Windows: > >" The service seems to remember the node name in effect when the service was >created, even in the absence of a 'nodename' option in dsm.opt. I don't know >whether there is a way to change the node name the service uses; we advise >client system administrators to remove the service and create a new one when a >Windows system is renamed." > >** Your way of fixing this is best; uninstalling then reinstalling the >scheduler. ** > >There is a registry entry for the TSM Scheduler service that contains > the node name. I used to have a problem with some of the new Windows servers > that came into TSM MISSing their backup for authentication reasons. >A Windows admin eventually told me why and their way to fix it. >In our case, the servers were all built from the same image. They all > had the same machine name. When TSM was installed and the Scheduler set up > and tested, it was under the standard "build" nodename. Subsequently, before > the machine went into production, it was renamed. Sometimes the nodename in > the dsm.opt file was changed, but authentication still failed. > >The Windows folks used to edit the Registry entry for the TSM Scheduler >service...but your method is much safer. > > > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >Thomas Denier >Sent: Thursday, June 02, 2011 3:20 PM >To: ADSM-L@VM.MARIST.EDU >Subject: Re: [ADSM-L] TSM & client machine renames > >-Paul Zarnowski wrote: - > >IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason >therefore recommends that you do not send any confidential or sensitive >information to us via electronic mail, including social security numbers, >account numbers, or personal identification numbers. Delivery, and or timely >delivery of Internet mail is not guaranteed. Legg Mason therefore recommends >that you do not send time sensitive or action-oriented messages to us via >electronic mail. This message is intended for the addressee only and may >contain privileged or confidential information. Unless you are the intended >recipient, you may not use, copy or disclose to anyone any information >contained in this message. If you have received this message in error, please >notify the author by replying to this message and then kindly delete the >message. Thank you. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: TSM & client machine renames
What happens if you don't rename the filespaces at the same time period of a machine rename? regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul Zarnowski Sent: Tuesday, June 07, 2011 2:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM & client machine renames Thank you for all of your suggestions. To answer some of your questions: - The nodename is usually specified in the dsm.opt, not defaulted from the machine name; - Our nodenames are generally NOT related to the machine name (but this may change as a result of our AD reorg); - We do not have central administration of all of our desktop systems, so we cannot "reach in" to each system from one central location (again, this will likely change AFTER the AD reorg, but that doesn't help me now); - Most of our systems use Scheduler Service, with a smaller percentage using CAD; - We have no standard disk configuration, so cloptsets are probably not a solution. Here is what I think we need to do: For each machine being renamed: 1. On TSM server, rename filespaces at same time period as machine rename (before the next daily backup runs); Preferably have tool that will allow us to trigger this rename remotely, in a secure manner; 2. On client system, edit the dsm.opt file and change any references to machine names to have the new machine name (e.g., in DOMAIN, INCLUDE, or EXCLUDE options); 3. IF the TSM nodename is being renamed, also on client system modify the registry entries to change the old nodename to the new nodename; Uninstalling and re-installing the scheduler will be cumbersome, so we will be looking for a script that can do this quickly; I'm also hoping to avoid a password re-seed. I don't know (yet) if we will be renaming TSM nodes as part of this exercise or not, but suspect we might be. ..Paul At 12:22 PM 6/7/2011, Huebschman, George J. wrote: >Paul, >Regarding the characteristic where the TSM Scheduler remembers the nodename. > >For Windows: > >" The service seems to remember the node name in effect when the service was >created, even in the absence of a 'nodename' option in dsm.opt. I don't know >whether there is a way to change the node name the service uses; we advise >client system administrators to remove the service and create a new one when a >Windows system is renamed." > >** Your way of fixing this is best; uninstalling then reinstalling the >scheduler. ** > >There is a registry entry for the TSM Scheduler service that contains > the node name. I used to have a problem with some of the new Windows servers > that came into TSM MISSing their backup for authentication reasons. >A Windows admin eventually told me why and their way to fix it. >In our case, the servers were all built from the same image. They all > had the same machine name. When TSM was installed and the Scheduler set up > and tested, it was under the standard "build" nodename. Subsequently, before > the machine went into production, it was renamed. Sometimes the nodename in > the dsm.opt file was changed, but authentication still failed. > >The Windows folks used to edit the Registry entry for the TSM Scheduler >service...but your method is much safer. > > > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >Thomas Denier >Sent: Thursday, June 02, 2011 3:20 PM >To: ADSM-L@VM.MARIST.EDU >Subject: Re: [ADSM-L] TSM & client machine renames > >-Paul Zarnowski wrote: - > >IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason >therefore recommends that you do not send any confidential or sensitive >information to us via electronic mail, including social security numbers, >account numbers, or personal identification numbers. Delivery, and or timely >delivery of Internet mail is not guaranteed. Legg Mason therefore recommends >that you do not send time sensitive or action-oriented messages to us via >electronic mail. This message is intended for the addressee only and may >contain privileged or confidential information. Unless you are the intended >recipient, you may not use, copy or disclose to anyone any information >contained in this message. If you have received this message in error, please >notify the author by replying to this message and then kindly delete the >message. Thank you. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: TSM & client machine renames
You get a second new filespace on the server. Confusion & waste. At 03:06 PM 6/7/2011, Hughes, Timothy wrote: >What happens if you don't rename the filespaces at the same time period of a >machine rename? > >regards > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul >Zarnowski >Sent: Tuesday, June 07, 2011 2:31 PM >To: ADSM-L@VM.MARIST.EDU >Subject: Re: TSM & client machine renames > >Thank you for all of your suggestions. > >To answer some of your questions: >- The nodename is usually specified in the dsm.opt, not defaulted from the >machine name; >- Our nodenames are generally NOT related to the machine name (but this may >change as a result of our AD reorg); >- We do not have central administration of all of our desktop systems, so we >cannot "reach in" to each system from one central location (again, this will >likely change AFTER the AD reorg, but that doesn't help me now); >- Most of our systems use Scheduler Service, with a smaller percentage using >CAD; >- We have no standard disk configuration, so cloptsets are probably not a >solution. > >Here is what I think we need to do: > >For each machine being renamed: >1. On TSM server, rename filespaces at same time period as machine rename >(before the next daily backup runs); Preferably have tool that will allow us >to trigger this rename remotely, in a secure manner; >2. On client system, edit the dsm.opt file and change any references to >machine names to have the new machine name (e.g., in DOMAIN, INCLUDE, or >EXCLUDE options); >3. IF the TSM nodename is being renamed, also on client system modify the >registry entries to change the old nodename to the new nodename; Uninstalling >and re-installing the scheduler will be cumbersome, so we will be looking for >a script that can do this quickly; I'm also hoping to avoid a password >re-seed. I don't know (yet) if we will be renaming TSM nodes as part of this >exercise or not, but suspect we might be. > >..Paul > > >At 12:22 PM 6/7/2011, Huebschman, George J. wrote: >>Paul, >>Regarding the characteristic where the TSM Scheduler remembers the nodename. >> >>For Windows: >> >>" The service seems to remember the node name in effect when the service was >>created, even in the absence of a 'nodename' option in dsm.opt. I don't know >>whether there is a way to change the node name the service uses; we advise >>client system administrators to remove the service and create a new one when >>a Windows system is renamed." >> >>** Your way of fixing this is best; uninstalling then reinstalling the >>scheduler. ** >> >>There is a registry entry for the TSM Scheduler service that contains >> the node name. I used to have a problem with some of the new Windows >> servers that came into TSM MISSing their backup for authentication reasons. >>A Windows admin eventually told me why and their way to fix it. >>In our case, the servers were all built from the same image. They >> all had the same machine name. When TSM was installed and the Scheduler set >> up and tested, it was under the standard "build" nodename. Subsequently, >> before the machine went into production, it was renamed. Sometimes the >> nodename in the dsm.opt file was changed, but authentication still failed. >> >>The Windows folks used to edit the Registry entry for the TSM Scheduler >>service...but your method is much safer. >> >> >> >>-Original Message- >>From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >>Thomas Denier >>Sent: Thursday, June 02, 2011 3:20 PM >>To: ADSM-L@VM.MARIST.EDU >>Subject: Re: [ADSM-L] TSM & client machine renames >> >>-Paul Zarnowski wrote: - >> >>IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason >>therefore recommends that you do not send any confidential or sensitive >>information to us via electronic mail, including social security numbers, >>account numbers, or personal identification numbers. Delivery, and or timely >>delivery of Internet mail is not guaranteed. Legg Mason therefore recommends >>that you do not send time sensitive or action-oriented messages to us via >>electronic mail. This message is intended for the addressee only and may >>contain privileged or confidential information. Unless you are the intended >>recipient, you may not use, copy or disclose to anyone any information >>contained in this message. If you have received this message in error, please >>notify the author by replying to this message and then kindly delete the >>message. Thank you. > > >-- >Paul ZarnowskiPh: 607-255-4757 >Manager, Storage Services Fx: 607-255-8521 >719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: Netware backup restores
No, you can run 1 NetWare server without a license. For recovery or whatever purposes. And, what you're terminating is probably your enterprise agreement, if you bought the licenses for the servers (doubtful with anything past NW 4) you can still run the servers for archival purposes, you just won't have any support with Novell if you have a problem. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, June 06, 2011 10:11 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Netware backup restores Stupid question time for which I am pretty sure I know the answer but must ask.. We are terminating our Netware license for Netware servers. So, effective July 1, we can not legally have any running/functioning Netware servers. >From everything I understand (please correct me if I am wrong), you CAN NOT restore Netware backups to anything other than a Netware server. So, as far as I am concerned (and have told my last remaining Netware server admins), any Netware backups after June 30, are mostly useless. Besides, the contents have been migrated to other Windoz servers. Yet we still have folks wanting to perform, last final backups of long dismounted volumes (thus flushed out of TSM, long ago). Am I correct on this? Am I missing anything? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
q occupancy or query file space which one shows the completeness of the export command data for verification?
Hello all, I exported a node ( and it's Data) from TSM SERVER A to TSM Server B, I checked the activity log and the export completed successfully. I did a q occu for the node and the numbers are different however a query file space and the numbers matchup exactly. Question Which one do I use to absolutely verify that everything was exported? I thought was query occupancy but I need to make very sure Thanks TSM Server A (original TSM Server) tsm: TSM>q occu DOVSRV41 Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - DOVSRV41 Bkup DOVSRV41\- 1 LTO48POOL 72,176 6,373.05 6,359.16 SystemSt- ate\NULL- \System State\Sy- stemState DOVSRV41 Bkup \\govsrv4- 3 LTO48POOL 26,703 11,056.96 11,001.54 1\c$ DOVSRV41 Bkup \\govsrv4- 2 LTO48POOL319,706 93,642.55 93,537.01 1\d$ tsm: TSM>q filespace DOVSRV41 (original TSM Server) Node Name Filespace FSID Platform Filespace Is Files-Capacity Pct Name Typepace (MB) Util Unicode? --- --- - - --- - DOVSRV41DOVSRV41\S-1 WinNTVSS Yes0.0 0.0 ystemStat- e\NULL\Sy- stem Stat- e\SystemS- tate DOVSRV41\\DOVSRV41-2 WinNTNTFS Yes3,350,654.0 1.4 \d$ DOVSRV41\\DOVSRV41-3 WinNTNTFS Yes 79,771.0 32.8 \c$ TSM Server B tsm: >q occu DOVSRV41 Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - DOVSRV41 Bkup DOVSRV41\- 1 LTO3POOL 56,103 4,372.56 4,372.01 SystemSt- ate\NULL- \System State\Sy- stemState DOVSRV41 Bkup \\govsrv4- 3 LTO3POOL 21,059 5,269.11 5,268.81 1\c$ DOVSRV41 Bkup \\govsrv4- 2 LTO3POOL 123,979 84,805.56 84,796.89 1\d$ Tsm> q filespace DOVSRV41 Node Name Filespace FSID Platform Filespace Is Files-Capacity Pct Name Typepace (MB) Util Unicode? --- --- - - --- - DOVSRV41DOVSRV41\S-1 (?) VSS Yes0.0 0.0 ystemStat- e\NULL\Sy- stem Stat- e\SystemS- tate DOVSRV41\\DOVSRV41-2 (?) NTFS Yes3,350,654.0 1.4 \d$ DOVSRV41\\DOVSRV41-3 (?) NTFS Yes 79,771.0 32.8 \c$
Re: q occupancy or query file space which one shows the completeness of the export command data for verification?
Q OCC is what I would go by, and my interpretation of those numbers (very scrunched up/misaligned on my iPhone screen) don't look right to me. I might expect some minor variation in physical/logical space occupied between source and target servers, but the number of files per filespace should certainly match up (providing you've exported like for like, and not active data only etc). Q FILES is pretty useless in this context - it reports capacity/utilisation of each filespace not how much data TSM actually has stored for it. Interested to see the comparative output of a Q AUDITOCC for this node on both servers (having run an AUDIT LIC first to update the table). David McClelland London, UK On 7 Jun 2011, at 23:51, "Hughes, Timothy" wrote: > Hello all, > > I exported a node ( and it's Data) from TSM SERVER A to TSM Server B, I > checked the activity log and the export completed successfully. > > I did a q occu for the node and the numbers are different however a query > file space and the numbers matchup exactly. > > Question Which one do I use to absolutely verify that everything was exported? > > I thought was query occupancy but I need to make very sure > > Thanks > > > > TSM Server A (original TSM Server) > > tsm: TSM>q occu DOVSRV41 > > Node Name Type Filespace FSID StorageNumber of Physical Logical >Name Pool Name Files Space Space > Occupied Occupied > (MB) (MB) > -- -- - -- - - - > DOVSRV41 Bkup DOVSRV41\- 1 LTO48POOL 72,176 6,373.05 6,359.16 > SystemSt- > ate\NULL- > \System > State\Sy- > stemState > DOVSRV41 Bkup \\govsrv4- 3 LTO48POOL 26,703 11,056.96 11,001.54 > 1\c$ > DOVSRV41 Bkup \\govsrv4- 2 LTO48POOL319,706 93,642.55 93,537.01 > 1\d$ > > > > tsm: TSM>q filespace DOVSRV41 (original TSM Server) > > Node Name Filespace FSID Platform Filespace Is Files-Capacity > Pct >Name Typepace (MB) Util >Unicode? > --- --- - - --- > - > DOVSRV41DOVSRV41\S-1 WinNTVSS Yes0.0 > 0.0 > ystemStat- > e\NULL\Sy- > stem Stat- > e\SystemS- > tate > DOVSRV41\\DOVSRV41-2 WinNTNTFS Yes3,350,654.0 > 1.4 > \d$ > DOVSRV41\\DOVSRV41-3 WinNTNTFS Yes 79,771.0 > 32.8 > \c$ > > > > TSM Server B > > tsm: >q occu DOVSRV41 > > Node Name Type Filespace FSID StorageNumber of Physical Logical >Name Pool Name Files Space Space > Occupied Occupied > (MB) (MB) > -- -- - -- - - - > DOVSRV41 Bkup DOVSRV41\- 1 LTO3POOL 56,103 4,372.56 4,372.01 > SystemSt- > ate\NULL- > \System > State\Sy- > stemState > DOVSRV41 Bkup \\govsrv4- 3 LTO3POOL 21,059 5,269.11 5,268.81 > 1\c$ > DOVSRV41 Bkup \\govsrv4- 2 LTO3POOL 123,979 84,805.56 84,796.89 > 1\d$ > > Tsm> q filespace DOVSRV41 > > Node Name Filespace FSID Platform Filespace Is Files-Capacity > Pct >Name Typepace (MB) Util >Unicode? > --- --- - - --- > - > DOVSRV41DOVSRV41\S-1 (?) VSS Yes0.0 > 0.0 > ystemStat- > e\NULL\Sy- > stem Stat- > e\SystemS- > tate > DOVSRV41\\DOVSRV41-2 (?) NTFS Yes3,350,654.0 > 1.4 > \d$ > DOVSRV41\\DOVSRV41-3 (?) NTFS Yes 79,771.0 > 32.8 > \c$
issue in mounts points
Hi All, we are having issues in one instance for one of the vlt , which is going to waiting for mount point volumes. we checked no rmt mismatch, paths are online and done resync from both library client and library manager. what else we can do other than this. server version 5.3 vtl version is - IBM dataprotectier 2.3 and vtl model is SUN x4600 below are device class properties, what is the ideal value for Mount Retention and Mount Wait(in this instance it has got 562 instances, in which we are having issues) Device Class Name: VLTO-E3 Device Access Strategy: Sequential Storage Pool Count: 3 Device Type: LTO Format: DRIVE Est/Max Capacity (MB): Mount Limit: DRIVES Mount Wait (min): 5 Mount Retention (min): 1 Label Prefix: ADSM Library: VLIB-E3 Directory: Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Off Scaled Capacity: Last Update by (administrator): Last Update Date/Time: 01/25/2010 10:39:17 please let us know if anybody has answer to it? Thanks Yuvaraj
