ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajb_5.4.0.1/rzajbrzajbz4backsd.htm

67 lines
4.1 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="Back up packet rules" />
<meta name="abstract" content="It might not seem necessary, but backing up your packet rules is always a good idea. In the event of a loss, your backups can save you the time and work it will take to re-create your files from scratch." />
<meta name="description" content="It might not seem necessary, but backing up your packet rules is always a good idea. In the event of a loss, your backups can save you the time and work it will take to re-create your files from scratch." />
<meta name="DC.Relation" scheme="URI" content="rzajbrzajbx2managingrulessd.htm" />
<meta name="DC.Relation" scheme="URI" content="../books/sc415304.pdf" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzajbz4-back_sd" />
<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 packet rules</title>
</head>
<body id="rzajbz4-back_sd"><a name="rzajbz4-back_sd"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Back up packet rules</h1>
<div><p>It might not seem necessary, but backing up your packet rules is
always a good idea. In the event of a loss, your backups can save you the
time and work it will take to re-create your files from scratch.</p>
<div class="section"><p>These are general tips you can use to ensure that you have an
easy way to replace lost files: </p>
<dl><dt class="dlterm">Print out the filter rules</dt>
<dd>You can store the printouts wherever they are most likely to be secure
and reenter the information as necessary. Printouts are also useful if you
need to search for an error in a filter rule. <p>For instructions on how to
print your packet rules, use the Packet Rules Editor online help.</p>
</dd>
<dt class="dlterm">Copy the information to a disk</dt>
<dd>Copying has an advantage over printouts: rather than reentering manually,
the information exists electronically. It provides you a straightforward method
for transporting information from one online source to another. <div class="note"><span class="notetitle">Note:</span> Your iSeries™ server
copies information to the system disk, not to a diskette. The rules files
are stored in the IFS file system on the iSeries server, not on a personal computer.
You may want to use a disk protection method as a backup means for protecting
the data that is stored on the system disk. </div>
</dd>
</dl>
</div>
<div class="section"><p>When using an iSeries server, you must plan a backup and recovery
strategy.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajbrzajbx2managingrulessd.htm" title="To maintain the security of your system and the integrity of your packet rules, periodically perform the management tasks.">Manage packet rules</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../books/sc415304.pdf" target="_blank">Backup and recovery</a></div>
</div>
</div>
</body>
</html>