- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- HP P4000 - Replication to Off-Site Best Practice
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
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
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
05-19-2016 06:52 AM
05-19-2016 06:52 AM
Looking for some best practices, we have two management groups of P4000s, one is for Production and another is for off-site replication. The production P4000s handle our VMWare Virtualized Enviornment. Each night we replicate the data from the Production P4000s to the off-site replication copy of the P4000s using the P4000 remote copy feature.
The biggest downside is that the Production P4000s have to maintain a copy of all the data in a snapshot. So, even though we have 10TB of capacity on our production P4000s, we can only use 5TB, as we have to keep the other 5TB for snapshot.
Is there anyway around this? Maybe through deduplication or some other technology? Or another way to replicate the data without having to basically have double the storage on the production side?
Any ideas welcome, thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2016 10:58 AM
05-19-2016 10:58 AM
Solutionsounds like you have the LUNs set as THICK provisioning. Set them to THIN and then the snapshots will only be as large as the actual changed data. There is generally no need to use Thick LUNs.
If you are really paranoid about over-provisioning, just create one LUN that nobody connects that is thick provisioned with some size buffer you think is appropriate and then if you ever do run into a full capacity problem, you can quickly delete it and get RW access to the luns back online.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2016 11:54 AM
05-19-2016 11:54 AM
Re: HP P4000 - Replication to Off-Site Best Practice
Ok, thanks, that got me going down the right path. It's actually due to the Network Raid 10 that the volumes take up 2x the space, not the snapshots themselves. thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2016 12:04 PM
05-19-2016 12:04 PM
Re: HP P4000 - Replication to Off-Site Best Practice
yes, NR10 will use 2x the raw capacity. A 5TB LUN should take up 10TB of raw SAN space when using NR10, but a snapshot of that 5TB LUN should only take up 2x the actual LUN delta over the time it exists starting at a minimum of 1GB (2GB for NR10).
Are your volumes Thin provisioned or thick? HP's best practice is THIN.