Getting more and more, times are over with just a quick edit in a file… to be honest I am still not sure what I like more…
That’s a nice new feature… always thought that it could not be sooooo difficult to get these results 🙂
root@server-bu:~# zfs recv rpool/server/data < email@example.com
root@server-bu:~# zpool monitor -t receive \
> -o done,pool,provider,speed,starttime,timestmp 1
done pool provider speed starttime timestmp
32.9G rpool receive 44.2M 19:29:48 19:42:31
32.9G rpool receive 44.1M 19:29:48 19:42:32
33.0G rpool receive 44.1M 19:29:48 19:42:33
33.0G rpool receive 44.1M 19:29:48 19:42:34
It’s about time… and yes, we got new system products… 😉
T7 and M7 systems are here, 1/2/4 sockets T servers and 8/16 sockets M server, where at the first look the M series has more RAS features like dual SPs and PCIe hot plugging… All servers come with M7 4.13 GHz 32core CPU and 512GB RAM per Socket using 16x 32GB DDR4 DIMMs…
Based on the M hardware a new SuperCluster combination was announced. Interessting could be the 1 CPU per server version… that will depend on the price…
Today Solaris 11.3 was released and following this also a new SolarisCluster 4.3.
Next step; I need such a box 🙂
Some words about the new Standard Edition 2 (SE2) …
SE2 will replace the current SE One and SE based on the same pricing as SE had (list price € 15.194,- per socket) and will also be licensed on system sockets (not on cores like EE). RAC is included but no other options or packs are available. Minimum named users are 10 NUPs per Server.
SE2 may be installed on servers with a maximum of two sockets. When running as RAC each server may only have 1 socket installed and the maximum are also two sockets, so two servers. On two socket servers, you “may” remove the second CPU or you can bind it with a certified hardware partitioning method like OracleVM for SPARC and x86, Solaris Container or AIX LPARs… (No VMware, no HyperV or KVMs).
Technical is it a 12c (>=126.96.36.199) and has a new resource cap with a maximum of 16 threads per server / DB installation, or 8 threads per node in a RAC.
All of this means, no SE setups on four socket machines and no two socket RAC nodes anymore. No cheap SEO which was at 1/3 of SE but yes, for that, you got a thread limitation. And be careful with NUPs, SE/SEO NUPs were per company, now they are per server.
SE/SEO support will end on 1st of September 2016 and will start directly with a sustaining support.
A lot of customers will not be very happy with this new product….
News around the new chip… that sounds cool: