No space available in storage pool STG_POOL_CLOUD and all successor pools

TitusBandugula05011988

ADSM.ORG Member
Joined
Apr 29, 2018
Messages
14
Reaction score
0
Points
0
Hello All,

I've created an on-premises S3 cloud storage pool (size 40TB) and updated the copy destination to this new pool (STG_POOL_CLOUD). However, some of the sqldb backups fail with the following error:

ANR0522W Transaction failed for session 49699 for node XXXXX_SQL (TDP MSSQL Win64) - no space available in storage pool STG_POOL_CLOUD and all successor pools.

Kindly find the storage pool settings:

Protect: BTHTSM01>q stg stg_pool_cloud f=d

Storage Pool Name: STG_POOL_CLOUD
Storage Pool Type: Primary
Device Class Name:
Storage Type: CLOUD
Cloud Type: S3
Cloud URL: http://xxx:xxx:xxx:xxx:xxx
Cloud Identity: xxxx
Cloud Location: ONPREMISE
Estimated Capacity:
Space Trigger Util:
Pct Util:
Pct Migr:
Pct Logical:
High Mig Pct:
Low Mig Pct:
Migration Delay:
Migration Continue:
Migration Processes:
Reclamation Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Cloud Reuse: 1
Migration in Progress?:
Amount Migrated (MB):
Elapsed Migration Time (seconds):
Reclamation in Progress?:
more... (<ENTER> to continue, 'C' to cancel)

Last Update by (administrator): TSMADMIN
Last Update Date/Time: 08/29/2018 09:46:06
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?:
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: Yes
Processes For Identifying Duplicates:
Compressed: Yes
Additional space for protected data:
Total Unused Pending Space:
Deduplication Savings: 130,072 M (21.64%)
Compression Savings: 291 G (63.34%)
Total Space Saved: 418 G (71.28%)
Auto-copy Mode:
Contains Data Deduplicated by Client?:
Maximum Simultaneous Writers: No Limit
Protect Processes:
Protection Storage Pool:
Protect Local Storage Pool(s):
Reclamation Volume Limit:
Date of Last Protection to Remote Pool:
Date of Last Protection to Local Pool:
Deduplicate Requires Backup?:
Encrypted: No
Cloud Space Utilized (MB): 172,658
Bucket Name: sqldb
Local Estimated Capacity: 0.0 M
Local Pct Util: 0.0
Local Pct Logical: 0.0
 

Attachments

  • sql_failed.txt
    7.6 KB · Views: 2
Protect: BTHTSM01>q stgpooldirectory f=d

Storage Pool Name: STG_POOL_xxxx
Directory: /tsmbkp/xxx
Access: Read-Only
Free Space(MB): 478,147
Total Space(MB): 503,836
File System: /tsmbkp/xxx
Absolute Path: /tsmbkp/xxx
 
The Access: Read-Only on the storage pool directory should be read-write I think.
 
Back
Top