Misc Links
Forum Archive
News Archive
File DB
 

Ads
 

Advertisement
 

Latest Forum Topics
wow 56 k modems are
Posted by Red Squirrel
on Oct 14 2013, 11:52:23 pm

I Need A Program
Posted by rovingcowboy
on Sep 23 2013, 5:37:59 pm

having trouble witn lan
Posted by rovingcowboy
on Sep 23 2013, 5:40:56 pm

new problem for me
Posted by rovingcowboy
on Sep 23 2013, 5:54:09 pm

RBC Royal Bank
Posted by Red Squirrel
on Aug 13 2013, 6:48:08 pm

 

Setting up a Backup Server
Home or office Backup Server Solution
By Red Squirrel


Scripts
If you have many jobs and many drives you'll probably want to set up some kind of script to easily call with different parameters and such, and this will make setting up scheduled backups much easier.

This is the main script I use, and pass the parameters to. Depending on your needs this script may do, or you may want to write your own. This script is static, meaning it should rarely need to be modified even if you add new jobs or modify some.

This script should be on a partition that is on the main drive (OS drive). This drive is never removed unlike the backup data drive(s). In addition to this main script, you then have separate scripts for different backup jobs which I'll refer to as job scripts. An example of such script would be



The parameters are passed on, and end up in the $1 variables.

This script should also reside in the main drive, and you can even split up the jobs in several scripts if you want. The main thing is, the passwords will all be in the same place, so it's only one area to worry about securing, vs if you put this script on the backup drive itself.

There's one last script to make, this script should exist on each backup drive with the same name. This is the script you call with your cron job. This script would simply call the proper backup script shown above. So if you put in the drive for Server A, then the script should call all the scripts that backup data from server A. So the backup jobs depend on which drive is in. If you simply scheduled each job, then you'd have to worry about inserting the right drive every day. This way, it matters less, you simply need to rotate the drives around in no particular order and it will still backup the right data to the right drives. It's not a bad idea to echo out the job name in this script, as well, so when you check the logs, it's the first thing you'll see and you know which drive was in at that time.

So basically you have
  • 1 main script that takes parameters and performs the backup
  • multiple job scripts with different parameters calling the main script
  • 1 script called the same thing, residing on the backup drive, calling the job scripts






Next Page
spacer
24712 Hits Pages: [1] [2] [3] [4] 1 Comments
spacer


Latest comments (newest first)
Posted by Onykage on February 02rd 2006 (09:55)
I highly recomend gentoo as a flavor a linux to use with a server. Like debian gentoo has a fetch/make-install script in it called emerge. Just goto /etc/portage/ to have a look on the gentoo site. You can find out all you need to know by pulling the -h (help) option on the emerge command.
spacer
View all comments
Post comment


Top Articles Latest Articles
- What are .bin files for? (669062 reads)
- Text searching in linux with grep (161180 reads)
- Big Brother and Ndisuio.sys (150471 reads)
- PSP User's Guide (139547 reads)
- SPFDisk (Special Fdisk) Partition Manager (117240 reads)
- How to Use MDADM Linux Raid (188 reads)
- What is Cloud Computing? (1225 reads)
- Dynamic Forum Signatures (version 2) (8769 reads)
- Successfully Hacking your iPhone or iTouch (18714 reads)
- Ultima Online Newbie Guide (35906 reads)
corner image

This site best viewed in a W3C standard browser at 800*600 or higher
Site design by Red Squirrel | Contact
© Copyright 2019 Ryan Auclair/IceTeks, All rights reserved