<!doctype html>
<html>
<head>
<title>Configuring Backups</title>
<link rel="stylesheet" href="styles/site.css" type="text/css">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" href="styles/icons.css" type="text/css">
<script src="js/jquery.min.js"></script>
<script src="tree/collapsibleTreeMenu.js"></script>
<link href="tree/collapsibleTreeMenu.css" rel="stylesheet" type="text/css">
</head>
<body class="theme-default aui-theme-default">
<div id="page">
<div id="main" class="aui-page-panel">
<div id="main-header">
<div id="breadcrumb-section">
<ol id="breadcrumbs">
<li> <span><a href="Rhapsody-Integration-Engine-6.5_133160975.html">Rhapsody Integration Engine 6.5</a></span> </li>
<li> <span><a href="Installing-or-Upgrading-Rhapsody_133164145.html">Installing or Upgrading Rhapsody</a></span> </li>
<li> <span><a href="Post-installation_133164146.html">Post-installation</a></span> </li>
</ol>
</div>
<h1 id="title-heading" class="pagetitle"> <span id="title-text">Configuring Backups</span> </h1>
</div>
<div id="content" class="view">
<div id="main-content" class="wiki-content group">
<p>The process of backing up refers to the copying and archiving of Rhapsody data. The primary purpose of Rhapsody backups is to recover data after a data loss event, be it by data deletion or corruption. The secondary purpose is to access earlier versions of data according to a site-specific data retention policy. Therefore, it is highly recommended you configure backups, particularly after completing a new installation.</p>
<p>Rhapsody provides internal backup and restore and scheduling tools which create a compressed archive (incremental or full) and place it in a system location for further management by system administrators (for long-term archiving, for example). Backups for the following backup areas are provided:</p>
<ul>
<li>Administration - user and authentication data.</li>
<li>Configuration - the configuration implemented by the engine.</li>
<li>Full - includes all of the active messaging and the state of the historic archive at the time. Caution should be exercised when restoring a full backup, because the engine would already have processed the active messages. Re-processing and re-transmission by the engine may cause problems.</li>
</ul>
<p>Refer to <a href="Backup-and-Restore_133164059.html">Backup and Restore</a> for details on how to configure backups.</p>
<p></p>
<p> </p>
</div>
</div>
</div>
</div>
</body>
</html>