Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend


Recovery is a broad topic that applies to several layers of a production database system, as well as processes and procedures practiced in the management of a system. It is important to understand which fault detection and recovery mechanisms exist at all layers of an enterprise application. Application-level robustness, network reliability, service dependencies (for example, naming, directory, routing, and so on) can all fail, and thus can all recover.

When examining the recovery of a database server, consider two primary recovery aspects:

  • Crash recovery, including the ORACLE instance recovery, that does not require data restoration from backup media

  • Data recovery, such as data loss incurred due to a crash, system fault, or human error that requires data restoration from backup media

The time required to perform data restoration from backup media is determined by several factors, such as the amount of data to be restored, the sustainable data rate of the backup device, and the sustainable data rate of the primary storage media. Data restoration time is measurable and can be benchmarked.

Two critical elements to any production data center best practice are rigorously testing and documenting recovery procedures. The time required for the manual intervention aspect of recovery, along with the human error factor, make documented recovery procedures a must.

Technology advances, coupled with lessons learned and data center best practices, have reduced the number of data restore scenarios. Redundant storage and better data integrity checking are among the key technologies that minimize the need to restore data following a crash. Our recovery exercise in this article uses the scenario of a database server crash and recovery when data restore is not required.

You can view a standalone database as a layered series of components where a hierarchical dependency exists—each layer requires that the layer below has completed recovery and is in a functional state. FIGURE 1 shows a standalone database server's layered components.

Figure 1FIGURE 1 Layered Components of a Standalone Database

Thus, for the typical standalone database server, the recovery process begins at the hardware layer and continues through the operating system, a host-based redundant array of inexpensive disks (RAID) manager (if present), and the database application.

Hardware Recovery

Sun's mid-range and enterprise server systems implement power-on self test (POST) and automatic system restart (ASR) features that improve overall system availability by allowing the system to boot around a failed component. During the boot process (including reboots following system crashes), the system firmware checks the integrity of the hardware through basic integrity checks. It flags a component that fails integrity checking. In this way, the system continues the boot process instead of stopping and requiring service (for example, replacing a hardware component).

The primary variables of hardware recovery time (assuming human intervention is not required) are the system size (number of processors, amount of physical memory, and number of I/O channels) and the POST execution level. The POST firmware can run more or less extensive diagnostic tests, depending on the level (which varies somewhat across product families). The Sun Fire 3800-6800 systems and the Sun Fire 12K and 15K servers all implement POST diagnostic levels. The 3800-6800 POST level nomenclature is different from the 12K and 15K. The former use names, whereas the 12K and 15K uses numbers.

The 3800-6800 POST levels are listed in TABLE 1, and the Sun Fire 12K and 15K POST diagnostic levels are listed in TABLE 2.

TABLE 1 Sun Fire 3800-6800 POST Levels

POST Level



Provides fastest POST run. No testing is done; only system board initialization.


Tests all system board components. Provides minimal test counts and patterns. No memory testing is done.


Runs all system board tests and patterns. Performs some memory and Ecache testing.


Performs all default/maximum testing, plus extensive memory and Ecache testing.


Includes mem1 testing plus DRAM testing.

TABLE 2 Sun Fire 12K and 15K POST Levels

POST Level



Probes and initializes the hardware at a minimum level.


Provides default level, basic testing of CPUs, memory, and I/O paths.


Performs additional memory testing.


Provides additional CPU and memory pattern testing.


Runs testing at the highest normal dialogistic level. Adds more extensive CPU, memory, and error detection testing.


Adds all patterns and locations for memory and Ecache testing.


Provides maximum level of testing, including memory and Ecache stress testing.

We reiterate that the size of the system is a significant factor in POST execution time. For example, a Sun Fire 15K with 16 CPUs and 32 Gigabytes of RAM has a considerably shorter POST execution time than a system with 72 CPUs and 576 Gigabytes of RAM, assuming the same POST diagnostic level. TABLE 3 provides some actual examples of execution time.

TABLE 3 POST Execution Time Examples

Sun Fire Platform


POST level

POST time


8/8 GB


4 minutes


8/8 GB


13 minutes


12/48 GB


23 minutes


12/48 GB


2 hours, 10 minutes


72/576 GB


29 minutes


The times are example data points and do not constitute a committed execution time for matching systems and configurations.

Generally, in environments where minimizing boot time and recovery time is critical, it is recommended that system administrators consider setting POST diag-levels to something below the default values, for example: init on Sun Fire 3800-6800 systems and 7 on Sun Fire 12K and 15K systems.

The trade-off is that a lower POST level reduces the ability for testing to find a faulty hardware component, which could cause an outage event. If your system is experiencing hardware problems, consider more extensive POST testing to assist in finding the hardware problem causes. However, when setting POST levels higher than default values, be sure that you fully understand the impact. For large systems, the higher testing levels might result in POST runs that take several hours. Higher POST settings should only be in conjunction with your service organization.

Solaris OS Recovery

The factors driving Solaris OS startup time are the following:

  • System size (hardware configuration)

  • Number and type of file systems mounted

  • Number of attached disk drives, or logical units (LUNs) in the case of intelligent storage controllers

Additionally, if a system crash is the result of a Solaris OS panic, the recovery process includes the time required for Solaris OS to generate a kernel core file.

  • The first phase is the initial core dump, where the file is written to the primary swap device, or a raw device configured with the dumpadm(1M) command. This action happens following the kernel panic, before the system reboots.

  • The second phase is the execution of the savecore(1M) command, which executes during boot and copies the kernel core file to a specified directory in the file system (for example, /var/adm/cores). The savecore(1M) command executes automatically during boot to the init level 2, from the /etc/rc2.d/S75savecore startup script.

To minimize boot, reboot, and recovery time, it is recommended that all required file systems have logging enabled. In Solaris 7 OE, the universal file system (UFS) provides a logging feature as a mount(1M) option. A logging file system typically does not require a time-consuming fsck(1M) command following a crash. Depending on the number and size of file systems, logging can significantly reduce restart time.

Also, it is advised for Solaris 8 OE and newer versions that you use the dumpadm(1M) command to configure a separate raw partition to hold a kernel dump file. This configuration has several advantages, including the ability to run savecore(1M) after a system is rebooted, instead of requiring savecore(1M) to complete before system initialization can finish.

RAID Manager Recovery

We include a section on host-based RAID software because of the impact it can have on system recovery time. The two volume RAID software packages on SPARC processor-based Solaris systems are Veritas Volume Manager (VxVM) from Veritas Corporation and Solaris™ Volume Manager (SVM), which is included with Solaris OS distributions, beginning with Solaris 8 OE.

Both volume managers maintain data areas for the storage of RAID configuration information and device state. During bootstrap, including recovery reboot, the volume manager software must insure the integrity of the configured RAID volumes. The time required to do this scales up linearly with the number of configured devices: volumes in the case of VxVM software and meta devices in the case of SVM software.

From a configuration perspective, it is recommended that a sufficient number of data regions for the volume and state information are configured equally across available disks and controllers. The SVM software uses meta device state databases, and VxVM software implements private regions. When configuring the system, evenly spread the meta device state databases or VxVM private regions across disks and controllers.

ORACLE Recovery

ORACLE recovery is well documented in several places, most notably the ORACLE 9i Database Performance Guide and Reference. ORACLE recovery is organized into two steps:

  • Cache recovery

  • Transaction recovery

Cache recovery, also known as rolling forward, is the application of all committed and uncommitted changes from redo log records to the underlying database files (the actual data blocks). Cache recovery is done first, and ORACLE must complete cache recovery before opening the database (completing the startup process).

Transaction recovery, also known as rolling back, is the application of the rollback segments to the underlying data files. This phase handles uncommitted transactions that were in progress when the crash occurred. Any change that was not committed needs to be undone, and the rollback segments facilitate this by keeping an unchanged copy of the data. Rollback begins after cache recovery is completed and the database is opened (the instance is "up").

Because the cache recovery phase is critical to getting the database back online, the focus of recovery tuning is directed at managing and tuning the roll-forward phase, which is about managing and tuning checkpointing. Checkpointing is an online database event that synchronizes the cached copy of disk blocks to the actual data files on disk. It is the flushing of modified block buffers from memory to disk, which in turn reduces redo log entries that would be required for an instance recovery. Checkpointing occurs regularly when an instance is up, and can be managed through both init.ora parameters and configuration decisions.

Managing checkpointing has the net effect of managing the amount of redo log records required for recovery. This is the essence of ORACLE recovery tuning, because the time required for ORACLE to recover is determined by:

  • Size of the redo log since the last checkpoint (number of redo log records that need to be applied)

  • Number of data blocks and the ratio of redo log records to data blocks

  • Input/Output Operations Per Second (IOPS) system capabilities

ORACLE has invested heavily in improving recovery time through extensive optimizations and improvements in the code, as well as providing features that allow administrators ease and flexibility in establishing predictable recovery times. Recovery-related init.ora tunables are summarized in TABLE 4.

TABLE 4 ORACLE init.ora Recovery Tunables

ORACLE Release



log_checkpoint_timeout, log_checkpoint_interval, recovery_parallelism


parallel_execution_message_size, log_checkpoint_timeout, log_checkpoint_interval, recovery_parallelism


fast_start_io_target, parallel_execution_message_size, log_checkpoint_timeout, log_checkpoint_interval, recovery_parallelism

Includes incremental (soft) checkpointing.


fast_start_mttr_target, fast_start_io_target, parallel_execution_message_size, log_checkpoint_timeout, log_checkpoint_interval, recovery_parallelism

Prior to the ORACLE 8.1 releases, only hard checkpointing was implemented, meaning that a checkpoint occurred if the log_checkpoint_timeout or log_checkpoint_interval threshold was reached, or a redo log was full and a log switch was required. In ORACLE 8.1, fast start checkpointing was introduced, with the fast_start_io_target init.ora parameter. Using this parameter, administrators can manage incremental (soft) checkpointing. Information on ORACLE fast start checkpointing is available in the Fast-Start: Quick Fault Recovery in ORACLE publication and on the Web at http://otn.oracle.com/deploy/availability/htdocs/fs_chkpt.html.

ORACLE further improved recovery features in ORACLE 9i with the addition of the fast_start_mttr_target init.ora parameter. In the next section, we examine ORACLE parameters.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020