[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#683422: ITP: rear -- Relax and Recover is a bare metal disaster recovery and system migration framework

Package: wnpp
Severity: wishlist
Owner: Thomas Schumm <thomas.schumm@gmx.de>

* Package name    : rear
  Version         : 1.13.0+1~2757396-1
  Upstream Author : Schlomo Schapiro, Gratien D'haese, Stefan Semmelroggen, Peer Heinlein, Dag Wieers, Jeroen Hoekx

* URL             : http://relax-and-recover.org
* License         : GPL2
  Programming Lang: bash
  Description     : Relax and Recover is a bare metal disaster recovery and system migration framework

Relax-and-Recover is a tool that implements a desaster recovery workflow for Linux.

It produces a bootable image. This image can repartition the
system. Once that is done it initiates a restore from backup. Restores to
different hardware are possible. Relax-and-Recover can therefore be used as a
migration tool as well.

Currently Relax-and-Recover supports various boot media (incl. ISO, PXE,
OBDR tape, USB or eSATA storage), a variety of network protocols (incl.
sftp, ftp, http, nfs, cifs) as well as a multitude of backup strategies
(incl.  IBM TSM, HP DataProtector, Symantec NetBackup, Bacula, rsync, duplicity).

Relax-and-Recover was designed to be easy to set up, requires no maintenance
and is there to assist when disaster strikes. Its setup-and-forget nature
removes any excuse for not having a disaster recovery solution implemented.

Recovering from disaster is made very straight-forward by a 2-step recovery
process so that it can be executed by operational teams when required.
When used interactively (e.g. when used for migrating systems), menus help
make decisions to restore to a new (hardware) environment.

Extending and integrating Relax-and-Recover into complex environments is made
possible by its modular framework. Consistent logging and optionally extended
output help understand the concepts behind Relax-and-Recover, troubleshoot
during initial configuration and help debug during integration.

Reply to: