首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >IBM 7.1不工作于主池的回收

问IBM 7.1不工作于主池的回收
EN

Stack Overflow用户
提问于 2015-09-07 10:50:26
回答 1查看 2K关注 0票数 0

我在IBMTSM7.1上遇到了问题,我的测试环境与主池空间回收有关。

虽然有多个具有可重声明空间的卷,但我始终会得到以下错误:

代码语言:javascript
复制
tsm: SERVER1>reclaim stg stgnasdisk thr=60 dura=60 wait=yes
ANR2111W RECLAIM STGPOOL: There is no data to process for STGNASDISK.
ANS8001I Return code 11.

Q卷片段:

代码语言:javascript
复制
E:\DATA\V306237716.BFS    STGNASDISK   PRIMARY         5.0 G    1.0    Full
E:\DATA\V306237717.BFS    STGNASDISK   PRIMARY         5.0 G    2.0    Full
E:\DATA\V306237718.BFS    STGNASDISK   PRIMARY         5.0 G    0.5    Full
E:\DATA\V306237719.BFS    STGNASDISK   PRIMARY         4.9 G   91.3    Full
E:\DATA\V306237720.BFS    STGNASDISK   PRIMARY         5.0 G   75.9    Full
E:\DATA\V306237721.BFS    STGNASDISK   PRIMARY         5.0 G    3.0    Full
E:\DATA\V306237722.BFS    STGNASDISK   PRIMARY         5.0 G    0.5    Full
E:\DATA\V306237723.BFS    STGNASDISK   PRIMARY         5.0 G   16.9    Full
E:\DATA\V306237724.BFS    STGNASDISK   PRIMARY         5.0 G    0.3    Full
E:\DATA\V34160080.BFS     STGNASDISK   PRIMARY         4.9 G   19.5    Full
E:\DATA\V34160081.BFS     STGNASDISK   PRIMARY         5.0 G   75.9    Full
E:\DATA\V34160082.BFS     STGNASDISK   PRIMARY         4.9 G   49.1    Full
E:\DATA\V34160083.BFS     STGNASDISK   PRIMARY         5.0 G   81.6    Full

卷显示99%的可收回空间,但仍未发生任何情况:

代码语言:javascript
复制
tsm: SERVER1>q vol E:\DATA\V306237716.BFS f=d

              Volume Name: E:\DATA\V306237716.BFS
        Storage Pool Name: STGNASDISK
        Device Class Name: PRIMARY
       Estimated Capacity: 5.0 G
  Scaled Capacity Applied:
                 Pct Util: 1.0
            Volume Status: Full
                   Access: Read/Write
   Pct. Reclaimable Space: 99.0
          Scratch Volume?: No
          In Error State?: No
 Number of Writable Sides: 1
  Number of Times Mounted: 6
        Write Pass Number: 1
Approx. Date Last Written: 07/24/2015 12:16:54
   Approx. Date Last Read: 08/14/2015 09:33:45
      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): SERVER_CONSOLE
    Last Update Date/Time: 07/24/2015 12:10:04
     Begin Reclaim Period:
       End Reclaim Period:

驱动器加密密钥管理器:逻辑块保护:否

复制池回收工作正常。存储池详细概述:

SERVER1>q stgnasdisk f=d

代码语言:javascript
复制
                Storage Pool Name: STGNASDISK
                Storage Pool Type: Primary
                Device Class Name: PRIMARY
               Estimated Capacity: 558 G
               Space Trigger Util: 38.4
                         Pct Util: 35.7
                         Pct Migr: 35.7
                      Pct Logical: 49.1
                     High Mig Pct: 90
                      Low Mig Pct: 70
                  Migration Delay: 0
               Migration Continue: Yes
              Migration Processes: 1
            Reclamation Processes: 1
                Next Storage Pool:
             Reclaim Storage Pool:
           Maximum Size Threshold: No Limit
                           Access: Read/Write
                      Description:
                Overflow Location:
            Cache Migrated Files?:
                       Collocate?: Group
            Reclamation Threshold: 100
        Offsite Reclamation Limit:
  Maximum Scratch Volumes Allowed: 25
   Number of Scratch Volumes Used: 1
    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): JEF
            Last Update Date/Time: 08/20/2015 17:46:49
         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?: Yes
 Processes For Identifying Duplicates: 1
        Duplicate Data Not Stored: 0  (0%)
                   Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No
     Deduplicate Requires Backup?:

100%的回收阈值是正常的,这是为了防止备份期间的回收。填海工程每天都要在维修阶段开始。

在这方面任何帮助都是非常受欢迎的。我搜索了一下网络,但没有找到任何解决问题的方法。

EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2015-09-14 20:04:20

问IBM关于这个问题。TSM至少需要一个没有重复的池,否则即使在数据过期时,它也永远不会回收主去达达池。

在测试环境中,我在去重复时有主池和复制池。

我创建了一个非反带复制池,现在恢复正常工作。

票数 2
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/32436869

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档