203 lines
12 KiB
HTML
203 lines
12 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="Backing up the integrated file system" />
|
|||
|
|
<meta name="abstract" content="Learn how to improve your integrated file system backups." />
|
|||
|
|
<meta name="description" content="Learn how to improve your integrated file system backups." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu148.htm" />
|
|||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|||
|
|
<meta name="DC.Format" content="XHTML" />
|
|||
|
|
<meta name="DC.Identifier" content="backinguptheintegratedfilesystem" />
|
|||
|
|
<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>Backing up the integrated file system</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="backinguptheintegratedfilesystem"><a name="backinguptheintegratedfilesystem"><!-- --></a>
|
|||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Backing up the integrated file system</h1>
|
|||
|
|
<div><p>Learn how to improve your integrated file system backups.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Use concurrent backup operations</h4><p>Reduce your backup
|
|||
|
|
windows by using multiple concurrent backups. To implement this approach you
|
|||
|
|
will need to determine some way to group your integrated file system data.
|
|||
|
|
Then you need separate SAV commands to concurrently save each of the subsets.
|
|||
|
|
You will need to consider the potential resource contention that can occur
|
|||
|
|
on the hardware resources being used. For example, performing concurrent backups
|
|||
|
|
on groups of data that are stored on the same set of disk units may cause
|
|||
|
|
contention on those disk units. You may decide to use multiple tape drives
|
|||
|
|
or a tape library system with multiple drives to run multiple concurrent SAV
|
|||
|
|
commands. </p>
|
|||
|
|
<p>For more information about concurrent backups, see <a href="rzaiurzaiuparandcon.htm">save to multiple devices</a>.</p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu148.htm">Save file systems</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div><div class="nested1" xml:lang="en-us" id="useonlinebackups"><a name="useonlinebackups"><!-- --></a><h2 class="topictitle2">Use online backups</h2>
|
|||
|
|
<div><p>These topics are things that you can consider to use for online backups.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Use BRMS online backup of Lotus(R) servers support</h4><p>Backup,
|
|||
|
|
Recovery and Media Services (BRMS) supports online backups of Lotus<sup>®</sup> server
|
|||
|
|
databases (such as Domino(TM) and Quickplace(TM)). An online backup is a backup
|
|||
|
|
that you do while your Lotus server databases are in use; there are no save-while-active
|
|||
|
|
synchronization points. You can direct your online backups to a tape device,
|
|||
|
|
media library, save file, or a Tivoli(R) Storage Manager server. BRMS can
|
|||
|
|
also create control groups that make it easy to use concurrent backups. Performing
|
|||
|
|
an online backup does not improve the performance of your backup. However,
|
|||
|
|
since your applications remain active, the duration of the backup is less
|
|||
|
|
important. </p>
|
|||
|
|
<p>For more information about BRMS online backups, see <a href="http://www.ibm.com/servers/eserver/iseries/service/brms/" target="_blank">Backup
|
|||
|
|
Recovery and Media Services</a>. </p>
|
|||
|
|
If you decide to use the BRMS online
|
|||
|
|
backup support, you can tune the performance of the backup to your data. For
|
|||
|
|
more information, see<a href="http://www-1.ibm.com/servers/eserver/iseries/service/brms/domperftune.htm" target="_blank"> performance
|
|||
|
|
tuning</a> on the BRMS web page.</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Use save-while-active</h4><p>The SAV command provides the
|
|||
|
|
SAVACT, SAVACTMSGQ, and SAVACTOPT parameters to support saving objects while
|
|||
|
|
active. </p>
|
|||
|
|
<p>For more information, see <a href="rzaiurzaiu300.htm">save-while-active</a>.</p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="nested1" xml:lang="en-us" id="backuplessdata"><a name="backuplessdata"><!-- --></a><h2 class="topictitle2">Back up less data</h2>
|
|||
|
|
<div><p>These topics are things that you can consider to use for backing up less
|
|||
|
|
data.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Use the CHGPERIOD parameter to only save changed objects</h4><p>The
|
|||
|
|
SAV command provides a <a href="rzaiurzaiu153.htm">CHGPERIOD parameter</a> that
|
|||
|
|
can be used to find and save only objects that have changed. In some cases,
|
|||
|
|
this can be an effective way to reduce the amount of data you need to back
|
|||
|
|
up. However, the system still needs to look at each object to determine which
|
|||
|
|
objects have changed. If you have many files it may still take a long time
|
|||
|
|
to determine which objects have changed. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Structure your directories to easily back up new files, omit
|
|||
|
|
data, or your group your data</h4><p>It may be beneficial to consider
|
|||
|
|
your backup strategy when you structure and name your directories. You may
|
|||
|
|
be able to group and name your files in some way that will make it easier
|
|||
|
|
to include or omit groups of directories or objects from your backups. You
|
|||
|
|
might want to group the directories such that you can back up all of the directories
|
|||
|
|
and files for an application, a user, or specified time period. </p>
|
|||
|
|
<p>For
|
|||
|
|
example, if you are creating many files each day or each week, it might be
|
|||
|
|
useful to create a directory to contain the new files. Consider implementing
|
|||
|
|
a naming convention for the directories such that you can back up only the
|
|||
|
|
directory that contains the new objects or omit older directories. </p>
|
|||
|
|
<div class="p">Example:
|
|||
|
|
Create a directory structure that uses the year, month, and week to store
|
|||
|
|
new objects.<pre>/2003
|
|||
|
|
/2003/01/01
|
|||
|
|
/2003/01/01
|
|||
|
|
/2003/01/02
|
|||
|
|
/2003/01/03
|
|||
|
|
/2003/01/04
|
|||
|
|
/2003/02</pre>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Omit objects from the backup</h4><p>The SAV command provides
|
|||
|
|
the OBJ parameter that specifies the objects to be included and omitted from
|
|||
|
|
the backup. The OBJ parameter lets you specify a list of 300 values to be
|
|||
|
|
included or omitted from the SAV command. The values can be either specific
|
|||
|
|
directories or objects or generic values that provide wild card support for
|
|||
|
|
the objects to be included or omitted. </p>
|
|||
|
|
<div class="p">Here are some examples of reasons
|
|||
|
|
why you might want to omit a directory or object from your backup: <ul><li>The directory or object is temporary and is not required if you need to
|
|||
|
|
recover your system. </li>
|
|||
|
|
<li>The directory or object is already backed up and has not changed since
|
|||
|
|
the last full backup.</li>
|
|||
|
|
<li>You are trying to group your integrated file system data so you can run
|
|||
|
|
multiple concurrent SAV commands.</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Pattern Parameter</h4><p>The SAV command provides the PATTERN
|
|||
|
|
parameter which lets you specify a list of 300 values which are used to group
|
|||
|
|
the save by either including or omitting objects which qualify for the save
|
|||
|
|
based on the OBJ parameter. The values can be either specific object names
|
|||
|
|
or generic values that provide wild card support for the objects to be included
|
|||
|
|
or omitted. </p>
|
|||
|
|
<div class="p">Here are some examples of reasons why you might want to
|
|||
|
|
include or omit objects which qualify for the save based on the OBJ parameter:<ul><li>You want to save an entire directory tree, but omit objects of a specific
|
|||
|
|
type or name.</li>
|
|||
|
|
<li>You want to save all objects of a specific type without specifying which
|
|||
|
|
directories they may reside in.</li>
|
|||
|
|
</ul>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> While less data may be saved, the amount of time to save the data
|
|||
|
|
may be increased. If patterns are specified on the PATTERN parameter, any
|
|||
|
|
object which qualifies for the save is compared to the list of objects on
|
|||
|
|
the PATTERN parameter.</div>
|
|||
|
|
For more information about the SAV command parameters,
|
|||
|
|
see <a href="../cl/sav.htm">SAV</a> in the Programming
|
|||
|
|
topic of the iSeries™ Information
|
|||
|
|
Center. </div>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Journal changes and save journal receivers</h4><p>You can
|
|||
|
|
journal changes to directories, stream files, and symbolic links. If you implement
|
|||
|
|
journaling on your integrated file system data, you may need to change your
|
|||
|
|
save strategy. Your new strategy should be to back up the objects less frequently
|
|||
|
|
and instead back up the journal receivers that contain the changes you’ve
|
|||
|
|
made to the objects. This could reduce the amount of data you need to back
|
|||
|
|
up. However, you will need to understand and consider the implications to
|
|||
|
|
your recovery procedures. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Implement Hierarchical Storage Management (HSM)</h4><p>If
|
|||
|
|
you have historical integrated file system data that is infrequently needed
|
|||
|
|
you might benefit from implementing Hierarchical Storage Management. Hierarchical
|
|||
|
|
Storage Management (HSM) automatically and transparently manages customer
|
|||
|
|
data across a storage hierarchy. The storage hierarchy can consist of high
|
|||
|
|
performance disk, compressed disk, and tape libraries. </p>
|
|||
|
|
<p>When and how
|
|||
|
|
often data is accessed on your server depends on the type of data. A set of
|
|||
|
|
data that is currently being used may be accessed many times a day (hot data),
|
|||
|
|
or it may have become historical data which is accessed less frequently (cold
|
|||
|
|
data). </p>
|
|||
|
|
<p>Through the Backup, Recovery and Media Services (BRMS) user-defined
|
|||
|
|
policies, HSM can migrate or archive and dynamically retrieve infrequently
|
|||
|
|
used data or historical data up or down a hierarchy of storage devices</p>
|
|||
|
|
<p>For
|
|||
|
|
more information, see <a href="http://www.ibm.com/servers/eserver/iseries/hsmcomp/" target="_blank">Hierarchical
|
|||
|
|
Storage Management.</a>.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Save to save files (SAVF) then save the SAVFs to tape with
|
|||
|
|
SAVSAVFDTA</h4><p>Some customers have found that they can reduce their
|
|||
|
|
backup window by first backing up their data to a save file (SAVF) rather
|
|||
|
|
than saving directly to tape. Significant performance improvements were made
|
|||
|
|
to backups to save files. Of course if you back up to a save file, you need
|
|||
|
|
to have adequate disk space available for the save file. Chapter 15 of the<a href="../books/sc410607.pdf" target="_blank"> iSeries Performance Capabilities Reference</a> can
|
|||
|
|
help you evaluate this approach on your system. You also will need to back
|
|||
|
|
up your save files to tape by using the Save Save File Data (SAVSAVFDTA) command.
|
|||
|
|
However, the <a href="../cl/savsavfdta.htm">SAVSAVFDTA </a> command
|
|||
|
|
does not need to be completed during your backup window. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Reduce or eliminate auditing during backup or recovery operations</h4><p>Measurements
|
|||
|
|
show that performing security auditing during save or restore operations (*SAVRST
|
|||
|
|
auditing) can decrease performance. Auditing provides valuable information
|
|||
|
|
about the actions being performed on your system and who is performing those
|
|||
|
|
actions. However, you need to balance the value of that information against
|
|||
|
|
the time you have available to perform a backup or recovery. This is especially
|
|||
|
|
true if you need to recover all or many objects in the integrated file system. </p>
|
|||
|
|
<p>For
|
|||
|
|
more information about security auditing, see chapter 9 of <a href="../books/sc415302.pdf" target="_blank">Security Reference</a>. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Reduce number of objects scanned during the backup</h4><p>Specifying
|
|||
|
|
the SCAN parameter during the backup may have significant performance impacts
|
|||
|
|
if scanning is enabled on the system. Scanning objects may be a valuable part
|
|||
|
|
of your system security, but you need to consider the amount of time scanning
|
|||
|
|
will add to your backup window.</p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
|
|||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
|||
|
|
</html>
|