FW: kinda OT: veritas netbackup

[Spears, Brian]

Hi,      I am the other guy involved in this issue of Not backing up OPEN files on Unix with Netbackup.     We are keeping 2 days of logs on disk  up to 60gig of logs..  The tape backup people are not happy about us   backing this up often to provide extra redundancy especially as we implement this for every oracle system we   have.   Yes, we have considered running other backups but we really wanted to see if Veritas could close this logic hole   for us because we have a directive to keep our solution simple and secure.   I know on windows its no problem and veritas squawks when the files are in use... Anyone know if the "only   BACKUP close files" feature exists in Unix.   Brian Spears Sr. Oracle Database Administrator OCP -----Original Message----- From: Yechiel Adar [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 11:50 AM To: Multiple recipients of list ORACLE-L Subject: Re: kinda OT: veritas netbackup Hello Joe   Just schedule another backup of the archive logs 1 hour (or 5 minutes) after the regular backup. NetBackup will take a second (complete) backup of the archive file and when you want to restore , restore the last copy of the files.   Yechiel Adar Mehish ----- Original Message ----- From: JOE TESTA To: Multiple recipients of list ORACLE-L Sent: Thursday, December 19, 2002 5:50 PM Subject: kinda OT: veritas netbackup RESEND:  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