[Rear-users] SF.net SVN: rear:[727] trunk/usr/share/rear/doc/Rear-release-notes.txt

gdha at users.sourceforge.net gdha at users.sourceforge.net
Tue Nov 15 16:50:01 CET 2011


Revision: 727
          http://rear.svn.sourceforge.net/rear/?rev=727&view=rev
Author:   gdha
Date:     2011-11-15 15:50:01 +0000 (Tue, 15 Nov 2011)
Log Message:
-----------
The first draft of the Release Notes for 1.12.0. Please send your remarks ASAP as the release of 1.12.0 is coming (soon).
Any blocking items? The only failing component is btrfs, but it is marked as experimental (so we're covered).

Modified Paths:
--------------
    trunk/usr/share/rear/doc/Rear-release-notes.txt

Modified: trunk/usr/share/rear/doc/Rear-release-notes.txt
===================================================================
--- trunk/usr/share/rear/doc/Rear-release-notes.txt	2011-11-14 08:53:03 UTC (rev 726)
+++ trunk/usr/share/rear/doc/Rear-release-notes.txt	2011-11-15 15:50:01 UTC (rev 727)
@@ -1,7 +1,5 @@
-= Release Notes for Relax and Recover (rear) version 1.11.0
-
 :Author: Gratien D'haese
-:Date: 20 July 2011
+:Date: 17 November 2011
 :Revision: 1.0
 :data-uri:
 :icons:
@@ -9,10 +7,13 @@
 :toc:
 :toclevels: 2
 
+= Release Notes for Relax and Recover (rear) version 1.12.0
+
 This document contains the release notes for the open source project "Relax and Recover" (abbreviated as rear).  Rear is hosted at SourceForge:
 
 . project rear : http://sourceforge.net/projects/rear
 . home of rear : http://rear.sourceforge.net/
+. download rear snapshots : http://download.opensuse.org/repositories/home:/sschapiro/
 
 This document is distributed with the following license: "Creative Commons Attribution-NoDerivs 3.0 Unported (CC BY-ND 3.0)". To read the license deed go to: http://creativecommons.org/licenses/by-nd/3.0/
 
@@ -27,25 +28,25 @@
 
 *	Hot maintenance capability. A rescue image can be made online while the system is running.
 *	Command line interface. Rear doesn't require a graphical interface to run, nor in creation mode, nor in rescue mode (console is enough).
-*	Support included for most common file systems, such as ext2, ext3 and ext4, reiserfs, jfs, xfs are also on our list, but are less tested. [Please give us feedback]
+*	Support included for most common file systems, such as ext2, ext3, ext4 and reiserfs, jfs, xfs, btrfs [NEW] are also on our list, but are less tested. [Please give us feedback]
 *	Hardware mirroring and RAID managers (like cciss) are known to work.
 *	LVM root volumes are supported.
 *	Integrates with external backup solutions such as:
 
 ..	GNU tar (BACKUP=NETFS)
-..	NEW! rsync (BACKUP=NETFS)
+..	rsync (BACKUP=NETFS)
 ..	Tivoli Storage Manager (BACKUP=TSM)
 ..	HP Data Protector (BACKUP=DP)
 ..	Symantec NetBacakup (BACKUP=NBU)
 ..	Galaxy 5, 6 and 7 (BACKUP=GALAXY)
-..	*NEW!* Bacula (BACKUP=BACULA)
+..	Bacula (BACKUP=BACULA)
 
 *	Udev support (except for some really ancient udev versions) which is the base for many new and important features:
 
 ..	kernel drivers for network cards and storage adapters are now loaded via udev
 ..	deal with network persistent names in udev rules
 ..	firmware loading
-..	persistent storage device names (though ReaR does nothing with this)
+..	persistent storage device names (though Rear does nothing with this)
 
 *	System reconfiguration
 
@@ -56,29 +57,58 @@
 *	Support new backup software: Bacula, both locally attached tapes (with bextract) and network-based backups. Also, in combination with OBDR tapes.
 *	Create OBDR tapes with method *mkbackup* and put the backup onto the tape to have a single-tape bootable recovery solution
 *	Label the OBDR tape with the method *labeltape* to avoid accidental overwrites with OBDR
-*	*NEW (EXPERIMENTAL)!* Create bootable disk (eSATA, USB ...) media with the backup included:
+*	*[NEW]* Create bootable disk (eSATA, USB ...) media with the backup included:
 ----
-NETFS_URL=usb:///dev/<device>
+BACKUP_URL=usb:///dev/<device>
 ----
 Together with *OUTPUT=USB* we have now a complete solution on hard disks (booting of it and restoring data).
 
 *	DHCP client support (IPv4 and IPv6) has been added. Auto detection is possible with new variable *USE_DHCLIENT=yes* (define in _local.conf_), or one can hard-code your special DHCP client with the variables *DHCLIENT_BIN* (for IPv4), and/or *DHCLIENT6_BIN* (for IPv6)
-*	*NEW!* Save layout and compare layouts for easy automation of making rear snapshots
-*	*NEW (EXPERIMENTAL)!* The possibility to use the new *layout* workflow instead of the current standard *dr* workflow. The *dr* workflow kept all important system information into a directory structure where the new *layout* workflow use files to keep the information centralized
-*	*NEW (EXPERIMENTAL)!* External USB booting now uses extlinux instead of syslinux, and therefore, the USB disk must first be formatted with an exy2, ext3, ext4 or bttfs based file system
+*	Save layout and compare layouts for easy automation of making rear snapshots
+*	*[NEW]* The possibility to use the new *layout* workflow instead of the current standard *dr* workflow. The *dr* workflow kept all important system information into a directory structure where the new *layout* workflow use files to keep the information centralized
+*	*[NEW]* External USB booting now uses extlinux instead of syslinux, and therefore, the USB disk must first be formatted with an exy2, ext3, ext4 or bttfs based file system
 
 NOTE: Features marked experimental are prone to change with future releases.
 
 == Rear Releases
 The first release of Rear, version 1.0, was posted to the web in July 2006. For each release, this chapter lists the new features and defect fixes. Note that all releases are cumulative, and that all releases of Rear are compatible with previous versions of Rear, unless otherwise noted.
 
+=== Version 1.12.0 (November 2011)
+
+*	Multiple copies of Rear archives (of the same or different systems) can be kept on an USB disk (with *OUTPUT=USB*).
+*	*[NEW!]* *BACKUP=RSYNC* workflow using +rsync+ executable. Both +ssh+ and +rsync+ methods are supported. E.g.
+----
+BACKUP=RSYNC
+OUTPUT=ISO
+BACKUP_URL=rsync://username@hostname/path	
+BACKUP_PROG=/usr/local/bin/rsync		(instead of the default rsync)
+----
+
+*	Added better named EXCLUDE variables, better control over what's restored:
+..	EXCLUDE_BACKUP contains components not included in the backup. They are recreated.
+..	EXCLUDE_RECREATE contains components not recreated. (Comments in LAYOUT file)
+..	EXCLUDE_RESTORE contains components whose filesystems are not restored from backup.
+..	EXCLUDE_RESTORE can also contain generic fs paths not constrained to mountpoints.
+
+*	The *layout* workflow is now the default instead of the *dr* workflow. Under _/var/lib/rear/layout_ all information of the system is kept in files.
+*	Arch Linux is now supported with rear.
+*	The option with rear +labeltape+ has been replaced with +format+ and can be used with tapes and external (USB, eSATA) devices. Usage:
+----
+rear format [/dev/st0|/dev/sdx]
+----
+
+*	Replaced NETFS_URL and ISO_URL by BACKUP_URL and OUTPUT_URL. However, old references will still be recognized and automatically renamed.
+*	Fedora 16 is supported including GRUB 2, and systemd as init replacement.
+*	Added the *BACKUP_URL=file:///PATH* with *BACKUP=NETFS* method (as described in _configuration-examples.txt_)
+*	*[NEW! EXPERIMENTAL!]* Btrfs file system backup and restore works, but some files seem to become corrupt. Advise is not to trust it (yet). At recreation of the btrfs file system the UUID number is automatically renamed in all configuration files (such as _/etc/fstab_ or _/boot/grub/menu.lst_).
+
 === Version 1.11.0 (May 2011)
 
 * +rear mkobdr+  method has been removed. To make an OBDR aware tape now just use the ''+rear mkbackup+'' method and define the proper variables in _/etc/rear/local.conf_ as
 ----
 BACKUP=NETFS
 OUTPUT=OBDR
-NETFS_URL=tape:///dev/nst0
+BACKUP_URL=tape:///dev/nst0
 ----
 
 * The site configuration file _/etc/rear/site.conf_ has been removed from the rear package, but can still be used if end-users want. The purpose of this is to enable sites to distribute this file through RPM or DEB packages that do not have a file conflict with the rear package. The distribution _/etc/rear/local.conf_ file contains only configuration examples as comments in order to not interfere with configurations in _site.conf_.
@@ -110,13 +140,13 @@
  (GRUB_RESCUE_PASSWORD) to avoid accidential recovery.
  The default password is *REAR*.
 * *EXPERIMENTAL!* Transfer ISO image to remote URL (ISO_URL). Please note that this
-feature will be extended to cover all output methods and then it will (probably) be renamed
+feature will be extended to cover all output methods. It has been renamed
 to OUTPUT_URL.
 * Removed various warnings, e.g. about NETFS not being a professional backup method.
-* *EXPERIMENTAL!* Partial support for Arch Linux has been added, more testing required.
+* Partial support for Arch Linux has been added, more testing required.
 * NEW! shell workflow is now really usable.
 * Make 32/64 bit handling much more robust, especially on systems having /lib32.
-* NETFS backup and restore with rsync working now (BACKUP_METHOD=rsync).
+* NETFS backup and restore with rsync working now (*BACKUP_PROG=rsync*).
 * Support udev on RHEL4.
 * Development snapshot have now a version like 0.0.REV where REV is the SVN revision used to build the development snapshot.
 * Greatly reduced log clutter (lvm warnings about leaked file descriptors, which is a bash bug, various irrelevant error and verbose output).
@@ -185,6 +215,10 @@
 to ia64 and ppc architectures, but these are less tested. Use the '+rear validate+' command after
 every successful DR test please and mail us the results.
 
+=== Choosing the best compression algorithm 
+The default backup program with Rear is (*BACKUP_PROG=tar*) GNU tar and the default compression used with tar is +gzip+. However, is using +gzip+ the best choice? We have done some tests and published the results. See link:http://www.it3.be/Joomla/index.php?option=com_content&view=article&id=76:rear-compression&catid=40:Open%20Source%20Projects&Itemid=54[Rear compression tests]
+
+
 == Known Problems and Workarounds
 *Issue Description*: System reconfiguration still has some weaknesses.
 
@@ -214,4 +248,21 @@
 First remove the older rear version by hand and then install the new version.
 The _local.conf_ is saved (as _local.conf.rpmsave_) when we execute '+rpm -e rear+'
 
+*Issue Description*: If SELinux is not disabled during backup (variable *BACKUP_SELINUX_DISABLE=* in _/etc/rear/local.conf_) then we might see errors in the +rear-$(hostname).log+ file such as:
+----
+tar: var/cache/yum/i386/15/updates/packages: Cannot setfilecon: No such file or directory
+----
+*Workaround*: 
+Make sure the *BACKUP_URL* destination understands extended attributes (CIFS is out of the question and NFS is problematic). When using local disks (or external USB devices) make sure the proper mount options are given in the *BACKUP_OPTIONS* variable, e.g.:
+----
+BACKUP_OPTIONS="rw,relatime,seclabel,user_xattr,acl,barrier=1,data=ordered"
+----
+TIP: *BACKUP_SELINUX_DISABLE=1* variable has been introduced in the _/usr/share/rear/conf/default.conf_ file to disable SELinux while the backup is running (default setting).
+
+*Issue Description*: Is incremental backup possible? With our default settings (*BACKUP=NETFS* and *BACKUP_PROG=tar*) we do not support incremental backups.
+
+*Workaround*: 
+However, when we change *BACKUP_PROG=rsync* we can use +rear mkbackuponly+ option which is in fact an incremental backup using the +rsync+ program. The same can be accomplished by using *BACKUP=RSYNC* and the proper *BACKUP_URL=rsync://hostname/PATH*.
+
+
 //vim: set syntax=asciidoc

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.





More information about the rear-users mailing list