Re: Splitting a big directory (disklist question)
On Thu, 30 Jan 2003, Chris Dahn wrote: > From the man page (of 2.4.2), it doesn't look like you can specify regular > expressions for the diskdevice. Thus, linux, pics and mydocs are okay, but > the others are failing (if I'm mistaken about this for 2.4.3, please correct > me). You are correct, however, in using tar. You should just need to split > those regular expressions into real directories that exist in /data/apps/. I actually just did this a few weeks ago for one of the partitions on our home directory fileserver. Now I have 80 more "diskdevices" than I used to have ;) In my case, it wasn't the size of the whole partition that was prohibitive. Rather, I was getting a timeout error from tar, and couldn't track down what file was causing it. So rather than lose the whole partition each time as the tar failed, I split it into 80 little filesystems, and now each one gets backed up independently, except, of course, for the one which is causing the error. The only drawback I see is that my disklist file and my email reports are longer, but it seems worth it to me. Nick **** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead
[SAGE-AU] Amanda users
Noel, You can break the process into two steps: 1. Run a cron job which will run the pre-script, copy /db1 to a staging location, and then run the post-script. 2. Have amanda backup the staging area, instead of /db1. Amanda likes to come up with it's own schedule for efficiency reasons, so I find it easiest to just decouple the snapshot from the backup on moving filesystems. Nick **** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead On Wed, 4 Sep 2002, Noel Paul wrote: > Hi, > > I am experimenting with Amanda on our database servers and have discovered > that we backing up our databases is proving to be a challenge using Amanda. > Specifically, we need to be able to run some pre/post script before/after > backing up certain filesystems within a backup session e.g. > > if I have the following: > > /db1 > / > /usr > /var > etc > > I want to be able to run a pre script before /db1 and a post script after > /db1, then continue backing up the rest of the filesystems in order. > > Also, Amanda seems to backup the filesystems according to its own order > instead of the order listed in the config file. > > Is there or will there be a feature that will incorporate pre/post scripts > per filesystems and also allow a specific order fo filesystems dump. > > Thank you. > > Noel Paul > Lead Unix Administrator > Mincom > Phone: 61-7-3364 9876 > Fax : 61-7-3364 9777 > Email : [EMAIL PROTECTED] > Http : www.mincom.com > > Mincom. The People. The Experience. The Vision. > > This transmission is for the intended addressee only and is confidential > information. If you have received this transmission in error, please delete > it and notify the sender. The contents of this E-mail are the opinion of the > writer only and are not endorsed by the Mincom Group of companies unless > expressly stated otherwise. > > >
Re: Backing up only certain directories?
Dale, You can specify any directory. Amanda won't cross partition boundries though, so if you specify / you won't get /var if it's on it's own partition. Nick **** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead On 3 Sep 2002, Dale Clapperton (lists) wrote: > Hi all > > Potentially stupid question.. Does AMANDA support backing up only a > certain directory on a host (ie /var/log for example) or only whole > partitions (ie /var) ?? > > Couldnt seem to find an answer to this on the site or in the FAQ, and > all the examples only seem to refer to partitions. > > Thanks > > Dale > > > > > >
Re: Multiple configurations, multiple tape devices?
On Tue, 4 Jun 2002, eggslammich wrote: > I currently have 2 configurations called Full and Incr > - Full > - Points to DLT as tape device > - Does only 0 level backups (using dumpcycle 0 and > always-full) > > - Incr > - points to DDS2 changer as tape device > - does only incremental backups > - mtx already working well Incrementals are relative to a given full dump. Doesn't amanda expect that full dump to be in the same configuration? Nick
Re: Mixed files and sub-dirs in disklist entry
You can have a disklist entry for projXXX which excludes certain directories. Then each of those directories can have its own disklist entry. Nick
Re: Getting My Data Back Off The Tape
On Wed, 29 May 2002, GIC MLs wrote: > I followed your advice and ran the command with the -tvf - flags, which > seemed to only give me a listing of directories.: Tar stores all the directories first, so if you are impatient, you might not wait around until the files start showing up :) Nick
Re: retain dump files on holding disk
On Wed, 29 May 2002, Jon LaBadie wrote:
> Skyblue thinking. Wouldn't this be just the level 0's you'd want retained?
> At least that is my antiquated impression of off-site archiving.
A level 0 from three days ago won't have a file I created two days
ago. A level 1 from one day ago will. So although level 0's are
necessary for restoring an entire directory, without the level n's,
you essentially have infrequent full backups. Therefore, I don't
see any reason to only store or retain level 0's.
By the way, since no one has piped up with an easy solution to
retaining dump images, here's my horrible hack, which has been
working very well for a week now. I call it from cron about an
hour after I start amdump.
#!/bin/sh
# I'd like to hold on to the dumped files, so that restores from the
# last 24 hours become very quick. I'll make hardlinks to the files
# in /packages/amanda/spool/*/*/ and I'll remove them before the next
# dump. (Maybe I can keep two days around, since I've got 80GB now.)
die() {
echo "$1"
exit $2
}
config=$1 # weekly or daily
config_dir=/packages/amanda/spool/$config
current=`ls -t $config_dir|egrep -v recent|head -1`
test -n "$current" || die "no current directory in $config_dir" 5
test -d $config_dir/recent || mkdir $config_dir/recent || die "couldn't
make $config_dir/recent" 6
test -d $config_dir/less_recent || mkdir $config_dir/less_recent || die
"couldn't make $config_dir/less_recent" 6
# poor-mans rotation:
rm -rf $config_dir/less_recent/*
mv $config_dir/recent/* $config_dir/less_recent/
while test -d $config_dir/$current
do
(cd $config_dir/$current && \
find . -type f \! -name '*.tmp' -exec ln {} $config_dir/recent/{} \;
2>/dev/null
)
sleep 1
done
echo "done capturing files from $config_dir/$current"
Re: Getting My Data Back Off The Tape
On Wed, 29 May 2002, GIC MLs wrote: > Now my problem is this... > > # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - usr.dump First make a scratch directory like this: mkdir /var/tmp/testing/ Then, from inside that directory, run the same dd command, but with "gtar -tvf -" so you can see exactly which files got into the archive. This also shows what the file names look like. They won't start with a slash, because tar strips those, but they probably will start with ./ depending on how tar was called. Ultimately, you'll probably need to use "gtar -xf - ./usr.dump" > And if the data transferred, where did it go to? Not to the directory wher I > ran the dd command from... Did it get sent back to the client automagically? I wouldn't take the chance of overwritting something accidentally. That's why I suggest you run the dd and tar commands from within a new, empty directory. ******** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead
retain dump files on holding disk
Couldn't find this anywhere in the FAQ-O-Matic, but I'd welcome a pointer if an answer is already floating around somewhere. I'd like to keep all the dump images on disk even after they get written to tape. My reasoning is that a large percentage of the restore requests I get from my users could be satisfied by files from the last day or two. If those files were still on disk, I could restore them without carrying a tape down to the machine room ;) Of course, I can't keep the files around indefinitely, so I imagine them getting rotated out after one or two days, depending on how much disk space I have to spare on the holding disk. Does amanda have a built-in way to do this, or does anyone have a hack to accomplish something close? Thanks, Nick **** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead
Re: "I know this message..." help restore entire system
On Wed, 3 Apr 2002, Lewis Watson wrote: > The kickstart config file works wonders when rebuilding. That will get the > bare metal install then use Amanda to restore the data. Works for me but I > would like to hear from others on this. Since the question was about a bad drive, I assume there's a new drive somewhere. I would mount it on a working client machine and drop the restored data on it. Am I missing some complexity here? Nick **** Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead
