Every month after the CPU (Critical Patch Update) Oracle releases
a new feature Release for Oracle Solaris.
In February 2022 it is a BIG one
Ansible 2.10
OpenSSL 3.0
ldm command enhancements
Ldom migration-class2 for SPARC T7/S7/T8
split -b
coreadm enhanced defaults
zpool -s flag
Apache 2.4.52
new FS /var/share/cores
and many, many FOSS updates
Stay tuned for more blogs about this new features
Showing posts with label zpool. Show all posts
Showing posts with label zpool. Show all posts
16 February 2022
New Features in Solaris 11.4 SRU42 (Feb 2022)
13 August 2021
Don't remove Data Disks from Solaris Zpools if performance is important
Solaris 11.4 delivers a new feature to remove data disks from existing zpools.
zpool remove myzpool <disk>
We used this feature a few times without problems on test environments.
But it has performance impact if the removed disk had data on it.
Especially if read performance is important. We know customers with oracle databases
where latency around 1ms is expected. After removing a disk from a
large zpool the performance was terrible and the only solution was to
re-create the zpool.
Important to understand there is an expected performance impact while the disk is removing.
Sure. The data needs to be copied to the remaining disks.
But even after the remove there can be a major performance impact when the data (from the removed disk) must be read, because the data copy added additional internal redirections.
The recommendation is to use this feature only after an accidentally add
of a disk to a wrong zpool. there is no performance impact if the
removed disk has no data.
Find the details of this recommendation in the Solaris 11.4 ZFS Manual:
https://docs.oracle.com/cd/E37838_01/html/E61017/remove-devices.html
To avoid such troubles we disabled the dataset -c remdisk feature for data disks
by default in VDCF Version 8.1.8
More about our VDCF Solaris Management product can be found on
https://www.jomasoft.ch/vdcf/
30 May 2020
Oracle Database on Solaris ZFS done right
ZFS is the default
filesystem on Oracle Solaris. It is
very easy to use with the
two commands zpool and zfs.
Disk management
Expand existing LUNs or
add additional LUNs if you
need more space. Since
Solaris 11.4 you can remove LUNs if you
want to shrink your pool.
Features
No need for filesystem
checks, because of the copy-on-write
implementation. You can
create snapshots and clones,
use encryption and
compression. Transfer data to other
systems using send/receive
or sharing.
Move the pools using
export/import to other systems.
ZFS builds the base for
the Solaris BootEnvironment (beadm)
where you are able to
update to and boot from different Solaris 11
Updates.
ZFS is my preferred
filesystem and volume manager, but
is everything perfect? No.
You need to carefully configure
ZFS to avoid and work
around fragmentation.
Oracle Database
You can run Oracle
Database very well on ZFS and profit
from snapshots, cloning
and other features. Especially
for larger databases (many
TB) with lots of data changes
you should setup
carefully.
Following a few
Best Practices based on own experiences
and Recommendations by
Oracle:
- data pool with log
device / 8KB recordsize for data / logbias=latency
- redo pool with log
device / 1MB recordsize / logbias=latency
- archive pool
/ 1MB recordsize
Add multiple LUNs for
striping. Use SSDs for highest performance.
If you are using SAN
increase zfs:zfs_vdev_max_pending
and ssd:ssd_max_throttle to 20.
Limit the ZFS Cache
(zfs:zfs_arc_max)
Make sure there is around
20% free space on the zpools.
Use a Server with 'enough'
Memory.
After many years of using
ZFS it always hurts, if I have
to use other more
complicated filesystem ....
Links
Pool Creation Practices
for an Oracle Database (Solaris 11.4 ZFS Guide)
Configuring Oracle ZFS for
an Oracle Database Whitepaper (2014)
Oracle DB erfolgreich
betreiben auf SPARC/LDoms/Solaris/ZFS (German Presentation)
Subscribe to:
Posts (Atom)