In that case Brian ... sorry, not going to
be any help. Good luck.
-----Original Message-----
From: Spears, Brian [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 12:05 PM
To: Multiple recipients of list ORACLE-L
Subject: FW: kinda OT: veritas netbackupYes, we have coded it to do this and it worksbut for many reasons.. including simplicity.... we want to avoidthis solution for the entire 12B enterprise solution... when it confusesothers, and is much more vulnerable for screwups with Mount point managementand recovery.Brian Spears-----Original Message-----
From: Kevin Lange [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 11:15 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: kinda OT: veritas netbackupHow about running a script just before the backup that1) Reads the current log number.2) Forces a log switch.3) Copies the logs to a seperate directory.4) Backups up that seperate directoryLeave the archive directory alone. Do not back it up.-----Original Message-----
From: JOE TESTA [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 9:50 AM
To: Multiple recipients of list ORACLE-L
Subject: kinda OT: veritas netbackupRESEND: never saw it get posted:Can we force veritas netbackup (HPUX) to NOT backup open files?Here is the problem: while arch process is writing out archive logs, the netbackup script that backs up the arch directory will write a partially written log to tape, we're trying to avoid that.is our only alternative determine(out of data dictionary) how many log groups we have and assuming 3, that if we take the max log seq# minus the numebr of groups we have, gives us the oldest log that we can be sure is complete?ie: current log is 543, we have 3 log groups, 543-3 = 540, since oracle wouldnt start overwriting # 540 until it was successfully archived, that we can back up, up thru log seq# 540 and can be sure # 540 is complete?thanks, joe