- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: CA and Vm ware ESX
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
тАО06-04-2010 04:11 AM
тАО06-04-2010 04:11 AM
I am planning to start replication, do a failover, suspend I/O, after the copy is normal suspend the DR, unpresent the LUN from 8000 and present the copied LUN from 8400 with the same LUN #. Either reboot the host or rescan the disks.
Is this the right approach or is there a different way to do this.
Really appretiate your inputs and knowledge.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 04:28 AM
тАО06-04-2010 04:28 AM
SolutionTake a look into the documentation about resignaturing datastores and re-registering all affected VMs. I have not checked with the latest 3.5 updates, but in previous versions resignaturing was necessary, because the SCSI inquiry string changes when you move from an EVA-8000 to an -8400.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 04:42 AM
тАО06-04-2010 04:42 AM
Re: CA and Vm ware ESX
i was also confused about the resignaturing of VM datastores. do you have any doc or manual where it states how to do the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 04:47 AM
тАО06-04-2010 04:47 AM
Re: CA and Vm ware ESX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 05:01 AM
тАО06-04-2010 05:01 AM
Re: CA and Vm ware ESX
From the ESX command line it is as simple as:
#esxcfg-advcfg -s 1 /LVM/EnableResignature
#esxcfg-rescan vmhba1
#esxcfg-rescan vmhba2
(or what ever you adapters are named)
For ESXi you have to use the VI client or the RCLI.
Don't forget to change the parameter back after the rescan:
#esxcfg-advcfg -s 0 /LVM/EnableResignature
This must only be done on one server - after the resignaturing has happened, you just do a rescan on the other servers and then re-register the VMs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 06:59 AM
тАО06-04-2010 06:59 AM
Re: CA and Vm ware ESX
I will ask the VM Team to consider the resignaturing but they want to know will there be any side effect on the VM guest hosts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2010 10:23 AM
тАО06-04-2010 10:23 AM
Re: CA and Vm ware ESX
When datastores are resignatured, their ID and the path to the VMs changes, e.g.:
/vmfs/volumes/4bc82cc3-66853bf4-5422-0025b3e0fb54/VSA2A/VSA2A.vmx
The "4b...54" part will be different after a resignature. So, it is a good idea to:
- make a list of all datastores and their IDs
-- on each server: # ls -1 /vmfs/volumes
- which VM is stored on which datastore and registered on which server:
-- on each server: # vmware-cmd -l
After the resignature, a datastore will also have a new, temporary name. You have to remove the old name from the vCenter database before you can rename the datastore back to the old one.
I think it is a good idea to try it out before the real move happens:
Create a new datastore and put one or two small VMs on it. Then unpresent the vdisk, rescan and move the vdisk to a new LUN address. Change the parameter for resignature and rescan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2010 06:15 AM
тАО06-05-2010 06:15 AM
Re: CA and Vm ware ESX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2010 09:21 AM
тАО06-05-2010 09:21 AM
Re: CA and Vm ware ESX
When you are prepared to resignature anyway, it does not matter if you keep the address/WWN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2010 07:56 AM
тАО06-08-2010 07:56 AM
Re: CA and Vm ware ESX
I guess we have no challenges for windows host. I can straight away present the replicated luns and the host will pick it up .
Kindly suggest.