• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3755
  • Last Modified:

storage vmotion fails

I have tried a few times to get a server moved to another storage device and it has failed three times giving me different errors

the first time two times i got:

Aneneral system error occurred:  The migration has exceeded the maximum sitchover time of 100 seconds.  ESX has preemptively failed the migration to allow the virtual machine to continue running on the source.  To avoid this failure, either increase the maximum allowable switchover time or wait until the virtual machine is performing a less intensive workload.

After reinsalling vmware tools i get

a general system error occurred: storage Vmotion failed to copy on or more of the VM's diskss.  Please consult the VM's log for more details looking for lines starting with "SVMotion".

The error above mentions the file "Servername-000001.vmdk" as the disk it could not copy.  This file has grown everytime i try to use vmotion (it may just be growing in general).

I need to move this server (worst case scenario shut it down and copy it i suppose), and i also need to deal with the vmdk file that is mentioned above.  Please, if any one has ideas or suggestions i am open to all.

I can't afford to make a mistake as this is a production server and rebuilding will take a too long to restore.  Thanks!!
0
IKtech
Asked:
IKtech
  • 8
  • 6
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Check ALSO, you do not have this server with ANY *SNAPSHOTS*

See my EE Article

HOW TO: VMware Snapshots :- Be Patient

It's either a very busy server, too many transaction occuring whilst the Storage vMotion is occuring, and the size of the snapshot is too large.

or, your storage system or network is too slow.

Have you tried, completing this our of hours, at a quiet time?

If you shut it down, you can perform a Cold Migration. (Right Click VM - Migrate)
0
 
IKtechAuthor Commented:
this happened in the middle of the night last night.  The vmdk file is rather large it is 450gb.  So maybe a cold migration is the way to go.

i also have the 175gb file named "servername-000001.vmdk"  i am assuming this is a snapshot used for storage vmotion and i would like to get rid of it.  If i do a cold migration will this get consolidated?  THanks!
0
 
IKtechAuthor Commented:
what if i just did a clone of the vm.  That should take care of the snapshot issue, right?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, clone the VM, will "clone out the snapshot"
0
 
IKtechAuthor Commented:
i got the server to migrate without  turning it off but i still have the snapshot file.  If i use "consolidate" option under the snapshot menu (this appears when right clicking the virtual machine in vcenter), will this fix the problem?  I want all the changes merged to the parent disk and the snapshot gone.

Or is my best bet the cloning idea?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Delete the Snapshot, if it appears in Snapshot Manager.

See my EE Article

HOW TO: VMware Snapshots :- Be Patient
0
 
IKtechAuthor Commented:
it does not appear in snapshot manager.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1. Create a new snapshot
2. wait 60 seconds
3. Delete Snapshot (this could take seconds, minutes, hours or days to complete!)

Read me EE Article Whilst Waiting and Be Patient, it's likely to stick at 95%, Wait!

this process, will delete all linked snapshots, is the VM running on a snapshot?
0
 
IKtechAuthor Commented:
Yes it is running on a snapshot.  If i click edit settings then click on the hard drive the disk file in the right side of the screen references the "servername-000001.vmdk" file.

the size of this file is 180GB.  I am worried that if taking a snapshot and use the delete all button works it will take a long time to finish.  I can't afford to have this server down for days at a time.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
that is possible, depend on transactions occuring in the VM, and datastore speed. The VM will still be up, but performance could be affected.

Once you start the deletion, you cannot stop it or cancel.

but remember, the longer you leave the issue, the worse it will get, and performance of the VM is currently suffering writing to a snapshot disk, and if you run out of storage, VM will stop!

It's quicker to Delete, if the VM is off, but VM will be down until finished.
0
 
IKtechAuthor Commented:
do you think the cloning idea would be less time consuming?
0
 
IKtechAuthor Commented:
BTW this server is running sql 2008.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Personally, I would shutdown, and complete the snapshot merge.
0
 
IKtechAuthor Commented:
Thanks!  that worked.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now