The Oracle Solaris deferred dump feature postpones the writing of a crash dump until a system reboots. When a system panic occurs, a core dump file is generated and preserved in memory. When the system comes back online, the core dump is extracted to the file system defined in the dump configuration created through the dumpadm(8) command. Once the dump is written, the system may reboot again to a multiuser configuration. Otherwise, the system proceeds to boot as normal.
Deferred dump takes advantage of Oracle technologies to retain memory across system reboots. The system state during a panic is recorded and preserved in memory for later analysis.
Deferred dump specifically benefits Oracle systems that have no local disks attached (for example, systems in the M7 series). It also increases overall system availability because the system can return to a running state more quickly after a kernel panic.
For information about saving a crash dump of the Oracle Solaris operating system, see the savecore(8) man page.