Skip to main content

Recovery

  • Chapter
  • First Online:
A Course in In-Memory Data Management
  • 1496 Accesses

Abstract

To handle steadily growing volumes of data and intensifying workloads, modern enterprise systems have to scale out, using multiple servers within the enterprise system landscape. With the growing number of servers—and consequently growing number of racks and CPUs—the probability of hardware-induced failures is rising.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 74.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 99.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Reference

  1. J. Wust, J.-H. Boese, F. Renkes, S. Blessing, J. Krueger, H. Plattner. Efficient logging for enterprise workloads on column-oriented in-memory databases, in CIKM 2012 (ACM, 2012)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Hasso Plattner .

Self Test Questions

Self Test Questions

 

  1. 1.

    Recovery

    What is recovery?

    1. (a)

      It is the process of recording all data during the run time of a system

    2. (b)

      It is the process of restoring a server to the last consistent state before its crash

    3. (c)

      It is the process of improving the physical layout of database tables to speed up queries

    4. (d)

      It is the process of cleaning up main memory, that is “recovering” space.

  2. 2.

    Server Failure

    What happens in the situation of a server failure?

    1. (a)

      The system has to be rebooted and restored if possible, while another server takes over the workload

    2. (b)

      The power supply is switched to backup power supply so the data within the main memory of the server is not lost

    3. (c)

      The failure of a server has no impact whatsoever on the workload

    4. (d)

      All data is saved to persistent storage in the last moment before the server shuts down.

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Plattner, H. (2013). Recovery. In: A Course in In-Memory Data Management. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-36524-9_29

Download citation

Publish with us

Policies and ethics