Re: [ADSM-L] TSM 6.1.2.0 - Let's reclaim...well..maybe not.
2009-09-14 08:37:41
Hi
If you don't copy primary pool FILEPOOL to copy pool, for reclamation you
must change option DEDUPREQUIRESBACKUP to no
but it is not good idea.....
Efim
2009/9/14 Stefan Folkerts <stefan.folkerts AT itaa DOT nl>
> Ok, I must be missing something here.
> Someboby please tell me why this is happening! :)
> The FILEPOOL storagepool is a deduped storagepool with a FILE device
> class backing it.
>
> 13:58:16 tsmserv01 : q vol f:\0000003c.bfs f=d
> Volume Name: F:\0000003C.BFS
> Storage Pool Name: FILEPOOL
> Device Class Name: FILEPOOL
> Estimated Capacity: 10.2 G
> Scaled Capacity Applied:
> Pct Util: 17.6
> Volume Status: Full
> Access: Read/Write
> Pct. Reclaimable Space: 82.4
> Scratch Volume?: Yes
> In Error State?: No
> Number of Writable Sides: 1
> Number of Times Mounted: 61
> Write Pass Number: 1
> Approx. Date Last Written: 09/11/2009 11:33:03
> Approx. Date Last Read: 09/11/2009 17:34:13
> 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):
> Last Update Date/Time: 08/28/2009 09:02:59
> Begin Reclaim Period:
> End Reclaim Period:
> Drive Encryption Key Manager:
>
> 13:58:24 tsmserv01 : reclaim stgpool filepool thres=30 duration=120
> ANR2111W RECLAIM STGPOOL: There is no data to process for FILEPOOL.
> ANS8001I Return code 11.
>
> Thanks!
>
> Salutations!
>
> Stefan
>
--
Efim
|
|
|