please read these links

http://www.filibeto.org/~aduritz/truetrue/solaris10/solaris-container-guide_detlef_ulrich.pdf


   http://docs.oracle.com/cd/E18752_01/html/817-1592/gdqlt.html (cloning)

http://hub.opensolaris.org/bin/view/Community+Group+zones/faq

regards
By the way S11 has better update integration with beadm (replace liveupgrade)
if possible you can migrate to S11




On 8/12/2012 6:48 AM, Jordi Espasa Clofent wrote:
Hi all,

The most of my production machines looks like:

* Solaris 10 Update 7 (now we're starting to migrate to Update 10)
* All the FS in classical UFS but /opt with ZFS
* All the zones inside /opt/zones
* All the zones containing a app server (Glassfish)
* All the critical app data is just managed/stored by a backend bbdd, so no data inside the zone but the app (Java files) itself

In case I have some real and weird problem in the zone (or even in the global one) we proceed:

- re-create the zone in another server (all the process is automated by backend scripts, it takes just 15/20 minutes)
- re-deploy the app in the zone (30/45 minutes)

So, in total, if zoneX is crashing, to be able to be up un running again is gonna take around 45min-1h05 aprox. That's acceptable for us, but obviously it would be amazing if we can reduce this needed time.

I'm just wondering if I can do it playing with some ZFS capability (as snapshots) since all the zones are always under /opt/zones, which, as I said, is ZFS.

Thanks in advance for all the suggestions.
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

--

<<attachment: laotsao.vcf>>

_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to