friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
8826eae394
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzatl_5.4.0.1/rzatlbackupcert.htm

102 lines
7.8 KiB
HTML
Raw Normal View History

Add readme and dist folders
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="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<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="Backup and recovery considerations" />
<meta name="abstract" content="Regularly back up the Pegasus repository as part of your existing backup plan. In most cases, you can recover a damaged repository by restoring the last backup copy." />
<meta name="description" content="Regularly back up the Pegasus repository as part of your existing backup plan. In most cases, you can recover a damaged repository by restoring the last backup copy." />
<meta name="DC.Relation" scheme="URI" content="rzatlkickoff.htm" />
<meta name="DC.Relation" scheme="URI" content="rzatlsslenable.htm" />
<meta name="DC.Relation" scheme="URI" content="rzatlcimconfig.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaiu/rzaiuintro.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzatlbackupcert" />
<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>Backup and recovery considerations</title>
</head>
<body>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<div class="nested0" id="rzatlbackupcert"><a name="rzatlbackupcert"><!-- --></a><img src="./delta.gif" alt="Start of change" /><h1 class="topictitle1">Backup and recovery considerations</h1>
<div><p>Regularly back up the Pegasus repository as part of your existing
backup plan. In most cases, you can recover a damaged repository by restoring
the last backup copy.</p>
<p>The Pegasus repository is located in the <span class="filepath">qibm/userdata/os400/cim</span> directory
in the integrated file system. Pegasus keeps definitions of the data about
managed objects and their providers in this repository. In addition, other
definitions might be added by clients and providers. </p>
<p>The definitions that are installed with the CIMOM server are as follows:</p>
<img src="./delta.gif" alt="Start of change" /><ul><li>root: The root namespace exists to conform to the DMTF specifications.</li>
<li>root/cimv2: The standard CIM Schemas go here. Also, the schemas for the
shipped providers.</li>
<li>root/PG_Interop: This is for provider registration. This space is reserved
exclusively for providers, and all providers must register here.</li>
<li>root/PG_Internal: This space is reserved for use by the Pegasus CIMOM
server only.</li>
<li>root/ibmsd: The namespace owned and used by IBM<sup>®</sup> Director, shipped with the base operating
system.</li>
</ul><img src="./deltaend.gif" alt="End of change" />
<p><img src="./delta.gif" alt="Start of change" />Pegasus also stores two important configuration files in the <span class="filepath">qibm/userdata/os400/cim</span> directory: <img src="./deltaend.gif" alt="End of change" /></p>
<img src="./delta.gif" alt="Start of change" /><ul><li>cimserver_current.conf. This file contains the current values that are
not defaulted.</li>
<li>cimserver_planned.conf. This file contains planned values, not yet in
effect and that are not defaulted. </li>
</ul><img src="./deltaend.gif" alt="End of change" />
<div class="attention"><span class="attentiontitle">Attention:</span> <img src="./delta.gif" alt="Start of change" />Do not attempt to manually edit the configuration
files. You must use the <span class="parmname">cimconfig</span> command.<img src="./deltaend.gif" alt="End of change" /></div>
<p> If the files in this directory are deleted, moved, or corrupted, you need
to restore them from the backup.</p>
<div class="important"><span class="importanttitle">Important:</span> <img src="./delta.gif" alt="Start of change" /><p> If the latest backed up repository
is from a V5R3 release, do not restore it to a system that has Pegasus V2.5.
After you install Pegasus V2.5 and upgrade the repository, back up the new
repository immediately after the CIM server has been restarted.</p>
<img src="./deltaend.gif" alt="End of change" /></div>
<p><img src="./delta.gif" alt="Start of change" />The server's SSL certificate and private key files are located
in the <span class="filepath">qibm/userdata/os400/cim/ssl/keystore</span> directory.
If you do not have a backup file for the CIM server’s SSL certificate files,
you can <a href="rzatlsslenable.htm#rzatlsslenable">re-create </a> the
certificates.<img src="./deltaend.gif" alt="End of change" /></p>
<div class="p"><img src="./delta.gif" alt="Start of change" />The other directories that are related to the CIM server's
SSL files are as follows: <ul><li>The server's CIM client truststore is located in /qibm/userdata/os400/cim/ssl/truststore.</li>
<li>The server's CIM Export client truststore is located in /qibm/userdata/os400/cim/ssl/exporttruststore.</li>
<li>The server's certificate revocation list is located in /qibm/userdata/os400/cim/ssl/crlstore. </li>
</ul>
<img src="./deltaend.gif" alt="End of change" /></div>
<p><img src="./delta.gif" alt="Start of change" />If you do not have backup files for truststore certificates
or certificate revocation lists, then you must re-create and add them to the
truststore or crlstore by using the <span class="parmname">ssltrustmgr</span> command
from qshell.<img src="./deltaend.gif" alt="End of change" /></p>
<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />Use the ssltrustmgr command to remove corrupted certificates
from the truststore. If the ssltrustmgr command fails to remove the corrupted
certificates, contact your service provider.<img src="./deltaend.gif" alt="End of change" /></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzatlkickoff.htm" title="The Common Information Model (CIM) is a standard developed by a consortium of major hardware and software vendors (including IBM) called the Distributed Management Task Force (DMTF) as part of the Web Based Enterprise Management (WBEM) initiative.">Common Information Model</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzatlcimconfig.htm" title="Configure the startup options for the CIMOM with the cimconfig command.">cimconfig usage information</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzatlsslenable.htm" title="For Pegasus to run in Secure Sockets Layer (SSL) mode, a private key and certificate are required. Pegasus checks for its private key and certificate during startup. If those files do not exist, Pegasus creates its private key and a self-signed 365-day certificate. You can also create a private key and certificate with this information.">Create an SSL key and certificate for Pegasus</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../rzaiu/rzaiuintro.htm">Backup your server topic</a></div>
</div>
</div><img src="./deltaend.gif" alt="End of change" /></div>
</body>
</html>
Reference in New Issue Copy Permalink