Mahesh
As I understand that is the issue.
The TSM server does not delete empty pre-defined volumes.
See here, 3rd paragraph:
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=%2Fcom.ibm.itsm.srv.doc%2Fc_devconcepts_volumes_ulw.html
I have never used pre-defined vols before but my understanding is that when
they are empty they should be reused.
Perhaps, someone else who has experience with using them could confirm.
Otherwise you may need to contact IBM support.
Is there a reason why you choose to predefine volumes?
If not dynamic allocation is preferred.... IMHO
It has zero maintenance and works flawlessly.
You can use both pre-defined and dynamically allocated volumes in the same stg
pool, so if there is no reason to have the PD volumes I would suggest using
dynamic and move the data from the PD vols and delete them.
-Rick Adamson
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Wednesday, October 09, 2013 10:31 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Pool
Rick,
We predefine all our volumes.
Mahesh
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rick Adamson
Sent: Wednesday, October 09, 2013 10:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Pool
Mahesh,
Below you mention 276 "defined" volumes. Looking at the volume names as in the
example below it appears that these volumes may have been pre-defined.
Do you know if in fact they are pre-defined volumes or were dynamically created
by the storage pool?
-Rick Adamson
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Wednesday, October 09, 2013 9:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Pool
Rick,
This is a FILE pool not a library. When a new volume is defined, I don't ever
see SCRATCH status as Yes.
For example, I just deleted /tsmfp/fp001/bf112, removed the file from the
filesystem. Then I did a define vol once again and here's the status.
q vol /tsmfp/fp001/bf109 f=d
Volume Name: /tsmfp/fp001/bf109
Storage Pool Name: FPOOL01
Device Class Name: FILE
Estimated Capacity: 204.8 G
Scaled Capacity Applied:
Pct Util: 0.0
Volume Status: Empty
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: No
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 1,462
Write Pass Number: 22
Approx. Date Last Written: 10/05/13 12:55:48
Approx. Date Last Read: 10/06/13 15:00:27
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator): ADMIN
Last Update Date/Time: 10/16/12 11:08:05
Begin Reclaim Period:
End Reclaim Period:
Drive Encryption Key Manager:
Logical Block Protected: No
And, filepool volumes do not show up in q libv command.
Thanks.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rick Adamson
Sent: Wednesday, October 09, 2013 9:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Pool
Storage pool volumes cannot be deleted if they are in use. For example, a
volume cannot be deleted if a user is restoring or retrieving a file residing
in the volume, if the server is writing information to the volume, or if a
reclamation process is using the volume.
The DELETE VOLUME command automatically updates the server library inventory
for sequential volumes if the volume is returned to scratch status when the
volume becomes empty. To determine whether a volume will be returned to scratch
status, issue the QUERY VOLUME command and look at the output. If the value for
the attribute "Scratch Volume?" is "Yes," then the server library inventory is
automatically updated.
If the value is "No," you can issue the UPDATE LIBVOLUME command to specify the
status as scratch. It is recommended that you issue the UPDATE LIBVOLUME
command after issuing the DELETE VOLUME command.
-Rick Adamson
-----Original Message-----
From: Rick Adamson
Sent: Wednesday, October 09, 2013 9:33 AM
To: 'ADSM: Dist Stor Manager'
Subject: RE: [ADSM-L] File Pool
What happens when you try to manually delete one of the empty volumes? Messages?
del vol <vol_name>
-Rick Adamson
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Chavdar Cholev
Sent: Wednesday, October 09, 2013 2:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] File Pool
Hi,
check q vol <empty_vol> f=d to see if it is in rw access.
if it is different then rw, you can use update vol <empty_vol> acc=readw.
I also would check actl to see how these vols have been processed/used by TSM
Thank you
Chavdar
On 10/9/2013 00:13, Tailor, Mahesh C. wrote:
> Hello.
>
> TSM 6.3.2.200 on AIX 7.1 fp6
>
> We have a filepool that has 276 (214GB) volumes defined for a total of approx
> 60TB. The occupancy is as follows.
>
> select sum(physical_mb) from occupancy
>
> Unnamed[1]
> ----------------------------------
> 45079209.31
>
>
> We have 75 empty volumes.
>
> select count(*) from volumes where stgpool_name='FPOOL01' and status='EMPTY'
>
> Unnamed[1]
> ------------
> 75
>
> So, the stgpool is not full and we have empty volumes, but TSM starts
> creating volumes and fills up the file system. Any idea why or any clues as
> to why it is doing this? It's probably something really obvious.
>
> More information:
>
> q devc file f=d
> Device Class Name: FILE
> Device Access Strategy: Sequential
> Storage Pool Count: 1
> Device Type: FILE
> Format: DRIVE
> Est/Max Capacity (MB): 204,769.0
> Mount Limit: 50
> Mount Wait (min):
> Mount Retention (min):
> Label Prefix:
> Library:
> Directory: /tsmfp/fp001,/tsmfp/fp002,/tsmfp/fp003
> Server Name:
> Retry Period:
> Retry Interval:
> Shared:
> High-level Address:
> Minimum Capacity:
> WORM: No
> Drive Encryption:
> Scaled Capacity:
> Primary Allocation (MB):
> Secondary Allocation (MB):
> Compression:
> Retention:
> Protection:
> Expiration Date:
> Unit:
> Logical Block Protection:
> Last Update by (administrator): ADMIN
> Last Update Date/Time: 10/08/13 16:07:14
>
> q stg fpool01 f=d
> Storage Pool Name: FPOOL01
> Storage Pool Type: Primary
> Device Class Name: FILE
> Estimated Capacity: 47,096 G
> Space Trigger Util: 38.8
> Pct Util: 45.4
> Pct Migr: 45.4
> Pct Logical: 99.1
> High Mig Pct: 90
> Low Mig Pct: 70
> Migration Delay: 0
> Migration Continue: Yes
> Migration Processes: 1
> Reclamation Processes: 2
> Next Storage Pool:
> Reclaim Storage Pool:
> Maximum Size Threshold: No Limit
> Access: Read/Write
> Description: Filepool for backups
> Overflow Location:
> Cache Migrated Files?:
> Collocate?: No
> Reclamation Threshold: 100
> Offsite Reclamation Limit:
> Maximum Scratch Volumes Allowed: 300
> Number of Scratch Volumes Used: 10
> Delay Period for Volume Reuse: 0 Day(s)
> Migration in Progress?: No
> Amount Migrated (MB): 0.00
> Elapsed Migration Time (seconds): 0
> Reclamation in Progress?: No
> Last Update by (administrator): ADMIN
> Last Update Date/Time: 10/08/13 15:07:15
> Storage Pool Data Format: Native
> Copy Storage Pool(s):
> Active Data Pool(s):
> Continue Copy on Error?: Yes
> CRC Data: No
> Reclamation Type: Threshold
> Overwrite Data when Deleted:
> Deduplicate Data?: No Processes For Identifying
> Duplicates:
> Duplicate Data Not Stored:
> Auto-copy Mode: Client Contains Data
> Deduplicated by Client?: No
>
> Thanks.
>
>
>
>
> ________________________________
>
> Notice: The information and attachment(s) contained in this communication are
> intended for the addressee only, and may be confidential and/or legally
> privileged. If you have received this communication in error, please contact
> the sender immediately, and delete this communication from any computer or
> network system. Any interception, review, printing, copying, re-transmission,
> dissemination, or other use of, or taking of any action upon this information
> by persons or entities other than the intended recipient is strictly
> prohibited by law and may subject them to criminal or civil liability.
> Carilion Clinic shall not be liable for the improper and/or incomplete
> transmission of the information contained in this communication or for any
> delay in its receipt.
________________________________
Notice: The information and attachment(s) contained in this communication are
intended for the addressee only, and may be confidential and/or legally
privileged. If you have received this communication in error, please contact
the sender immediately, and delete this communication from any computer or
network system. Any interception, review, printing, copying, re-transmission,
dissemination, or other use of, or taking of any action upon this information
by persons or entities other than the intended recipient is strictly prohibited
by law and may subject them to criminal or civil liability. Carilion Clinic
shall not be liable for the improper and/or incomplete transmission of the
information contained in this communication or for any delay in its receipt.
________________________________
Notice: The information and attachment(s) contained in this communication are
intended for the addressee only, and may be confidential and/or legally
privileged. If you have received this communication in error, please contact
the sender immediately, and delete this communication from any computer or
network system. Any interception, review, printing, copying, re-transmission,
dissemination, or other use of, or taking of any action upon this information
by persons or entities other than the intended recipient is strictly prohibited
by law and may subject them to criminal or civil liability. Carilion Clinic
shall not be liable for the improper and/or incomplete transmission of the
information contained in this communication or for any delay in its receipt.
|
