113 lines
7.7 KiB
HTML
113 lines
7.7 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Recover lost data after an unplanned outage" />
|
|
<meta name="abstract" content="You may lose data as a result of an unplanned outage, such as a disk failure. The most extreme example of data loss is losing your entire site, such as what might happen as a result of a natural disaster." />
|
|
<meta name="description" content="You may lose data as a result of an unplanned outage, such as a disk failure. The most extreme example of data loss is losing your entire site, such as what might happen as a result of a natural disaster." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_unplanned.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzalwlost_data" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Recover lost data after an unplanned outage</title>
|
|
</head>
|
|
<body id="rzalwlost_data"><a name="rzalwlost_data"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Recover lost data after an unplanned outage</h1>
|
|
<div><p>You may lose data as a result of an unplanned outage, such as a
|
|
disk failure. The most extreme example of data loss is losing your entire
|
|
site, such as what might happen as a result of a natural disaster. </p>
|
|
<p> There are a few ways that you can prevent your data from being lost in
|
|
these situations or at least limit the amount of data that is lost.</p>
|
|
<div class="section"><h4 class="sectiontitle">Backup and recovery</h4><p>It is imperative that you have
|
|
a proven strategy for backing up your server; the time and money you spend
|
|
creating this strategy is more than recovered should you need to restore lost
|
|
data or perform a recovery. Once you have created a strategy, you must ensure
|
|
that it works by testing it, which involves performing a backup and recovery
|
|
and then validating that your data was backed up and restored correctly. If
|
|
you change anything on your server, you need to assess whether your backup
|
|
and recovery strategy needs to change.</p>
|
|
<p>Every system and business environment
|
|
is different, but, ideally, you should try to do a full backup of your system
|
|
at least once a week. If you have a very dynamic environment, you will also
|
|
have to back up changes to objects on your system since the last backup. Then,
|
|
if you have an unexpected outage and need to recover those objects, you can
|
|
recover the latest version of them.</p>
|
|
<p>For guidance on how to create a
|
|
backup and recovery strategy, see <a href="../rzaj1/rzaj1overview.htm">Plan
|
|
a backup and recovery strategy</a>. For instructions on how to perform
|
|
backups on your server, see <a href="../rzaiu/rzaiuintro.htm">Back
|
|
up your server</a>. For information on how to restore your server, see
|
|
<a href="../rzaiu/rzaiurecover.htm">Recover your server</a>.</p>
|
|
<p>If
|
|
you would like a solution to help you manage your backup and recovery strategy
|
|
and your backup media, you can use Backup, Recovery and Media Services (BRMS).
|
|
<dfn class="term">BRMS</dfn> is a program that helps you implement a disciplined approach
|
|
to managing your backups, and provides you with an orderly way to retrieve
|
|
lost or damaged data. Using BRMS, you can manage your most critical and complex
|
|
backups, including online backups of Lotus<sup>®</sup> servers, simply and easily. You
|
|
can also recover your system fully in the event of a disaster or failure.</p>
|
|
<p>In
|
|
addition to these backup and recovery features, BRMS enables you to track
|
|
all of your backup media from creation to expiration. You no longer have to
|
|
keep track of which backup items are on which volumes, and worry that you
|
|
will accidentally write over active data. You can also track the movement
|
|
of your media to and from offsite locations.</p>
|
|
<p>For detailed information
|
|
on the tasks that BRMS can help you perform, see <a href="../rzai8/rzai8overview.htm">Backup,
|
|
Recovery and Media Services</a>.</p>
|
|
<p>For help in planning and managing
|
|
your backup and recovery strategy, contact <a href="http://www.ibm.com/services/continuity/recover1.nsf/documents/home" target="_blank">IBM<sup>®</sup> Business Continuity and Recovery Services</a> <img src="www.gif" alt="Link outside Information Center" />.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Limit the amount of data that is lost</h4><p>You can group
|
|
your disk drives into logical subsets called <dfn class="term">disk pools</dfn> (also
|
|
known as auxiliary storage pools or ASPs). The data in one disk pool is isolated
|
|
from the data in the other disk pools. If a disk unit fails, you only have
|
|
to recover the data that was stored in the disk pool that the failed disk
|
|
unit was a part of.</p>
|
|
<p>For detailed information on disk pools, disk pool
|
|
types, and examples of how to use disk pools for different purposes, see <a href="../rzaly/rzalyaspsovrvw.htm">Disk pools</a>. For information
|
|
on how to configure disk units and disk pools, see <a href="../rzaly/rzalydmkickoff.htm">Disk
|
|
management</a>.</p>
|
|
<p> <span class="uicontrol">Independent disk pools</span> are
|
|
disk pools that can be brought online or taken offline without any dependencies
|
|
on the rest of the storage on a system. This is possible because all of the
|
|
necessary system information associated with the independent disk pool is
|
|
contained within the independent disk pool. Independent disk pools offer a
|
|
number of availability and performance advantages in both single and multiple
|
|
system environments. For detailed information, see <a href="../rzaly/rzalyoverview.htm">Independent
|
|
disk pools</a>.</p>
|
|
<p><img src="./delta.gif" alt="Start of change" /><strong>Logical partitions</strong> provide the
|
|
ability to divide one system into several independent systems. The use of
|
|
logical partitions is another way that you can isolate data, applications,
|
|
and other resources. You can use logical partitions to improve the performance
|
|
of your server, such as by running batch and interactive processes on different
|
|
partitions. You can also protect your data by installing a critical application
|
|
on a partition apart from other applications. Then, if another partition fails,
|
|
that program is protected.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
<p>For detailed information on logical partitions
|
|
and how to use them, see <a href="../rzait/rzaiticlpar.htm">Logical
|
|
partitions</a>.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwshorten_unplanned.htm" title="Unplanned outages do occur, and a key to availability is to ensure that when they do occur you can recover from them as quickly as possible.">Shorten unplanned outages</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |