Looking for tape drive backup replacements?

Most people today are getting tired of having to replace tape drives every couple of years. Tape drives are getting more expensive and become less durable over time. Here is what the market has found to be a cheaper more reliable solution. The Tanberg RDX and the Dell RD1000. Both act like tape drives, but use a hard disk drive as its backup media. Lets compare!
Comparisons	Tape Drives	RD1000 & RDX Backup Drives
Average Cost for a unit	$500 - $2000	$100 - $350
Average Cost for media (2)	$100 - $300	$200 - $400
Average Life of unit	2-4 years
Reliable Multiple backups on 1 media	NO	YES

LONE-TAR 4.3.2.2 Update

Just released the latest update to the 4.3.2.x series of LONE-TAR & AIR-BAG.

If you are using encryption please update to 4.3.2.2 ASAP. This is a free update to all 4.3.x LONE-TAR users.

Update includes:

• Added bug fix for SSH backups that spanned multiple days. This update has the fix.
• Changed how logs get loaded to remote SSH server after successful backup/verify. Now only the last catalog gets uploaded rather than the entire '/log' directory.
• Enhanced encryption support for AIR-BAG with LONE-TAR encryption on their backups.

New postNDR program

         DESTRUCTIVE RESTORE after a full NON DESTRUCTIVE RESTORE

           (c)2010 Lone Star Software Corp.  ALL RIGHTS RESERVED

         --------------------------------------------------------

                         postNDR  ${Ver}

  1. NDR stands for Non-Destructive-Restore.

  2. In the event you install a fresh OS on a new hard drive, and want

     to restore the data from a previous systems LONE-TAR Backup,

     a Non-Destructive-Restore will PREVENT any of the files that exist

     on the NEW hard drive from being clobbered by files that exist on

     the LONE-TAR backup media.

  3. However, there are certain files that you DO want to over-write

     from the LONE-TAR backup media to the new hard drive (assuming same OS).

  4. Prior to any crash and while your system is up and running,

     postNDR  will create a tarball with these desired files and directories.

  5. After a Non-Destructive-Restore, simply restore this tarball and all

     printers, startup scripts, and root profiles will be put back in place.

  6. It is recommended that you execute this script from within your roots

     crontab file 20 minutes PRIOR to your LONE-TAR nightly backup. EXAMPLE:

     10   2   *   *   1,2,3,4,5   /usr/lone-tar/postNDR -backup

     30   2   *   *   1,2,3,4,5   exec /usr/lone-tar/ltar.M.cron 1

     " ; rtn2 ; clear ;

  echo "         --------------------------------------------------------

         DESTRUCTIVE RESTORE after a full NON DESTRUCTIVE RESTORE

           (c)2010 Lone Star Software Corp.  ALL RIGHTS RESERVED

         --------------------------------------------------------

                         postNDR  ${Ver}

  7. The file name that contains the inclusion list of files to archive is:

     ${NDR_lst}

  8. The '-create' flag will create a generic inclusion list.  If this

     inclusion file list does not exist, it will be automatically created.

  9. The list of files and directories in this file MUST be viewed and

     and confirmed by your systems administrator.  Add or delete files or

     directories to this list to serve your needs using the '-edit' flag.

     **CAUTION** Symbolic links MUST have the real file in the list as well.

 10. Do NOT use wild-cards in your inclusion list.

 11. If a file name exists in your inclusion list, and does not exist on

     the system, it will simply be ignored.

 12. Please report to  'support@cactus.com'  any files that should be ADDED

     to this generic script that may have been over looked.

LONE-TAR Command-line Syntax v4.3.x

Command Example 1: Backup a single file/directory

Backup Device >>> /dev/st0
Block Factor >>> 20
Directory being backed up >>> /bin

# cd /
# lone-tar Cvfb /dev/st0 20 ./bin

This command-line calls the LONE-TAR program and indicates:

C create an archive using no compression
v display files being backed up on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

As you can see, the C and v has no argument, while the f, b functions do. Notice there is no flag for the directory you want backed up. Just place whatever files or directories you wish to backup after all the proper flags and arguments.

---

Command Example 2: Backup multiple files/directories

Backup Device >>> /dev/rStp0
Block Factor >>> 20
Directories being backed up >>> /bin & /var/spool & /usr2

# cd /
# lone-tar Cvfb /dev/rStp0 20 ./bin ./var/spool ./usr2

C create an archive using no compression
v display files being backed up on the screen but keep NO catalog
f use the device which is named /dev/rStp0
b block size of 20 for the media

The only difference with this example and example 1 is the amount of directories being backed up.

---

Command Example 3: Backup an inclusion list

Backup Device >>> /dev/rcd0
Block Factor >>> 120
Inclusion List >>> /tmp/Backup.list

# cd /
# lone-tar CvfbF /dev/rcd0 120 ./tmp/Backup.list

C create an archive using no compression
v display files being backed up on the screen but keep NO catalog
f use the device which is named /dev/rcd0
b block size of 120 for the media

F backup all files contained in an inclusion list

Example Contents of the inclusion list /tmp/Backup.list

./usr/backups
./u2/database/user/dan
./usr
./tmp/roster.file

Anytime you make an inclusion list, it is great practice to begin every entry with a’./’

---

Command Example 4: Backup a single file/directory with compression

Backup Device >>> /dev/st0
Block Factor >>> 120
Directory being backed up >>> /bin

# cd /
# lone-tar Pvfb /dev/st0 120 ./bin

P create an archive using software compression
v display files being backed up on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

---

Command Example 5: Backup an entire system with exclusions

Backup Device >>> /dev/st0
Block Factor >>> 120
Directory being backed up >>> /

# cd /
# lone-tar MvfbE /dev/st0 120 ./usr2

M create a Master Backup Archive
v display files being backed up on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media
E exclude a file or directory from a backup

So command 5 does a full system backup, but excludes the directory '/usr2'.
You may use as many 'E' flags as much as you want in one command to match the needed exclusions. Or use the 'X' flag to exclude an inclusion list of files and directories.

---

Command Example 6: Listing of files on an archive

# lone-tar tvfb /dev/st0 20

t lists files on a LONE-TAR archive.
v display files being listed on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

Watch and see the tape fly with a list of its contents. The t is mnemonic for table-of-contents.

---

Command Example 7: Level 1 Verification on an archive

# lone-tar Tvfb /dev/st0 20

T verify files on a LONE-TAR archive using a Level 1 Verification Process.
v display files being verified on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

---

Command Example 8: Level 2 Verification (Byte-by-Byte) on an archive

# lone-tar TTvfb /dev/st0 20

TT verify files on a LONE-TAR archive using a Level 2 Verification Process.
v display files being verified on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

This is the verification LONE-TAR uses on EVERY backup from the Menu or from one of our scripts. This is the most recommended way to verify files and is the most used.

---

Command Example 9: Restore a directory to its original place on the hard drive

# cd /
# lone-tar xvfb /dev/st0 20 ./usr/brad/

x restore files from LONE-TAR archive
v display files being restored up on the screen but keep NO catalog
f use the device which is named /dev/st0
b block size of 20 for the media

This command will restore all the contents of '/usr/brad' to its original place on the hard drive.

**NOTE**
Any time you are doing a restore of a directory and all its sub-contents, please use a trailing '/' at the end of the entry. Otherwise you will just restore the directory name and nothing else.

---

Command Example ?: Do not see a command example that you needed?

Request one by emailing support through our Support Email Form

Table 1. Summary of Verification and Listing Functions

Verify or List Function	Option
Catalog file - create carbon copy of screen output	-V
Exclude file or directory from Bit-level-verification	-E xx
Exclude a list of files or directories from Bit-level-verification	-X xx
List files on LONE-TAR backup archive	-t
Verify files on LONE-TAR backup archive (Level 1 Verification)	-T
Verify files on LONE-TAR backup archive (Level 2 Verification) Byte-by-Byte Verification **Recommended**	-TT

Table 2. Summary of Restore Options Available

Restore Capability Desired	Option
Catalog file - create carbon copy of screen output	-V
Exclude file or directory from being restored on the command-line	-E xx
Exclude a list of files or directories from being restored	-X xx
Flat file restore - preserve ONLY the filename part of the full path	-zFLAT
Relative Restore; Places files to a different directory other than their original spot on the hard drive xx = Your Directory Name	-zWHERE=xx
Interactive restore (approve or disapprove each file)	-w
Interactive Non-Destructive restore (same as above but only files that do not exist)	-Nw
Non-Destructive restore (restore only files not already on the system)	-N
Restore files modified after a specified date	-zDATE
Restore files modified on or before a specified date	-zDATEBEFORE
Restore files - needed on any restore	-x
Restore files placed in a list	-F xx
Symbolic link - restore the contents of the symbolic link if it already exists	-h
Strip leading slash from pathname before restoring	-A
Update files on hard disk with newer files on tape	-U

Table 3. Summary of Primary Backup Command-line Options

Backup Functions	Option
Backup with no compression	-C
Backup with compression	-P
Backup with compression on seeking device	-nc
Incremental backup	-I
Master backup	-M

Table 4. Summary of Secondary Backup Command-line Options

Backup Modifiers	Option
Add files to the end of a seeking device	-r
Backup files modified after a given date	-zDATE=xx
Backup a raw device file	-zDEV=xx
Backup virtual files using virtual file processing. Use environment variable	VIRUTAL_LIST
Catalog file creation - create carbon copy of backup screen output	-V
Change group number of files	-g
Compression - compress executable files also	-Z
Compression - minimum size file to compress	-L xx
Device block size	-b xx
Device capacity, accepts MB, GB, TB (with a limit of 2TB)	-k xx
Device name (name of backup device)	-f xx
Device has seeking ability	-n
Exclude a file or directory from the backup	-E xx
Exclude a list of files or directories from the backup	-X xx
File List - backup ALL files contained in this file list	-F xx
Linked files - report any unresolved links encountered during backup	-l
Locking - use Enforced File Locking	-RR
Locking - use Unenforced File Locking	-R
Locking - use No File Locking with Master or Incremental Backups	-RRR
Preserve file access times	-a
Prevent a file from being split across volumes	-e
Restart a backup on a given file	-zRESTART=xx
Speed option using double buffering (up to 100% faster)	-S
Starting directory	-zWHERE=xx
Symbolic link - backup its contents (not the link info)	-h

How to utilize a good backup scheme for Remote or Off-Site Backups

The biggest issue companies face when doing remote or off-site backups, is the amount of time it takes to complete these backups. Normally companies would do Master backups (Complete System Backups) every day to a tape drive or something local. What if you want to backup to a Remote Site using only a standard cable connection?


The best way around this dilemma is to switch up how you run backups. For example, we at Lone Star ALWAYS recommend this backup scheme when doing it Off-Site:

- Do 2 Master Backups a week (Preferably at the beginning and at the end of the week).
- Do the rest of the days using an Incremental Backup which backs up ONLY the files that have changed since your last successful Master backup.

So if you ever had to deal with a Disaster Recovery Restore using our product, all you would have to do to be back up and running would be to restore your latest LONE-TAR Master backup first, then restore your latest LONE-TAR Incremental backup next. It is that easy.

This method says you time and money! Especially if you are paying an off-site data center money for each GB used.