Hi Community,
Does anybody know if deploying boot from SAN ESX servers using snapcloning is supported?
It seems a pretty fast way to deploy multiple blades and just wondered if there were any reasons not to do it...
Cheers,
merse
I've tried this, and ran into issues, becaues the servers were exact clones. It was a pain to change hostid, mac addresses, config files, that pointed to the old name. It was taking longer than a simple install did. You're better off creating a kickstart script instead, or even creating from scratch. It will save you time and a migraine later.
-KjB
I've tried this, and ran into issues, becaues the servers were exact clones. It was a pain to change hostid, mac addresses, config files, that pointed to the old name. It was taking longer than a simple install did. You're better off creating a kickstart script instead, or even creating from scratch. It will save you time and a migraine later.
-KjB
Many thanks KjB!
merse
I'd still like to know if snapcloning is a supported method of building ESX servers...?
I'm developing a scripted install for RDP but the SAN guys are questioning why when they they've built several ESX servers at a different site by snapcloning a master. They've changed the hostname and IP address and seem to be working ok but I'm worried that there is something underlying that could bite later.
What other unique information from the master has been cloned that would need changing?
Any advive appreciated and still more points available...!
Cheers,
merse
You can do it, but it is not supported. And just because you CAN do something doesn't mean you SHOULD do it. A kickstart install is less of a "fight" anyway.
Dave
Thanks for that Dave.
Anybody got a link to an 'official' statement about what the only supported methods are?
Cheers,
merse