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)
