[BlueOnyx:18111] Migration decision

[Chris Gebhardt - VIRTBIZ Internet]

We have a migration to schedule, and I've been thinking about what the 
best way forward might be, since we have a couple of options.   I 
thought I would post that here and see what kind of feedback there may be.

Existing Servers:  2x physical BlueOnyx 5208R.   No problems with 
integrity or underlying system.   Simply time to move off the hardware.

Target Servers:  Would like to virtualize under Aventurin{e} as either 
5208R or 5209R virtuals.

There are ways, if one is careful, to take a physical BlueOnyx server 
and "convert" it to an Aventurin{e} virtual.   I've done this several 
times with older 5106R installations with good success.   I know there 
will be hurdles to overcome with 510(7/8)R or 520(7/8)R and I'll 
probably need some guidance on scripting that.   But that is one option. 
   The benefit is it keeps an existing server without the headaches of 
CMU migration.

And then of course, the standard recommendation is to do a cmuExport 
from the existing system, then cmuImport that onto the new one.   That's 
pretty well old-hat around here as we do it all the time.  The benefit 
is it's very predictable.   The drawback is it's a bit of a hassle.

One consideration that I have:  I'm concerned about the BlueOnyx Shop 
purchases.   If we migrate the system P2V-style, then we don't have to 
worry about NewLinQ being able to grab new software, because the 
software will all come along.   If we CMU, then we often times run into 
the issue where NewLinQ says a manual reset is needed, and that can wind 
up taking precious hours or even days at a very inconvenient time.

So there we go.   Thoughts and comments appreciated.

-- 
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ