Solaris8 and 9 Container on Solaris Cluster
By tf on Jun 23, 2008
If you are still running applications on Solaris 8 using SPARC hardware and maybe even using Sun Cluster 3.0, then you should get a plan ready to upgrade to a more recent releases like Solaris 10 and Solaris Cluster 3.2 02/08.
As you might know the last ship date for Solaris 8 was 02/16/07, the end of Phase 1 support is scheduled for 3/31/09.
Sun Cluster 3.0 is also reaching its end of life as announced within the Sun Cluster 3.2 Release Notes for Solaris OS.
In case you can not immediately upgrade to a newer Solaris release, Sun recently announced the Solaris 8 Container, which introduces the solaris8 brand type for non-global zones on Solaris 10. The packages can be freely downloaded for evaluation and would require subscription for the RTU and support.
While the solaris8 brand type is NOT extending the support life for Solaris 8, it allows you a phased approach for migrating to Solaris 10 and leveraging new hardware platforms while the application still runs within a Solaris 8 runtime environment.
Before going through the virtual to physical (p2v) migration, the existing Sun Cluster 3.0 configuration and packages need to get removed. See the Sun Cluster 3.0 System Administration Guide for more details on how to achieve that. This also means that there is no cluster framework running within the solaris8 brand type zone. Therefore existing standard agents can not be used. However, the sczsh component of the HA Container agent can be used to manage an application running within that solaris8 branded zone.
Of course any migration should get carefully planned.