June 17, 2009 at 9:21 am
I know for me, the biggest excitement that I get from the VM world is when we start talking about testing. Being able to clone my production server and then apply version updates to the clone is where I get all the warm and fuzzy feelings. 😀
June 17, 2009 at 9:32 am
Don't forget that cloning doesn't mean you ignore data safety/control issues. Keep that production data safe! Even in test VMs.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 17, 2009 at 11:38 am
Steve Jones - Editor (6/17/2009)
Don't forget that cloning doesn't mean you ignore data safety/control issues. Keep that production data safe! Even in test VMs.
++
sanitize scripts are a must! Also remember to nuke log-files or anywhere else PII or other sensitive info might reside.
You also need to remember the clone will have the same system name, fixed IP if assigned, etc. So bring it up in a private network (easily facilitated within the host system on most virtualization plaforms) or 'off' the network entirely, (controlled from VM settings, no need to go 'pull the net cable' physically) and change those values so you don't conflict with the system the clone was made from.
Regarding testing... I could go on for a long time.. VM's absolutely rock for testing. I've gone entirely virtual for this, and I never want to go back to physical machines unless there's no way around it.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply