Hosting Backup is a set if PHP command line scripts that provides an easy way to backup hosted Web sites to your local computer. It works with sites hosted on Linux servers with MySQL databases using FTP.

HostingBackup uses lftp (http://lftp.yar.ru/) to download all the files from your remote server.

HostingBackup uses rc4 encryption, so you do not need to have PHP compiled with mcrypt.

HostingBackup is tested on Linux local computer with PHP 4.3.x and lftp 3.0.x.

The remote component will manage some operations like optimization and dump of MySQL databases.

The local component will manage the execution of backups and other utilities like the generation of crypted passwords and the automatic installation of the remote component.

To allow an easy way to backup all hosted MySQL databases we store the main password for the account directly on the remote server, crypted with rc4.

When we call the dump script we pass the decrypt key.

To catch the login data an hacker should read the crypted password written on the server and intercept the key on the net.

What’s New in This Release:

· Add: “–comments=false” to mysqldump
· Add: “set FOREIGN_KEY_CHECKS=0;” to mysqldump
· Add: “–add-drop-table” to mysqldump

Sources mirror 1

What’s New in This Release:

· Julio Feferman noticed that the log file was vaporware

Sources mirror 1 (tar.bz2)

The goal is to use round robin synchronisation of incremental backup pools, where the source of data ranges from a personal laptop to a file store, over unused bandwidth where the data rate is dynamically controlled, including compression, according to load and availability. Some of the features above have been implemented, and the scripts are a toolkit to help users set up their own project as well as help the writer improve the system.

By using a number of backup nodes either between sites say between offices, homes, on a campus or over WAN’s, which could be dedicated to storage or used for existing services, have a round robin synchronisation of incremental backup pools where the source of data ranges from a personal laptop to a file store over unused band-width where the data rate is dynamically controlled, including compression, according to load and availability.

The above download is an attempt to define a subset of the description on this page – a partially working prototype that hopefully has potential to expand.

The incremental data retention tuned to the needs of an organisation so that some data is always available from any node in the backup pool quickly to within a certain time frame and tape storage stations strategically places in various secure locations for older data retention. This system would avoid using prohibitively expensive packages by reusing resources, building on Open Source technologies and have a coherent strategy across many sites increasing the level of redundancy to a high degree.

With layers of indexing, accounting and central management facilities. An assumption is that individual file encryption the responsibility of the file owner, this does not rule out hard drive or partition encryption of individual nodes considered to reside at insecure locations. If used for these locations physical security automatic fail-safe measures to trigger archive deposits useless upon theft can be deployed. Similar fail-safe techniques deployed for attempted network security breaches. Virus scanners would be set to scan existing archives periodically and on entry to the archive pool.

CCTV surveillance can used to further increase the security, by deterrent and useful records of intruders. In fact the protocol itself can be used as a method to ensure integrity of the photographic records. To this end the protocol should meet necessary requirements according to the data protection act of 1998.

Referencing Long-term Archive Protocol (LTAP) I-D – Section 10 paragraph 4 and 11 (final paragraph) discusses redundancy and brokerage – it this area that DIAP may be in a position to expand or become a new I-D.

Sources mirror 1 (tar)

Sources mirror 1 (tar.gz)

If you have two computers which should sync their files with each other, you just need an external hard disk, which will Black Mirror automatically use as a backup storage. That way, you can never accidentally delete a file forever.

And because Black Mirror is written in Perl, it is platform-independent, i.e., you can use the exact same program on every computer to keep them in sync, no matter what OS they’re running.

INSTALLATION AND USAGE:

After installing the application with the supplied setup script, you can simply start backing up your files with a command that looks like that:

blkmror {desired_directory} {external_harddisk}

Of course, the two arguments in braces are two paths to the respective folders or drives. Then you just sync the files with

blkmror {external_harddisk} {desired_directory}

to the other computer. From now on, you always can reverse the process to keep your files in sync, you don’t even have to run through the whole process.

The only thing to remember is that the first path (the source directory) is the one that contains the “more recent” files. (Don’t worry if you swapped the arguments, nothing would happen.)

What’s New in This Release:

· Relative paths as arguments work properly. [Bugfix]
· Improved error reports on the command line.
· Symbolic links will not be backed up or synchronized. [Bugfix]
· New switches: “Sync attributes/modes of files too”, “Remove x-modes from files”, “No special treatment for packages”, “Clean up backup directory”.
· Improvements of the backup procedure, including notifications.
· Upgrade scripts for an easier updating process.

Sources mirror 1 (zip)

· Update existing archives quickly
· Backup multiple folders to a storage location
· Create or extract protected archives
· Lessen effort by using archiving profiles and lists

Ark (2.6.3) is handy but it doesn’t seem to:

· Create archives with passwords
· Extract (some) archives with passwords
· Update existing archives by default

Q7Z is a simple application that attempts to fill these voids. It probably won’t become a total archiving solution.

Requirements:

· Python
· Qt4
· PyQt4
· Make
· Tar
· P7Zip

For installation instructions, see INSTALL.txt. If you encounter any problems, see ISSUES.txt and send me an email if necessary.

What’s New in This Release:

· Remote mode: ‘r’ option for sending archives to a mounted remote site
· Konq Service Menu: included separator and reordered the entries
· Error message: is now displayed when the failed operation returned nothing
· Error message: removed after the user cancels a profiling operation
· Profile names: Now enforcing the “.txt” extension when saving profiles
· Profile actions: improved status strip message in certain cases
· Operation feedback: now slightly more accurate
· Code structure: several minor changes

Debian DEB mirror 1

RedHat RPM mirror 1

Sources mirror 1 (tar.bz2)

Sources mirror 2 (tar.bz2)

Sources mirror 3 (tar.bz2)

Free, Open-source Ghost can be used to image Windows XP machines with a single partition, but Vista support is coming very soon.

What’s New in This Release:

· The default theme was changed from BrownBark to BlackEye.
· A theme option was added to the configuration file. Fast Disk wipe was added.
· Disk surface test was added.
· The Linux kernel was updated to 2.6.23.8.
· Kernel module support was removed.
· Kernel swap disk support was removed.
· A ramdisk size option was added to the configuration file.
· GUI support was added to the FOG service. Graphical configuration was added to the FOG service.
· The Task Reboot sub-service was added.
· The IP address was changed from a mandatory to optional field.
· The host upload was modified, making the IP address optional here too.
· The ability to delete image files from the Web GUI was added.

Sources mirror 1 (tar.gz)

rsback makes rotating backups using the common rsync program and some standard file utilities on Unix-based backup hosts. Its purpose is to mirror certain file trees from a remote host or from the local system and to store them as rotating archives in backup repositories on the local backup host. The file structure, permissions, ownerships and time stamps of the mirrored data are the same as in the original sources.

rsback is a kind of front end to rsync written in Perl which allows a system administrator to configure and execute backups of different file trees located on remote hosts or on the local system (e.g tasks for hourly, daily, weekly, monthly, … backups).

If rsback is executed at regular intervals (preferably scheduled by cron jobs), it maintains rotating backup archives. To restore files from the backup repository no special restore procedure is necessary. To recover files or directories, you just copy them from the archive tree back to the original location or wherever you want to place them.

The combination of rsync’s powerful capabilities and the extensive use of hard links for copying archives within the local file system results in a fast and disk space saving backup technique.

Usagesback-0.6.2.pl [-OPTIONS [-MORE_OPTIONS]] [--] [PROGRAM_ARG1 ...]

The following single-character options are accepted:

With arguments: -c
Boolean (without arguments): -h -v -i -d

Options may be merged together. — stops processing of options.
Space is not required between options and their arguments.

What’s New in This Release:

· New parameter update = (in mode = rsync). This causes just a “simple” rsync on the most recent backup set of the refered task (no rotation). There are no other parameters necesarry, they are taken from the refered task section.

Background:

To get consistent backups of live systems (data bases, virtual machines, …) these have to be shutdown before. To speedup backups of such systems, this procedure may help in some cases:

Step 1: Run a backup task of the running system (live-backup). Use ‘ignore_rsync_errors = 24′ (vanished source files).
Step 2: Shutdown the system.
Step 3: Run a task with ‘update = live-backup’ to take an update snapshot of the backup from Step 2.
Step 4: Restart the system.

The downtime (during step 3) should be considerably shorter compared to step 1 because only those files which have changed in the meantime have to be transfered.

· Warnings are now written to STDOUT, too. This may be helpful if rsback is lauched by cron jobs with commands like rsback -vc /etc/rsback-mywork.config >> /var/log/rsback/mywork.log. In this case, usually the owner of the job will be informed by mail if something went wrong (was written to STDERR). But errors have not been written to the log file (STDOUT) which made debugging often difficult. This can now be changed with warnings_to_stdout = yes

· Re-sorted CANGELOG. last entry first now.

Source mirror 1 (tar.gz)

What is packet writing?

There are three methods for writing data (or audio) to a CD using a CD recorder: Track-at-Once (TAO), Disc-at-Once (DAO) and Packet Writing. Track-at-Once is, by far, the most popular method today. Both Track-at-Once and Disc-at-Once use a table of contents mechanism to look up each chunk of data written to the disc. Use of a Table of Contents (TOC) requires that each session (or disc) must be closed at the end of a write, updating the table of contents which allows that session to be readable. Use of TAO and DAO methods also requires the creation of an ISO image before the disc may be written; converting the data from its form on your filesystem to a form that can be cleanly written to CD.

Packet writing is a method quite different from TAO and DAO; it is designed for writing data to CD in small increments. Packet writing must be supported by hardware (not all CD writers support packet writing). The largest benefit in packet writing comes in its ease of use; packet writing enables the user to copy files to CD without mastering any images previously, allowing someone to copy files to CD without requiring significant technical knowledge. Combined with a CD-RW drive and CD-RW media, packet writing provides an extremely simple, versatile, and inexpensive method for performing regular backup of crucial data.

What does this project provide?

Existing tools for Linux, such as cdrecord provide proper mechanisms to support Track-at-Once and Disc-at-Once writing methods, but are currently unable to properly support packet writing due to two missing components. The first, support for packet writing hardware, is provided by this project in the form of patches to the Linux kernel.

The other major component to the packet writing process is support of the UDF (Universal Disk Format) filesystem. UDF provides a filesystem capable of understanding large amounts of storage space (such as that found on DVDs), and is far more optimal for use with packet writing than the ISO9660 format used with traditional Track-at-Once and Disc-at-Once methods. UDF support for Linux is under development by the Linux UDF project.

The combination of the packet writing support provided by this project and the UDF filesystem support provided by the Linux UDF project, Linux will soon have access to the full benefit of packet writing technology, including potential benefits in data backup and mainstream desktop storage.

What’s New in This Release:

· (scsi) use implicit segment recounting for all hbas
· fix speed setting, was consistenly off on most drives
· only print capacity when opening for write
· fix off-by-two error in getting/setting write+read speed (affected reporting as well as actual speed used)
· possible to enable write caching on drive
· do ioctl marshalling on sparc64
· avoid unaligned access on flags, should have been unsigned long of course
· fixed missed wakeup in kpacketd
· b_dev error (two places)
· fix buffer head b_count bugs
· fix hole merge bug, where tail could be added twice
· fsync and invalidate buffers on close
· check hash table for buffers first before using our own
· add read-ahead
· fixed several list races
· fix proc reporting for more than one device
· change to O_CREAT for creating devices
· added media_change hook
· added free buffers config option
· pkt_lock_tray fails on failed open (and oopses), remove it. unlock is done explicitly in pkt_remove dev anyway.
· added proper elevator insertion (should probably be part of elevator.c)
· moved kernel thread info to private device, spawn one for each writer
· added separate buffer list for dirty packet buffers
· fixed nasty data corruption bug
· remember to account request even when we don’t gather data for it
· add ioctl to force wakeup of kernel thread (for debug)
· fixed packet size setting bug on zero detected
· changed a lot of the proc reporting to be more readable to “humans”
· set full speed for read-only opens

Source mirror 1 (tar.gz)

Moreover, if you are a developer and want contribute, the modular nature of synbak will allow you to easly write new backup methods, reports, and translations.

Here are some key features of “Synbak”:

· useful to backup servers, workstations and also laptops (not always network connected computers)
· input and output strings on UTF-8 charset format only
· easy concept and structure
· system, method and report concept
· support many backup methods
· common config file and interface for configuring every backup method
· fully multi user backup system, can run under normal user accounts or root user to keep all remote file permissions
· auto erase of old backups
· powerful reporting facility
· very understandably backups reports
· backup speed calculation
· provide many backups information
· you can create esclusion filters using regexp expressions
· modular architecture for developers
· ALL remote backups can be specified using a standard URI (Uniform Resource Identifiers) format (ex. cifs://usr:pwd@host/share)
· auto mounting and umounting of remote cifs/smb shares
· fully localized using the standard GNU gettext framework

Backup Methods:

Rsync
· backup of local and remote files using the beautiful and super fast ‘rsync’ protocol
· incremental backups
· total backups
· local backups
· remote backups via ssh, rsync and smb/cifs protocols
· auto mounting/umounting of remote system shares using smb/cifs protocols

Tar

· backup of local files into tar archives
· bzip2 compression
· gzip compression
· backup verify

MySQL

· backup dumps of local or remote MySQL servers
· bzip2 compression for sql dumps
· local multiple database dumps specifying the MySQL database dir (will create a dump for each database found)
· remote databases backup in a single SQL dump
· database inclusion pattern
· database exclusion pattern

LDAP

· backup dumps of local or remote LDAP (Light Weight Directory Access Protocol) directory servers
· bzip2 compression for ldif dumps
· ldif dump of remote LDAP servers

Tape

· backup to tape archives (ex. DAT, DLT, etc…)
· multi loader support (device changer/loader)
· eject of tape at backup end
· backup verify

Laser Disc

· backup to misc laser compact disks
· CD/R/RW
· DVD/R/RW/RAM
· eject of device at backup end

Report Methods:

HTML

· a very friendly gui wil provide all infos that an administrator or an end user need

RSS

· with the emerging RSS (Really Simple Syndication) protocol usage, you will find this report facility very useful, use it with your RSS aggregator

EMail

· receive via email the backup reports, the subject will describe if your backup gone well or not

What’s New in This Release:

· The MySQL method was almost completely rewritten with a lot of useful features.
· Now you can use the -M switch to make split database dumps (with each database in a separate dump file).
· The Italian translation was corrected.
· Volume tag (barcode) reporting was added for tape media changers that support this.
· A text string was added to exclude databases from Oracle’s backups.
· The CIFS umount function was fixed.
· Cleanups were done in the calendar PHP extension.
· Updates were made to the FAQ file.

RedHat RPM mirror 1

RedHat SRPM mirror 1

Source mirror 1 (tar.gz)