Marcel Hofstetter Solaris Blog: #solaris

Showing posts with label #solaris. Show all posts

25 February 2022

Solaris 11.4 SRU42 (Feb 2022) - /var/share/cores FS and coreadm defaults

/var/share/cores is now a separate filesystem

-bash-5.1$ zfs list rpool/VARSHARE/cores
NAME                  USED AVAIL REFER MOUNTPOINT
rpool/VARSHARE/cores   31K 22.1G    31K /var/share/cores

If you upgrade from a previous SRU to SRU42 or later,
cleanup /var/share/cores first, because the files
will be migrated to the new filesystem.

coreadm has now better defaults for the core file naming

root@marcel49:~# coreadm | head -3
     global core file pattern: /var/cores/core.%z.%f.%u.%p
     global core file content: default
kernel zone core file pattern: /var/cores/kzone.%z.%t

with this new core file pattern, the cores can be easier identified
and are less often overwritten.

root@marcel49:~# ls -lh /var/cores/core.marcel49.sleep.0.21198
-rw-------   1 root     root       4.16M Feb 25 13:19 /var/cores/core.marcel49.sleep.0.21198

If the pattern was not configured before the upgrade to SRU42 or later
the new default is set automatically.

If you used another pattern before you upgraded to SRU42 or later
you can set it manually to the new standard/default.

coreadm -g /var/cores/core.%z.%f.%u.%p

09 November 2021

Oracle Solaris and SPARC Server Online Event 12/2021

EMEA, Dec 1st
JAPAC, Dec 7th
NAM, Dec 8th

https://sites.oracle.com/site/oracle-systems/post/announcing-oracle-systems-engineering-forum-2021-oracle-servers

25 October 2021

Performance Impact of a Large Solaris 11 IPS Repo

The content and size of a Solaris IPS Repo has impact on your update processes.
Of course more SRUs increase the size of the repository and the duration of package downloads and operations.

To compare the difference we have two repos on a SPARC S7 LDom.

A first one with 60 updates: all U4 SRUs and a few U3 SRUs

-bash-5.0$ ipsadm -c show_repo repository=http://192.168.20.75:8282 | grep entire@ | wc -l
60

The second repo only with U4 GA and latest SRU38

-bash-5.0$ ipsadm -c show_repo repository=http://192.168.20.75:8283 | grep entire@ | wc -l
2

When replacing the publisher on a target server the catalog is downloaded and analyzed.
Look at this huge difference

# time pkg set-publisher -G "*" -g http://192.168.20.75:8282 solaris

real 4m23.097s

user 4m9.363s
sys 0m12.151s

# time pkg set-publisher -G "*" -g http://192.168.20.75:8283 solaris

real 0m37.629s
user 0m34.968s

sys 0m2.287s

On a SPARC S7 LDom with 3 zones a pkg update -n (trial run) takes nearly
9 minutes with the large IPS Repo.

# time pkg update -n -C 5 --be-name u4.sru38 entire@11.4,5.11-11.4.38.0.1.101.6
...
Planning linked: 3/3 done

real 8m46.280s

user 19m25.699s
sys 0m38.675s

With the smaller repo less than 6 minutes.

Planning linked: 3/3 done

real 5m59.820s
user 12m59.500s

sys 0m27.611s

Summary
Re-create your IPS repo from time to time after updates when you for sure don't need older SRUs anymore.
But always add the GA version first, and then the required SRUs additionally.

20 November 2020

Solaris 11.4 SRU27 with Zones Sheet on the Dashboard

Solaris 11.4 GA was released in 08/2018. Since then Oracle published an update (SRU) each month.

We are now at SRU27 (November 2020). This new SRU contains a bunch of new features.

My favorite is the Zones Sheet where you can see how the Resource Usage of your zones is.

Check out all the other changes on the Oracle Solaris Blog

https://blogs.oracle.com/solaris/announcing-oracle-solaris-114-sru27

Many details on Twitter by Alan Coopersmith
https://twitter.com/alanc/status/1329196081041735682

02 November 2020

Solaris 11 Upgrade on Veritas Cluster with Failover Zones

For efficient Solaris 11 upgrades on Veritas Cluster do the following

1. Disable Evacuation of the Solaris Zones

/opt/VRTSvcs/bin/hagrp -modify myzone_sg Evacuate 0

After the Solaris 11 Upgrade and reboot the Zones are not evacuated to the other Cluster Node.

2. Double check AutoStartList

Check and set the AutoStartList of your Solaris Zones Service Group to make sure
the Zones are attached to the same Node they are currently running on.

/opt/VRTSvcs/bin/hagrp -modify myzone_sg AutoStartList node1 node2

With this setup you can upgrade your first node, reboot and verify all Zones are running fine.

pkg update --be-name s11.3.36 entire@0.5.11,5.11-0.175.3.36
init 6

If all is well with your Solaris Zones and Apps you can do the same with your second node.

And after all your nodes are upgraded you can enable Evacuation again.

/opt/VRTSvcs/bin/hagrp -modify myzone_sg Evacuate 1

Happy Upgrading ..

17 September 2020

Events about SPARC, Solaris, ZFS and ... Q3/Q4 2020

Last Updated 23.11.2020

PLANNED Events

ONLINE: UKOUG Virtual Conference 2020
12/01/2020 - 12/09/2020

https://ukoug.org/general/custom.asp?page=UKOUGagenda20

Online: 12/08/2020 14:00 GMT / 15:00 CET

Oracle Database on Solaris ZFS done right

Event History and Recordings

ONLINE: Oracle Systems Engineering Forum: Oracle Storage (EMEA)
11/17/2020 13:00 - 15:30 CET

https://go.oracle.com/LP=100716?intcmp=WWMK200922P00030:ow:evp:cpo:::RC_WWMK200922P00029:OER400094388&src1=:so:ch:or:dg:::RC_WWMK200707P00061

ONLINE: DOAG 2020 Conference (Germany)
11/17/2020 - 11/19/2020

https://2020.doag.org/de/home/

Onsite: 11/17/2020 15:00

Einsatz der Recovery Appliance - Ist es wirklich so einfach?

Online: 11/19/2020 13:00

Oracle Database on Solaris ZFS done right

ONLINE: Oracle Systems Engineering Forum: Oracle Servers (EMEA)
11/03/2020 13:00 - 15:30 CET

https://go.oracle.com/LP=99024?src1=:ow:lp:cpo:::LPD400085579&intcmp=WWMK200707P00014:ow:lp:cpo:::LPD400085579

ONLINE: Oracle Systems Engineering Forum: Oracle Storage (US)

10/13/2020 9:00am PT

https://go.oracle.com/LP=99389?elqCampaignId=266566&src1=:so:tw:or:dg:oinf::&SC=:so:tw:or:dg:oinf::&pcode=WWMK200827P00084

ONLINE: Oracle Systems Engineering Forum: Oracle Servers (US)
09/29/2020 9:00am PT

https://go.oracle.com/LP=99024?src1=:ow:lp:cpo:::LPD400085579&intcmp=WWMK200707P00014:ow:lp:cpo:::LPD400085579

Recording 2h 40mins is available

29 August 2020

Why we are using SPARC LDoms

Oracle and Fujitsu SPARC Servers include the LDoms Technology. There are no additional costs.
If you see the "Marketing" name 'Oracle VM Server for SPARC'. That is exactly this LDoms Technology.

You can create individual Domains with dedicated CPU and RAM resources running
different Solaris Releases. Use of CPU and RAM is very efficient, because there is no software layer involved. You can add and remove CPU and RAM while the LDoms is running!

Access to Disk and Network can be done virtualized. Performance is good. Using such a virtualized setup the Domains can be live migrated between Servers with the same type of CPU. You can cold migrate (with downtime) between different types of Server in a few minutes.

You place different customers and applications in different LDoms. Good aproach to consolidate your environment.

We at JomaSoft use this technology very successful since years ourselfs and at customer sites.
Our VDCF tool makes deployment and management of LDoms very easy.

Learn more:
https://www.oracle.com/virtualization/vm-server-for-sparc/

https://www.oracle.com/technetwork/server-storage/vm/ovmsparc-best-practices-2334546.pdf

https://blog-archive.global.fujitsu.com/easy-flexible-control-of-your-virtualized-datacenter-with-vdcf-2/

https://www.jomasoft.ch/vdcf/