77 lines
5.3 KiB
HTML
77 lines
5.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="concept" />
|
|
<meta name="DC.Title" content="Considerations for restoring objects saved with SAVSTG" />
|
|
<meta name="abstract" content="If you restore a system from Save Storage (SAVSTG) media, the primary remote journal function concerns have to do with configuration changes involving additionally defined remote journals." />
|
|
<meta name="description" content="If you restore a system from Save Storage (SAVSTG) media, the primary remote journal function concerns have to do with configuration changes involving additionally defined remote journals." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisaverestre.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/savstg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirsavconsidrcv.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakirsavstg" />
|
|
<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>Considerations for restoring objects saved with SAVSTG</title>
|
|
</head>
|
|
<body id="rzakirsavstg"><a name="rzakirsavstg"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Considerations for restoring objects saved with SAVSTG</h1>
|
|
<div><p>If you restore a system from Save Storage (SAVSTG) media, the primary
|
|
remote journal function concerns have to do with configuration changes involving
|
|
additionally defined remote journals.</p>
|
|
<p>These remote journals were established after the SAVSTG media was produced.
|
|
If a primary system is restored from SAVSTG media, journal receivers can be
|
|
restored back to the primary system from versions saved from any of the associated
|
|
remote journals in the remote journal environment. If a backup system is restored
|
|
from SAVSTG media, then the catch-up phase for activating the remote journal
|
|
can replicate all necessary journal receivers that are still online from the
|
|
primary system to the restored backup system. Those journal receivers that
|
|
are not online, and were attached to a *TYPE1 remote journal, can be restored
|
|
back to the backup system. They can be restored from any saved versions of
|
|
the journal receivers that were previously taken from one of the following:</p>
|
|
<ul><li>The primary system</li>
|
|
<li>Any of the associated remote journals in the remote journal environment</li>
|
|
</ul>
|
|
<p>See the Rules for saving and restoring journal receivers link below for
|
|
the journal receiver restore rules which is typically used for this type of
|
|
restore.</p>
|
|
<p>Another consideration occurs as part of the processing that is performed
|
|
by the system when restoring journal receivers. Before associating a journal
|
|
receiver with a local journal and retaining any remote journal information,
|
|
the journal library name, and the system name or the independent disk pool
|
|
name must be correct. This allows the system to differentiate between a local
|
|
journal that was originally created and one that was restored to a different
|
|
physical system using SAVSTG media. This case assumes that the user assigns
|
|
a new system name as part of the SAVSTG procedure.</p>
|
|
<p><img src="./delta.gif" alt="Start of change" />In one example case, the system was restored using
|
|
SAVSTG media but was not restored to the same physical system. However, the
|
|
restored system still had the same name as the system from where the media
|
|
was produced. This situation can cause problems and should be avoided.<img src="./deltaend.gif" alt="End of change" /></p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakisaverestre.htm" title="The following information describes general considerations for save and restore operations with remote journals:">Considerations for save and restore operations with remote journals</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakirsavconsidrcv.htm" title="The restore relationships for journal receivers associated with remote journals are described in this topic.">Rules for saving and restoring journal receivers</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/savstg.htm">Save Storage (SAVSTG) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |