- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- VMware 4.0, EVA and cloning datastores
Operating System - VMware
1753390
Members
7292
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО06-17-2010 08:41 AM
тАО06-17-2010 08:41 AM
Hi. Looking at a VMware vSphere 4.0 server. Been using MSA storage, just added an EVA 6400. We can create and present datastore storage just fine.
Now we find we want to take an existing datastore (EVA vdisk) and move it to a different vdisk (in a different disk group) presumably using the EVA to make a clone. Once it's cloned, how do we unmount the old datastore and mount the new datastore without creating a new partition, clobbering the clone?
Or do we not use the EVA to clone the datastore?
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
Now we find we want to take an existing datastore (EVA vdisk) and move it to a different vdisk (in a different disk group) presumably using the EVA to make a clone. Once it's cloned, how do we unmount the old datastore and mount the new datastore without creating a new partition, clobbering the clone?
Or do we not use the EVA to clone the datastore?
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 10:39 AM
тАО06-17-2010 10:39 AM
Solution
When you create a clone, you most likely will have to resignature it and re-register all VMs on that datastore. That is not such a great thing, beleive me.
Why not just create the new datastore and then migrate the VMs? If the licenses allow it, use an online "Storage VMotion" - if not, use vCenter's "cold migration" feature which will copy the data while the VM is powered off.
Why not just create the new datastore and then migrate the VMs? If the licenses allow it, use an online "Storage VMotion" - if not, use vCenter's "cold migration" feature which will copy the data while the VM is powered off.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 10:48 AM
тАО06-17-2010 10:48 AM
Re: VMware 4.0, EVA and cloning datastores
Thank you, Uwe. It just seemed logical to offload the VMware servers and let the EVA do what it's good at. This particular datastore just contains install kits and images, so virtual machine motion didn't seem to be an issue.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 11:45 AM
тАО06-17-2010 11:45 AM
Re: VMware 4.0, EVA and cloning datastores
Yes, that makes coping a bit painful and a new datastore name could screw up some scripts.
There are some problems one could face:
- if you just unpresent the original and then rescan so that ESX removes the old SCSI LUNS is could have negative effects on *all* VMS, even if they are located on other datastores.
You can find some more information if you search for "all paths down" or "APD", e.g.:
c01908147 - VMware ESX Server 4.x - Server reboots when LUNs are presented/unpresented from EVA
- the original datastore is registered in the vCenter database and often linked by other objects, e.g. VMs, which makes deletion a bit hard.
It should be possible to remove the links, e.g. by unregistering the VMs, then deleting (!!) the original datastore, unpresenting the vdisk and rescanning. Then present the clone, rescan, resignature, ...
- Or, just unpresent the original and rescan (watch about APD). Alter the clone's LUN WWN to that of the original and present it under the original LUN address, then rescan.
- One way to minimize disruptions due to APD I've attemped once was:
-- migrate all VMs off one server
-- unpresent the vdisk from that server only
-- rescan
-- repeat with next server
I didn't encounter a problem, but, hey, maybe I was just lucky.
No amount of planning will ever replace dumb luck
(no, sorry, I did not invent that)
There are some problems one could face:
- if you just unpresent the original and then rescan so that ESX removes the old SCSI LUNS is could have negative effects on *all* VMS, even if they are located on other datastores.
You can find some more information if you search for "all paths down" or "APD", e.g.:
c01908147 - VMware ESX Server 4.x - Server reboots when LUNs are presented/unpresented from EVA
- the original datastore is registered in the vCenter database and often linked by other objects, e.g. VMs, which makes deletion a bit hard.
It should be possible to remove the links, e.g. by unregistering the VMs, then deleting (!!) the original datastore, unpresenting the vdisk and rescanning. Then present the clone, rescan, resignature, ...
- Or, just unpresent the original and rescan (watch about APD). Alter the clone's LUN WWN to that of the original and present it under the original LUN address, then rescan.
- One way to minimize disruptions due to APD I've attemped once was:
-- migrate all VMs off one server
-- unpresent the vdisk from that server only
-- rescan
-- repeat with next server
I didn't encounter a problem, but, hey, maybe I was just lucky.
No amount of planning will ever replace dumb luck
(no, sorry, I did not invent that)
.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP