- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- HPE Nimble Storage Solution Specialists
- >
- Nimble CS3000 capacity/deduplication issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2023 07:41 AM - last edited on тАО08-24-2023 08:33 PM by support_s
тАО08-24-2023 07:41 AM - last edited on тАО08-24-2023 08:33 PM by support_s
We've been receiving the following error message. We are considering expanding capacity on this storage array. Would expanding likely resolve the issue below?
"Array NimbleVeeam in pool default is approaching the maximum limits on its internal resources required for efficient data deduplication. On reaching these limits, the system will skip deduplication efforts. The array will still continue to serve I/O. To take preventive measures, refer to documentation and/or InfoSight wellness report."
Volumes
197.8 TiB of 215.3 TiB
Total used 91.9%
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2023 08:28 PM
тАО08-24-2023 08:28 PM
SolutionHi TSAdvisor,
Yes, the issue will be resolved by expanding physical capacity.
Please follow the below steps to expand the storage capacity.
1. Analyze your current storage usage and performance requirements.
2. You can free up some capacity by deleting unused VMs, and VVs and deleting duplicate data if any.
3. If you still facing storage capacity issues after deleting unused VMs, VVs, and duplicate data, you will need to expand the storage capacity by adding new disks.
4. Make sure your new disks meet your capacity and performance requirements.
6. Utilize your storage array's automated data redistribution feature to balance data across all disks, ensuring optimal performance and utilization.
7. After data migration, thoroughly test the functionality and performance of the virtual machines and applications.
8. You should consider implementing a long-term capacity planning strategy as your storage needs continue to grow.
Note: Ensure you have a reliable backup of all your data before making any changes.
Hope this helps.
Regards,
Satish
Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2023 12:00 PM - last edited on тАО08-30-2023 07:57 AM by Sunitha_Mod
тАО08-25-2023 12:00 PM - last edited on тАО08-30-2023 07:57 AM by Sunitha_Mod
Re: Nimble CS3000 capacity/deduplication issue
@Satish04 Satish, are you sure that expanding the capacity will resolve the issue? The CS3000 has a Maximum Deduplication Capacity of 40 TiB. Perhaps this is the maximum limits referred to in the error message. In this case, a controller upgrade will be necessary to resolve the issue.