Tel: 0800 999 3282
Data Recovery Companies HomeNews Data Recovery NewsletterSitemap
Print-friendly version

Understanding Linux Data Backup And Recovery

Understanding Linux Data Backup And Recovery
Linux provides numerous options for configuring storage, such as Logical Volume Management (LVM), Software RAID (metadisks), and many various filesystem types. After a full system failure, recovering a server to its previous configuration can be quite a daunting task.


Also the cost involved to have a hardware technician perform the work could be very expensive. Add a change in disk hardware to the mix, and you may experience days of downtime!

While SBAdmin for Linux is a tape and disk backup management solution with many advanced features for managing your user data backup and restore strategy, it is the full system backup and recovery features that set us apart. Storix SBAdmin for Linux is the leader in Adaptable System Recovery (ASR).

This is the process to be able to perform hardware migration of the entire system (operating system and user data) onto different system and disk configurations. SBAdmin understands your Linux system and can individually backup and restore files, directories, filesystems, raw partitions, volume groups, raw logical volumes, software RAID devices or the entire system in case of disaster recovery.


Another versatile advantage is that backups can be archived to local or remote tape or disk. Most bare metal restore products for Linux create disk images that limit your ability to flexibly restore the system.

SBAdmin records your system and storage configuration with each system backup. This information can then be used to rebuild the system from the ground up. Since we are rebuilding the system and not copying the system, within our System Installation Menus, you can easily make changes to that configuration to restore onto completely different hardware.

SBAdmin for Linux can not only restore your user data, but also can easily rebuild and restore your entire system. Every detail, including the disk placement of partitions, logical volumes (LVM1 & LVM2) and RAID devices, file system types and attributes is retained.

You can then change the configuration when reinstalling from a system backup to install onto different hardware or migrate to a different software storage configuration to increase flexibility, performance and availability. When it comes to Linux backup and recovery SBAdmin offers the most flexibility and reliability.

SBAdmin is very versatile and supports virtually any Linux distribution including RedHat (RHEL and Fedora), SuSE (SLES and OpenSuse), Ubuntu, Debian, Mandriva and Slackware, on the following hardware platforms.

Intel 32-bit (x86) systems, AMD64, EM64T, and x86_64 64-bit systems, IBM System p (pSeries/RS6000) and System i (iSeries), IA64 Itanium II (HP Integrity).

For more information about Linux backup and recovery or to learn more about how to  data backup  visit our site.storix_4x4_bigger.png


Controller Card Failure Controller Card Set-up Corruption RAID Container Crash Consecutive hard drive failures in a server supporting RAID Server unable to boot up The server powers up and OS loads, but some important activities refuse to start Grinding and clicking sounds emanating from the server Display screens projecting error messages like Hard drive cannot be detected RAID controller failure Server operating system malfunction RAID Rebuild failure RAID array or volumes that won't mount after a server crash Server configuration corruption or damage Hardware conflicts Viruses or other malicious intent Server won't boot Inaccessible drives and partitions Applications that are unable to run or load data Corrupt files/data Bad sectors Virus attack Hard disk drive component failure Hard drive crashes Fire or water damage Media surface contamination and damage Accidental reformatting of partitions Accidental deletion of data Lost volume Broken arrays Physically or Logically Damaged Drives within the Array Missing Volume Tables Corrupted RAID Configurations Lost container Volume Corruption Multiple Disk Failure Controller Failure Server Configuration Lost Missing Container RAID Container Crash Raid Addition of incompatible drives RAID array or volumes that won't mount after a server crash Multiple drive failure (or multiple drives go offline) Rebuild failure RAID1 RAID0 RAID5 Exchange Program Failure Exchange Boot Problems Information stores are above 16Gb Limit Running Out of Disk Space Hard Drive Corruptions Within The Main Exchange Files Partition Table Errors Transaction Logs Filling Up Diskspace Jet Errors File Size Over 16Gb Limit ESE97 Error Codes Remote Access Service (RAS) Errors Malicious Deletion of Data CRC error Hard drive is clicking or ticking Hard drive beeps Primary Hard Disk not found. Press F1 to Continue Master Boot Record Not Found JET_errRecordNotFound JET_errKeyDuplicate Illegal duplicate key JET_errReadVerifyFailure Read verification error 4294966278 Unable to mount database Corruption in Database Corrupt or improper database backups