54 lines
3.5 KiB
HTML
54 lines
3.5 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="reference" />
|
|
<meta name="DC.Title" content="Backup and recovery for a distributed relational database" />
|
|
<meta name="abstract" content="In a single-server environment, backup and recovery take place locally. But in a distributed database, backup and recovery also affect remote locations." />
|
|
<meta name="description" content="In a single-server environment, backup and recovery take place locally. But in a distributed database, backup and recovery also affect remote locations." />
|
|
<meta name="DC.subject" content="backup, planning for, recovery, planning" />
|
|
<meta name="keywords" content="backup, planning for, recovery, planning" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1managestrat.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbal1backuprec" />
|
|
<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 for a distributed relational database</title>
|
|
</head>
|
|
<body id="rbal1backuprec"><a name="rbal1backuprec"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Backup and recovery for a distributed relational database</h1>
|
|
<div><p>In a single-server environment, backup and recovery take place
|
|
locally. But in a distributed database, backup and recovery also affect remote
|
|
locations.</p>
|
|
<div class="section"><p>The <span class="keyword">iSeries™ server</span> allows
|
|
individual tables, collections, or groups of collections to be backed up and
|
|
recovered. Although backup and recovery can only be done locally, you might
|
|
want to plan to have less critical data on a server that does not have adequate
|
|
backup support. Backup and recovery procedures must be consistent
|
|
with data that might exist on more than one application server. Because you
|
|
have more than one server in the network, you might want to save such data
|
|
to a second server so that it is always available to the network in some form.
|
|
Strategies such as these need to be planned and laid out specifically before
|
|
a database is distributed across the network.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1managestrat.htm" title="When you are managing a distributed relational database, keep these strategies in mind.">Develop a management strategy for a distributed relational database</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |