87 lines
6.0 KiB
HTML
87 lines
6.0 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="Back up less data" />
|
||
|
|
<meta name="abstract" content="You can reduce planned outages by backing up smaller amounts of data at different times. There are several ways that you can isolate the data on your system for this type of operation." />
|
||
|
|
<meta name="description" content="You can reduce planned outages by backing up smaller amounts of data at different times. There are several ways that you can isolate the data on your system for this type of operation." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwbackup_window.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="rzalwpieces" />
|
||
|
|
<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>Back up less data</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalwpieces"><a name="rzalwpieces"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Back up less data</h1>
|
||
|
|
<div><p>You can reduce planned outages by backing up smaller amounts of
|
||
|
|
data at different times. There are several ways that you can isolate the data
|
||
|
|
on your system for this type of operation. </p>
|
||
|
|
<div class="p"><div class="note"><span class="notetitle">Note:</span> You can use <a href="../rzai8/rzai8overview.htm">Backup,
|
||
|
|
Recovery and Media Services</a> to perform all of these kinds of backups.</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Incremental backups</h4><p>Incremental backups enable you
|
||
|
|
to save changes to objects since the last time they were backed up. There
|
||
|
|
are two types of incremental backups: cumulative and changes-only. A <dfn class="term">Cumulative
|
||
|
|
backup</dfn> specifies a backup that includes all changed objects and new
|
||
|
|
objects since the last full backup." save the changes to an object since the
|
||
|
|
last full backup of that object. This is useful for objects that do not change
|
||
|
|
very often, or do not change greatly between full backups. A <dfn class="term">changes-only
|
||
|
|
backup</dfn> includes all changed objects and new objects since the last
|
||
|
|
incremental or full backup.</p>
|
||
|
|
<p> Incremental backups are especially useful
|
||
|
|
for data that changes frequently. For example, you do a full backup every
|
||
|
|
Saturday night. You have some libraries that are used extensively and so you
|
||
|
|
need to back them up more frequently than once a week. You can use incremental
|
||
|
|
backups on the other nights of the week instead of doing a full backup to
|
||
|
|
capture them. This will shorten your backup window while also ensuring that
|
||
|
|
you have a backup of the latest version of those libraries.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Security data and configuration data</h4><p>You can also
|
||
|
|
reduce planned outages by isolating certain kinds of data and then backing
|
||
|
|
it up separately. Security data includes user profiles, authorization lists,
|
||
|
|
and authority holders. Configuration data includes information about how your
|
||
|
|
server is set up, such as line descriptions, device descriptions, and configuration
|
||
|
|
lists. These types of data are saved as part of a full system backup, but
|
||
|
|
you can also save them separately without having to shut your system down.
|
||
|
|
For details on how to back up these types of data, see <a href="../rzaiu/rzaiurzaiu001.htm">Manually save parts of your server</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Omit certain items</h4><p>You can also reduce your backup
|
||
|
|
window by reducing the number of objects you save or preventing objects from
|
||
|
|
being saved more than once. You can do this by choosing to omit certain objects
|
||
|
|
from a backup. For example, you may want to save all user libraries except
|
||
|
|
for temporary libraries. You can choose to omit all temporary libraries from
|
||
|
|
your backup, which will shorten the length of backup processing. Many of the
|
||
|
|
commands that you use to save your system give you the option to omit items
|
||
|
|
from the backup. For details on these commands, see <a href="../rzaiu/rzaiusavecommands.htm">Commands
|
||
|
|
to save parts of your server</a> and <a href="../rzaiu/rzaiurzaiu154.htm">Commands
|
||
|
|
to save specific object types</a>. You can also use <a href="../rzai8/rzai8overview.htm">Backup, Recovery and Media Services</a> to
|
||
|
|
omit items from a backup.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">Data archiving</h4><p>Data that is not needed
|
||
|
|
for normal production can be archived and taken offline. It is brought online
|
||
|
|
only when needed, perhaps for month-end or quarter-end processing. The daily
|
||
|
|
backup window is reduced since the archived data is not included.</p>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwbackup_window.htm" title="By reducing the amount of time it takes to complete your backups, you can also reduce the amount of time your system is unavailable.">Shorten backup windows</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|