From: syltremzulu@videotron.ca   
      
   You should keep 2 copies of your archive logs, on separate disks.   
   On separate servers if possible.   
      
   Look at LOG_ARCHIVE_DEST_n syntax   
      
   I keep one copy on a mirrorred disk locally, and one copy on another machine   
   which is in a different city.   
      
   But should your database "crash", as you say, most of the times your archive   
   logs will still be available. You`ll have lost one datafile, or any part of   
   the database but not your archive logs (as long as they are kept on their   
   own disk or storage device), so you can recover.   
   If you loose your archive logs in both locations (if you save them onto 2   
   locations that is) you still have the database. Just hurry to take a good   
   backup of it.   
      
   Loosing everything can only happen if the server bursts into flames (or   
   something of the like), in which case you need more than your archive logs   
   to recover, you need a complete disaster plan.   
      
   Regards,   
      
   Syltrem   
      
      
      
   "Tho Nguyen"  a écrit dans le message de   
   news:d177c6d9.0408130930.65c97d51@posting.google.com...   
   > Hi, folks!   
   >   
   > I am new to RMAN and now trying to configure it. There is one issue   
   > concerning me.   
   > Let's say I backup the target database every 6:PM and the database   
   > generates about 100 archived logs every day.   
   > So what happens if the database crashs at 5PM? I have the backup at   
   > 6PM of the last day only and no backup of archive logs generated   
   > between that time.   
   > Have anynone experienced that any what is your solution?   
   >   
   > Thank a bunch.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)