60 lines
4.1 KiB
HTML
60 lines
4.1 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="JKLINT backup strategy" />
|
||
|
|
<meta name="abstract" content="JKLINT is the system that JKL uses for their website and e-mail. While this data is critical to their business, it is fairly static-- they don't make a lot of changes to the user profiles or configuration data on the system." />
|
||
|
|
<meta name="description" content="JKLINT is the system that JKL uses for their website and e-mail. While this data is critical to their business, it is fairly static-- they don't make a lot of changes to the user profiles or configuration data on the system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzai8backupscenario.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzai8jklint" />
|
||
|
|
<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>JKLINT backup strategy</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzai8jklint"><a name="rzai8jklint"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">JKLINT backup strategy</h1>
|
||
|
|
<div><p>JKLINT is the system that JKL uses for their website and e-mail.
|
||
|
|
While this data is critical to their business, it is fairly static-- they
|
||
|
|
don't make a lot of changes to the user profiles or configuration data on
|
||
|
|
the system.</p>
|
||
|
|
<br /><img src="rzai8503.jpg" alt="" /><br /><p>They need continuous availability for the critical data on this system,
|
||
|
|
and they accomplish that by having a second system, JKLINT2, that shadows
|
||
|
|
JKLINT. They use a high availability replication solution to copy the data
|
||
|
|
from JKLINT to JKLINT2. Then, if JKLINT goes down, they can switch to JKLINT2.</p>
|
||
|
|
<p>There is no time to bring JKLINT down for a full backup, so Sharon instead
|
||
|
|
backs up JKLINT2, since it is a replication of JKLINT. She does a full backup
|
||
|
|
of JKLINT2 every weekend using the *System backup policy that came with BRMS.
|
||
|
|
She uses the Lotus<sup>®</sup> server
|
||
|
|
policy (QLTSSVR) to do an online backup of their Lotus Notes<sup>®</sup> mail databases every
|
||
|
|
night except the night of the full backup.</p>
|
||
|
|
<p><strong>Another possible setup:</strong> Sharon investigated using logical partitions
|
||
|
|
on JKLINT and JKLINT2 to increase the security of these systems. They could
|
||
|
|
use the a firewall to filter all but e-mail on one partition
|
||
|
|
and all but web traffic on the other partition. Then, the web partition would
|
||
|
|
be protected from any security threats that might come through e-mail, which
|
||
|
|
is a common route of attack. While this setup would have allowed for greater
|
||
|
|
security, it also increased the level of complexity in their network, and
|
||
|
|
Sharon decided that at this point they would stay with the simpler setup.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzai8backupscenario.htm" title="Sharon's backup plan for JKL took into account each server's purpose, workload, and availability requirements.">Scenario: Backup using BRMS</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|