<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>RedHatVN Network &#187; backup</title>
	<atom:link href="http://redhatvn.net/tag/backup/feed" rel="self" type="application/rss+xml" />
	<link>http://redhatvn.net</link>
	<description>Shared Linux problems</description>
	<lastBuildDate>Tue, 07 Sep 2010 08:08:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Shrinking ext3 partition</title>
		<link>http://redhatvn.net/shrinking-ext3-partition</link>
		<comments>http://redhatvn.net/shrinking-ext3-partition#comments</comments>
		<pubDate>Fri, 25 Dec 2009 03:51:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Centos]]></category>
		<category><![CDATA[Cpanel]]></category>
		<category><![CDATA[Directadmin]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[backup]]></category>

		<guid isPermaLink="false">http://redhatvn.net/?p=949</guid>
		<description><![CDATA[*** Make sure you have a back up prior to proceeding. *** Boot into rescue mode. Unmount partition if mounted and check disk: umount /dev/sda1 e2fsck -vn /dev/sda1 Remove journaling from ext3 partition and revert to ext2, as resize2fs does not work on ext3 partition. (Note: This step should not be necessary in recent kernels.) [...]]]></description>
			<content:encoded><![CDATA[<p>*** Make sure you have a back up prior to proceeding. ***<br />
<span id="more-949"></span></p>
<ol>
<li>Boot into rescue mode.</li>
<li>Unmount partition if mounted and check disk:
<div><code>umount /dev/sda1<br />
e2fsck -vn /dev/sda1</code></div>
</li>
<li>Remove journaling from ext3 partition and revert to ext2, as resize2fs does not work on ext3 partition. (Note: This step should not be necessary in recent kernels.)
<div><code>tune2fs -O ^has_journal /dev/sda1</code></div>
</li>
<li>Force check the partition:
<div><code>e2fsck -vf /dev/sda1</code></div>
</li>
<li>Resize the partition making sure that you don&#8217;t shrink it lesser than the disk space currently used else you may lose data.
<div><code>resize2fs /dev/sda1 6000M</code></div>
</li>
<li>Make a note of the blocks and block size. You can also run:
<div><code>dumpe2fs /dev/sda1</code></div>
</li>
<li>Delete /dev/sda1 partition and create a smaller one with fdisk:
<div><code>fdisk /dev/sda</code></div>
</li>
<li>Recreate the partition /dev/sda1 with the starting point at the default location and the ending point at number of blocks from the resize2fs output (1536000) multiplied by the size of a block (4K). So, the end point would be 1536000 * 4 = 6144000K.</li>
<li>Run partprobe and resize2fs utility with no size arguments:
<div><code>partprobe /dev/sda<br />
resize2fs /dev/sda1</code></div>
<p>Note: If resize2fs errors out, you may need to further increase the block size by a small percentage (3 to 5%).</li>
<li>Run a disk check for the final time before restoring the journal.
<div><code>e2fsck -vn /dev/sda1<br />
tune2fs -j /dev/sda1</code></div>
</li>
<li>Reboot and check everything in file-system is intact.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://redhatvn.net/shrinking-ext3-partition/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Extending ext3 partition</title>
		<link>http://redhatvn.net/extending-ext3-partition</link>
		<comments>http://redhatvn.net/extending-ext3-partition#comments</comments>
		<pubDate>Fri, 25 Dec 2009 03:52:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Centos]]></category>
		<category><![CDATA[Cpanel]]></category>
		<category><![CDATA[Directadmin]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[backup]]></category>

		<guid isPermaLink="false">http://redhatvn.net/?p=952</guid>
		<description><![CDATA[*** Make sure you have a back up prior to proceeding. *** Boot into rescue mode. Unmount partition if mounted and check disk: umount /dev/sda1 e2fsck -vn /dev/sda1 Delete /dev/sda1 partition and create a bigger one with fdisk: fdisk /dev/sda Recreate the partition /dev/sda1 with the starting point at the default location and the ending [...]]]></description>
			<content:encoded><![CDATA[<p>*** Make sure you have a back up prior to proceeding. ***<br />
<span id="more-952"></span></p>
<ol>
<li>Boot into rescue mode.</li>
<li>Unmount partition if mounted and check disk:
<div><code>umount /dev/sda1<br />
e2fsck -vn /dev/sda1</code></div>
</li>
<li>Delete /dev/sda1 partition and create a bigger one with fdisk:
<div><code>fdisk /dev/sda</code></div>
</li>
<li>Recreate the partition /dev/sda1 with the starting point at the default location and the ending point at highest possible cylinder. (Note: if you are extending by merging two partitions, the data in the second partition is lost so make sure to backup data you need.)</li>
<li>Run partprobe and resize2fs utility with no size arguments:
<div><code>partprobe /dev/sda<br />
resize2fs /dev/sda1</code></div>
</li>
<li>Reboot and check everything in file-system is intact.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://redhatvn.net/extending-ext3-partition/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows Server Backup Step-by-Step Guide for Windows Server 2008</title>
		<link>http://redhatvn.net/windows-server-backup-step-by-step-guide-for-windows-server-2008</link>
		<comments>http://redhatvn.net/windows-server-backup-step-by-step-guide-for-windows-server-2008#comments</comments>
		<pubDate>Wed, 02 Dec 2009 09:12:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Windows]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[win2k8]]></category>

		<guid isPermaLink="false">http://redhatvn.net/?p=705</guid>
		<description><![CDATA[The Windows Server Backup feature provides a basic backup and recovery solution for computers running the Windows Server® 2008 operating system. Windows Server Backup introduces new backup and recovery technology and replaces the previous Windows Backup (Ntbackup.exe) feature that was available with earlier versions of the Windows operating system. What is Windows Server Backup? The Windows Server Backup feature [...]]]></description>
			<content:encoded><![CDATA[<p>The Windows Server Backup feature provides a basic backup and recovery solution for computers running the Windows Server® 2008 operating system. Windows Server Backup introduces new backup and recovery technology and replaces the previous Windows Backup (Ntbackup.exe) feature that was available with earlier versions of the Windows operating system.<br />
<span id="more-705"></span></p>
<h2>What is Windows Server Backup?</h2>
<div id="sectionSection0">
<p>The Windows Server Backup feature in Windows Server 2008 consists of a Microsoft Management Console (MMC) snap-in and command-line tools that provide a complete solution for your day-to-day backup and recovery needs. You can use four wizards to guide you through running backups and recoveries. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, or the system state. You can recover volumes, folders, files, certain applications, and the system state. And, in case of disasters like hard disk failures, you can perform a system recovery, which will restore your complete system onto the new hard disk, by using a full server backup and the Windows Recovery Environment.</p>
<p>You can use Windows Server Backup to create and manage backups for the local computer or a remote computer. You can also schedule backups to run automatically and you can perform one-time backups to augment the scheduled backups.</p>
<div>
<table border="0">
<tbody>
<tr>
<th align="left"> <img src="http://i.technet.microsoft.com/cc770266.Important%28en-us,WS.10%29.gif" alt="Important" />Important</th>
</tr>
<tr>
<td>Windows Server Backup is available in all editions of Windows Server 2008 (both 32-bit and 64-bit versions). However, the Windows Server Backup snap-in is not available for the Server Core installation option of Windows Server 2008. To run backups for computers with a Server Core installation, you need to either use the command line or manage backups remotely from another computer. In addition, Windows PowerShell is not available for the Server Core installation option, so the cmdlets for Windows Server Backup are also not available on this type of installation.<!----></td>
</tr>
</tbody>
</table>
<p><!----></div>
</div>
<h2>What’s new in Windows Server Backup?</h2>
<div id="sectionSection1">
<p>Windows Server Backup includes the following improvements:</p>
<ul>
<li> <strong>Faster backup technology</strong>. Windows Server Backup uses Volume Shadow Copy Service (VSS) and block-level backup technology to back up and recover your operating system, files and folders, and volumes. After the first full backup is created, you can configure Windows Server Backup to automatically run incremental backups by saving only the data that has changed since the last backup. Even if you choose to always perform full backups, your backup will take less time than it did in earlier versions of Windows.</li>
<li> <strong>Simplified restoration</strong>. You can restore items by choosing a backup and then selecting specific items from that backup to restore. You can recover specific files from a folder or all the contents of a folder. In addition, previously, you needed to manually restore from multiple backups if the item was stored on an incremental backup. But this is no longer true—you can now choose the date of the backup version for the item you want to restore.</li>
<li> <strong>Simplified recovery of your operating system</strong>. Windows Server Backup works with new Windows recovery tools to make it easier for you to recover your operating system. You can recover to the same server—or if the hardware fails, you can recover to a separate server that has similar hardware and no operating system.</li>
<li> <strong>Ability to recover applications</strong>. Windows Server Backup uses VSS functionality that is built into applications like Microsoft® SQL Server® to protect application data.</li>
<li> <strong>Improved scheduling</strong>. Windows Server Backup includes a wizard that guides you through the process of creating daily backups. System volumes are automatically included in all scheduled backups so that you are protected against disasters.</li>
<li> <strong>Offsite removal of backups for disaster protection</strong>. You can save backups to multiple disks in a rotation, which enables you to move disks from an offsite location. You can add each disk as a scheduled backup location and, if the first disk is moved offsite, Windows Server Backup will automatically save backups to the next disk in the rotation.</li>
<li> <strong>Remote administration</strong>. Windows Server Backup uses an MMC snap-in to give you a familiar and consistent experience for managing your backups. After you install the snap-in, you can access this tool through Server Manager or by adding the snap-in to a new or existing MMC console. Then, you can manage backups on other servers by clicking the <strong>Action </strong>menu in the snap-in, and then clicking <strong>Connect to Another Computer</strong>.</li>
<li> <strong>Automatic disk usage management</strong>. After you configure a disk for a scheduled backup, Windows Server Backup automatically manages the disk usage—you do not need to be concerned about running out of disk space after repeated backups. Windows Server Backup will automatically reuse the space of older backups when creating new backups. The management tool displays the backups that are available and the disk usage information. This can help you plan for provisioning additional storage to meet your recovery objectives.</li>
<li> <strong>Extensive command-line support</strong>. Windows Server Backup includes the <strong>wbadmin</strong> command and documentation, which enable you to perform all of the same tasks at the command line that you can perform by using the snap-in. For more information, see the Command Reference (<a id="ctl00_MTCS_main_ctl02" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl02',this);" href="http://go.microsoft.com/fwlink/?LinkId=93131">http://go.microsoft.com/fwlink/?LinkId=93131</a>). You can also automate backup activities through scripting.In addition, Windows Server 2008 contains a collection of Windows PowerShell™ commands (cmdlets) for Windows Server Backup that you can use to write scripts to perform backups. For more information, see <a id="ctl00_MTCS_main_ctl03" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl03',this);" href="http://go.microsoft.com/fwlink/?LinkId=93317">http://go.microsoft.com/fwlink/?LinkId=93317</a>.</li>
<li> <strong>Support for optical media drives and removable media</strong>. You can manually back up volumes directly to optical media drives, such as DVD drives, and also to removable media. This offers a solution if you want to create backups that can easily be moved offsite on a one-time basis. This version of Windows Server Backup retains support for manual backups to shared folders and hard disks.</li>
</ul>
</div>
<h2>Who should use Windows Server Backup?</h2>
<div id="sectionSection2">
<p>Windows Server Backup is intended for use by everyone who needs a basic backup solution—from small business owners to IT professionals in large enterprises. However, the design makes it especially well-suited for smaller organizations or individuals who are not IT professionals.</p></div>
<h2>Special considerations</h2>
<div id="sectionSection3">
<p>You must be a member of the Administrators group or Backup Operators group to use Windows Server Backup.</p>
<p>In Windows Server 2008, the firewall has been enabled by default. If you are managing the backups of another computer using the Windows Server Backup snap-in, your connectivity to the remote computer may be affected and can be resolved by changes in the firewall rules. While working on the local computer, you are not affected.</p>
<p>Also, if you are a current user of the previous backup feature (Ntbackup.exe) that shipped in earlier versions of Windows, and plan to switch to the new Windows Server Backup, you might be affected by the following issues and changes:</p>
<ul>
<li>Settings for creating backups will not be upgraded when you upgrade to Windows Server 2008. You will need to reconfigure settings.</li>
<li>You will need a separate, dedicated disk for running scheduled backups.</li>
<li>Only NTFS-formatted volumes on a locally attached disk can be backed up.</li>
<li>You can no longer back up to tape. (However, support of tape storage drivers is still included in Windows Server 2008.) Windows Server Backup supports backing up to external and internal disks, DVDs, and shared folders.You cannot recover backups that you created with Ntbackup.exe by using Windows Server Backup. However, a version of Ntbackup.exe is available as a download to Windows Server 2008 for users who want to recover data from backups created using Ntbackup.exe. The downloadable version of Ntbackup.exe is only for recovering backups for older versions of Windows and cannot be used to create new backups in Windows Server 2008. To download Ntbackup.exe, see <a id="ctl00_MTCS_main_ctl04" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl04',this);" href="http://go.microsoft.com/fwlink/?LinkId=82917">http://go.microsoft.com/fwlink/?LinkId=82917</a>.</li>
</ul>
</div>
<h2>How to install Windows Server Backup</h2>
<div id="sectionSection4">
<p>To access backup and recovery tools for Windows Server 2008, you must install the <strong>Windows Server Backup</strong>, <strong>Command-line Tools</strong>, and <strong>Windows PowerShell</strong> items that are available in the Add Features Wizard in Server Manager. This installs the following tools:</p>
<ul>
<li>Windows Server Backup Microsoft Management Console (MMC) snap-in</li>
<li> <strong>Wbadmin</strong> command-line tool</li>
<li>Windows Server Backup cmdlets (Windows PowerShell commands)</li>
</ul>
<div>
<table border="0">
<tbody>
<tr>
<th align="left"> <img src="http://i.technet.microsoft.com/cc770266.note%28en-us,WS.10%29.gif" alt="note" />Note</th>
</tr>
<tr>
<td>To install Windows Server Backup features in Server Manager, you must be a member of the Backup Operators or Administrators group. You can also access Windows Server Backup from Server Manager, under the <strong>Storage</strong> node.<!----></td>
</tr>
</tbody>
</table>
<p><!----></div>
<p><strong>To install backup and recovery tools</strong></p>
<ol>
<li>Click <strong>Start</strong>, click <strong>Server Manager</strong>, in the left pane click <strong>Features</strong>, and then in the right pane click <strong>Add Features</strong>. This opens the Add Features Wizard.</li>
<li>In the Add Features Wizard, on the <strong>Select Features</strong> page, expand <strong>Windows Server Backup Features</strong>, and then select the check boxes for <strong>Windows Server Backup </strong>and<strong> Command-line Tools</strong>.You will receive a message that Windows PowerShell is also required to be installed with these features.
<div>
<table border="0">
<tbody>
<tr>
<th align="left"> <img src="http://i.technet.microsoft.com/cc770266.note%28en-us,WS.10%29.gif" alt="note" />Note</th>
</tr>
<tr>
<td>If you just want to install the snap-in and the <strong>Wbadmin</strong> command-line tool, expand <strong>Windows Server Backup Features</strong>, and then select the <strong>Windows Server Backup</strong> check box. In this case, Windows PowerShell is not required.<!----></td>
</tr>
</tbody>
</table>
<p><!----></div>
</li>
<li>Click <strong>Add Required Features</strong>, and then click <strong>Next</strong>.</li>
<li>On the <strong>Confirm Installation Selections</strong> page, review the choices that you made, and then click <strong>Install</strong>. If there is an error during the installation, it will be noted on the <strong>Installation Results</strong> page.</li>
<li>Then, to access these backup and recovery tools, do the following:
<ul>
<li>To access the Windows Server Backup snap-in, click <strong>Start</strong>, click <strong>Administrative Tools</strong>, and then click <strong>Windows Server Backup</strong>.</li>
<li>To access and view the syntax for <strong>Wbadmin</strong>, click <strong>Start</strong>, right-click <strong>Command Prompt</strong>, and then click <strong>Run as administrator</strong>. At the prompt, type: <strong>wbadmin /?</strong></li>
<li>For instructions to access and view the Help for the Windows Server Backup cmdlets, see GettingStarted.rtf at: &lt;<em>systemdrive</em>&gt;:\Windows\System32\WindowsPowerShell\v1.0\Documents\&lt;<em>language</em>&gt;.</li>
</ul>
</li>
</ol>
</div>
<h2>Step-by-step instructions</h2>
<p>Use the following links for key backup and recovery tasks:</p>
<ul>
<li>For instructions for backing up a server running Windows Server 2008, see <a id="ctl00_MTCS_main_ctl07" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl07',this);" href="http://go.microsoft.com/fwlink/?LinkId=110462">http://go.microsoft.com/fwlink/?LinkId=110462</a>.</li>
<li>For instructions for recovering a server running Windows Server 2008, see <a id="ctl00_MTCS_main_ctl08" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl08',this);" href="http://go.microsoft.com/fwlink/?LinkId=110463">http://go.microsoft.com/fwlink/?LinkId=110463</a>.</li>
<li>For instructions for backing up and recovering a server running Active Directory Domain Services, see <a id="ctl00_MTCS_main_ctl09" onclick="javascript:Track('ctl00_MTCS_main_ctl00|ctl00_MTCS_main_ctl09',this);" href="http://go.microsoft.com/fwlink/?LinkId=110466">http://go.microsoft.com/fwlink/?LinkId=110466</a>.</li>
</ul>
<p>source: <a href="http://technet.microsoft.com/en-ca/library/cc770266%28WS.10%29.aspx">http://technet.microsoft.com/en-ca/library/cc770266%28WS.10%29.aspx</a></p>
]]></content:encoded>
			<wfw:commentRss>http://redhatvn.net/windows-server-backup-step-by-step-guide-for-windows-server-2008/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enabling VSS for Hyper-V Backups With Windows Server Backup</title>
		<link>http://redhatvn.net/enabling-vss-for-hyper-v-backups-with-windows-server-backup</link>
		<comments>http://redhatvn.net/enabling-vss-for-hyper-v-backups-with-windows-server-backup#comments</comments>
		<pubDate>Wed, 02 Dec 2009 09:09:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Windows]]></category>
		<category><![CDATA[vps]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[win2k8]]></category>

		<guid isPermaLink="false">http://redhatvn.net/?p=702</guid>
		<description><![CDATA[As with anything you should be backing up your Hyper-V machines.  I think that just goes without saying.  Backing up Hyper-V has gotten easier with the addition of VSS and Windows Server Backup (WSB).  WSB is a new feature in Windows Server 2008 that replaces the old NTBackup from days gone by.  It is not [...]]]></description>
			<content:encoded><![CDATA[<p>As with anything you should be backing up your Hyper-V machines.  I think that just goes without saying.  Backing up Hyper-V has gotten easier with the addition of VSS and Windows Server Backup (WSB).  WSB is a new feature in Windows Server 2008 that replaces the old NTBackup from days gone by.  It is not installed by default but can be easily added with the Add Features wizard in Server Manager.  Once installed there is one last setting you must configure before backing up the Hyper-V virtual machines.</p>
<p>While Hyper-V does support VSS backups, it is not enabled by default.  I am not sure why but you need to set a few registry settings to get WSB to recognize the Hyper-V VSS writer.  You can enable this with the following two registry settings.</p>
<p><span id="more-702"></span>Under <strong>HKLM\Software\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\ApplicationSupport</strong> add the following key {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE</p>
<p>Then under that newly created key add a new REG SZ string called <strong>Application Identifier</strong> with the value <strong>Hyper-V</strong>.  Once that is done you are ready to go!  To make it a bit easier you can copy and paste the following to a command line (with administrative privileges) and it will get it all set up for you.  You will need to set this on all Hyper-V servers in your organization but there is no reboot required!</p>
<blockquote><p>reg add &#8220;HKLM\Software\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\ApplicationSupport\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}&#8221;</p>
<p>reg add &#8220;HKLM\Software\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\ApplicationSupport\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}&#8221;<br />
/v &#8220;Application Identifier&#8221; /t Reg_SZ /d Hyper-V</p></blockquote>
<p>For more information see:</p>
<p><a href="http://technet.microsoft.com/en-ca/library/cc770266.aspx">Windows Server 2008 Backup Step By Step</a></p>
]]></content:encoded>
			<wfw:commentRss>http://redhatvn.net/enabling-vss-for-hyper-v-backups-with-windows-server-backup/feed</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
		<item>
		<title>Centralized Backup Server With Amanda On CentOS</title>
		<link>http://redhatvn.net/centralized-backup-server-with-amanda-on-centos</link>
		<comments>http://redhatvn.net/centralized-backup-server-with-amanda-on-centos#comments</comments>
		<pubDate>Tue, 01 Dec 2009 04:18:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Centos]]></category>
		<category><![CDATA[Cpanel]]></category>
		<category><![CDATA[Directadmin]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[shell script]]></category>
		<category><![CDATA[vps]]></category>
		<category><![CDATA[Amanda]]></category>
		<category><![CDATA[backup]]></category>

		<guid isPermaLink="false">http://redhatvn.net/?p=595</guid>
		<description><![CDATA[This document describes how to set up a centralized network backup with Amanda. We will use virtual tape to store the backup. In my environment, I have 2 Linux servers that I want to backup. 192.168.20.200 (Alpha) : /home/kulathep 192.168.20.201 (Beta) : /data and /var I am going to build a new server with Amanda [...]]]></description>
			<content:encoded><![CDATA[<p>This document describes how to set up a centralized network backup with Amanda. We will    use virtual tape to store the backup.<br />
<span id="more-595"></span></p>
<p>In my environment, I have 2 Linux servers that I want to backup.</p>
<p><span>192.168.20.200</span> (Alpha) : <span>/home/kulathep</span></p>
<p><span>192.168.20.201</span> (Beta) :  <span>/data</span> and <span>/var</span></p>
<p>I am going to build a new server with Amanda as a centralized backup server.</p>
<p><span>192.168.20.202</span> (Gamma)</p>
<h3>Setup Server (Gamma)</h3>
<p>1. Install Amanda with yum:</p>
<p><code>yum -y install amanda*</code></p>
<p>2. Edit Amanda conf in <span>xinetd.d</span>:</p>
<p><code>vi /etc/xinetd.d/amanda<br />
vi /etc/xinetd.d/amandaidx<br />
vi /etc/xinetd.d/amidxtape</code></p>
<p>Change <span>Disable = yes</span> to <span>Disable = no</span>.</p>
<p>3. Copy Amanda conf files:</p>
<p><code>cp -r /etc/amanda/DailySet1 /etc/amanda/intra</code></p>
<p>4. Edit <span>amanda.conf</span>:</p>
<p><code>vi /etc/amanda/intra/amanda.conf</code></p>
<blockquote><p>org &#8220;Configuration name&#8221;<br />
mailto &#8220;email&#8221;<br />
netusage 600 Kbps</p>
<p>dumpcycle 2 weeks<br />
runspercycle 10<br />
tapecycle 15 tapes</p>
<p>#tpchanger &#8220;chg-manual&#8221;<br />
tpchanger &#8220;chg-disk&#8221;</p>
<p>changerfile &#8220;/etc/amanda/intra/changer&#8221;</p>
<p>#tapedev &#8220;null:&#8221;<br />
tapedev &#8220;file:/backup/intra/slots&#8221;</p>
<p>#tapetype HP-DAT<br />
#labelstr &#8220;^DailySet1-[0-9][0-9]*$&#8221;</p>
<p>tapetype HARDDISK<br />
define tapetype HARDDISK {<br />
comment “Backup to Virtual Tape”<br />
length 3072 mbytes # each tape is 3 Gigs<br />
}</p>
<p># amrecover_changer &#8220;null:&#8221;<br />
amrecover_changer &#8220;changer&#8221;</p>
<p>#infofile &#8220;/etc/amanda/DailySet1/curinfo&#8221; # database DIRECTORY<br />
#logdir &#8220;/etc/amanda/ DailySet1&#8243; # log directory<br />
#indexdir &#8220;/etc/amanda/ DailySet1/index&#8221; # index directory<br />
infofile &#8220;/var/log/amanda/intra/curinfo&#8221; # database DIRECTORY<br />
logdir &#8220;/var/log/amanda/intra&#8221; # log directory<br />
indexdir &#8220;/var/log/amanda/intra/index&#8221; # index directory</p></blockquote>
<p>With this configuration, Amanda will do a full backup every 2 weeks, and an incremental backup every week day. The backup will be stored and rotated on 15 virtual tapes.</p>
<p>5. Edit <span>disklist</span> (tell Amanda which servers, directory to backup, what dumptype to use).</p>
<p><code>vi /etc/amanda/intra/disklist</code></p>
<p>Remove every lines including “localhost /etc comp-root-tar” at the end of the file.  And add:</p>
<blockquote><p>alpha   /home/kulathep     comp-user-tar<br />
beta          /data     comp-user-tar<br />
beta          /var     comp-user-tar</p></blockquote>
<p>Note: See <span>amanda.conf</span> for the dumptype.</p>
<p>6. Edit <span>hosts</span> file:</p>
<p><code>vi /etc/hosts</code></p>
<p>Add:</p>
<blockquote><p>192.168.20.200 alpha<br />
192.168.20.201 beta</p></blockquote>
<p>7. Create backup directory (we will store the backup here):</p>
<p><code>mkdir -p -m 770 /backup/intra/slots<br />
chown -R amanda:disk /backup</code></p>
<p>8. Create tape list:</p>
<p><code>touch /etc/amanda/intra/tapelist<br />
chown –R amanda:disk /etc/amanda/intra</code></p>
<p>9. Create slots (virtual tapes):</p>
<p><code>su - amanda<br />
cd /backup/intra/slots<br />
for ((i=1; $i&lt;=15; i++)); do mkdir slot$i; done<br />
ln -s slot1 data</code></p>
<p>10. Test virtual tapes:</p>
<p><code>/usr/sbin/ammt -f file:/backup/intra/slots status</code></p>
<p>11. Label the virtual tapes:</p>
<p><code>for ((i=1; $i&lt;=15; i++)); do /usr/sbin/amlabel intra intra-$i slot  $i; done</code></p>
<p>12. Reset the tape:</p>
<p><code>/usr/sbin/amtape intra reset</code></p>
<p>13. Edit <span>.amandahosts</span> to allow communications from clients:</p>
<p><code>vi /var/lib/amanda/.amandahosts</code></p>
<blockquote><p>alpha amanda<br />
beta amanda<br />
gamma amanda</p></blockquote>
<p>14. Start xinetd service:</p>
<p><code>su –<br />
service xinetd start</code></p>
<p>15. Check amanda process:</p>
<p><code>lsof | grep amanda</code></p>
<h3>Set Up Client</h3>
<p>1. Install amanda client with yum:</p>
<p><code>yum -y install amanda-client</code></p>
<p>2. Edit file <span>.amandahosts</span> to allow communications from server:</p>
<p><code>vi /var/lib/amanda/.amandahosts</code></p>
<blockquote><p>gamma amanda</p></blockquote>
<p>3. Edit <span>xinetd.d</span>:</p>
<p><code>vi /etc/xinetd.d/amanda</code></p>
<blockquote><p>Disable = no</p></blockquote>
<p>4. Start xinetd:</p>
<p><code>service xinetd start</code></p>
<p>5. Check Amanda service:</p>
<p><code>lsof | grep amanda</code></p>
<h3>Backup Data</h3>
<p>1. Check tapes and clients   on server:</p>
<p><code>su - amanda<br />
/usr/sbin/amcheck intra</code></p>
<p>2. Dump manually:</p>
<p><code>/usr/sbin/amdump intra</code></p>
<p>3. Add amdump to cron:</p>
<p><code>crontab –e</code></p>
<blockquote><p>0 16 * * 1-5    /usr/sbin/amcheck -m intra<br />
45 0 * * 2-6    /usr/sbin/amdump intra</p></blockquote>
<p>The first line checks the tape/clients and sends an email if it found something wrong (no  email if everything is okay) at 4pm.</p>
<p>The second line dumps at 12.45am on weekdays.</p>
<h3>Restore Data</h3>
<p>1. Prepare tapes:</p>
<p><code>cd /tmp<br />
/usr/sbin/amtape intra slot 1 # select slot1 (tape1)<br />
/usr/sbin/ammt -t file:/backup/intra/slots rewind # rewind</code></p>
<p>2.1. Restore everything from every server:</p>
<p><code>/usr/sbin/amrestore file:/backup/intra/slots</code></p>
<p>2.2. Restore only a server and a directory:</p>
<p><code>/usr/sbin/amrestore file:/backup/intra/slots beta /var</code></p>
<p>3. Extract:</p>
<p><code>tar xvf &lt;Restored files&gt;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://redhatvn.net/centralized-backup-server-with-amanda-on-centos/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->