Solaris 10 p2v migration issue

UNIX Solaris
1

Hi All,

We need to move Physical Solaris 10 system to Virtual Solaris 10(p2v). Both the servers having Solaris 10(Generic_147440-25) means physical server which we are going to move is having Solaris 10 and this physical server will be converted as a virtualserver on another physical server having Solaris 10 and same kernel version.

We are following below link

https://sites.google.com/site/syscookbook/solaris/zones-ngz-migrate-physical-server

Now our question is as per our above mentioned link we need to install SUNWs8brandk package if we are doing migration from Solaris 8 SPARC to a Solaris 8 local zone running on a Solaris 10 global zone.

But in our case both the source(which become physical to virtual) and destination servers are running with Solaris 10 with same verision of kernel patch. Do we need to install any below mentioned brand packages

SUNWs8brandr
SUNWs8brandu
SUNWs9brandr
SUNWs9brandu

Or do we need to install any other packages before p2v migration .Please confirm.

Regards,

2

Hi,

Just for clarification and to see if I have things correct;

You are running Solaris 8 branded containers in a Solaris 10 Global which resides on a physical machine (could you say what it is?). You wish to virtualise this on an other machine thus making the Solaris 8 Branded containers virtualised inside a virtual machine?

I may have picked this up wrong - so just asking for some clarification - normally you would install all the Brand packages only in a global, not sure how they would perform otherwise.

Regards

Dave

3

I'm asking the same question as gull04 but perhaps in a different way:

Q: Will you have Solaris 8 or Solaris 9 running ANYWHERE in your final environment? If yes, please explain. Or will everything be Solaris 10?

4

I will explain in simpler manner. Well host1 is physical machine (having solaris 10/Generic_147440-25) which will be moved as a zone on host2 (having solaris 10/Generic_147440-25). I would like to know do I have to follow above mention link except installing below mention packages or do I have to install any special packeges about which I should know or if any other thing is require the please kindly let me know

SUNWs8brandr
SUNWs8brandu
SUNWs9brandr
SUNWs9brandu

5

So it sounds like the answer to my question is 'no'. You do not have any Solaris 8 or 9 in the configuration.

Those packages are needed if you want to run Solaris 8 and/or Solaris 9 as a virtual machine under a Solaris 10 Global Zone.

If you don't need to run Solaris 8/9 as a virtual machine then you don't need those packages; 8brand or 9brand.

6

Hi,

As hicksd8 said, you'll only need the brand packages if you are deploying Solaris 8 ot 9 branded containers - so in your case you won't need the packages.

Regards

Dave

7

Hi Hicksd8/gull04,

Thanks for your reply & clearing my doubts. Just for more clearity, please also let me know whether I can use above mention link (process/steps mention in the link without installing above mention 4 packages) for moving solaris 10 (physical) on host1 to virtual on host2 running solaris 10.

Regards

8

Hi,

There should be no problems with using the process as described leaving out the package installation for the branded containers. With the usual caveats around disk space and networking etc.

Regards

Dave

9

I agree with gull04 that the process should work but personally I'd prefer to start with Oracle documentation.

Chapter

Obviously, if you have problems, post your question(s) here.

10

I would like to understand if you have experience with P2V pricing.
Example: How much do I need to spend to get my one Physical Machine converted to Virtual Machine.
I have my ESXi environment, P2V tools are already in place.
Looking for rough figure along with efforts(Man Days) needed

Below are areas I foresee of Effort Estimation

Activity Man Hrs/Server
Data Collection (Inventory)
Application Compatibility
Utilization
Capacity Planning Per Server(CPU,RAM,DisksSpace)
Conversion from Physical to Virtual using Conversion Tool
Post Build testing (Stress test, UAT)
Operational Acceptance
Build ESXi Host