70 lines
4.3 KiB
HTML
70 lines
4.3 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="task" />
|
||
|
<meta name="DC.Title" content="Back up the intrusion detection policy file" />
|
||
|
<meta name="abstract" content="You should back up your intrusion detection (IDS) policies to eliminate the need to re-create your policies in the event of a server outage or power loss." />
|
||
|
<meta name="description" content="You should back up your intrusion detection (IDS) policies to eliminate the need to re-create your policies in the event of a server outage or power loss." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaubsetup.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415304.pdf" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzaubbackup" />
|
||
|
<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 the intrusion detection policy file</title>
|
||
|
</head>
|
||
|
<body id="rzaubbackup"><a name="rzaubbackup"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Back up the intrusion detection policy file</h1>
|
||
|
<div><p>You should back up your intrusion detection (IDS) policies to eliminate
|
||
|
the need to re-create your policies in the event of a server outage or power
|
||
|
loss.</p>
|
||
|
<div class="p"> Your IDS policies can be stored locally or exported to a directory
|
||
|
server. You must back up the IDS policies in the following directories: <ul class="simple"><li><span class="filepath">QIBM/UserData/OS400/QOS/ETC</span></li>
|
||
|
<li><span class="filepath">QIBM/ProdData/OS400/QOS/</span></li>
|
||
|
</ul>
|
||
|
You must also back up your directory server publishing agent for the
|
||
|
QoS server. The publishing agent contains the directory server name, the distinguished
|
||
|
name (DN) for the QoS server, port used to access the directory server, and
|
||
|
authentication information. In the event of a loss, your backups can save
|
||
|
you the time and work it takes to re-create your policies from scratch.</div>
|
||
|
<div class="section">Follow these steps to ensure that you can easily replace lost IDS
|
||
|
policies:</div>
|
||
|
<ol><li class="stepexpand"><span><strong>Use integrated file systems backup and recovery
|
||
|
programs.</strong></span> <p>The <cite>Backup and recovery</cite> book provides
|
||
|
instructions on conducting backups from integrated file systems.</p>
|
||
|
</li>
|
||
|
<li class="stepexpand"><span><strong>Print out the policies.</strong></span> <p>You can
|
||
|
store the printouts wherever they are most likely to be secure and re-enter
|
||
|
the information as necessary.</p>
|
||
|
</li>
|
||
|
<li class="stepexpand"><span><strong>Copy the information to a disk.</strong></span> <p>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.</p>
|
||
|
</li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaubsetup.htm" title="Learn how to set up an intrusion detection policy for the first time.">Set up a new intrusion detection policy</a></div>
|
||
|
</div>
|
||
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
<div><a href="../books/sc415304.pdf" target="_blank">Backup and Recovery PDF</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|