howart
asked on
How to connect a recoverd datastore to the old vm's
I got a VMware cluster with several inaccessible vm's
I recovered the datatore where the machines or on with
esxcfg-volume -r <datastore-id>
Now i can see the recovered datastore next to the old one, which has a label with inactive.
How do I proceed? How do I connected the machines to the recovered datastore with the name
snap-5fce93e5-GT_Backup_Te st-VMs?
GT_Backup_Test-VMs is the name of the old inactive datatsrore
I recovered the datatore where the machines or on with
esxcfg-volume -r <datastore-id>
Now i can see the recovered datastore next to the old one, which has a label with inactive.
How do I proceed? How do I connected the machines to the recovered datastore with the name
snap-5fce93e5-GT_Backup_Te
GT_Backup_Test-VMs is the name of the old inactive datatsrore
Do you want to reconnect the vm as full functionning hosts or just have the possibility to recover the data on them ?
ASKER
I want to reconnect them as full functioning hosts.
Hi
If I understand right your problem, I think you need to change the Storage name to its original name.
Jail
If I understand right your problem, I think you need to change the Storage name to its original name.
Jail
ASKER
After surfing the internet and some puzzeling I got the following pocedure:
Well i did the following:
browse the snap-5fce93e5-GT_Backup_Te st-VMs datastore
look for the *vmx file
right-clickit and choose add to inventory
give the machine a new name <machine-name>-restored
power up the machine
answer the question that it is a copy of an existing machine in the summary tab of the vm
go to to the console and logged into the machine
set its ip address.
removed the old inaccessible machine from the inventory
Hura we are up and running again with the most
Please correct me if there is a better one.
But thx anyway.
Well i did the following:
browse the snap-5fce93e5-GT_Backup_Te
look for the *vmx file
right-clickit and choose add to inventory
give the machine a new name <machine-name>-restored
power up the machine
answer the question that it is a copy of an existing machine in the summary tab of the vm
go to to the console and logged into the machine
set its ip address.
removed the old inaccessible machine from the inventory
Hura we are up and running again with the most
Please correct me if there is a better one.
But thx anyway.
Hi
But this is the right way if you have access to that Storage. Do you have already access to that Storage? And the Storage name is the same as before?
If yes, yes that is the right way to do it. And if you have many VMs, and want to register all, you can run a script that will add all to your inventory in the vCenter
Jail
But this is the right way if you have access to that Storage. Do you have already access to that Storage? And the Storage name is the same as before?
If yes, yes that is the right way to do it. And if you have many VMs, and want to register all, you can run a script that will add all to your inventory in the vCenter
Jail
ASKER
about 4 vms
First I had toe recover the snapshots
login on the ESX host
list hte volumes with
# esxcfg-volume --list
this will give you a list of snapshot volumes
Mount the snapshot with
# esxcfg-volume --mount <datastoreID>
and resign them
# esxcfg-volume -r <datastoreID>
the snapshot will now appear in the datastore list of vSphere client.
and then browse that datastore for the vmx files.
etc.
First I had toe recover the snapshots
login on the ESX host
list hte volumes with
# esxcfg-volume --list
this will give you a list of snapshot volumes
Mount the snapshot with
# esxcfg-volume --mount <datastoreID>
and resign them
# esxcfg-volume -r <datastoreID>
the snapshot will now appear in the datastore list of vSphere client.
and then browse that datastore for the vmx files.
etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
;) thx mate
Hi
Glade to help, but you did find your way ;)
Jail
Glade to help, but you did find your way ;)
Jail