- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- MSA P2000 G3 volume migration
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
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
04-19-2012 04:27 AM - edited 04-19-2012 04:30 AM
04-19-2012 04:27 AM - edited 04-19-2012 04:30 AM
Hi!
I have an MSA P2000 G3 FC unit with 6 disks. I need to migrate every data from the old disks to new ones (9 disks). How can I achieve this? Unfortunately I can't just copy everything from a server, because one of the volumes on the current vdisc is the boot volume for the server which is connected to it.
Any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2012 05:12 AM
04-19-2012 05:12 AM
SolutionProvisioning > Create Volume Copy
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2012 05:42 AM - edited 04-19-2012 05:43 AM
04-19-2012 05:42 AM - edited 04-19-2012 05:43 AM
Re: MSA P2000 G3 volume migration
With volume copy I have a problem. According to the manual:
"The first time a volume copy is created of a standard volume, the volume is converted to a master volume
and a snap pool is created in the volume’s vdisk. The snap pool’s size is either 20% of the volume size or
the minimum snap-pool size, whichever is larger."
My problem is, the entire vdisk is used by the volumes. So there is no space left for the snap pool creation.
Can I allocate snap pool from a different vdisk? (I can't increase the original vdisk size, because the new disks are not SATA, but SAS drives)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2012 06:39 AM
04-19-2012 06:39 AM
Re: MSA P2000 G3 volume migration
Nevermind, reading the same manual a bit more i can answer my own question:
"A snap pool and its associated master volumes can be in different vdisks, but must be
owned by the same controller."
Thanks for the suggestion.