112 lines
6.4 KiB
HTML
112 lines
6.4 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="topic" />
|
||
|
|
<meta name="DC.Title" content="Backup options for virtual and directly attached disk" />
|
||
|
|
<meta name="abstract" content="Read to learn about backup options for virtual and directly attached disks for Linux and i5/OS utilities." />
|
||
|
|
<meta name="description" content="Read to learn about backup options for virtual and directly attached disks for Linux and i5/OS utilities." />
|
||
|
|
<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="rzalmbackupoptions" />
|
||
|
|
<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 options for virtual and directly attached disk</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalmbackupoptions"><a name="rzalmbackupoptions"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Backup options for virtual and directly attached disk</h1>
|
||
|
|
<div><p>Read to learn about backup options for virtual and directly attached
|
||
|
|
disks for Linux and i5/OS<sup>®</sup> utilities.</p>
|
||
|
|
<p>There are two types of options for backing up and recovering data involving
|
||
|
|
Linux partitions on the iSeries™ server:</p>
|
||
|
|
<ul><li>Utilities that run within Linux</li>
|
||
|
|
<li>Commands that run within i5/OS</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Utilities that run within Linux</h4><p>Utilities that run
|
||
|
|
within Linux benefit those users who have Linux installed to a native disk
|
||
|
|
and those users who cannot vary off their Linux partition while they are backing
|
||
|
|
up data. The most common data backup utility in Linux is the tar (a contraction
|
||
|
|
of tape archive) utility. The tar utility archives files and directories into
|
||
|
|
one file that you can save in either of two ways: </p>
|
||
|
|
<ul><li>You can write the file directly to a virtual or directly attached tape
|
||
|
|
device. For information about this alternative, see <a href="rzalmsaverestore.htm">Save and restore hosted Linux files to and from the host's shared tape drive</a>.</li>
|
||
|
|
<li>You can write the file to a file in the partition's file system. Following
|
||
|
|
is an example of this alternative.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Example:</span> <var class="varname">tar -cvf /tmp/etc.tar
|
||
|
|
/etc</var></div>
|
||
|
|
<p>Where, in the above example:</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e54">Variable</th>
|
||
|
|
<th valign="top" id="d0e56">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e54 "><var class="varname">c</var></td>
|
||
|
|
<td valign="top" headers="d0e56 ">create a tar file</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e54 "><var class="varname">v</var></td>
|
||
|
|
<td valign="top" headers="d0e56 ">verbose (show the files that are being added to the
|
||
|
|
tar file</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e54 "><var class="varname">f</var></td>
|
||
|
|
<td valign="top" headers="d0e56 ">name of the tar file follows</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e54 "><var class="varname">/tmp/etc.tar</var></td>
|
||
|
|
<td valign="top" headers="d0e56 ">name of the tar file</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e54 "><var class="varname">/etc</var></td>
|
||
|
|
<td valign="top" headers="d0e56 ">object to be added to the tar file</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Since <var class="varname">/etc</var> is a directory, the utility adds
|
||
|
|
all the contents of the directory and its subdirectories to the tar file.</div>
|
||
|
|
<p>After
|
||
|
|
you create the tar, you can save it to an offline medium in several ways,
|
||
|
|
including writing it to a virtual or directly attached tape device or copying
|
||
|
|
it to the IFS for inclusion in a subsequent save/restore operation.</p>
|
||
|
|
<p>You
|
||
|
|
can tar the data on a Linux partition during normal server usage, and you
|
||
|
|
can easily automate and start the tar utility by using the partition's cron
|
||
|
|
daemon (a scheduling mechanism for Linux; cron is an abbreviation of chronology).
|
||
|
|
You can also use the at utility to schedule a single backup request. For example,
|
||
|
|
if you want to use the tar utility to back up the /etc directory at 10 p.m.
|
||
|
|
on the 19th of September, you could enter the following Linux command:</p>
|
||
|
|
<blockquote><pre>at 10pm Sep 19 -f tar.command</pre>
|
||
|
|
</blockquote>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> For
|
||
|
|
additional information about the tar, at, and cron utilities, use the Linux
|
||
|
|
man (an abbreviation for manual) command. For example, <kbd class="userinput">man tar</kbd></div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">i5/OS commands</h4><p>Users
|
||
|
|
of virtual disks also have powerful tools to use in i5/OS for backup and recovery. They can
|
||
|
|
use the Save Object (SAV) and Restore Object (RST) commands to save and restore
|
||
|
|
entire virtual disks in their current state.</p>
|
||
|
|
<p>The SAV command saves the
|
||
|
|
directory that has the same name as the virtual disk under the QFPNWSSTG directory
|
||
|
|
in the integrated file system. This method of backup and recovery is most
|
||
|
|
effective if the Linux kernel is saved in a PrEP start partition on the virtual
|
||
|
|
disk. On most Linux distributions, this normally occurs as part of a default
|
||
|
|
installation.</p>
|
||
|
|
<p>If you save the Linux kernel in a PrEP partition, you
|
||
|
|
can restore and start the Linux partition after a total iSeries reinstallation.
|
||
|
|
You can also transport and restore saved virtual disks to other iSeries servers
|
||
|
|
via FTP and tape.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|