Re: backup Oracle DB at AMANDA server
Paul Bijnens wrote: Mike Delaney wrote: On Fri, Mar 04, 2005 at 06:07:19PM +0100, Paul Bijnens wrote: Last time I looked at doing backups of Oracle (Ora 6-7-8), I approached it as follows: first set each tablespace in hot backup mode (alter tablespace TS begin backup) then doing a filesystem backup of all the directories with datafiles, using plain amanda DLE's, then setting each tablespace out of hot backup mode, (alter tablespace TS end backup); then force a redo log switch (alter system switch logfile) and then doing a backup of the archived redologs. Ouch. If that database is seeing any signifigant activity during the backup, you're going to be generating *alot* of redo with that approach. Putting the whole database in backup mode at once is typically frowned upon unless you're using something like mirror splitting or snapshots so you can turn backup mode off after a few seconds. That's why you do it during the night... And on Solaris I do use snapshots, which takes indeed a few seconds only, for all the DLE's, not only the oracle datafiles. Never "File changed while reading" messages anymore. A pitty snapshots on Linux LVM2 does not work (yet). On some older systems still running a 2.4.18 kernel and LVM1, I use snapshots too (and MySQL instead of Oracle: a magnitude or two less in footprint, and still suitable for the tasks I need.) It has been working for me for atleast 3 months now.. I had a couple of oopses at first but they were apparantly fixed in later kernels. /Andreas
Re: amstatus does not understand "estimate server"
Hi, on Freitag, 04. März 2005 at 22:52 I wrote to amanda-users: SGW> There have been lines added, but AFAI can see now they grep the wrong SGW> infos: SGW> But amstatus only gets the line starting with setup_estimate: SGW> # amstatus, line 158 SGW> elsif(/setup_estimate: (\S+):(\S+): command .*, options:[...] SGW> so amstatus doesn't show anything meaningful for those DLEs. SGW> Just a missing paragraph in amstatus.pl.in ... Update on this: planner.c reports the "server estimates" in a different format, maybe this should be the same as the other estimates. Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amstatus does not understand "estimate server"
Hi, Kevin, on Freitag, 04. März 2005 at 20:36 you wrote to amanda-users: KD> None of the "estimate server" DLEs are listed as "wait for dumping". KD> The DLEs aren't listed at all until the dump starts. KD> amstatus probably needs a few extra lines for parsing the output for KD> "estimate server". There have been lines added, but AFAI can see now they grep the wrong infos: # /usr/adm/amanda/daily/amdump setup_estimate: oops1:/: command 0, options: none[...] and later: planner time 0.483:server estimate for host oops1 disk /: 0 -> 3131170K, 1 -> 23150K, -1 -> -2K which contains the needed informations. But amstatus only gets the line starting with setup_estimate: # amstatus, line 158 elsif(/setup_estimate: (\S+):(\S+): command .*, options: [...] so amstatus doesn't show anything meaningful for those DLEs. Just a missing paragraph in amstatus.pl.in ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: backup Oracle DB at AMANDA server
Mike Delaney wrote: On Fri, Mar 04, 2005 at 06:07:19PM +0100, Paul Bijnens wrote: Last time I looked at doing backups of Oracle (Ora 6-7-8), I approached it as follows: first set each tablespace in hot backup mode (alter tablespace TS begin backup) then doing a filesystem backup of all the directories with datafiles, using plain amanda DLE's, then setting each tablespace out of hot backup mode, (alter tablespace TS end backup); then force a redo log switch (alter system switch logfile) and then doing a backup of the archived redologs. Ouch. If that database is seeing any signifigant activity during the backup, you're going to be generating *alot* of redo with that approach. Putting the whole database in backup mode at once is typically frowned upon unless you're using something like mirror splitting or snapshots so you can turn backup mode off after a few seconds. That's why you do it during the night... And on Solaris I do use snapshots, which takes indeed a few seconds only, for all the DLE's, not only the oracle datafiles. Never "File changed while reading" messages anymore. A pitty snapshots on Linux LVM2 does not work (yet). On some older systems still running a 2.4.18 kernel and LVM1, I use snapshots too (and MySQL instead of Oracle: a magnitude or two less in footprint, and still suitable for the tasks I need.) Is Oracle 9-10 any different for "hot backup mode" (i.e. more complicated than it need to be?). Not that I'm aware of. alter tablespace begin backup is still there, and reportedly they've added an alter database begin backup to put all tablespaces in backup mode at once for the snapshot crowd. RMAN is, however, the preferred backup method these days - it's typically much faster than copying the datafile, either cold or in backup mode, and doesn't cause the database to generate additional redo the way backup mode does. Need to study again, I see... Currently, I run RMAN backups of our databases to disk, and let Amanda pick up both the RMAN output and the archive logs. I keep the last three RMAN runs around, plus all archive logs that RMAN hasn't backed up at least 3 times. That way, even if the Amanda run overlaps the RMAN run and a disaster occurs before the next time Amanda runs, I can still restore from the previous RMAN run + archive logs. Unfortunately, this doesn't scale too well, since you need anywhere from 2-3 times as much space for the RMAN output as your database + archive logs require (and I've got nearly as much space taken by archive logs as I have datafiles). For larger databases, I be inclined to go the alter database begin backup + snapshot route. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: backup Oracle DB at AMANDA server
Hi, Paul, on Freitag, 04. März 2005 at 18:07 you wrote to amanda-users: PB> Last time I looked at doing backups of Oracle (Ora 6-7-8), I PB> approached it as follows: first set each tablespace in hot backup mode PB> (alter tablespace TS begin backup) then doing a filesystem backup PB> of all the directories with datafiles, using plain amanda DLE's, PB> then setting each tablespace out of hot backup mode, (alter PB> tablespace TS end backup); then force a redo log switch (alter PB> system switch logfile) and then doing a backup of the archived redologs. PB> No need to stop the database at all. PB> The dirty trick with amanda here is getting the archived redo logs done PB> after the rest. That is difficult, because the datafiles PB> are spread over different DLE's, and, as another thread this week PB> already explained, you can't very well specify an order for the DLE's PB> in amanda. My solution was to mirror the archived redologs to a PB> different machine. Having a tapebackup of datafiles + archived redologs PB> on two different machines was enough to restore the database. That PB> mirror was kept up to date during daytime too. PB> To be really sure, I did a full export too (also nice to restore a PB> single table if needed). PB> Is Oracle 9-10 any different for "hot backup mode" (i.e. more PB> complicated than it need to be?). Paul, Bert, and anyone else: Could anyone of you imagine writing a small "Howto back up Oracle dbs" for the docs? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: backup Oracle DB at AMANDA server
On Fri, Mar 04, 2005 at 06:07:19PM +0100, Paul Bijnens wrote: > Last time I looked at doing backups of Oracle (Ora 6-7-8), I > approached it as follows: first set each tablespace in hot backup mode > (alter tablespace TS begin backup) then doing a filesystem backup > of all the directories with datafiles, using plain amanda DLE's, > then setting each tablespace out of hot backup mode, (alter > tablespace TS end backup); then force a redo log switch (alter > system switch logfile) and then doing a backup of the archived redologs. > Ouch. If that database is seeing any signifigant activity during the backup, you're going to be generating *alot* of redo with that approach. Putting the whole database in backup mode at once is typically frowned upon unless you're using something like mirror splitting or snapshots so you can turn backup mode off after a few seconds. > Is Oracle 9-10 any different for "hot backup mode" (i.e. more > complicated than it need to be?). Not that I'm aware of. alter tablespace begin backup is still there, and reportedly they've added an alter database begin backup to put all tablespaces in backup mode at once for the snapshot crowd. RMAN is, however, the preferred backup method these days - it's typically much faster than copying the datafile, either cold or in backup mode, and doesn't cause the database to generate additional redo the way backup mode does. Currently, I run RMAN backups of our databases to disk, and let Amanda pick up both the RMAN output and the archive logs. I keep the last three RMAN runs around, plus all archive logs that RMAN hasn't backed up at least 3 times. That way, even if the Amanda run overlaps the RMAN run and a disaster occurs before the next time Amanda runs, I can still restore from the previous RMAN run + archive logs. Unfortunately, this doesn't scale too well, since you need anywhere from 2-3 times as much space for the RMAN output as your database + archive logs require (and I've got nearly as much space taken by archive logs as I have datafiles). For larger databases, I be inclined to go the alter database begin backup + snapshot route.
amstatus does not understand "estimate server"
I'm finally completing a backup run using "estimate server" for my samba backups. It's mostly working correctly, but there are some minor problems. The dumping finished already, I'm just waiting for the tape. amstatus does not understand the output from the "estimate server" option. amstatus tells me: estimated : 37 8374354k which I believe is only the Linux backups, which use the default "estimate client". I also get: wait for dumping: 00k ( 0.00%) even when there are "estimate server" DLEs left to dump. These DLEs eventually get dumped, but amstatus suggests that the amdump is further along than it is. None of the "estimate server" DLEs are listed as "wait for dumping". The DLEs aren't listed at all until the dump starts. amstatus probably needs a few extra lines for parsing the output for "estimate server". -- Kevin Dalley [EMAIL PROTECTED]
Re: Sockets?
Paul Bijnens <[EMAIL PROTECTED]> writes: > Erik P. Olsen wrote: >> I receive from the amdump processes a lot of "socket ignored" >> messages. >> I assume this means that there is no indication on the dump media (in >> casu tapes) of the ignored sockets. Then, what's the proceedure if one >> has to recover a filesystem with sockets? Should I keep the messages so >> that I could create the sockets manually? > > > You may ignore the messages. I added them to the RE_NORMAL list > in client-src/sendbackup-gnutar.c . Actually, AM_NORMAL_RE, for those trying to search for the right macro. Should something like this be added to the configuration file? I prefer not changing the source code in order to ignore more output. -- Kevin Dalley [EMAIL PROTECTED]
Re: backup Oracle DB at AMANDA server
Jon LaBadie wrote: Sorry to ride on Bert's posting, but I don't have a copy of the original. I didn't see the original either, so I jump on too. my Oracle developers & users don't allow me stop Oracle DB :(. now, I make hot backup of Oracle DataBase, then backup files write to the local tape. It seems, thet i can't stop DB, & use your nicely solution :(. Last time I looked at doing backups of Oracle (Ora 6-7-8), I approached it as follows: first set each tablespace in hot backup mode (alter tablespace TS begin backup) then doing a filesystem backup of all the directories with datafiles, using plain amanda DLE's, then setting each tablespace out of hot backup mode, (alter tablespace TS end backup); then force a redo log switch (alter system switch logfile) and then doing a backup of the archived redologs. No need to stop the database at all. The dirty trick with amanda here is getting the archived redo logs done after the rest. That is difficult, because the datafiles are spread over different DLE's, and, as another thread this week already explained, you can't very well specify an order for the DLE's in amanda. My solution was to mirror the archived redologs to a different machine. Having a tapebackup of datafiles + archived redologs on two different machines was enough to restore the database. That mirror was kept up to date during daytime too. To be really sure, I did a full export too (also nice to restore a single table if needed). Is Oracle 9-10 any different for "hot backup mode" (i.e. more complicated than it need to be?). Another bad news -- this hot backup finished very closed to start of work day -- i can't run amdump at estimated time, because i have at I think I don't understand this sentence "i can't run amdump at estimated time". Can you elaborate on this? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Re[6]: backup Oracle DB at AMANDA server
On Fri, Mar 04, 2005 at 04:17:18PM +0100, [EMAIL PROTECTED] wrote: > That's too bad; Sorry to ride on Bert's posting, but I don't have a copy of the original. > bad news :(( > > my Oracle developers & users don't allow me stop Oracle DB :(. > > now, I make hot backup of Oracle DataBase, then backup files write to > the local tape. > It seems, thet i can't stop DB, & use your nicely solution :(. > > Another bad news -- this hot backup finished very closed to start of > work day -- i can't run amdump at estimated time, because i have at > least 3 servers, with big size data for backup... I think that i'm > don't have time to finish backup, before our workers start the job... > > Finally, new question: > can I create different amanda configuration (example -- daily & > dailyora). At first I backup all my servers, exclude Oracle DB, fn > second -- only Oracle DB. > > admump daily -- I'm run at the night, > amdump dailyora -- at the morning, with rsh from Oracle DB server, > after hot backup finished... > > > and the major -- both backups must white to the same tape. > (I have tape changer HP 1/8 autoloader, Ultrium LTO2 Tape). > > If I descibe same amanda.conf, with same labelstr, same tapelist and > different disklist, does the amanda white data from both amdump to the > same tape at one day? > > I hope, that I can explain enough my problem... Maybe this is where the amanda parameter "starttime", discussed recently on this list, can be used. Perhaps you could start your amdump as you do now, but for the oracle DLE set the starttime to a time the hot backup is sure to be done. If I understand starttime properly (I'm not sure I do) if amdump has nothing else to do except for delayed DLEs, it will sleep around with an alarm clock set, rather than finishing. At the appointed time it will awaken and do the delayed DLEs I can see synchronization problems, amdump will not know if the hot backup is really done yet or not. That will be the SA's task and you will have to start the ora hot backup early enough to ensure it is. I presume that backing up a partially completed ora dump is highly undesireable. If that is so, perhaps an all or none arrangement would be better. Your ora DLE could backup a specific directory. Your ora backup script could create the dump in a parallel directory (same file system) and when the dump was completed it could mv or ln the dump file(s) to the directory amanda backs up. That way amanda backs up either an empty directory or the completed dump. Perhaps you could also arrange that if it was missed today it could be left there and taped with tomorrows ora dump. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Sockets?
Erik P. Olsen wrote: I receive from the amdump processes a lot of "socket ignored" messages. I assume this means that there is no indication on the dump media (in casu tapes) of the ignored sockets. Then, what's the proceedure if one has to recover a filesystem with sockets? Should I keep the messages so that I could create the sockets manually? You may ignore the messages. I added them to the RE_NORMAL list in client-src/sendbackup-gnutar.c . It is the responsability of the program that want to listen to such a socket to create it (using the socket(2) call). (And how would you create those sockets manually, apart from running the necessary program?) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Re[6]: backup Oracle DB at AMANDA server
That's too bad; But, you can indeed have multiple configurations; these will be in seperate directories However they can NOT be on the same tape, for some reason, Amanda is very picky about that kind of things. You should have 2 sets of tapes, one set for the nightly and one set for the daytime backups. In your case your directory structure will be something like this : /etc/amanda/daily/ containing the disklist and amanda.conf and /etc/amanda/dailyora also containing the disklist and amanda.conf but with (of course other content) Or, if all machines have access to the tape device, you could have the amanda configuration on all machines, but then you must be careful that you know what job is doing exactly what. Ideally, there should be only one 'master' server (the indexserver) that controls the other server's backups. Kind regards, Bert De Ridder PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be http://www.mobileware.be Jack$on <[EMAIL PROTECTED]> 04/03/2005 15:59 Please respond to Jack$on <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re[6]: backup Oracle DB at AMANDA server Hello Bert, Friday, March 4, 2005, 4:13:13 PM, you wrote: Bpb> Of course I'm interested in your results; Bpb> if I have the time, I will help you with problems that might arise. Bpb> Good luck, Jack$on. bad news :(( my Oracle developers & users don't allow me stop Oracle DB :(. now, I make hot backup of Oracle DataBase, then backup files write to the local tape. It seems, thet i can't stop DB, & use your nicely solution :(. Another bad news -- this hot backup finished very closed to start of work day -- i can't run amdump at estimated time, because i have at least 3 servers, with big size data for backup... I think that i'm don't have time to finish backup, before our workers start the job... Finally, new question: can I create different amanda configuration (example -- daily & dailyora). At first I backup all my servers, exclude Oracle DB, fn second -- only Oracle DB. admump daily -- I'm run at the night, amdump dailyora -- at the morning, with rsh from Oracle DB server, after hot backup finished... and the major -- both backups must white to the same tape. (I have tape changer HP 1/8 autoloader, Ultrium LTO2 Tape). If I descibe same amanda.conf, with same labelstr, same tapelist and different disklist, does the amanda white data from both amdump to the same tape at one day? I hope, that I can explain enough my problem... -- Best regards, Jack$on mailto:[EMAIL PROTECTED]
Re[6]: backup Oracle DB at AMANDA server
Hello Bert,
Friday, March 4, 2005, 4:13:13 PM, you wrote:
Bpb> Of course I'm interested in your results;
Bpb> if I have the time, I will help you with problems that might arise.
Bpb> Good luck, Jack$on.
Bpb> Kind regards,
Bpb> Bert De Ridder
Bpb> PeopleWare NV - Head Office
Bpb> Cdt.Weynsstraat 85
Bpb> B-2660 Hoboken
Bpb> Tel: +32 3 448.33.38
Bpb> Fax: +32 3 448.32.66
Bpb> PeopleWare NV - Branch Office Geel
Bpb> Kleinhoefstraat 5
Bpb> B-2440 Geel
Bpb> Tel: +32 14 57.00.90
Bpb> Fax: +32 14 58.13.25
Bpb> http://www.peopleware.be
Bpb> http://www.mobileware.be
Bpb> Jack$on <[EMAIL PROTECTED]>04/03/2005 14:58
Bpb> Please respond to
Bpb> Jack$on <[EMAIL PROTECTED]>
Bpb> To
Bpb> [EMAIL PROTECTED]
Bpb> Subject
Bpb> Re[4]: backup Oracle DB at
Bpb> AMANDA server
Bpb> Hello Bert,
Bpb> Friday, March 4, 2005, 3:44:54 PM, you wrote:
Bpb>> You have to configure amanda like this
Bpb>> on the server where the oracle database is located.
Bpb>> I guess you could call it a client,
Bpb>> since the real scheduling is done on the 'index server'
Bpb>> And the indexing server sends the tar
Bpb>> command to the other servers.
Bpb>> Adapt the script to your local needs,
Bpb>> if you need some special processing, that goes in the parts where
Bpb> the if's
Bpb>> are :
Bpb>> if ( $file ne '/dev/null' )
Bpb>> {
Bpb>> if ( $dir eq '/your/oracle/dir'
Bpb>> )
Bpb>> {
Bpb>> system "echo 'Start
backup oracle at ' /var/lib/amanda/runtime" ;
system "date
Bpb>> /var/lib/amanda/runtime";
Bpb>> system ( "command
to stop oracle /var/lib/amanda/runtime" );
Bpb>> }
Bpb>> }
Bpb>> If you want to back up another directory,
Bpb>> just add them to your disklist on the index server, this script
Bpb> will perform
Bpb>> no special operation on the server to be backed up for the other
Bpb> directories.
Bpb>> It will just perform the tar like it is supposed to.
Bpb>> Dumptypes are no compile time options,
Bpb>> that are options that are put in your amanda.conf file.
Bpb>> Something like this :
Bpb>> define dumptype client-compress {
Bpb>> global
Bpb>> program "GNUTAR"
Bpb>> compress client best
Bpb>> priority high
Bpb>> index yes
Bpb>> }
Bpb>> In your disklist there will be an entry
Bpb>> like this :
Bpb>> oracleserver /your/oracle/dir
Bpb>> client-compress
Bpb>> The --with-gnutar=/bin/amandatar is
Bpb>> when you build amanda (which you should do; you cannot use an rpm
Bpb> that
Bpb>> you downloaded somewhere to use this functionalilty).
Bpb>> So : download the sources, untar them
Bpb>> ( tar -xvzf amanda_version.tgz )
Bpb>> cd to the dir where the source is extracted
Bpb>> configure the source tree, use your
Bpb>> own system policy concerning /usr/local etc :
Bpb>> ./configure \
Bpb>> --with-user=amanda \
Bpb>> --prefix=/usr/local \
Bpb>> --exec-prefix=/usr \
Bpb>> --bindir=/usr/bin \
Bpb>> --sbindir=/usr/sbin \
Bpb>> --libexecdir=/usr/lib/amanda
Bpb>> \
Bpb>> --with-configdir=/etc/amanda
Bpb>> \
Bpb>> --with-group=disk \
Bpb>> --with-gnutar=/bin/amandatar
Bpb>> \
Bpb>> --with-gnutar-listdir=/var/lib/amanda/gnutar-lists
Bpb>> \
Bpb>> --with-tmpdir=/tmp/amanda \
Bpb>> --with-smbclient=/usr/bin/smbclient
Bpb>> \
Bpb>> --mandir=/usr/local/man
Bpb>> build the sources :
Bpb>> make
Bpb>> install the resulting binaries :
Bpb>> make install
Bpb>> Now you can use your home-built Amanda
Bpb>> :-)
Bpb> wow...
Bpb> from 2 mail's I known more, then from many MAN's pages, FAQ
Bpb> different articles :).
Bpb> thanx a lot! I'm really miss checking the directory name in your
Bpb> script.
Bpb> thank for the explanation at describing of dumptapes. Now I'm really
Bpb> understand how it work :). I think... :)
Bpb> Now, i try setup, configure test it. Later i'm send my results, if
Bpb> someone interested on it...
bad news :((
my Oracle developers & users don't allow me stop Oracle DB :(.
now, I make hot backup of Oracle DataBase, then backup files write to
the local tape.
It seems, thet i can't stop DB, & use your nicely solution :(.
Another bad news -- this hot backup finished very closed to start of
work day -- i can't run amdump at estimated time, because i have at
least 3 servers, with big size data for backup... I think that i'm
don't have time to finish backup, before our workers start the job...
Finally, new question:
can I create different amanda configuration (example -- daily &
dailyora). At first I backup all my servers, exclude Oracle DB, fn
second -- only Oracle DB.
admump daily -- I'm run at the night,
amdump dailyora -- at the morning, with rsh from Oracle DB server,
after hot backup finished...
and the major -- both backups must white to the same tape.
(I have tape changer HP 1/8 autoloader, Ultrium LTO2 Tape).
If I descibe same amanda.conf, with same labelstr, same tapelist and
different disklist, does the amanda white data from both amdump to the
same tape at one day?
I hope, that I can explain
Re: Re[2]: backup Oracle DB at AMANDA server
You have to configure amanda like this
on the server where the oracle database is located.
I guess you could call it a client,
since the real scheduling is done on the 'index server'
And the indexing server sends the tar
command to the other servers.
Adapt the script to your local needs,
if you need some special processing, that goes in the parts where the if's
are :
if ( $file ne '/dev/null' )
{
if ( $dir eq '/your/oracle/dir'
)
{
system "echo 'Start
backup oracle at ' >> /var/lib/amanda/runtime" ;
system "date >>
/var/lib/amanda/runtime";
system ( "command
to stop oracle >> /var/lib/amanda/runtime" );
}
}
If you want to back up another directory,
just add them to your disklist on the index server, this script will perform
no special operation on the server to be backed up for the other directories.
It will just perform the tar like it is supposed to.
Dumptypes are no compile time options,
that are options that are put in your amanda.conf file.
Something like this :
define dumptype client-compress {
global
program "GNUTAR"
compress client best
priority high
index yes
}
In your disklist there will be an entry
like this :
oracleserver /your/oracle/dir
client-compress
The --with-gnutar=/bin/amandatar is
when you build amanda (which you should do; you cannot use an rpm that
you downloaded somewhere to use this functionalilty).
So : download the sources, untar them
( tar -xvzf amanda_version.tgz )
cd to the dir where the source is extracted
configure the source tree, use your
own system policy concerning /usr/local etc :
./configure \
--with-user=amanda \
--prefix=/usr/local \
--exec-prefix=/usr \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--libexecdir=/usr/lib/amanda
\
--with-configdir=/etc/amanda
\
--with-group=disk \
--with-gnutar=/bin/amandatar
\
--with-gnutar-listdir=/var/lib/amanda/gnutar-lists
\
--with-tmpdir=/tmp/amanda \
--with-smbclient=/usr/bin/smbclient
\
--mandir=/usr/local/man
build the sources :
make
install the resulting binaries :
make install
Now you can use your home-built Amanda
:-)
Kind regards,
Bert De Ridder
PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66
PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25
http://www.peopleware.be
http://www.mobileware.be
Jack$on <[EMAIL PROTECTED]>
04/03/2005 14:02
Please respond to
Jack$on <[EMAIL PROTECTED]>
To
[EMAIL PROTECTED]
cc
amanda-users@amanda.org
Subject
Re[2]: backup Oracle DB at
AMANDA server
Hello Bert,
Friday, March 4, 2005, 2:39:19 PM, you wrote:
Bpb> I don't even take credit for this solution;
Bpb> all credits should go to Paul Bijnens - also on this list.
Bpb> (alles kits, Paul ? ;-) )
Bingo! :)
beautiful!!! :)
Thanx a lot!
finaly -- some dumes questions.
i build amanda whith my tar scripts at client?
and using at amanda server comp-root-tar...
but if I must backup several directories, but only 1 of them needs
Oracle stop...
May I compile amanda, with any different dumptype?
example -- comp-root-oratar
what about it?
--
Best regards,
Jack$on
mailto:[EMAIL PROTECTED]
Re: backup Oracle DB at AMANDA server
Build amanda with this parameter :
--with-gnutar=/bin/amandatar
In this /bin/amandatar you can do something
like this :
( I know this perl code is probably
awful coding, but it works)
#!/usr/bin/perl
use Getopt::Long qw(:config pass_through);
$result = GetOptions (
'directory=s' => \$dir,
'file=s' => \$file
);
if ( $file ne '/dev/null' )
{
if ( $dir eq '/your/oracle/dir'
)
{
system "echo 'Start
backup oracle at ' >> /var/lib/amanda/runtime" ;
system "date >>
/var/lib/amanda/runtime";
system ( "command
to stop oracle >> /var/lib/amanda/runtime" );
}
}
# reconstruct command line
while ( $ARGV[0] ne '' )
{
$val = $ARGV[0] ;
unshift ( @NEWARGV, $val, ) ;
shift @ARGV;
}
while ( $NEWARGV[0] ne '' )
{
$val = $NEWARGV[0] ;
unshift ( @ARGV, $val ) ;
shift @NEWARGV;
}
if ( $dir ne '' )
{
unshift ( @ARGV, '--directory',
$dir );
}
if ( $file ne '' )
{
unshift ( @ARGV, '--file', $file
);
}
if ( $file ne '/dev/null' )
{
system "echo 'Backing up
directory ' $dir >> /var/lib/amanda/runtime" ;
}
unshift ( @ARGV , "/bin/tar"
) ;
system ( @ARGV ) ;
# postprocessing
#
if ( $file ne '/dev/null' )
{
if ( $dir eq '/your/oracle/dir'
)
{
system ( "command
to start oracle >> /var/lib/amanda/runtime" );
system "echo 'End
backup oracle at ' >> /var/lib/amanda/runtime" ;
system "date >>
/var/lib/amanda/runtime";
}
}
exit 0;
I don't even take credit for this solution;
all credits should go to Paul Bijnens - also on this list.
(alles kits, Paul ? ;-) )
Kind regards,
Bert De Ridder
PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66
PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25
http://www.peopleware.be
http://www.mobileware.be
Jack$on <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/03/2005 13:27
Please respond to
Jack$on <[EMAIL PROTECTED]>
To
amanda-users@amanda.org
cc
Subject
backup Oracle DB at AMANDA
server
Hello amanda-users,
I have configured AMANDA Server, my daily & weekly backups from
my
servers working successful...
but I wonna backup My Oracle Database by The AMANDA.
previously, i must do export of DB, or stop Oracle Database...
only after this i may backup my Database files, or export files...
but how i can synchronize my export procedure & amanda backup?
PS I'm sorry for my bad English...
--
Best regards,
Jack$on
mailto:[EMAIL PROTECTED]
Sockets?
Hi, I receive from the amdump processes a lot of "socket ignored" messages. I assume this means that there is no indication on the dump media (in casu tapes) of the ignored sockets. Then, what's the proceedure if one has to recover a filesystem with sockets? Should I keep the messages so that I could create the sockets manually? -- Regards, Erik P. Olsen
Re: backup Oracle DB at AMANDA server
> Hello amanda-users, > > I have configured AMANDA Server, my daily & weekly backups from my > servers working successful... > but I wonna backup My Oracle Database by The AMANDA. > previously, i must do export of DB, or stop Oracle Database... > only after this i may backup my Database files, or export files... > but how i can synchronize my export procedure & amanda backup? Via crontab. Write a script that stops Oracle, backs up and then run amdump. That's what we do. > > PS I'm sorry for my bad English... > > -- > Best regards, > Jack$on mailto:[EMAIL PROTECTED] > > -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
Re[2]: backup Oracle DB at AMANDA server
Hello Bert, Friday, March 4, 2005, 2:39:19 PM, you wrote: Bpb> I don't even take credit for this solution; Bpb> all credits should go to Paul Bijnens - also on this list. Bpb> (alles kits, Paul ? ;-) ) Bingo! :) beautiful!!! :) Thanx a lot! finaly -- some dumes questions. i build amanda whith my tar scripts at client? and using at amanda server comp-root-tar... but if I must backup several directories, but only 1 of them needs Oracle stop... May I compile amanda, with any different dumptype? example -- comp-root-oratar what about it? -- Best regards, Jack$onmailto:[EMAIL PROTECTED]
backup Oracle DB at AMANDA server
Hello amanda-users, I have configured AMANDA Server, my daily & weekly backups from my servers working successful... but I wonna backup My Oracle Database by The AMANDA. previously, i must do export of DB, or stop Oracle Database... only after this i may backup my Database files, or export files... but how i can synchronize my export procedure & amanda backup? PS I'm sorry for my bad English... -- Best regards, Jack$on mailto:[EMAIL PROTECTED]
