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

We run logging to tape during office hours (when most of the logs are created). The operator cancels the logging to tape at the end of the day and logs out the terminal so it is not left logged in when unsupervised. The regular backups can then be run using the same tape drive. This assumes that the system has sufficient available log space on disk to allow for all overnight processing, but works as a compromise for us. However, we insisted that a second tape drive was essential on the basis that tape drives are not absolutely fault-free, and we cannot afford to be without at least one reliable working tape drive at all times. I would spend the money... -- Agnes Rivers-Moore agnes@croydon.library.gov.uk > 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). >Mike Segel wrote: > The recommended configuration is two tape drives, but hey, > its your call. The cost of a tape drive is relatively cheap > compared to consulting time or other hardware costs. >