Free data recovery tools software for linux

The gzip Recovery Toolkit attempts to automate the recovery of data from corrupted gzip files (including tarballs) through a program called gzrecover. gzip Recovery Toolkit package is still very experimental at this point.
99% of "corrupted" gzip archives are caused by transferring the file via FTP in ASCII mode instead of binary mode. Please re-transfer the file in the correct mode first before attempting to recover from a file you believe is corrupted.
This program is provided AS IS with absolutely NO WARRANTY. It is not guaranteed to recover anything from your file, nor is what it does recover guaranteed to be good data. The bigger your file, the more likely that something will be extracted from it. Also keep in mind that this program gets faked out and is likely to "recover" some bad data. Everything should be manually verified.
Usage:
Run gzrecover on a corrupted .gz file. Anything that can be read from the file will be written to a file with the same name, but with a .recovered appended (any .gz is stripped). You can override this with the -o option.
To get a verbose readout of exactly where gzrecover is finding bad bytes, use the -v option to enable verbose mode. This will probably overflow your screen with text so best to redirect output to a file.
Once gzrecover has finished, you will need to manually verify any data recovered as it is quite likely that our output file is corrupt and has some garbage data in it. If your archive is a tarball, read on.
For tarballs, the tar program will choke because GNU tar cannot handle errors in the file format. Fortunately, GNU cpio (tested at version 2.5 or higher) handles corrupted files out of the box.
Heres an example:
$ ls *.gz
my-corrupted-backup.tar.gz
$ gzrecover my-corrupted-backup.tar.gz
$ ls *.recovered
my-corrupted-backup.tar.recovered
$ cpio -F my-corrupted-backup.tar.recovered -i -v
If you have a previous release, please note that the patches to GNU tar have been discontinued. They were only marginally successful at best and GNU cpio does what is needed out of the box and does it far better.
Enhancements:
- Documentation updates, including a man page, plus code cleanup to better enable inclusion in GNU/Linux packages and eliminate compilation warnings.

Kaboot Linux Operating system aims to provide an operating system which you can take anywhere and has all your favourite programs on.
Kaboot operating system is avaliable as a Live CD or Live USB you can take with you anywhere.
A number of different versions are avaliable, two optimised for size or speed, one for functionality, and one science based.
All containing a host of useful programs able to boot virtually any computer (meeting the minimum requirements) from CD and
USB.Kaboot is still in active development and if you find a bug or fix, you can let me know in the forums.
Enhancements:
- A network bug was fixed.
- A few debugging utilities were added.
- Hotplugging was implemented.

Data::Report provides a framework for flexible reporting.

Data::Report is a flexible, plugin-driven reporting framework. It makes it easy to define reports that can be produced in text, HTML and CSV. Textual ornaments like extra empty lines, dashed lines, and cell lines can be added in a way similar to HTML style sheets.

The Data::Report framework consists of three parts:
The plugins

Plugins implement a specific type of report. Standard plugins provided are Data::Report::Plugin::Text for textual reports, Data::Report::Plugin::Html for HTML reports, and Data::Report::Plugin::Csv for CSV (comma-separated) files.
Users can, and are encouraged, to develop their own plugins to handle different styles and types of reports.

The base class
The base class Data::Report::Base implements the functionality common to all reporters, plus a number of utility functions the plugins can use.

The factory
The actual Data::Report module is a factory that creates a reporter for a given report type by selecting the appropriate plugin and returning an instance thereof.

Make CD-ROM Recovery makes a bootable (El Torito) disaster recovery image (CDrec.iso), including backups of the linux system to the same CD-ROM (or CD-RW) if space permits, or to a multi-volume CD-ROM set. Otherwise, the backups can be stored on another local disk, NFS disk or (remote) tape.

After a disaster (disk crash or system intrusion) the system can be booted from the CD-ROM and one can restore the complete system as it was (at the time mkCDrec was run) with the command /etc/recovery/start-restore.sh

Disk cloning (clone-dsk.sh script) allows one to restore a disk to another disk (the destination disk does not have to be of the same size as it calculates the partition layout itself). A thrid script, restore-fs.sh, will restore only one filesystem to a partition of your choice, and the user can choose with which filesystem the partition has to be formatted.

Linux 2.2.x, 2.4.x and 2.6.x kernels are supported, and if size of the kernel is not too big a boot floppy can be made, otherwise a 2.88 Mb boot floppy will be emulated on CD-ROM.

MkCDrec supports ext2 , ext3, minix, xfs , jfs, reiserfs file systems, LVM and software RAID (multiple devices). Each file system is backed up as a compressed tar archive (including the tar log). The compress program used is the users choice (compress, gzip, bzip2, lzop,...)

But there is more: msdos, fat, vfat and ntfs mounted partitions are recognized and are saved as compressed dumps (on CD, tape, etc.)
The user has the possibility to encrypt all backups with openssl if desired (see the Config.sh configuration file for more information).

To restore your system completely just boot from the first CD-ROM made by mkCDrec and type "/etc/recovery/start-restore.sh " to restore everything from CD. Automatic Disaster Recovery and One Button Disaster Recovery are supported by mkCDrec too.
With the clone-dsk.sh script one can restore selective a disk or partitions to another free disk.

mkCDrec supports IDE (inclusive ATA), SCSI disks, hardware RAID based disks (e.g. Compaq SMART2 Disk Array), LVM and software RAID. With an El-Torito CD-ROM you can boot from an IDE or SCSI based CD-ROM drive on IA32/64, powermac and x86_64 GNU/Linux based computer systems only.

aB Backup Tools is a toolset for creating and maintaining backups and recoveries of important data on your system.
Enhancements:
- memory leaks fixed,
- options optimized,
- some look changes.

Data::PropertyList is a Perl module that can convert arbitrary objects to/from strings.

SYNOPSIS

use Data::PropertyList qw(astext fromtext);

$hash_ref = { items => [ 7 .. 11 ], key => value };
$string = astext($hash_ref);
# ...
$hash_ref = fromtext($string);
print $hash_ref->{items}[0];

$array_ref = [ 1, { key => value }, Omega ];
$string = astext($array_ref);
# ...
$array_ref = fromtext($string, -array=>1 );
print $array_ref->[1]{key};

Data::Propertylist provides functions that turn data structures with nested references into NeXTs Property List text format and back again.

You may find this useful for saving and loading application information in text files, or perhaps for generating error messages while debugging.

astext( $reference ) : $propertylist_string;

Writes out a nested Perl data structure in NeXT property list format.

fromtext( $propertylist_string ) : $hash_ref

fromtext( $propertylist_string, -array=>1 ) : $array_ref

Reconstructs a Perl data structure of nested references and scalars from a NeXT property list. Use the -array flag if the string encodes an array rather than a hash.

Data::Encrypted is a Perl module to transparently store encrypted data via RSA.

SYNOPSIS

# functional interface:
use Data::Encrypted file => "./.$0-encrypted-data", qw(encrypted);

# note: login and password are not *really* the login and
# password values, only the desired prompt!
my $login = encrypted(login);
my $password = encrypted(password);

# script continues, connecting to some secure resource (database,
# website, etc).

__END__

# alternative, OO interface:
use Data::Encrypted;

my $enc = new Data::Encrypted file => "./.$0-encrypted-data";
my $login = $enc->encrypted(login);
my $password = $enc->encrypted(password);
$enc->finished(); # close and release lock on storage file

# script continues, connecting to some secure resource (database,
# website, etc).

__END__

[ then, back at the command line: ]

% myscript.pl
Data::Encrypted value for login not found, please enter: *****
Data::Encrypted value for password not found, please enter: ********
[ script merrily continues ... ]

% myscript.pl
[ script merrily continues, no prompting this time ... ]

Often when dealing with external resources (database engines, ftp, telnet, websites, etc), your Perl script must supply a password, or other sensitive data, to the other system. This requires you to either continually prompt the user for the data, or to store the information (in plaintext) within your script. Youd rather not have to remember the connection details to all your different resources, so youd like to store the data somewhere. And if you share your script with anyone (as any good open-source developer would), youd rather not have your password or other sensitive information floating around.

Data::Encrypted attempts to fill this small void with a simple, yet functional solution to this common predicament. It works by prompting you (via Term::ReadPassword) once for each required value, but only does so the first time you run your script; thereafter, the data is stored encrypted in a secondary file. Subsequent executions of your script use the encrypted data directly, if possible; otherwise it again prompts for the data. Currently, Data::Encrypted achieves encryption via an RSA public-key cryptosystem implemented by Crypt::RSA, using (by default) your own SSH1 public and private keys.

Data::Region Perl module can define hierarchical areas with behaviors.

SYNOPSIS

use Data::Region;

$r = Data::Region->new( 8.5, 11, { data => PageObj->new() } );
$r->data( PageObj->new() );

foreach my $c ( $r->subdivide(2.5,3) ) {
$a = $c->area(0.25,0.25, 2.25,2.75);
$a2 = $c->area(0.25,0.25, -0.25,-0.25); # as offset from lower right

($t,$m,$b) = $a->split_vertical(2,5,1); # sequential heights
($t,$m,$b) = $a->split_vertical_abs(0,2,7); # absolute offsets
($l,$r) = $a->split_horizontal(2); # $l gets width of 2, $r gets the rest

my($x1,$y1,$x2,$y2) = $a->coords();
my $data = $a->data(); # data inherits from parent, if not set
$a->action( sub { $data->setfont("Times-Bold", 10);
$data->text($x1,$y1, "Some Text");
$data->line( $_[0]->coords() ); # the non-closure way
} );
}
$r->render(); # heirarchically perform all the actions

# Get some info about a region:
($w,$h) = ( $a->width(), $a->height() );
($x1,$y1, $x2,$y2) = $a->coords();
($x1,$y1) = $a->top_left();
($x2,$y1) = $a->top_right();
($x1,$y2) = $a->bottom_left();
($x2,$y2) = $a->bottom_right();

Data::Region allows you to easily define a set of nested (2-dimensional) areas, defined by related coordinates, and to associate actions with them. The actions can then be performed hierarchically from any root of the tree.

Data::Region was written to provide an easy way to do simple page layout, but has, perhaps, more general uses.