VMware

This Question is Answered

2 "helpful" answers available (6 pts)
10 Replies Last post: Jun 21, 2009 6:41 PM by Aaron1Oregon  

How do I kill Ghetto script once running? posted: Jun 20, 2009 8:37 PM

Click to view Aaron1Oregon's profile Novice 9 posts since
Jun 20, 2009

I accidently ran the wrong script and now I do not know how to cancel the script. Since it takes many hours to run the back up, I also think it important to be able to cancel it.

I tried these commands to see if it would show as a process in action that I could kill but could not figure it out.

Commands: ps -aef and Ps auxww

Any help will be greatly appreciated. I would also like to know where to look to start learning the basics commands,

it seems like that is what matters most is ability to call commands in putty.

Thanks

Aaron

Re: How do I kill Ghetto script once running?

1. Jun 20, 2009 8:49 PM in response to: Aaron1Oregon
Click to view norregaard's profile Expert 237 posts since
Nov 26, 2007

Hi. You're on the right track. Use the 'ps' command to identify the proces and then kill the process with the 'kill' command.

ps -auxwww | grep <name of process>

kill -9 <process id>

the link below provides a bit more detail:

http://www.vi-tips.com/2009/04/howto-power-off-or-kill-vm-that-is.html

Re: How do I kill Ghetto script once running?

2. Jun 20, 2009 10:06 PM in response to: Aaron1Oregon
Click to view @m!t's profile Enthusiast 53 posts since
Apr 8, 2008

In ESX 3.5 classic ,all the linux command will work..


Re: How do I kill Ghetto script once running?

3. Jun 21, 2009 8:44 AM in response to: Aaron1Oregon
Click to view DSTAVERT's profile Virtuoso 2,464 posts since
Nov 30, 2003
I would be very careful killing any script. The Ghetto script uses other vmware tools and you may leave those tools in an incomplete state.
.

Re: How do I kill Ghetto script once running?

5. Jun 21, 2009 9:52 AM in response to: Aaron1Oregon
Click to view DSTAVERT's profile Virtuoso 2,464 posts since
Nov 30, 2003
Don't use KILL to cure management issues. If you have overly long processes, change the processes. Run the script multiple times, 1 for each VM if you need to. Killing a script or any process should be a last resort "I am in great danger if I don't" situation. Let the script complete. Make this a learning time. You can easily leave the host machine in an unstable condition. The script itself launches other tools to create snapshots, copy files etc. If you kill the script there are other things that won't get cleaned up. Snapshots for instance, partial copies.

Re: How do I kill Ghetto script once running?

7. Jun 21, 2009 10:46 AM in response to: Aaron1Oregon
Click to view DSTAVERT's profile Virtuoso 2,464 posts since
Nov 30, 2003
For the Disklib_Check() error you probably need to provide a little more information. Running in debug mode and testing only. Version of the script etc. Might want to post that question to the ghetto documents area so that lamw can comment.

The speed of the copy looks to be close to 30GB per hour. Not too bad.

You will need to decide what your disaster plan is. How long can your organization be without access to vital information and processes. I wouldn't want to be dependent on a single ESXi host. A second machine as a standby and testing. Having the NFS store attached to both your production host and the standby host would give you the opportunity to test your backup process.

Ghetto creates a copy of the disk files and a copy of the vmx file. That is enough to run the virtual machine but not a true point in time copy. A clone of a machine would also have additional files like memory, bios, etc. and depending on the process and tools used may also not be a true point in time copy.

Re: How do I kill Ghetto script once running?

9. Jun 21, 2009 1:45 PM in response to: DSTAVERT
Click to view DSTAVERT's profile Virtuoso 2,464 posts since
Nov 30, 2003
It really depends on the individual VM. The ghetto copy could be all you need. If you have databases then a copy occasionally and traditional sql backups inside the VM could be the answer. Web servers are less critical but you want to capture site updates and maybe logs. Domain controllers have other issues. You can't bring them back on line from a clone without doing AD repair.
You really should look at the recovery process more than anything. Once you have a copy it can be added to inventory and started. Think about each vm individually and what might be the approach to satisfy your disaster requirements. And practice, practice.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities