Topic: Different ways to clone your server with LONE-TAR Article Bookmarks
Keywords: clone, sync, recovery None at the moment
Operating Systems: All
YouTube Video none

There are several ways to clone a Linux/UNIX Production Server.

Option 1 - Automated Restore with AIR-BAG
Option 2 - Guided Step-by-Step Restore with AIR-BAG
Option 3 - Sync your data with LONE-TAR
Option 4 - Non-Destructive Restore with LONE-TAR

 

Option 1: Automated Restore with AIR-BAG

1. 	Boot off AIR-BAG CD 
2. 	Make sure Backup Device where Master backups are located is accessible
3. 	Select option # 7 (Test Backup and Hard Drive Accessibility)

		If step #3 fails for whatever reason, please do NOT proceed to step #4.

4. 	Select option # 1 (Automated Restore)

 

Option 2: Guided-Step-by-Step Restore with AIR-BAG

For partition based systems only. LVM support coming soon.

1. Boot off AIR-BAG CD.
2.	Make sure Backup Device where Master backups are located is accessible
3. 	Select option # 7 (Test Backup and Hard Drive Accessibility)

		If step #3 fails for whatever reason, please do NOT proceed to step #4.

4.	Select Option # 2 (Guided Step-by-Step Restore)
	Select the number that corresponds to the hard drive to prepare.

	You will now manually be running the utility 'fdisk'
	At anytime during this process you can hit [Ctrl-Alt-F3] to see original partition table when AIR-BAG was created.

	When you get into fdisk you will see something like this:

		Drive: /dev/sda
	   Command (m for help):

	This prompt requires a flag to begin editing the fdisk table.
	

5. 	Once you have finished making changes to the fdisk table, write and exit.

6. 	Next select Option 'A' (Format ALL Partitions)
	AIR-BAG will now go through each partition and format accordingly.

7.	After format is complete, select Option 'C' (Continue to the Restore)

8.	Select Option 'A' (Restore ALL)

	Once restore is complete, remove AIR-BAG boot media and reboot the server.

 

Option 3: Sync your data with LONE-TAR

1. 	After you have successfully completed either Option #1 or Option #2, we are ready to setup a sync.
	The best backup scheme to accomplish this is to setup a Selective Backup of user data.

	We will make an inclusion list of all the filesystems and directories.

	Default Inclusion List for LONE-TAR Selective Backups: /log/backup

		all entries added must begin with a './' {DOT SLASH}

2.	Execute a backup of the Selective Inclusion List from Production Server.

3. 	Restore backup to Cloned Server.

	
	Important Note: The whole process of Option #3 cannot be completed entirely through CRON.
	                In order to complete the Restore portion unattended will require a custom
			script. If you would like us to make a custom script for you, please 
			request a script to be made by Emailing Support. Must have active Subscription.

 

Option 4: Non-Destructive Restore with LONE-TAR

1. 	This option is only useful when a user needs to recovery a server without any AIR-BAG Disaster Recovery boot media.
	The first step in this Option is first loading a fresh operating system on new Production Server.

	Please make sure you use the same OS that was on your Production Server so there will be no issues with your applications
	once restored with LONE-TAR.

	Watch our video on installing Linux for scratch.

2.	Once you are booted onto the new Production Server, we need to install the latest version of LONE-TAR. 
	Download LONE-TAR at

	FTP: ftp.cactus.com
	WEB: www.cactus.com/download.html 

	Click here to view our LONE-TAR Installation Guide

3. 	Setup the backup device to the same exact settings as it was before the Production Server crashed.

4. 	Now lets get ready for the restore.

	Type this command from the shell as user 'root':
	# ltmenu
		Select Option 5 (Restore Menu)
			Select Option 9 (Additional Features Menu)
			Select Option 1 (Non-destructive) - Set to ON
			Type 'q' to quit
				Select Option 1 (Restore entire backup to hard disk.)
				Confirm your device

	Now LONE-TAR will begin restoring only the files that exist on the backup but not the hard drive.

5. 	Once that is done, 95% of your data is back. Now what needs to happen is restoring certain files destructive 
	before you are back to being fully recovered.

	Such files that would need to be restored destructive would be but not limited to:

		/etc/passwd
		/etc/ftpusers
		/etc/profile
		/etc/shadow
		/etc/hosts
		/etc/group