... but it'll be more like 2010.05. We've wondered what the delay has been and has caused us quite a bit of stress. The X change log clearly now shows build 134a, the predecessor to OpenSolaris 2010.03. It was updated April 24th.
Several have noted the pending bugs in OpenSolaris 2010.03 as being the cause for delay. That's possible but one other reason is also perhaps Oracle is wanting to remove some software that they no longer want, for example, the Xvm which Oracle wants to replace with Oracle VM.
Interesting little thread about the Sun/Oracle version of OpenSolaris distribution.
Let's hope this gets the momentum it needs to reach a final conclusion about the big silence from Oracle regarding OpenSolaris.
We had several web sites hosted by lighttpd on a single server. We wanted to make on-line backups of them, something we've procrastinated a long time! Once you see how simple it is to make online backups of your data with our OpenSolaris VPS ZFS file system, we hope you won't follow the same path as us and spend some minor time now to save some trouble later.
We wanted to make backup of all the data in /var/lighttpd, where all of our actual web site data lives. Here's what we did.
root@mask:/# zfs create zones/mask/ROOT/lighttpd
root@mask:/# zfs get mountpoint zones/mask/ROOT/lighttpd
NAME PROPERTY VALUE SOURCE
zones/mask/ROOT/lighttpd mountpoint legacy inherited from zones/mask/ROOT
root@mask:/#
Now disable lighttpd, move the data, and create new ZFS snapshot.
root@mask:/# svcadm disable lighttpd14
root@mask:/# mv /var/lighttpd /var/lighttpd.old
root@mask:/# zfs set mountpoint=/var/lighttpd zones/mask/ROOT/lighttpd
root@mask:/# cd /var
root@mask:/var# mv lighttpd.old/* lighttpd
root@mask:/var# zfs snapshot zones/mask/ROOT/lighttpd@backup
root@mask:/var# zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
zones/mask/ROOT/lighttpd@backup 0 - 411M -
zones/mask/ROOT/zbe@backup 143M - 1.12G -
root@mask:/var#
That's it! What just happened?
We took a snapshot of the full file system as it was when we ran that zfs snapshot command. This is a real file system backup, which can be used to restore to if there is ever a need.
Of course, this is just the beginning. You can destroy snapshots and use these snapshots to make offline backups. More on these topics later, or better yet, give them a shot yourself. There are lots of resources on Google.
Want to learn more? Why not purchase our OpenSolaris VPS servers from Entic.net, powered by ZFS? We're sure you'll love it. It'll simplify your life, and you might even like it more than Linux!
This doesn't apply to just Tomcat, but we'll use Tomcat as an example. If get Java heap size errors along with those nasty OutOfMemoryError exceptions, here's what you need to do.
root@vps1:~# svccfg -s svc:/network/http:tomcat6 setenv JAVA_OPTS -Xmx256m
root@vps1:~# svccfg refresh svc:/network/http:tomcat6
root@vps1:~# svccfg restart svc:/network/http:tomcat6
That should do it. You can use the good old pargs [pid] command to make sure the above JAVA_OPTS were taken.
Small post here. Check out this document we found for tuning databases running on ZFS/OpenSolaris VPS.