PROTECT STG feature
Hello Today I made a test on the source sever I run: Protect stg sourrce stg purgedata=all Got the output: 2/23/2015 11:44:49 ANR4980I The protect storage pool process for V7000_5 is completed. Extents protected: 0 of 0. Extents deleted: 940733 of 940733. Amount protected: 0.00 of 0.00. Amount failed: 0.00. Amount transferred: 0.00. Elapsed time: 0 Day(s), 0 Hour(s), 3 Minute(s). (SESSION: 12979) So far so good … Run on both servers source and target: an expire inv But still om my target server have data !!! (1.3%) tsm: TSMREP>q stg dedupcontainer Storage Device Storage Estimated Pct Pool Name Class Name TypeCapacity Util --- -- - -- - DEDUPCONTA-DIRECTORY 10,231 G 1.3 IINER And .. tsm: TSMREP>q container Container Storage Containe- State Pool Namer Type - - --- h:\dcd1\00\004e.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\004f.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0051.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0052.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0053.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0054.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0055.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0056.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0057.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0058.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\0059.dcf DEDUPCONTAI- Dedup Available NER h:\dcd1\00\005a.dcf DEDUPCONTAI- Dedup Available NER My reuse is: Delay Period for Container Reuse: 0 I made a protect stg again to see if it will begin from scratch but NO: 12/23/2015 12:12:38 ANR4980I The protect storage pool process for V7000_5 is completed. Extents protected: 0 of 0. Extents deleted: 0 of 0. Amount protected: 0.00 of 0.00. Amount failed: 0.00. Amount transferred: 0.00. Elapsed time: 0 Day(s), 0 Hour(s), 0 Minute(s). (SESSION: 12979) What I missed ??? Best Regards Robert Hello all A question about the new feature PROTECT STG in V7.1.3 , I made a test and it’s working fine. I wonder how to delete the data in the target server , if I want to stop to protect my primary stg . I figure I need first to run: 1.protect stgpoolsourcepool purgedata=all Will delete only the data on the targetpool of the specific sourcepool (correct ?) 2.upd stg sourcepool protect=”” Did I need other commands ? Best Regards Robert
Select from Occupancy table is blank for Directory pool
We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating backups on other primary pools to directory container pools, which are named ‘DEDUP'. I need to count MB in the DEDUP pools by node for all pertinent nodes. When I run ‘q occupancy ’ from an Admin command line, the logical_mb in the DEDUP pool for that node is displayed, like this: tsm: TSMBL01>q occ esappj10 Node Name Type Filespace FSID Storage Number of Physical Logical Name Pool Name FilesSpace Space Occupied Occupied (MB) (MB) -- -- -- --- --- --- ESAPPJ10Bkup / 3 DEDUP19,011- 799.10 ESAPPJ10Bkup /boot 2 DEDUP64- 244.57 ESAPPJ10Bkup /home 4 DEDUP10,462- 415.37 ESAPPJ10Bkup /opt 5 DEDUP27,215- 7,545.83 ESAPPJ10Bkup /usr 6 DEDUP86,980- 5,377.92 ESAPPJ10Bkup /var 1 DEDUP10,042- 4,102.47 But, when I run a select statement on the Occupancy table for the same node, the output is blank, like this: tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10' LOGICAL_MB - Surely there is a way to do this. Can someone tell me how to get that data from the Occupancy table, or another table, if I am looking in the wrong place? Thank you, Keith Arbogast Indiana University
Re: Select from Occupancy table is blank for Directory pool
Hi Keith, Try this: select sum(logical_mb) from occupancy where node_name='ESAPPJ10' On Wed, Dec 23, 2015 at 8:50 PM, Arbogast, Warren K wrote: > We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating backups > on other primary pools to directory container pools, which are named > ‘DEDUP'. > > I need to count MB in the DEDUP pools by node for all pertinent nodes. > > When I run ‘q occupancy ’ from an Admin command line, the > logical_mb in the DEDUP pool for that node is displayed, like this: > > > tsm: TSMBL01>q occ esappj10 > > > Node Name Type Filespace FSID Storage Number of Physical > Logical > > Name Pool Name FilesSpace > Space > > Occupied >Occupied > > (MB) >(MB) > > -- -- -- --- --- > --- > > ESAPPJ10Bkup / 3 DEDUP19,011- > 799.10 > > ESAPPJ10Bkup /boot 2 DEDUP64- > 244.57 > > ESAPPJ10Bkup /home 4 DEDUP10,462- > 415.37 > > ESAPPJ10Bkup /opt 5 DEDUP27,215- >7,545.83 > > ESAPPJ10Bkup /usr 6 DEDUP86,980- >5,377.92 > > ESAPPJ10Bkup /var 1 DEDUP10,042- >4,102.47 > > > > But, when I run a select statement on the Occupancy table for the same > node, the output is blank, like this: > > > tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10' > > >LOGICAL_MB > > - > > > > Surely there is a way to do this. Can someone tell me how to get that data > from the Occupancy table, or another table, if I am looking in the wrong > place? > > Thank you, > Keith Arbogast > Indiana University > > > > >
Re: Select from Occupancy table is blank for Directory pool
Hi Stephen, Thank you for sharing that idea. It didn’t quite reveal the mystery of the Occupancy table yet. I wonder whether new tables or new attributes have been added for directory container pools? tsm: TSMBL01>select sum(logical_mb) from occupancy where node_name='ESAPPPJ10' Unnamed[1] -- tsm: TSMBL01> On 12/23/15, 15:01, "ADSM: Dist Stor Manager on behalf of Stefan Folkerts" wrote: >Hi Keith, >Try this: >select sum(logical_mb) from occupancy where node_name='ESAPPJ10' > >On Wed, Dec 23, 2015 at 8:50 PM, Arbogast, Warren K wrote: > >> We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating backups >> on other primary pools to directory container pools, which are named >> ‘DEDUP'. >> >> I need to count MB in the DEDUP pools by node for all pertinent nodes. >> >> When I run ‘q occupancy ’ from an Admin command line, the >> logical_mb in the DEDUP pool for that node is displayed, like this: >> >> >> tsm: TSMBL01>q occ esappj10 >> >> >> Node Name Type Filespace FSID Storage Number of Physical >> Logical >> >> Name Pool Name FilesSpace >> Space >> >> Occupied >>Occupied >> >> (MB) >>(MB) >> >> -- -- -- --- --- >> --- >> >> ESAPPJ10Bkup / 3 DEDUP19,011- >> 799.10 >> >> ESAPPJ10Bkup /boot 2 DEDUP64- >> 244.57 >> >> ESAPPJ10Bkup /home 4 DEDUP10,462- >> 415.37 >> >> ESAPPJ10Bkup /opt 5 DEDUP27,215- >>7,545.83 >> >> ESAPPJ10Bkup /usr 6 DEDUP86,980- >>5,377.92 >> >> ESAPPJ10Bkup /var 1 DEDUP10,042- >>4,102.47 >> >> >> >> But, when I run a select statement on the Occupancy table for the same >> node, the output is blank, like this: >> >> >> tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10' >> >> >>LOGICAL_MB >> >> - >> >> >> >> Surely there is a way to do this. Can someone tell me how to get that data >> from the Occupancy table, or another table, if I am looking in the wrong >> place? >> >> Thank you, >> Keith Arbogast >> Indiana University >> >> >> >> >>
Re: VE 7.1.4 install issues
The last suggestion is check md5 for the file: my MD5 is (TDP for VE/7.1.4-TIV-TSMVE-Windows.zip) = aa63c2ad188053d874defb771aa44e50 size: 1005866783 and extract files to directory with shot name (c:\VE\) Elfim > 21 дек. 2015 г., в 19:19, Schaub, Steve написал(а): > > Thanks, but UAC was already fully disabled. It acts like the installer is > trying to launch another setup before a previous one has completed. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim > Sent: Saturday, December 19, 2015 5:28 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] VE 7.1.4 install issues > > Hi, > try to disable UAC on Windows (don’t forget to change the registry EnableLUA) > and repeat. > Efim > >> 18 дек. 2015 г., в 22:23, Schaub, Steve написал(а): >> >> Anyone seen this? I'm testing a fresh install of TSM for VE 7.1.4 on a >> newly built, never used Win2012R2 server. running setup, using "typical" >> install. It looks like it is at the end of the datamover part of the >> install when I get a pop windows stating "Another instance of this setup is >> already running. Please wait for the other instance to finish and then try >> again." When I click ok, I get "The wizard was interrupted before Data >> Protection for VMWare suite could be completely installed." I have tried >> multiple reboots. It looks like only the BA client was installed. I don't >> see any other setup or install applications in task manager. >> >> Thanks, >> >> Steve Schaub >> Systems Engineer II, Backup/Recovery >> Blue Cross Blue Shield of Tennessee >> >> >> -- >> Please see the following link for the BlueCross BlueShield of >> Tennessee E-mail disclaimer: >> http://www.bcbst.com/email_disclaimer.shtm > > -- > Please see the following link for the BlueCross BlueShield of Tennessee > E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: Select from Occupancy table is blank for Directory pool
Try REPORTING_MB. Also Select colname from syscat.columns where tabname='OCCUPANCY" and tabschema='TSMDB1' richard -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Arbogast, Warren K Sent: Wednesday, December 23, 2015 3:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Select from Occupancy table is blank for Directory pool Hi Stephen, Thank you for sharing that idea. It didn’t quite reveal the mystery of the Occupancy table yet. I wonder whether new tables or new attributes have been added for directory container pools? tsm: TSMBL01>select sum(logical_mb) from occupancy where node_name='ESAPPPJ10' Unnamed[1] -- tsm: TSMBL01> On 12/23/15, 15:01, "ADSM: Dist Stor Manager on behalf of Stefan Folkerts" wrote: >Hi Keith, >Try this: >select sum(logical_mb) from occupancy where node_name='ESAPPJ10' > >On Wed, Dec 23, 2015 at 8:50 PM, Arbogast, Warren K wrote: > >> We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating >> backups on other primary pools to directory container pools, which >> are named ‘DEDUP'. >> >> I need to count MB in the DEDUP pools by node for all pertinent nodes. >> >> When I run ‘q occupancy ’ from an Admin command line, the >> logical_mb in the DEDUP pool for that node is displayed, like this: >> >> >> tsm: TSMBL01>q occ esappj10 >> >> >> Node Name Type Filespace FSID Storage Number of Physical >> Logical >> >> Name Pool Name FilesSpace >> Space >> >> Occupied >>Occupied >> >> (MB) >>(MB) >> >> -- -- -- --- >> --- >> --- >> >> ESAPPJ10Bkup / 3 DEDUP19,011- >> 799.10 >> >> ESAPPJ10Bkup /boot 2 DEDUP64- >> 244.57 >> >> ESAPPJ10Bkup /home 4 DEDUP10,462- >> 415.37 >> >> ESAPPJ10Bkup /opt 5 DEDUP27,215- >>7,545.83 >> >> ESAPPJ10Bkup /usr 6 DEDUP86,980- >>5,377.92 >> >> ESAPPJ10Bkup /var 1 DEDUP10,042- >>4,102.47 >> >> >> >> But, when I run a select statement on the Occupancy table for the >> same node, the output is blank, like this: >> >> >> tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10' >> >> >>LOGICAL_MB >> >> - >> >> >> >> Surely there is a way to do this. Can someone tell me how to get that >> data from the Occupancy table, or another table, if I am looking in >> the wrong place? >> >> Thank you, >> Keith Arbogast >> Indiana University >> >> >> >> >>
Re: Select from Occupancy table is blank for Directory pool
Richard, Thank you for both answers. REPORTING_MB is the basic answer. And, thanks for the select reminder. Keith tsm: TSMBL01>q occ esappj10 Node Name Type Filespace FSID Storage Number of Physical Logical Name Pool Name FilesSpace Space Occupied Occupied (MB) (MB) -- -- -- --- --- --- ESAPPJ10Bkup / 3 DEDUP19,011- 799.10 ESAPPJ10Bkup /boot 2 DEDUP64- 244.57 ESAPPJ10Bkup /home 4 DEDUP10,462- 415.37 ESAPPJ10Bkup /opt 5 DEDUP27,215- 7,545.83 ESAPPJ10Bkup /usr 6 DEDUP86,980- 5,377.92 ESAPPJ10Bkup /var 1 DEDUP10,042- 4,102.47 tsm: TSMBL01>select filespace_name,stgpool_name,reporting_mb from occupancy where node_name='ESAPPJ10' FILESPACE_NAME: /boot STGPOOL_NAME: DEDUP REPORTING_MB: 244.57 FILESPACE_NAME: /var STGPOOL_NAME: DEDUP REPORTING_MB: 4102.47 FILESPACE_NAME: /home STGPOOL_NAME: DEDUP REPORTING_MB: 415.37 FILESPACE_NAME: / STGPOOL_NAME: DEDUP REPORTING_MB: 799.10 FILESPACE_NAME: /opt STGPOOL_NAME: DEDUP REPORTING_MB: 7545.83 FILESPACE_NAME: /usr STGPOOL_NAME: DEDUP REPORTING_MB: 5377.92 On 12/23/15, 15:34, "ADSM: Dist Stor Manager on behalf of Richard Cowen" wrote: >Try REPORTING_MB. >Also > >Select colname from syscat.columns where tabname='OCCUPANCY" and >tabschema='TSMDB1' >richard > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of >Arbogast, Warren K >Sent: Wednesday, December 23, 2015 3:07 PM >To: ADSM-L@VM.MARIST.EDU >Subject: Re: [ADSM-L] Select from Occupancy table is blank for Directory pool > >Hi Stephen, >Thank you for sharing that idea. It didn’t quite reveal the mystery of the >Occupancy table yet. I wonder whether new tables or new attributes have been >added for directory container pools? > >tsm: TSMBL01>select sum(logical_mb) from occupancy where node_name='ESAPPPJ10' > > >Unnamed[1] >-- > > > >tsm: TSMBL01> > > > > > > > >On 12/23/15, 15:01, "ADSM: Dist Stor Manager on behalf of Stefan Folkerts" > wrote: > >>Hi Keith, >>Try this: >>select sum(logical_mb) from occupancy where node_name='ESAPPJ10' >> >>On Wed, Dec 23, 2015 at 8:50 PM, Arbogast, Warren K wrote: >> >>> We are running TSM/EE 7.1.4 on RHEL6, and are actively migrating >>> backups on other primary pools to directory container pools, which >>> are named ‘DEDUP'. >>> >>> I need to count MB in the DEDUP pools by node for all pertinent nodes. >>> >>> When I run ‘q occupancy ’ from an Admin command line, the >>> logical_mb in the DEDUP pool for that node is displayed, like this: >>> >>> >>> tsm: TSMBL01>q occ esappj10 >>> >>> >>> Node Name Type Filespace FSID Storage Number of Physical >>> Logical >>> >>> Name Pool Name FilesSpace >>> Space >>> >>> Occupied >>>Occupied >>> >>> (MB) >>>(MB) >>> >>> -- -- -- --- >>> --- >>> --- >>> >>> ESAPPJ10Bkup / 3 DEDUP19,011- >>> 799.10 >>> >>> ESAPPJ10Bkup /boot 2 DEDUP64- >>> 244.57 >>> >>> ESAPPJ10Bkup /home 4 DEDUP10,462- >>> 415.37 >>> >>> ESAPPJ10Bkup /opt 5 DEDUP27,215- >>>7,545.83 >>> >>> ESAPPJ10Bkup /usr 6 DEDUP86,980- >>>5,377.92 >>> >>> ESAPPJ10Bkup /var 1 DEDUP10,042- >>>4,102.47 >>> >>> >>> >>> But, when I run a select statement on the Occupancy table for the >>> same node, the output is blank, like this: >>> >>> >>> tsm: TSMBL01>select logical_mb from occupancy where node_name='ESAPPJ10' >>> >>> >>>LOGICAL_MB >>> >>> - >>> >>> >>> >>> Surely there is a way to do this. Can someone tell me how to get that >>> data from the Occupancy table, or another table, if I am looking in >>> the wrong place? >>> >>> Thank you, >>> Keith Arbogast >>> Indiana University >>> >>> >>> >>> >>>
