Re: Logical Logs - store on tape, disk or to /dev/null?

In article <35CB9067.4CDB7087@segel.NOSPAM-.KING.OF.MYDOMAIN.-NOSPAM.com>, mikey@segel.NOSPAM-.KING.OF.MYDOMAIN.-NOSPAM.com (Mike Segel) wrote: > Stephan Stresing wrote: > > > > Hi, > > recently I posted the onconfig of one of our client sites and one > > comment I got was, if we were really not interested in the logical > > logs because LTAPEDEV is set to /dev/null. This made me post this > > message because I want to know how you handle this: are 2 tape devices > > connected to your servers or are you storing the logs to disk? We have > > set this option to /dev/null because our client only has 1 tape device > > (changer) and usually they need it for the regular backup (filesystem > > as well as database). > > At our site we write the logs to disk and back them up every night, so > > if we need them, we could restore them from our normal filesystem > > back- > > up set. > > Now, it's your turn... :-) How do you handle this kind of "problem"? > > TIA, > > Hmmmmmm. > I don't think it is a problem per se. > Does setting the LTAPEDEV to /dev/null still put the engine into continuous logging on restart? Surely if this is still the case and the log fills then it will be marked as archived to /dev/null. So when you come to a restore the engine will not allow you back out the logs to real tape 'cos it thinks there are already archived somewhere. So aren't we back at a level 0[12] restore with no log roll forward. I'm happy to be flamed over this view as I don't set LTAPEDEV to null Paul Watson # I don't suffer from WF Software Ltd. # stress, I'm just Tel. (+44) 1436 674729 # a carrier Fax. (+44) 1436 678693 #